The Software Engineer's Guidebook

Written by Gergely Orosz, a former engineer and manager at Uber, Microsoft, and Skyscanner, and author of The Pragmatic Engineer Newsletter, this book is the practical guide he wishes he'd had early in his career. It follows the typical software engineering career arc and pairs durable 'soft' skills (owning your career, performance reviews, promotions, collaboration, stakeholder management) with the 'hard' craft of engineering (coding, debugging, testing, software architecture, shipping to production, and building reliable systems). Rather than offering one-size-fits-all rules, it equips readers with a toolkit of approaches and the judgment to know when to apply each, grounded in how Big Tech, scaleups, startups, and traditional companies actually operate. If you want to grow as an engineer—accelerate your impact, take ownership of your trajectory, and understand what's expected at each level—this is a reference you'll return to for years.

What it argues

A factor model expressing how design levers and conditions (career ownership behaviors, engineering practices, collaboration, business understanding) drive psychological and behavioral states (reliability reputation, trust capital, influence) and outcomes (career progression, software reliability, team execution). Inferred from the book's structured, level-based guidance.

Key ideas it contributes

• Career Ownership Behaviors — The proactive stance an engineer takes toward their own professional development, treating their career as their responsibility rather than their manager's.
• Work Visibility and Communication — The degree to which an engineer's accomplishments, challenges, and impact are known and understood by managers, peers, and stakeholders.
• Getting Things Done Effectively — An engineer's capacity to reliably deliver impactful, properly-completed work by focusing on priorities, unblocking themselves, breaking down and estimating work, and taking initiative.
• Engineering Craft Proficiency — The depth and breadth of an engineer's technical skill in coding, languages, frameworks, debugging, refactoring, and use of productive tools.
• Healthy Engineering Practices — The adoption of proven processes and techniques—testing, code reviews, CI/CD, documentation, planning, and safe shipping—that improve software quality, maintainability, and iteration speed.
• Collaboration and Teamwork Quality — The effectiveness with which an engineer works with others through reviews, pairing, mentoring, feedback, cross-team work, and stakeholder management.
• Business and Product Understanding — An engineer's comprehension of how the company makes money, customer needs, key metrics (North Stars, KPIs, OKRs), profit/cost centers, and industry dynamics.
• Reputation as Reliable Engineer — The shared perception among managers and peers that an engineer consistently delivers impactful, properly-done work, unblocks themselves, and communicates well.