"Advice would be really appreciated!
Clarification:
To download the app, do users need to go to the app store/or open a web browser to click download? [Assume the interviewer said it is up to me]
Approach :
summarize the overall process of sharing
listing out how could we optimize every step in the process to make sharing features effective
ranking each feature by their priorities
setting metrics, perform A/B tests and evaluate results.
**Step1: Summarize Shari"
Anonymous Chinchilla - "Advice would be really appreciated!
Clarification:
To download the app, do users need to go to the app store/or open a web browser to click download? [Assume the interviewer said it is up to me]
Approach :
summarize the overall process of sharing
listing out how could we optimize every step in the process to make sharing features effective
ranking each feature by their priorities
setting metrics, perform A/B tests and evaluate results.
**Step1: Summarize Shari"See full answer
"One technique we like to use when explaining technical concepts to non-technical people is to use analogies to help with memory retention.
For this type of question, we'll use the Restaurant example:
> Imagine you're at a restaurant with a variety of waiters - each waiter will only take your order for one specific item (i.e. one waiter for pizza, one waiter for pasta, etc.). An API is like a waiter in this example as it will only perform a specific order. An SDK on the other hand is like having"
Exponent - "One technique we like to use when explaining technical concepts to non-technical people is to use analogies to help with memory retention.
For this type of question, we'll use the Restaurant example:
> Imagine you're at a restaurant with a variety of waiters - each waiter will only take your order for one specific item (i.e. one waiter for pizza, one waiter for pasta, etc.). An API is like a waiter in this example as it will only perform a specific order. An SDK on the other hand is like having"See full answer
"I have this approach of:
30% seniors, to help the semi senior to grow.
30% to 35% semi seniors, to help the jr to grow.
37% to 40% jr or software engineers.
With this approach and can foster a culture of grow but also be prepared to rotation of the team.
And if you have to add more people, the onboarding is more simple."
Cristian A. - "I have this approach of:
30% seniors, to help the semi senior to grow.
30% to 35% semi seniors, to help the jr to grow.
37% to 40% jr or software engineers.
With this approach and can foster a culture of grow but also be prepared to rotation of the team.
And if you have to add more people, the onboarding is more simple."See full answer
"When I was working as a project manager in the QVC, I was working with the marketing and content management team. We had two sets of customers, one was planners (a team that plan the product portfolio and decide which product should go at what time and the other team were called schedulers, this team add the commercial between each product description clip. Our team was responsible to create a UI for them to use the existing product clips from each episode and use them to create new episodes. T"
Kunkun D. - "When I was working as a project manager in the QVC, I was working with the marketing and content management team. We had two sets of customers, one was planners (a team that plan the product portfolio and decide which product should go at what time and the other team were called schedulers, this team add the commercial between each product description clip. Our team was responsible to create a UI for them to use the existing product clips from each episode and use them to create new episodes. T"See full answer