Program manager Interview Questions

How dod you tackle this problem. I would say, you can have a wrapper and try to increase the timeout. Or try to download the data at a specific interval so you don't timeout. What was your approach?

One thing to make sure of is that you ask a lot of clarifying questions to eliminate any variables or unknowns you have. In this case, I had to determine what the network architecture was like - centralized or distributed (is network latency a concern?), what was the process flow? Could I resolve the issue by paginating the data coming back as opposed to displaying it all at once? Use what you know of human beings and their limitations. No one is going to be able to digest 1000s of records in one shot. Perhaps a summary with drill down would work? But you'll need to understand what the data is being used for before suggesting something like this (more clarifying questions) What about caching and reverse proxy? the effectiveness of that will depend on your network architecture, I presented several solutions, ranging from cheap and easy to complex and expensive. I actually gave the correct solution that the interviewer wanted (and the one they actually implemented in real life as this was an actual issue) but the interviewer kept me going to explore more and more ideas Pro Tip: Take notes!! the interviewer will give you a lot of information at once, don't try to memorize it all, write down all the salient points!

Can I know what was the solution the interviewer expected in this case?

Since I did not know the skills of the other candidates, I am not able to tell you how I am different. I am able to tell you about a combination of skills that may allow me to be highly flexible team member.

I was able to describe the vision and mission as well as highlight how some of the programs deliver that mission to young people in communities across BC.

Scalable, bounded and practically measurable

Address the issue with the individual. Map out pros and cons. Move to supervisor if needed.

For the linked list we could use a label as "visited" so if in traversing a linked list we get to the node with visited label, we know that there is circle in the linked list.

How would you know the amount of time you have before shipping a feature to production is enough for you to complete development?