A few pointers for technical interviews (thread):
- After the prompt, ask for a minute to gather your thoughts. those 30 seconds feel longer to you than they actually are. (use this time to plot out what you know, + structure including how you& #39;ll know or metric your success)
1/
- After the prompt, ask for a minute to gather your thoughts. those 30 seconds feel longer to you than they actually are. (use this time to plot out what you know, + structure including how you& #39;ll know or metric your success)
1/
- Ask clarifying questions. "It sounds like the kind of service I& #39;d access through a mobile app, does that seem accurate?" or "Are there budget considerations for this customer I should be aware of?" types of questions will get you to have more specific architectural ideas.
2/
2/
- Identify assumptions you& #39;ve made. If 2 possible routes, identify those--& pick 1 or ask interviewer to pick 1. "Based on what you told me about customer, it sounds like they don& #39;t have time to do x & so will do x minus y" is helpful for interviewer to understand your logic.
3/
3/
- Research interviewer ahead of time. Keep in mind what their frame of reference is. Use lexicon that fits them.
- Have a checklist to go through when solving situational problems. (Budget, timeframe, security considerations, interoperability, dependencies, etc.)
4/
- Have a checklist to go through when solving situational problems. (Budget, timeframe, security considerations, interoperability, dependencies, etc.)
4/