My interview loop for a Technical Account Manager role was confirmed for later this week, with five interviews scheduled, but I still haven't been told which two technical domains will be covered in the technical-depth portion.
During the phone interview, I was told I would be assessed on two domains and that the interview details would identify them. However, the recruiting coordinator's emails didn't include that information. They directed me to my recruiter, whom I've contacted several times since before the phone interview without receiving a response. A colleague also tried reaching out and was only told that I would receive instructions soon.
The phone interviewer suggested that I focus on networking, compute, and architecture, so I've been preparing those areas. I also never received the form where candidates supposedly identify their strongest domains. Based on what I understand, the loop may include two technical interviews covering depth and breadth, along with three behavioral interviews focused heavily on leadership principles.
Should I simply prepare the areas suggested by my phone interviewer and attend the loop, or is there another way to confirm the domains? I've also prepared 16 STAR stories from my consulting experience. Is that enough for five interviews, and is it okay that the stories aren't specifically technical?
3 Answers
I’d follow the guidance from the phone interviewer and prioritize networking, compute, and architecture. Interviewers generally assess depth based on the strengths you discussed during the phone screen and what your background supports, rather than expecting you to suddenly demonstrate expertise in an unrelated specialty.
Also review the fundamentals of adjacent areas such as databases, serverless services, API gateways, and newer platform services. The technical interviews usually test whether you can reason through systems and explain tradeoffs, not just recite memorized product details. For behavioral rounds, prepare three or four especially strong stories and practice emphasizing your individual contribution instead of repeatedly saying “we.” Include the outcome, numbers where possible, what went wrong, and what you learned.
Your STAR stories don’t need to be technical. They need to demonstrate the relevant leadership principles, clearly explain what you personally did, and include measurable results. Sixteen is probably plenty if the stories are flexible enough to cover different themes. Focus on your strongest examples rather than trying to prepare a separate story for every possible principle.
Technical expectations can vary by location and interview format, so there may not be a universal answer. In many cases, the recruiter only has the information recorded during the phone screen, while the interview panel follows the competencies you identified or demonstrated there. Since the interviewer specifically recommended networking and compute, preparing those areas is the most practical choice.
You probably can’t meaningfully build deep expertise in an entirely new domain in a week or two. Make sure your basics are solid, understand how the major services fit together, and be ready to explain your reasoning when designing or troubleshooting an architecture.
That matches my understanding too. The exact process can differ by region, but the phone-screen discussion and the candidate’s stated strengths are usually more useful than waiting for a generic prep document.