> Markdown version of [/videos/100641-when-writing-code-is-no-longer-the-bottleneck](https://www.wearedevelopers.com/videos/100641-when-writing-code-is-no-longer-the-bottleneck). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # When Writing Code is No Longer the Bottleneck If AI agents can write the code, what actually makes a developer senior? Faris Aziz explains why your future career growth depends on solving people debt and de-risking business decisions. - **Speakers:** Faris Aziz - **Event:** HalfStack Vienna 2026 - **Published:** November 19, 2026 - **Duration:** 31:22 - **URL:** https://www.wearedevelopers.com/videos/100641-when-writing-code-is-no-longer-the-bottleneck - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/89818a77cd5c3b1d7fed7c6da4cb75ac/thumbnails/thumbnail.jpg?time=30000ms ## Summary Faris Aziz challenges traditional notions of software engineering seniority in an era where AI agents have commoditized code generation. While the dictionary defines seniority by tenure, true engineering maturity has nothing to do with time served or raw code output. Instead, seniority is fundamentally about value creation and de-risking business decisions. As AI transformations prompt companies to evaluate roles based on what tasks can be delegated to markdown-driven coding agents, developers can no longer rely on syntax mastery alone to justify their value proposition. Navigating this shift requires recognizing knowledge gaps and cultivating team trust. Because accelerated development cycles often trigger the Dunning-Kruger effect, admitting what you do not know and asking foundational questions for the benefit of the team signals genuine authority. Furthermore, how engineers communicate directly reflects system reliability; building architectures on unvalidated assumptions causes "your software to be as shaky as your words." Aziz outlines five pillars for evaluating career progression across individual contributor (IC) and engineering manager (EM) tracks: technology, systems, people, process, and influence. As coding agents flatten the technology axis, engineers must lean harder into human-centric pillars like cross-functional leadership, system ownership, and open-source community influence. When writing code is no longer the bottleneck, an engineer's primary responsibility is keeping the product moving and acting as a force multiplier. Rather than viewing career growth as a rigid binary between IC and management tracks, developers should adapt to organizational needs while maintaining proactive transparency—such as using structured 1-on-1 documents to give leadership peace of mind and prevent micromanagement. Ultimately, senior engineers must address "people debt" alongside technical debt, use RAID (risks, assumptions, issues, dependencies) frameworks to manage product risk, and build authentic, non-transactional professional networks to own their career trajectories end-to-end. **Keywords:** software engineering seniority, ai coding agents, staff engineer career path, de-risking technical decisions, dunning-kruger effect in tech, engineering career frameworks, individual contributor vs engineering manager, system ownership and accountability, cross-functional team trust, technical debt vs people debt, RAID framework product development, automated PR reviews, engineering force multiplier, observability and monitoring, authentic developer networking, managing up in engineering ## Chapters 1. **Questioning traditional engineering seniority and career progression** (00:56) — Relying on job titles for authority or salary overlooks the need to define true engineering seniority beyond standard career tracks. 1. **Separating years of experience from actual value creation** (03:16) — Measuring seniority purely by tenure fails to capture impact, whereas true experience comes from delivering user value and de-risking technical decisions. 1. **Building empathy and foresight to de-risk production systems** (06:04) — Gaining trust to manage production systems requires developing empathy and pattern recognition from past failures rather than just accumulating age. 1. **Navigating AI layoffs and automating pull request reviews** (09:22) — As AI transformations trigger mass layoffs and role evaluations, engineers can use coding agents and GitHub CLI to automate repetitive PR feedback. 1. **Learning observability and admitting knowledge gaps on teams** (12:13) — Early production bugs with Stripe webhooks and React useEffect highlight why admitting knowledge gaps and asking basic questions builds foundational team knowledge. 1. **Aligning team trust with honest technical communication** (16:22) — Misrepresenting infrastructure skills or relying on unvalidated assumptions during planning leads to fragile software and erodes engineering trust. 1. **Evaluating career growth across five organizational pillars** (19:39) — While AI flattens the technology adoption curve, engineers can still multiply their impact across systems ownership, people, processes, and community influence. 1. **Owning product direction and building stakeholder peace of mind** (23:57) — When working in unmotivated teams or rigid career tracks, proactive communication with leadership builds trust and prevents micromanagement. 1. **Cultivating authentic networks and managing people debt** (27:36) — Because AI-generated resumes flood hiring pipelines, long-term career resilience depends on authentic networking, addressing people debt, and owning outcomes. ## Related Moments - [Navigating developer bottlenecks and human accountability](https://www.wearedevelopers.com/videos/100265-fireside-chat-in-conversation-with-werner-vogels-cto-of-amazon-com) (from "Fireside Chat - In conversation with Werner Vogels, CTO of Amazon.com") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/c3fba11645fa617695aa063f0772a420/thumbnails/thumbnail.jpg?time=50830ms - [Evolving the developer role beyond writing code syntax](https://www.wearedevelopers.com/videos/100549-building-the-agentic-software-factory) (from "Building the Agentic Software Factory") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/474e67dfbb08c1bc010cee59bbd6fb4d/thumbnails/thumbnail.jpg?time=192244ms - [Preserving the software engineering growth path for junior developers](https://www.wearedevelopers.com/videos/1735-engineering-mindset-in-the-age-of-ai-gunnar-grosch-aws) (from "Engineering Mindset in the Age of AI - Gunnar Grosch, AWS") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/ead760cd99e6dff2c4c01a604a55196c/thumbnails/thumbnail.jpg?time=176445ms - [Navigating technical debt generation in the era of AI](https://www.wearedevelopers.com/videos/1342-your-code-as-a-crime-scene) (from "Your Code as a Crime Scene") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/96819c3c070dfc725789b9d2b5d88a54/thumbnails/thumbnail.jpg?time=115085ms - [Evolving engineering leadership strategies in an AI-driven era](https://www.wearedevelopers.com/videos/100533-zta-zero-token-architecture) (from "ZTA: Zero Token Architecture") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/518d39672cd4a9884244eab77668b789/thumbnails/thumbnail.jpg?time=226592ms - [Balancing AI tool mandates with developer trust and productivity](https://www.wearedevelopers.com/videos/1365-wearedevelopers-live-the-weekly-developer-show-with-chris-heilmann-and-daniel-cranney) (from " WeAreDevelopers LIVE - the weekly developer show with Chris Heilmann and Daniel Cranney") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/7c26ff352c76f13c068aa46a8f88cd77/thumbnails/thumbnail.jpg?time=226085ms ## Related Articles - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers) - [Transforming Software Development: The Role of AI and Developer Tools](https://www.wearedevelopers.com/magazine/527-transforming-software-development-the-role-of-ai-and-developer-tools) - [Between AI Euphoria and Quality Engineering: Why We Are in Danger of Unlearning Software Quality](https://www.wearedevelopers.com/magazine/801-between-ai-euphoria-and-quality-engineering-why-we-are-in-danger-of-unlearning-software-quality) ## Related Jobs - [Staff Software Engineer, Copilot Code Review](https://www.wearedevelopers.com/jobs/ext/4743636-staff-software-engineer-copilot-code-review) at **GitHub** - [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/3929243-staff-developer-advocate-github-security-lab) at **GitHub** - [Principal Software Engineer, Copilot Code Review](https://www.wearedevelopers.com/jobs/ext/4667602-principal-software-engineer-copilot-code-review) at **GitHub** - [Senior Software Engineer - Semantic Data Lake (Open)SDE3](https://www.wearedevelopers.com/jobs/48597-senior-software-engineer-semantic-data-lake-open-sde3) at **WEX** - [Principal Software Engineer, Copilot Code Review](https://www.wearedevelopers.com/jobs/ext/3926064-principal-software-engineer-copilot-code-review) at **GitHub** - [Senior Solutions Engineer](https://www.wearedevelopers.com/jobs/ext/4554090-senior-solutions-engineer) at **GitHub**