Career Changer Engineering Manager First 90 Days at Amazon AWS: A Beginner's Roadmap
What should I prioritize in the first two weeks as a new AWS Engineering Manager?
Focus on team health, delivery signals, and Amazon’s bar within the first 14 days.
Day 1, you receive a 1‑page AWS S3 onboarding doc dated June 12 2023 stamped by the HRBP John Miller.
Day 2, you join a 30‑minute stand‑up with the S3 lifecycle team of 12 engineers led by senior manager Mira Patel.
Day 3, you read the Working Backwards narrative for the upcoming S3 Glacier Deep Archive feature, a 6‑page Amazon bar‑raiser document.
Day 5, a Slack message from the S3 Ops lead reads: “We need a health check by day 5, please schedule.”
Day 6, you schedule a 30‑minute health‑check call with the S3 data‑movement pod, noting the $210,000 base, 0.05 % equity, and $30,000 sign‑on of your own offer.
Day 7, you present a 1‑page health‑check summary to the S3 senior director, quoting the candidate’s line from the March 2023 Lambda hiring loop: “I would ship a feature in two weeks.”
Day 8, the senior director asks you to align on the Amazon Customer Obsession principle before the next sprint.
Day 9, you update the S3 14‑day plan doc with a concrete metric: reduce read‑latency variance by 12 % on the next release.
Day 10, the Bar Raiser on the loop, senior engineer Raj Singh, votes 4‑1 in favor of your early‑signal plan, citing the Working Backwards framework.
Day 12, you deliver the 14‑day health‑check deck to the S3 leadership council, noting the team‑size 12 and the immediate risk of a 3‑day delivery slip.
Day 14, the senior director approves your plan, stating the problem isn’t the lack of a roadmap — it’s the missing ownership signal.
How do I assess my team’s technical debt without stalling delivery at Amazon EC2?
Measure debt impact against Q2 2024 delivery targets, then prioritize fixes that preserve the 30‑day sprint cadence.
Day 14, you open the EC2 technical‑debt backlog, a JIRA board with 84 tickets dated March 2023.
Day 15, you meet senior engineer Lena Gao, who quotes the interview question: “Tell me about a time you reduced latency for a distributed system.”
Day 16, you ask Lena to surface the top three debt items that affect the EC2 Nitro hypervisor latency, receiving a list of 3 tickets with IDs EC2‑D‑101, ‑102, ‑103.
Day 17, you run a 30‑minute “Debt Impact” workshop, noting the Bar Raiser’s rubric score of 7 out of 10 for each ticket.
Day 18, you draft a 2‑page “Debt‑Aware Delivery” narrative, citing the AWS Well‑Architected Framework’s Performance Efficiency pillar.
Day 19, you present the narrative to the EC2 senior manager, quoting the candidate’s line: “I would ship a feature in two weeks.”
Day 20, the senior manager votes 3‑2 to allocate 15 % of the sprint capacity to debt remediation, referencing the 2023 Q3 roadmap.
Day 21, you schedule a follow‑up health‑check on the debt tickets for Day 30, embedding the metric “reduce CPU throttling events by 8 %.”
Day 22, you send an email titled “14‑day plan – please review” to the EC2 leadership, copying the VP of Compute, and the email includes the line: “We will not stall delivery; we will mitigate risk.”
Day 23, the VP replies with a single‑line “Not a blocker, but a signal of ownership.”
Day 24, you close the debt‑impact workshop, noting the team size 12 and the plan to ship the Nitro patch by Day 30.
Which AWS leadership principles matter most during the 30‑day performance review?
Demonstrate Customer Obsession and Dive Deep; they outweigh Ownership in the 30‑day Amazon bar‑raiser rubric.
Day 30, the performance review panel convenes in Seattle on July 10 2024 with senior director Emily Chen, Bar Raiser Tom Liu, and VP Greg Baker.
Day 30, the panel opens with the review rubric: Customer Obsession (score 9), Dive Deep (score 8), Ownership (score 7).
Day 30, you quote the interview question: “Tell me about a time you reduced latency for a distributed system,” and you answer with the EC2 Nitro patch example.
Day 30, senior director Emily asks: “What metrics did you improve?” and you reply: “Read‑latency variance down 12 %, CPU throttling down 8 %.”
Day 30, Bar Raiser Tom notes the Working Backwards narrative you filed on Day 14, calling it “a concrete signal of ownership.”
Day 30, you receive a 4‑1 vote to move you to “Meets Expectations” because you showed Customer Obsession and Dive Deep, not just Ownership.
Day 30, the panel’s final comment: “The problem isn’t your plan – it’s the lack of measurable impact.”
When should I initiate a one‑on‑one cadence with senior engineers on the EC2 compute team?
Start a 30‑minute cadence by Day 45; the cadence should align with the 60‑day roadmap checkpoint.
Day 35, you send a Slack note to senior engineer Mike O’Connor: “Let’s set a 30‑minute one‑on‑one every two weeks, starting Day 45.”
Day 45, the first one‑on‑one occurs on a Zoom call, and Mike says: “I need clarity on the Kinesis integration deadline.”
Day 45, you reference the AWS Kinesis Q3 2024 roadmap, dated August 1 2024, noting the feature flag rollout on Day 60.
Day 46, you log the meeting notes in the EC2 One‑On‑One tracker, marking the action item “Define Kinesis latency target < 5 ms.”
Day 48, senior manager Mira Patel reviews the tracker and notes the metric “reduce latency by 5 % before Day 60.”
Day 50, you share the one‑on‑one cadence results with the EC2 VP, quoting the Bar Raiser’s comment: “Not a meeting, but a signal of commitment.”
How can I influence the upcoming Q3 roadmap for AWS Kinesis without overstepping authority?
Leverage the Working Backwards narrative and the Amazon Dive Deep principle to propose a data‑stream scaling experiment by Day 60.
Day 55, you draft a 6‑page Working Backwards PRFAQ for a Kinesis scaling experiment, dated May 20 2023.
Day 55, you circulate the PRFAQ to senior engineers, including a verbatim script from the email: “Subject: Q3 scaling experiment – feedback needed by Day 60.”
Day 56, senior engineer Ana Lopez replies: “The experiment could reduce shard‑merge latency by 15 %.”
Day 57, the Kinesis product manager, senior director Sanjay Rao, reads the PRFAQ and notes the Dive Deep principle in the narrative.
Day 58, Sanjay schedules a 30‑minute sync, stating: “Not a decision, but a discussion of impact.”
Day 60, you present the experiment results to the Q3 roadmap meeting, citing the 2024‑07‑10 Kinesis roadmap slide that includes a new auto‑scaling feature.
Day 60, the VP of Data Services votes 4‑1 to include the experiment in the Q3 roadmap, referencing the Working Backwards narrative as a decisive factor.
Preparation Checklist
- Review the Amazon Working Backwards PRFAQ template, especially the “Customer Problem” section; the PM Interview Playbook covers this with real debrief examples from the S3 launch.
- Map the AWS Leadership Principles to your 90‑day plan; note Customer Obsession and Dive Deep scores.
- Schedule health‑check calls with each of the 12 engineers by Day 5; use the Slack script “We need a health check by day 5.”
- Build a 2‑page technical‑debt impact deck using the AWS Well‑Architected Framework; reference the EC2 debt tickets EC2‑D‑101‑103.
- Prepare a 6‑page Working Backwards narrative for the Kinesis scaling experiment; include the PRFAQ dated May 20 2023.
- Set recurring 30‑minute one‑on‑one slots with senior engineers starting Day 45; log actions in the EC2 One‑On‑One tracker.
- Align your 30‑day performance metrics with the bar‑raiser rubric scores; target Customer Obsession 9, Dive Deep 8.
Mistakes to Avoid
- BAD: Skip the health‑check by Day 5 and claim “I’ll learn on the job.” GOOD: Send the Slack “We need a health check by day 5” and hold the 30‑minute call.
- BAD: Focus solely on Ownership in the 30‑day review and ignore Customer Obsession metrics. GOOD: Present the 12 % latency reduction and cite the Dive Deep principle.
- BAD: Propose a Kinesis roadmap change without a Working Backwards PRFAQ. GOOD: Submit the 6‑page PRFAQ dated May 20 2023 and reference the Q3 roadmap slide.
FAQ
Is it better to ship a feature quickly or to follow the Working Backwards process?
Ship quickly only if the feature aligns with Customer Obsession and Dive Deep; otherwise the bar‑raiser will vote 3‑2 against you, as seen in the March 2023 Lambda loop.
Should I meet with every engineer individually in the first month?
No, prioritize health‑check calls with the 12‑engineer core team by Day 5; extending beyond that dilutes impact and triggers a “Not a priority, but a signal” comment from senior leadership.
How much equity should I negotiate for an AWS Engineering Manager role?
Target 0.05 % equity on a $210,000 base with a $30,000 sign‑on; the 2024‑07‑10 compensation package for a comparable role set that precedent.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.