Turn interviews into job offers at top tech companies

My primary focus is Product Managers, both technical and non-technical, and Technical Program Managers, especially at senior and principal levels. I also work with candidates in adjacent roles when their interviews assess transferable skills such as product judgment, technical depth, execution, or behavioral storytelling.

My coaching is direct, tailored, and focused on helping you improve quickly. I identify the gaps most likely to affect your interview, explain what an interviewer may be hearing, and give you concrete ways to improve. I use frameworks when they help, but generally favor focused deep dives over scripted answers or high-fidelity mocks.

Yes. Amazon is an area of deep expertise because I spent nine years there as a Principal PMT and interviewer, but most of my clients interview elsewhere. For other companies, I tailor preparation using the role context, recruiter guidance, current interview information, patterns from previous clients, and my perspective as an experienced interviewer. I will be transparent about what is known rather than presenting assumptions as insider knowledge.

It depends on your goals, your current level, and how much preparation you actually need. I do not sell packages upfront because I do not think I can responsibly tell you how many sessions you need before I understand those things. I also believe I should earn your trust one session at a time. Some clients get what they need from a single focused session. Others choose to continue across several interview areas or work with me over multiple sessions. After working together, I can give you a more informed view of where additional coaching would be useful. There is never an expectation that you commit to a package.

Yes. If your interview is close, we can focus on the highest leverage areas and make the most of the time you have. That said, I typically recommend starting at least a week before your interview when possible. Clients who give themselves more time generally have better outcomes because they have time to absorb feedback, practice, and come back with stronger answers.

Bring whatever context will help us make the session useful. That might include the role or job description, interview format, recruiter guidance, or specific stories and questions you want to work on. You do not need to arrive with polished answers or fully prepared material. We can work from wherever you are in your preparation.

Yes. Part of my job is to give you an honest assessment of where you are, not just make you feel more confident going into an interview. If I see gaps that materially increase your risk, I will tell you. In some cases, I advise clients to consider postponing an interview rather than going ahead before they are ready. That is not always the right decision. Delaying can have costs too, so I will help you think through the tradeoffs based on your readiness, the opportunity, your timeline, and how much more preparation is likely to help. The decision is yours. My role is to help you make it with a realistic view of where you stand.

I am not a general purpose career coach. I think of career conversations with me more as mentorship, informed by my own experience as a product and technology leader and by years mentoring others at Amazon. That can be useful if you are thinking through a career transition, evaluating opportunities, navigating your path as a PM or TPM, preparing for a promotion, or working through a situation where my experience is relevant. If there is a good match between what you are trying to figure out and what I can credibly help with, I am happy to work through it with you. If the topic falls outside my experience, I will tell you.

For Technical Product Managers, I coach candidates on demonstrating technical depth. That includes explaining how systems work, reasoning through technical constraints and tradeoffs, and clearly communicating your role in technical decisions. I do not coach traditional software engineering system design interviews. For example, I would not be the right coach for a prompt like “Design a globally scalable chat service” where the candidate is expected to drive the architecture from an engineer’s perspective.