Why I Work at Amazon: Insights from a Principal Engineer

Did you know that imposter syndrome plagues even the most seasoned engineers? In this article, I address pressing interview and career questions from a principal engineer’s perspective.

Am I really a senior engineer if I don't know system design?

Many software engineers wonder: if you’re a Senior Software Engineer but lack hands-on system design experience, does the title still apply? As one viewer asked, “If I don’t know system design, am I really a senior?” The answer is yes—“senior” is simply an adjective in your title that signifies years of experience, not mastery of every domain.

If your target company places heavy emphasis on system design during interviews, it makes sense to brush up on patterns, scalability concepts, and trade-offs beforehand. Otherwise, don’t let one skill gap undermine your confidence. Your title at Amazon or elsewhere reflects overall engineering experience, not every niche topic.

How do I prepare for behavioral interview questions?

Behavioral interviews are a critical part of the interview process at Amazon and many other tech firms. Storytelling can be the key to standing out. One viewer asked if they should script their stories to avoid forgetting details. I recommend preparing six to eight solid anecdotes—successes, challenges, teamwork moments—that demonstrate the level at which you’re interviewing.

You don’t need to memorize a script word for word; instead, structure each tale with a clear beginning, middle, and end. Use the STAR framework (Situation, Task, Action, Result) to ensure you cover critical points. Practice speaking these stories out loud so you can adapt them on the fly during the interview without losing coherence.

Are you really a principal engineer?

Doubts about high-level titles are common in tech. Some assume “Principal Engineer” is more myth than reality. As a Principal Engineer at Amazon, I can confirm that this role exists across tech companies and is verifiable on LinkedIn. Levels do vary by organization, but the title is far from fictitious.

“I’m not trying to pull a fast one—check my LinkedIn to see that I’m really a Principal Engineer at Amazon.”

Trust the ecosystem of public profiles and endorsements that back up senior IC titles.

Why choose the staff+ IC route instead of being a manager?

The choice between a high-level individual contributor (IC) role and a management track is pivotal for many engineers. In tech, you can rise to Staff or Principal Engineer without ever managing direct reports—a privilege that few industries offer. Outside of tech, seniority often requires becoming a manager.

Management involves hiring, firing, performance reviews, and team dynamics—tasks that drift away from hands-on code and architecture. If you pursue an IC path and later decide to manage, the transition is usually smoother than the reverse. Keeping your career options open and choosing the path that aligns with your passion is essential for long-term satisfaction in your engineering career.

How do I sell my ideas to leadership?

Pitching ideas effectively requires understanding your leadership’s priorities. A viewer noted that management cares about different metrics than individual engineers do. To win buy-in, frame your proposal around a problem your leaders face—whether it’s reducing attrition, improving product velocity, or cutting operational costs.

For example, if employee turnover is high, demonstrate how your plan could boost retention through mentorship programs or streamlined onboarding. By aligning your suggestions with business objectives, you speak the language of decision-makers and significantly increase the chances of approval.

If you know so much why do you use a teleprompter?

Using a teleprompter isn’t about lacking expertise; it’s about delivering a clear, well-structured message. Early in my YouTube career, I relied on prompts to ensure I hit all my talking points efficiently. It’s a tool to help convey complex engineering concepts in a concise way.

Now, I’m gradually moving toward more spontaneous delivery. But even seasoned speakers use notes or slides to stay organized—especially when explaining intricate architectural patterns or career advice.

What's your advice on getting to the next level? FAANG engineers intimidate me.

It’s natural to feel intimidated when comparing yourself to engineers at top tech companies. Social media often highlights only polished successes, creating a skewed benchmark. Rather than measuring yourself against curated profiles, focus on your own growth areas.

Imposter syndrome is nearly universal among high-performing engineers; it doesn’t indicate a lack of ability. Embrace continuous learning—take on challenging projects, seek feedback, and build your network. Over time, you’ll carve out a career path that reflects your unique strengths, not someone else’s highlight reel.

If you're so smart why do you work for Amazon?

A viewer provocatively asked why, with my background, I choose Amazon. This question hinges on a synecdoche fallacy—equating one part (me) with the whole (Amazon). My day-to-day experience is just mine and may differ greatly from broader narratives about the company.

I enjoy the role, the scale of problems, and the growth opportunities here. If my priorities change, I’m free to explore another team at Amazon or move to a different company altogether. In software engineering, you have the flexibility to find what best aligns with your career aspirations.

Takeaway:
• Regularly assess your career alignment and lean into your unique engineering strengths to advance confidently and overcome imposter syndrome.

What experiences have you had with navigating career dilemmas or handling imposter syndrome in tech? Share your thoughts below, and let’s discuss!