# Amazon software engineer role guideline AI | Miyagami > Amazon's new SDE role guideline expects daily AI use and measures long-term outcomes. What it means for engineering leaders hiring in 2026. Source: https://www.miyagami.com/de/resources/news/amazon-rewrites-engineer-role-guideline-around-ai [Home](https://www.miyagami.com/de/)/ [Resources](https://www.miyagami.com/de/resources)/ [News](https://www.miyagami.com/de/resources/news)/ Amazon rewrites its engineer role guideline around AI # Amazon rewrites its engineer role guideline around AI Amazon's revised SDE guideline expects AI use from every engineer and judges them on customer and team outcomes, with token counts called flawed. **[Dale Wesdorp](https://www.linkedin.com/in/dale-wesdorp/)** Co-Founder, Miyagami Neuigkeiten 3 Min. Lesezeit 27. Oktober 2026 On 27 October 2026 Amazon published a memo from Terk Terkowitz, VP and Distinguished Engineer at Worldwide Amazon Stores, describing a revised role guideline for its software development engineers (SDEs). The memo says AI is changing software engineering "both more quickly and more fundamentally" than earlier shifts such as cloud and microservices, and that Amazon will measure engineers on outcomes instead of tool usage. ## What the memo says Amazon's SDE guidelines have historically avoided naming technologies. This time the Senior Principal and Distinguished Engineer communities debated whether AI is different, and concluded that it is. The memo tells engineers to learn and apply AI in daily work, and states that AI will be at the centre of software engineering practice. The guideline does not define what good AI practice looks like. Amazon's reasoning is that any definition written now "will likely look antiquated by this time next year". It focuses on what stays constant: impact on customers, on the business and on teams. The memo is also open about measurement. Amazon prefers to judge engineers on long-term outcomes, which it describes as time delayed and hard to isolate. Where it has used input metrics such as token usage or AI tool adoption, or throughput metrics such as code changes and reviews, it calls them flawed proxies. It also says that finding where AI falls short is "a finding, not a failing". Two further points stand out. Amazon says engineers who stay close to their products and customers get the most from AI, and it wants to reverse a trend of some engineers becoming less connected to the business. It also says its approach can serve as a model for its customers. ## Was das für Engineering-Teams bedeutet The memo supports a pattern seen in this year's surveys: usage is easy to count and outcomes are not. If your team tracks prompts, accepted suggestions or lines of code, Amazon's own reading is that those numbers describe activity. Cycle time, review time, defect rates and customer results are slower to collect and closer to what the business cares about. It also shifts what the job description asks for. Amazon expects AI use from every SDE and then evaluates the judgement applied on top of it: knowing the customer, owning the result and deciding when AI output is not good enough. ## Was das für die Einstellung von Entwicklern bedeutet A large employer that expects daily AI use and measures outcomes sets a reference point for what a senior engineer looks like in 2026. A candidate who lists tools tells you little. A candidate who can describe a product result they owned, and where AI output fell short and what they did about it, gives you the evidence the memo points to. That shapes interviews as well. Testing someone with AI tools on and off, in a real codebase, shows both their own skill and how they direct and check an agent. Miyagami's engineers are each tested by an AI-native tech lead who works with AI every day, and you can read how that works on [how we vet](https://www.miyagami.com/de/how-we-vet). If you are weighing a senior hire against that standard, [AI-native engineers](https://www.miyagami.com/de/hire/ai-native-engineers) describes the profile. The memo is one company's guideline for its own staff and does not report measured productivity results. It shows how a large engineering organisation now frames the role, and it gives engineering leaders a published position to compare their own expectations against. Quellen - [Amazon, An update from Amazon engineering leadership on the role of the developer in the age of AI](https://www.aboutamazon.com/news/company-news/amazon-software-engineer-role-guideline-ai), 27. Oktober 2026 - [PPC Land, Amazon calls AI usage metrics 'deeply flawed' but keeps using them](https://ppc.land/amazon-calls-ai-usage-metrics-deeply-flawed-but-keeps-using-them/), 28. Oktober 2026 - [Times of India, Amazon updates AI usage rules for engineers, sends memo](https://timesofindia.indiatimes.com/technology/tech-news/amazon-updates-ai-usage-rules-for-engineers-sends-memo-we-are-seeing-the-beginning-of-ais-effect-on-software-engineering/articleshow/135249517.cms), 28. Oktober 2026 Unser Auswahlverfahren Jeder Engineer, den wir bei Kunden einsetzen, durchläuft zwei Assessments: eines ohne KI-Tools, eines mit. Beide Scorecards sind veröffentlicht. [Unser Auswahlverfahren](https://www.miyagami.com/de/how-we-vet) Engineers einstellen? Eine shortlist mit Senior AI-native Engineers in drei Werktagen. [Shortlist anfordern](https://www.miyagami.com/de/shortlist) ## Weitere Neuigkeiten [Alle Neuigkeiten](https://www.miyagami.com/de/resources/news) [23. Oktober 20262 Min. Lesezeit ### 32 % verzichteten auf einen Software-Kauf, um die Funktion mit KI-Agenten selbst zu entwickeln Lesen](https://www.miyagami.com/de/resources/news/32-percent-skipped-software-purchase-to-build-with-ai) [20. Oktober 20262 Min. Lesezeit ### 87 % sagen, KI beschleunigt die Arbeit, aber nur 28 % erleben weniger Reibungsverluste Lesen](https://www.miyagami.com/de/resources/news/ai-speeds-up-developers-but-friction-remains-atlassian) [12. Oktober 20262 Min. Lesezeit ### KI-Agenten erzeugen 30 % mehr Code, aber keine zusätzliche Software Lesen](https://www.miyagami.com/de/resources/news/ai-coding-agents-add-30-percent-more-code-no-more-output) Kontakt aufnehmen ## Shortlist in drei Tagen erhalten Sie schicken uns die Rollen und den Stack, in einem kurzen Formular oder in einem 30-minütigen Gespräch. Innerhalb von drei Werktagen erhalten Sie Senior Engineers mit Namen zur Prüfung, jeweils mit beiden Scorecards, und Sie können innerhalb von fünf Werktagen einstellen. [Shortlist anfordern](https://www.miyagami.com/de/shortlist) Bewertet auf **Clutch** 42 Bewertungen [ISO 27001 Zertifiziert](https://trust.miyagami.com/) Dreißig Minuten mit Dale buchen Der Kalender wird von HubSpot bereitgestellt und setzt eigene Cookies. Laden Sie ihn hier, oder buchen Sie direkt auf der HubSpot-Seite. [Buchungsseite öffnen](https://sales.miyagami.com/meetings/dwesdorp)