My Technical Account Manager Interview at AWS

Overview

This video is a first-person account of how the creator secured a Technical Account Manager (TAM) role at AWS. It emphasizes that the path to an offer is rarely straightforward and often depends on networking, persistence, and navigating logistical issues.

Main points / narrative of the hiring journey

Backstory + long targeting period

• The creator says they pursued AWS for about two years, applying roughly 25 times before landing this opportunity.
• Their strategy centered on networking with “Amazonians” (people inside AWS) through:
  • conversations
  • coffee chats
  • research on the company and roles
• The goal was to prepare well enough to genuinely answer “why AWS” instead of cramming at the last minute.

Unexpected recruiter connection

• Two years earlier, the creator connected with a woman who was initially linked to an AWS tech program.
• When she posts a TAM role, she resurfaces in the process—apparently requiring bilingual skills (language not confirmed; Spanish/Mandarin mentioned).
• She first checks where the creator is based; the conversation pauses.
• Days later, she follows up with a Dallas-based TAM role.

Applying to “Senior TAM” and role “leveling”

• The creator worried they might not meet the requirements for Senior TAM.
• They were encouraged to apply anyway because AWS can level candidates during the interview process (for example, L4/L5/L6).
• This shifts the mindset from perfect match required to get into the interview pipeline; leveling happens later.

Administrative hurdle: missing the online assessment email

• After completing an intake form for skills, an online assessment is expected.
• The creator never receives the assessment email, and cannot get immediate help from the recruiter on a Friday.
• Through their network, another AWS contact escalates internally.
• The assessment arrives only after that intervention—highlighting the value of having connections inside AWS.

Online assessment preparation

• The creator studies the online guidance and concludes the AWS assessment covers fundamentals across multiple tracks, including:
  • networking
  • security
  • databases
  • devops basics
• They note the questions often require terminology-level understanding, with examples such as:
  • OSI model
  • symmetric vs. asymmetric encryption
  • cluster/container concepts
• They also report the assessment includes:
  • a technical portion
  • a behavioral/leadership principles portion
• They emphasize:
  • it is not proctored
  • it appears to have no strict time pressure
  • they still treated it as straightforward but worth reviewing

Recruiter phone screen and relocation discussion

• After passing the assessment, the recruiter asks whether the creator is willing to relocate to California.
• The creator recently moved to Dallas (about 7 months earlier, with their wife) and is initially reluctant to move again.
• They consult their wife, who encourages proceeding with the process and handling relocation later if needed, framed through faith-driven discernment.
• The creator agrees to move forward while expressing reluctance.

Phone screen + loop interview

• The first “real” interview is a video call with a senior TAM, described as conversational rather than harsh.
• The creator struggles with two questions—specifically missing use-case details after initially giving definitions.
• Later, they find answers on LinkedIn and send them back as follow-up.
• About 3 weeks later, they advance to the loop:
  • a series of multiple back-to-back interviews
  • described as a long day (roughly 5–7 hours, depending on scheduling gaps)

Network support during loop preparation

• In the weeks leading up to the loop, the creator messages many TAMs for help.
• A subset responds, but only a small number (around 4) became highly involved:
  • daily mentorship
  • story feedback
  • preparation guidance

Loop interview experience

• They describe four interviews within the loop:
  • two more technical
  • two leadership-focused (including a bar raiser)
• Scheduling confusion happens at the start:
  • the first interviewer is late due to miscommunication
  • the recruiter resolves it quickly
• The second interview is a tech breadth discussion:
  • it moves rapidly across domains (networking → security → databases → devops)
  • they must answer at the fundamental level without over-explaining
• They say their strongest stories were not purely technical:
  • leadership and problem-solving stories from earlier work as a sports event project manager
  • high stakes, many teams, constant issues

Hiring manager interview uncertainty

• The final hiring manager round feels worse than expected.
• They believe their response didn’t align with the interviewer’s preferred approach after extensive follow-up on one question.

After the loop: “passed” but no immediate offer

• The recruiter tells them:
  • they did not receive an offer for that specific job/team
  • the panel felt they were a strong fit for Amazon/TAM generally, but not a fit for that particular team/job
• The recruiter then works to place them on another team.
• Team placement could take weeks to months.
• During this time, the creator also interviews elsewhere but remains committed to AWS.

Team placement outcome: offer without relocation

• Eventually, the recruiter emails that a team is found and the creator can go straight to offer with no further interview (contrary to the earlier expectation of another hiring manager interview).
• In the final call, the creator learns:
  • the team is in Dallas
  • so they do not have to relocate to California
• They also note:
  • the offer salary is a major increase over their previous job
  • it gives them strong leverage for negotiation

Overarching themes / takeaways

• AWS hiring is not linear: candidates can “pass” stages but still not get an offer for the first team; placement can come later.
• Networking matters: it helps with the assessment and with mentorship during preparation.
• Preparation includes logistics: scheduling issues, assessment timing, and managing long interview loops.
• Story quality matters as much as technical knowledge: leadership and problem-solving stories (not just cloud jargon) helped.
• Trust and persistence: the creator attributes the final Dallas outcome to providence and emphasizes that opportunities can surface through unexpected turns.

Presenters / contributors

• Presenter/creator: Rex Tech (the narrator)