CTO and Engineering Leadership Career Guide
Explore the route from senior engineer into engineering leadership: the manager and staff-plus fork, what each track pays, how teams are run, and staying current on architecture, security and AI.
How we research our career guides
The Top Engineering Leadership News, in 5 Minutes.
We handpick the best engineering leadership newsletters and distill the key news and insights into a 5-minute audio briefing, texted to you every morning.
Try the Engineering Briefing, FreeFree
At a glance
Engineering Leadership at a Glance
Computer and information systems managers are a 685,800-job occupation in the United States, projected by the Bureau of Labor Statistics to grow 16 percent from 2025 to 2035 with about 53,500 openings a year. The common picture, a CTO who stopped coding and now sits in meetings, describes one job out of many. Engineering leadership also covers engineering managers who own a team's delivery and development, directors and VPs who own a whole function, platform and infrastructure leaders who own the systems everyone else builds on, security leaders who own exposure, and staff-plus individual contributors who lead technically without managing anyone. That last group matters, because management is not the only ladder and the fork between the two is the decision most senior engineers reach by drifting rather than choosing. Pay follows scope rather than years served: the median for computer and information systems managers was $175,140 in May 2025, against $135,980 for software developers and $213,990 for chief executives. The strengths the work rewards are not only technical. The leaders who last are the ones who can write clearly, decide with incomplete information, and refuse work in a way the business accepts. The direction of travel is set by AI, which DORA's research describes as an amplifier of whatever an organisation already is, moving the job from buying tools to fixing the platform underneath them.
Key Industry Statistics
$175,140
Median pay, computer and information systems managers (May 2025)US Bureau of Labor Statistics
685,800
Computer and information systems manager jobs (2025)US Bureau of Labor Statistics
69.3%
Software development postings that are senior-level (Q1 2026)Indeed Hiring Lab
32.7%
Developers who trust the accuracy of AI outputStack Overflow Developer Survey 2025
Common Roles
- Engineering Manager
- Director of Engineering
- VP of Engineering
- Chief Technology Officer
- Staff or Principal Engineer
- Head of Platform
Where Leaders Work
- Product companies
- Enterprise IT
- Startups and scale-ups
- Consultancies and agencies
- Financial services
- Public sector and defence
Credentials That Matter
- Computer science degree
- Shipped production systems
- Cloud architecture certifications
- Security framework literacy
- A management credential
Key Areas in Engineering Leadership
People Management
Hiring, performance, growth and delivery, judged on the team's output rather than your own.
Platform & Infrastructure
The internal developer platform, the cloud bill and the paved road every team builds on.
Architecture & Strategy
Long-lived decisions about systems, data and interfaces that outlast any single roadmap.
Security & Risk
Secure development practice, incident response and the exposure a board will ask about.
AI Enablement
Tooling, policy and the platform work that decides whether AI adoption actually pays.
Staff-Plus Practice
Technical leadership without direct reports: strategy, review and influence across several teams.
Engineering Leadership Jobs & Salaries
Federal wage data measures occupations rather than job titles, so this ladder reads as scope rather than years served. Every figure is the May 2025 median from the Occupational Outlook Handbook.
Computer network architects
$134,050
Software developers
$135,980
Computer and information research scientists
$140,300
Computer and information systems managers
$175,140
Chief executives
$213,990
Source: US Bureau of Labor Statistics, Occupational Outlook Handbook, May 2025 wage data, accessed October 2026.
Engineering Leadership Career Paths
Engineering leadership is not one ladder. It is four tracks that start from the same senior engineering seat and then diverge sharply in what they reward, what they pay, and how much of the week is still technical.
- Tech Lead2 to 5 yearsStill writing code, but accountable for a team's technical direction and for unblocking other people first.
- Engineering Manager4 to 8 yearsOne team's delivery, hiring and performance. The first job measured entirely on other people's output.
- Senior or Group Manager7 to 12 yearsManagers reporting to you. You now change outcomes by changing structure rather than by intervening.
- Director of Engineering10 or more yearsA function, a budget and a headcount plan, argued against the rest of the executive team.
Credential that fits A management credential, or a record of teams that stayed
There is no federal occupation code for a staff engineer, a head of platform or a chief technology officer. Engineering managers and above are counted under computer and information systems managers, and company officers under chief executives, which is why the leadership figures on this page come from those two occupations rather than from a code of their own.
A Typical Day in Engineering Leadership Jobs
Five roles that carry most of the discipline's headcount, ordered from the first leadership step to the executive seat. The schedules are representative rather than universal: company size, stage and the on-call rota move everything.
Tech LeadEntry-Level · First Leadership StepStill writing code, but accountable for a team's technical direction and for the decisions nobody else is placed to make.
- 09:00Check what broke overnight, then clear the review queue before anyone is blocked by it.
- 10:00Stand-up, followed by the two conversations stand-up revealed were needed and could not happen there.
- 11:00Your own focused block. It is the first thing the day eats, so it is defended rather than hoped for.
- 14:00Design review on the next piece of work, mostly asking what happens when the assumption is wrong.
- 16:00Write the decision down. Anything agreed only in a call will be re-litigated within a month.
Engineering ManagerEntry to Mid · One TeamOne team's delivery, hiring and growth, and the first job where none of the output on your name is yours.
- 08:30Read the delivery board and the incident channel. You are looking for the thing nobody has escalated.
- 09:30One-to-ones. The most valuable hour of the week and the first one cancelled when the week gets hard.
- 12:00Interviews and candidate debriefs, plus the requisition argument you are having with finance.
- 14:00Planning and prioritisation with product, where most of the week's real negotiation happens.
- 16:30Write the weekly update. Deciding what to leave out is most of the skill in it.
Staff EngineerMid-Level · Cross-Team TechnicalTechnical leadership with no direct reports: the shared system, the migration, and the architecture nobody owns yet.
- 09:00Deep work on the hardest part of the current migration, before the calendar fills up.
- 11:00Architecture review with two teams whose services are about to be coupled more tightly than either realises.
- 13:00Write the design document. Influence at this level travels as prose rather than as meetings.
- 15:00Pair with a mid-level engineer on something they are stuck on. Half the job is raising other people.
- 17:00Review the proposals that would quietly make the system harder to change, and say so early.
Director of EngineeringSenior-Level · FunctionSeveral teams, a budget and a headcount plan, with most of the leverage now in structure rather than intervention.
- 08:00Metrics review across teams: throughput and instability together, plus attrition and open requisitions.
- 09:30Skip-level conversations, which are how you find out what your managers are not telling you.
- 11:30Cross-functional planning with product and finance, where the quarter is actually decided.
- 14:00Platform and cloud cost review. Unit economics, not totals, because totals persuade nobody.
- 16:00Performance calibration and the two difficult conversations you have been scheduling around.
Chief Technology OfficerExecutive · Whole CompanyTechnical bets, build versus buy, security and AI posture, and the board conversation about all of them.
- 08:00Scan what moved overnight: disclosures, model releases, competitor launches, and anything that changes a bet.
- 09:30Executive team meeting. Engineering is one input among several and is argued for in business terms.
- 11:00Architecture or security governance: what reaches production, how it is evaluated, who is accountable.
- 14:00Customer or partner conversation, usually the technical reassurance a deal is waiting on.
- 16:00Board or investor preparation, translating three years of engineering into one page of consequence.
JOB SEARCH
How to Get an Engineering Leadership Job in 2026
Whether you are taking a first team, choosing between the manager and staff-plus tracks, or going for a function, the same three questions decide it: what the field expects now, what you can already evidence, and how you answer for it in a room.
Entry-Level
Step Into Engineering Leadership
What changes the day you stop being measured on your own output, how the manager and staff-plus tracks differ, and what a panel checks when you have led nothing yet.
What you should know about the field
The two ladders, what each one pays, and the market you will be hiring into.
The manager track and the staff-plus track are both ladders
The Bureau of Labor Statistics counts the management route as computer and information systems managers, SOC 11-3021: a 685,800-job occupation with a May 2025 median of $175,140, projected to grow 16 percent to 2035 with about 53,500 openings a year. The technical route is not counted under a single code, but its nearest federal proxies are real jobs with real wages: computer and information research scientists, SOC 15-1221, at $140,300 with 22 percent projected growth, and computer network architects, SOC 15-1241, at $134,050, an occupation BLS says typically requires five or more years of prior experience.
The useful conclusion is that a senior engineer is choosing between two ladders rather than deciding whether to be promoted. The management ladder is wider and better paid at the top. The technical ladder is narrower, grows faster in percentage terms, and does not require you to give up the work you are good at.
What a first-line engineering manager is accountable for
Software Engineering Management is one of the eighteen knowledge areas in SWEBOK v4.0, the IEEE Computer Society's body of knowledge for the profession, published in 2024 and revised in September 2025. Treating it as a knowledge area rather than a rank is the right frame: it sits beside architecture, testing, security and economics rather than above them.
In practice the accountability is delivery, people and the system, measured together. DORA's current model uses five metrics, three for throughput (change lead time, deployment frequency, failed deployment recovery time) and two for instability (change fail rate, deployment rework rate). A manager who improves the first three while the last two degrade has not improved anything.
The pay step into management is real but narrower than expected
The gap between the software developer median of $135,980 and the computer and information systems manager median of $175,140 is about $39,000 in May 2025 data. That is a genuine step, but it is a step onto a different job rather than a raise for the same one, and the deep technical proxy of computer and information research scientists already sits at $140,300.
Industry moves the number as much as the title does. BLS records median pay for computer and information systems managers at $200,510 in information, $182,510 in finance and insurance, $179,510 in computer systems design, $178,110 in manufacturing and $176,950 in management of companies. Changing sector can be worth more than changing level.
The junior hiring market is a problem you inherit
Indeed's Hiring Lab found that senior-level positions made up 69.3 percent of software development job postings in the first quarter of 2026, the highest tilt of any sector it measured. Nationwide the mix is roughly the opposite: about 14 percent senior, 40 percent mid-level and 46 percent entry-level.
Entry-level postings have fallen since their 2022 peak and were down 7.5 percent year on year by May 2026, and the Hiring Lab notes research finding that people who enter during weak hiring can carry lower wages for up to a decade. For a new manager this is not a macro story. It decides whether you can staff a team with anyone you will still be able to promote in three years.
Skills employers look for
What a hiring executive checks in someone who has been excellent at a job they are about to stop doing.
Delegating without losing the thread
Writing that survives being forwarded
Running a blameless incident review
Westrum's typology, which DORA uses, separates organisations by what happens to a messenger. In a generative culture messengers are trained and failure leads to inquiry; in a pathological one failure leads to scapegoating. Which one you run is set by how you behave in the first hour after an outage.
Reading delivery metrics honestly
Interview questions and answers
First-leadership questions, and what the panel is listening for underneath them.
Why do you want to manage, and what will you miss about writing code?
What they are looking for: Whether you chose this or drifted into it, and whether you understand that you are swapping jobs rather than being promoted.
I want it because the thing I enjoyed most in my last two years was unblocking other people and arguing about what we should build, not the implementation. What I will miss is finishing something in an afternoon. I have made peace with a feedback loop measured in quarters, and I would rather know that now than discover it in month three.
Make it yours: Name a concrete loss. Candidates who claim they will miss nothing read as people who have not done the job or thought about it.
How would you spend your first ninety days leading a team you did not build?
What they are looking for: Whether you listen before you reorganise, and whether you have any way of measuring the team other than vibes.
Thirty days of one-to-ones and reading: the incident history, the deploy frequency, the code review wait times, the last two planning cycles. Then I would name the one or two things that are obviously broken and fix the cheapest of them visibly. I would not restructure anything in the first quarter, because I would not yet know which constraint is real.
Make it yours: Say what you would measure, by name. A ninety-day plan with no data in it is a list of intentions.
Tell me about a technical decision you made that turned out to be wrong.
What they are looking for: Whether you can be wrong out loud, and whether you noticed from evidence or from someone telling you.
I split a service that did not need splitting, because the team was large rather than because the deployment coupling demanded it. Lead time got worse and we spent a quarter on coordination we had not had before. We merged two of the pieces back. The test I use now is whether a service can be deployed independently of the things it depends on.
Make it yours: Land on the rule you took from it. A mistake with no changed heuristic reads as a story rather than learning.
How do you tell whether a team is actually delivering well?
What they are looking for: A stated model rather than a feeling, and an awareness that speed alone is not an answer.
I look at throughput and instability together: lead time, deploy frequency and recovery time against change failure rate and rework. If throughput is rising while failures are rising, we are borrowing. Then I check the human side, because a team that is quietly hating the work will show up in the numbers two quarters later.
Make it yours: Pair every speed metric with a stability one out loud. That pairing is the whole point of the question.
Mid-Level
Own a Function or a System
How to move from one team to several, or from senior engineer to staff-plus, and what a platform, a cloud bill and an AI policy start to demand of you.
What you should know at this stage
Where leverage actually comes from once you are past your first team, and what the research says about each lever.
Platform quality decides whether AI adoption pays
DORA reports that by 2025, 90 percent of organisations used an internal developer platform and 76 percent had a dedicated platform team. The finding that matters for a leader is conditional: where platform quality is high, AI's effect on organisational performance is strong and positive, and where platform quality is low the effect is negligible.
That reframes an AI strategy as a platform strategy. Individual coding gains are lost again if testing, security review or deployment is slow, which is why DORA treats the platform as the thing that distributes and governs the tools. It also warns of a J-curve: early gains, then a dip as complexity grows, then a higher plateau.
A clear AI stance is a leadership artefact, not a wiki page
DORA names a clear and communicated AI stance as one of the capabilities that amplify AI's benefits. It defines the stance as a widely shared, easy-to-understand framework telling developers how the organisation expects them to use AI, which tools are allowed, and how they will be supported. Without one, teams split between excessive caution and unvetted tools.
The implementation DORA recommends is a three-bucket framework: prohibited, permitted with guardrails, and allowed, published as a living document with executive sponsorship and a cross-functional working group. Its research found that a clear stance turns AI's usually neutral effect on developer friction into a decrease.
Architecture is an organisational decision
DORA's loosely coupled teams capability sets a hard test: a service is only loosely coupled if it can be deployed independently of the services it depends on. A great many systems described as service-oriented fail that test, and the symptom is that small changes trigger large failures and constant cross-team coordination.
Conway's Law is the leadership consequence. A system tends to mirror the communication structure of the organisation that built it, so DORA recommends the Inverse Conway Maneuver: design the teams to match the architecture you want. It also points out that architecture should fit scale, and cites Google's Datastore, one of the largest NoSQL services anywhere, running with around eight people.
Cloud spend becomes your problem before it becomes finance's
The FinOps Framework, maintained by the FinOps Foundation as a project of LF Projects, is the closest thing to a standard here. It runs on three phases, Inform, Optimize and Operate, across four domains: understand usage and cost, quantify business value, optimize usage and cost, and manage the practice itself.
Two of its principles are the ones that land on an engineering leader. Business value drives technology decisions, and everyone takes ownership of their own technology usage. In practice that means allocation and unit economics have to exist before any optimisation argument can be made, which is engineering work rather than finance work.
Skills employers look for
What separates a competent manager from the one an organisation is restructured around.
Hiring against a tilted market
Treating the platform as a product
DORA's named platform pitfalls are all leadership failures: building without user research, acting as gatekeepers, operating as a ticket queue, shipping one large release, and imposing one model on every team. The fix is a minimum viable platform for the most common workflow, designed for extension.
Security as everyone's daily work
DORA cites State of DevOps research finding high performers spend 50 percent less time remediating security issues, because the work is built in rather than inspected at the end. NIST's Secure Software Development Framework, SP 800-218, gives the same idea a structure: prepare the organisation, protect the software, produce well-secured software, respond to vulnerabilities.
Deciding in public
DORA's five leadership characteristics are vision, inspirational communication, intellectual stimulation, supportive leadership and personal recognition. Its test for vision is blunt and worth borrowing: people across the organisation should be able to describe it consistently without looking it up.
Interview questions and answers
Mid-career questions, where the subject shifts from your own judgement to the system you are running.
How would you decide whether to build an internal developer platform?
What they are looking for: Whether you would start from developer pain and the most common workflow, or from a technology you wanted to use.
I would find the single workflow that most teams repeat and measure what it costs them today in wait time. If that is large, I would build the minimum viable version of it for that workflow only, designed so other teams can extend it. I would also commit to a dip, because platforms usually get worse before they get better.
Make it yours: Scope it to one workflow and say the dip out loud. Unbounded platform proposals are the ones executives have already seen fail.
Walk me through how you would set your organisation's policy on AI coding tools.
What they are looking for: Whether you would write a usable stance rather than a legal notice, and whether you know what you are optimising.
Three buckets: prohibited, permitted with guardrails, and allowed. Written with security, legal and two working engineers, published where people actually look, and revisited on a schedule rather than whenever something goes wrong. The aim is to remove uncertainty, because uncertainty produces both excessive caution and people quietly using unvetted tools.
Make it yours: Name who writes it with you. A policy written by one function alone is the failure mode interviewers are probing for.
Your senior engineers want microservices. How do you decide?
What they are looking for: Whether you can separate an architectural argument from an organisational one, and whether you will be captured by the loudest engineer.
I would ask what deployment coupling we actually have today and how often one team waits on another. If teams can already ship independently, the split buys nothing. If they cannot, I would split along the boundary that is blocking, not along the whole domain model, and I would expect the team structure to change with it.
Make it yours: Make the independent-deployability test explicit. It is the thing that separates a reasoned answer from a fashion.
How do you handle an underperformer who is also your only expert in something?
What they are looking for: Whether you will act despite the dependency, and whether you see the dependency itself as the real failure.
I would treat them as two problems. The performance conversation happens on its normal timeline, documented, with a clear bar. Separately I would start removing the single point of failure immediately, through pairing and written documentation, because the fact that one person holds that knowledge is my mistake rather than theirs.
Make it yours: Separate the two problems explicitly. Answers that delay the conversation because of the dependency are the wrong answer.
Senior-Level
Lead the Function or the Company
The three directions senior engineering leadership goes: the executive seat, the staff-plus technical summit, and the founder or chief technology officer route, each a different labour market.
What you should know at this stage
The senior routes diverge sharply, and the federal numbers say something uncomfortable about how many seats exist.
The executive step is a change of occupation
Chief executives, SOC 11-1011, had a median of $213,990 in May 2025 across about 291,600 jobs, and the occupation is projected to grow only 3 percent from 2025 to 2035. Computer and information systems managers, by contrast, are 685,800 jobs growing 16 percent with roughly 53,500 openings a year.
The shape of that is worth absorbing before you plan a career around it. The seats above director are far fewer and growing far more slowly than the ones below, so the realistic senior path for most people is scope and sector rather than title.
Industry moves senior pay more than title does
Against an overall May 2025 median of $175,140 for computer and information systems managers, BLS records $200,510 in information, $182,510 in finance and insurance, $179,510 in computer systems design and related services, $178,110 in manufacturing and $176,950 in management of companies and enterprises.
The spread between the top and bottom of that list is larger than many internal promotions, which is the argument for treating a sector move as a legitimate senior career step rather than a sideways one.
AI and security governance land on the CTO's desk
NIST's AI Risk Management Framework, NIST AI 100-1, was released in January 2023 and organises the work into four functions: govern, map, measure and manage. Its Generative AI Profile, NIST-AI-600-1, followed in July 2024 and addresses risks specific to generative systems.
Alongside it sit the Cybersecurity Framework 2.0 and the Secure Software Development Framework, SP 800-218. None of these is a checklist, and NIST says so explicitly about the SSDF: they are risk-based starting points and a shared vocabulary for talking to auditors, customers and a board.
The technical ladder does not stop at manager
Computer and information research scientists, SOC 15-1221, sit at a $140,300 median across 38,600 jobs, projected to grow 22 percent to 2035, with a master's degree as the typical entry. Computer network architects, SOC 15-1241, sit at $134,050 across 181,800 jobs and typically require five or more years of prior experience.
SWEBOK v4.0 makes the same point structurally: software engineering management is one of eighteen knowledge areas, listed beside architecture, security, economics and professional practice rather than above them. Management is a discipline within the profession, not its summit.
Skills employers look for
What a company is buying when it hires a senior engineering leader rather than an experienced manager.
Translating engineering into money and risk
Governing tools you did not build
The NIST AI Risk Management Framework's four functions, govern, map, measure and manage, are a usable spine for deciding which AI systems reach production, how they are evaluated and who is accountable when they are wrong. The Generative AI Profile extends it to the systems your engineers are already using. The need is evidential rather than theoretical: Stack Overflow's 2025 survey found 84 percent of developers using or planning to use AI tools while only 32.7 percent trusted the accuracy of the output.
Building a culture that reports bad news
Designing an apprenticeship the market will not supply
Interview questions and answers
Senior questions, where the subject is the function, the budget and the company rather than the team.
What is your three-year technical strategy, and what would make you abandon it?
What they are looking for: Whether you have a strategy rather than a roadmap, and whether it has falsifiable conditions attached.
Mine would be to make the common path cheap: one paved road, one deployment model, one observability stack, so new work is fast by default. I would abandon it if the business moved into a domain with genuinely different constraints, for example regulated on-premise deployment, where a single path would become the bottleneck rather than the accelerant.
Make it yours: Give a real abandonment condition. A strategy nothing could falsify is a statement of taste.
How do you present an engineering budget to a board that wants it smaller?
What they are looking for: Translation. Whether you can convert an engineering argument into cost, risk and optionality without becoming defensive.
I would bring unit economics rather than totals: cost per transaction, cost per customer, and the trend. Then I would show which spend is keeping the lights on, which is buying speed, and which is buying optionality, and offer a specific reduction in the third with the consequence named. Boards fund arguments that come with a cost of inaction attached.
Make it yours: Bring one number per category and one concrete cut you are willing to make. Open defences get the cut made for you.
A critical vulnerability lands in a dependency you ship. Walk me through day one.
What they are looking for: Whether you have a process rather than heroics, and whether you can say what you do not know to a customer.
First establish whether we are actually exposed, which needs an inventory of what we ship and where. Then contain, patch, and tell customers what we know and what we do not, on our own timeline rather than a journalist's. Afterwards the question is not who missed it but why our inventory could not answer the exposure question in minutes.
Make it yours: Lead with the inventory. Leaders who begin at the patch are describing the second hour, not the first.
How do you know your AI investment is returning anything?
What they are looking for: Whether you measure outcomes or seat counts, and whether you know what conditions the return depends on.
Seats bought is not a measure. I would watch throughput and instability together, because the research is clear that adoption can raise one and damage the other, and I would check whether platform quality is good enough for the gains to survive review and deployment. If it is not, the honest answer is that the investment is in the platform first.
Make it yours: Name the conditional. An answer that claims an unqualified return is the one senior interviewers discount.
Why Engineering Leaders Need to Stay Informed
Model capabilities, cloud pricing, security disclosures and the hiring market all move faster than any planning cycle. A leader who is a quarter behind makes decisions from assumptions that have already expired, and the cost appears in architecture, budget and attrition rather than in a single bad meeting.
Read more
The second reason is positional. Your engineers read the primary sources daily, and a leader who learns about a shift from their own team has already lost the room on it.
The bottom line
Engineering Leadership Is Changing Fast. Stay Ahead.
The federal numbers and the daily work point the same way. Computer and information systems management is projected to grow 16 percent to 2035, roughly 53,500 openings a year, at a median of $175,140. The demand is there. The advantage goes to leaders who see a shift before their teams feel it.
Stay Informed with Hark's Engineering Leadership Briefing
How it works
Curated from the best newsletters
Hark's editorial team handpicks the sources worth following. See how we rank
The news that matters in 5 minutes
Hark distills the most important stories into a concise audio briefing.
Texted to you every morning
You set the time and listen when you want.
Go deeper if you want
Upgrade to the 15-minute briefing and select up to 50 newsletters.

The 10 Engineering Leadership Newsletters We Handpicked
The Rundown AI
Rowan Cheung
- Free
- Daily
- 2M readers
Rowan Cheung's daily five-minute rundown of AI news and tools, teaching 2 million+ readers what just shipped and how to actually use it.
Why CTOs & engineering leaders read it
A five-minute daily on what shipped in AI and how to use it. For an engineering leader it is the fastest read on what your teams and your board will both be asking about this week.
More about this newsletter
Rowan Cheung's The Rundown AI is one of the largest AI newsletters, a daily digest of model launches, tools, and industry news built for a broad audience. Each issue turns the day's biggest release into a workflow you can try the same morning. Breadth over depth, delivered fast.
Best for: Anyone who wants to keep up with AI in five minutes a day. It's the largest AI newsletter for a reason: every issue turns the day's biggest model release or tool launch into something you can actually try that morning, no technical background needed.
Superhuman AI
Zain Kahn
- Free
- Daily
- 1.5M readers
Zain Kahn's daily briefing on AI news, tools, and how-tos, engineered for busy professionals and read by 1.5 million+ subscribers.
Why CTOs & engineering leaders read it
A daily on AI news, tools and how-tos built for busy professionals. Useful for the tooling layer, which is where most of an engineering org's actual AI adoption happens.
More about this newsletter
Zain Kahn's Superhuman AI is built around using AI at work: practical tool tips, prompts, and news framed for productivity in a quick daily read. It is the fastest scan of the big AI dailies. Best for professionals who want practical how-to alongside the headlines.
See the other 8 newsletters
TLDR AI
TLDR
- Free
- Daily (weekdays)
- 1.1M readers
TLDR's daily AI edition compresses research papers, product launches, and industry news into a five-minute weekday read for over a million subscribers.
Why CTOs & engineering leaders read it
TLDR's daily AI edition, compressing research, product launches and industry news into a five-minute weekday read. The fastest way to keep pace with the field your teams are building in.
More about this newsletter
TLDR AI compresses the day's AI research, product launches, and industry news into one-sentence summaries you can scan in minutes. It is the most technical of the big AI dailies, written with engineers in mind. Efficient, dense, and no-nonsense.
TLDR
TLDR Newsletter
- Free
- Daily
- 8M readers
Five-line summaries of the day's engineering, startup, and science links.
Why CTOs & engineering leaders read it
Five-line summaries of the day's engineering, startup and science links. The cheapest way to stay close to what your engineers are reading.
More about this newsletter
Five-line summaries of the day's tech, startup, and programming links, chosen for engineers rather than investors. No commentary and no filler; the TLDR homepage claims more than eight million readers.
The Download
MIT Technology Review
- Free
- Daily
- 250k readers
MIT Technology Review's daily dose of what matters in emerging technology, written with institutional rigor.
Why CTOs & engineering leaders read it
MIT Technology Review's daily on emerging technology, institutional and hype free. The version of a technology story you can repeat to a board without being wrong.
More about this newsletter
MIT Technology Review's daily briefing distills what matters in emerging technology, drawing on the magazine's own reporting on AI, biotech, climate, and computing. It is institutional, sober, and reliably free of hype. One of the few tech dailies with a real newsroom behind it.
Best for: Readers who want emerging tech coverage from a real newsroom: sober, hype free daily reporting on AI, biotech, climate, and computing from MIT Technology Review.
The Pragmatic Engineer
Gergely Orosz
- Free
- Frequent
- 1.1M readers
Deeply reported dispatches on how Big Tech and startups actually build software, from an ex-Uber engineering leader.
Why CTOs & engineering leaders read it
Deeply reported dispatches on how Big Tech and startups actually build software. The most useful writing available on how engineering organizations really work.
More about this newsletter
Gergely Orosz, formerly an engineering manager at Uber, reports on how software actually gets built inside Big Tech and startups: engineering culture, compensation, layoffs, and deep dives into real systems. His reporting on tech companies is read industry-wide. The deep dives are paid, but the free weekly issues keep casual readers current.
TLDR Dev
TLDR (TLDR Media)
- Free
- Daily
- 470k readers
Daily software engineering news, tools, and web dev links in a five minute read.
Why CTOs & engineering leaders read it
Daily software engineering news, tools and web dev links in a five minute read. What your teams are reading, which is worth knowing directly rather than second hand.
More about this newsletter
TLDR Dev is the software engineering edition of the TLDR network: one daily email of programming news, new tools, and web development links, each with a one-paragraph summary. It is aggregation, not commentary, tuned for working developers across the stack. Best for engineers who want the day's dev news skimmed in five minutes.
ByteByteGo Newsletter
Alex Xu (ByteByteGo)
- Freemium
- 1M readers
System design newsletter by Alex Xu, co-author of the System Design Interview books, explaining complex architectures in plain language with heavy use of diagrams.
Why CTOs & engineering leaders read it
Alex Xu's system design newsletter, explaining complex architecture in clear diagrams. Good for keeping your own technical judgment sharp as you move further from the code.
More about this newsletter
Issues break down how large systems work (Docker internals, network protocols, the tech stacks behind companies like Netflix) in the same diagram-first style as Xu's bestselling system design books. Hosted on Substack with a free tier and paid deep-dive content; the site claims over 1,000,000 readers.
Dark Reading Daily
Dark Reading (Informa TechTarget)
- Free
- Daily
Daily email from cybersecurity news site Dark Reading covering threats, vulnerabilities, data breaches, and defense strategy for security professionals.
Why CTOs & engineering leaders read it
Headlines and analysis from one of the most widely read enterprise-security sites. The standing reminder that security is an engineering problem before it is a security-team problem.
More about this newsletter
Headlines and analysis from one of the most widely read enterprise-security news sites, spanning attack and breach news, vulnerability disclosures, and CISO-level strategy across its 14 topic sections. Free; Dark Reading is part of Informa TechTarget and also offers weekly topical editions.
SecurityWeek Daily Briefing
SecurityWeek (Wired Business Media)
- Free
- Daily
A daily email briefing on cybersecurity threats, breaches, and industry news.
Why CTOs & engineering leaders read it
A daily briefing on threats, breaches and industry news. A second security source, which matters most while the first is still calling something unconfirmed.
More about this newsletter
SecurityWeek's daily briefing collects the day's cybersecurity news: threats, breaches, vulnerabilities, funding, and expert columns, written for practitioners and CISOs. Coverage is trade-press straight rather than alarmist. Best for security professionals and technically minded readers who want a reliable daily industry pulse.
You May Also Like
- Software EngineersThe page below this one: what your engineers do all day, how they are hired and paid, and the craft you are moving further from every year.
- DevOps and SREReliability engineering, incident response and the platform work that decides whether your delivery metrics move, written for the people who own the paved road.
- Product ManagersYour closest counterpart: how roadmaps, discovery and prioritisation actually get decided, which is useful context whenever you are arguing about what engineering should build next.
- Cybersecurity ProfessionalsSecurity as a discipline rather than a quarterly audit, covering threat work, frameworks and the specialists you will hire once exposure becomes a board-level question.
Frequently Asked Questions
Entry-Level
What does an engineering manager or CTO actually do all day?
The day is delivery, people and the system, in whatever proportion the week demands. A first-line engineering manager spends it on one-to-ones, planning and prioritisation with product, hiring, and reading the delivery and incident signals for the thing nobody has escalated yet. A CTO spends it on technical bets, build-versus-buy decisions, security and AI posture, and the executive and board conversations about all of them. The common thread is that almost nothing on your name is work you did yourself, which is the single largest adjustment from senior engineering.
Is engineering leadership a good career in 2026 and beyond?
On the federal numbers, yes. Computer and information systems managers are a 685,800-job occupation with a May 2025 median of $175,140, projected to grow 16 percent from 2025 to 2035 with about 53,500 openings a year, which is much faster than average. The caution sits higher up: chief executives are only 291,600 jobs growing 3 percent, so the seats above director are few and slow to open. The realistic senior path for most people is wider scope and a better-paying sector rather than a title.
Should you move into engineering management or stay on the staff-plus IC track?
Treat it as a choice between two ladders rather than a promotion you accept. Management is wider, better paid at the top, and measured entirely on other people's output. The technical ladder has no single federal occupation code, but its neighbours are substantial jobs: computer and information research scientists at a $140,300 median growing 22 percent to 2035, and computer network architects at $134,050. The question worth answering honestly is which feedback loop you can live with, one measured in quarters or one measured in systems.
What qualifications or degree do you need to become an engineering leader?
The Bureau of Labor Statistics lists a bachelor's degree as the typical entry-level education for computer and information systems managers, usually in a computer-related field, along with substantial prior experience in a technical role. There is no licence and no mandatory credential. Some employers prefer a management or business qualification for senior posts, but the usual qualification is a record of shipped systems and teams that stayed, which is why the route runs through senior engineering rather than around it.
How long does it take to go from senior engineer to engineering manager?
Most people take the first step after roughly four to eight years of engineering, usually via a tech lead role where the accountability for a team's technical direction arrives before the headcount does. There is no fixed clock, because the trigger is organisational: a team grows past the point where one person can hold it. The useful preparation is to take the unglamorous parts early, the hiring loops, the incident reviews, the onboarding of a new joiner, because a panel asks for evidence rather than intent.
What is the difference between a tech lead, an engineering manager and a VP of engineering?
A tech lead still writes code and owns a team's technical direction, without usually owning performance or pay. An engineering manager owns one team's delivery, hiring and growth and is measured on the team's output rather than their own. A VP of engineering owns execution across the whole organisation: the hiring plan, the operating model, the cost base. Between the last two sit senior managers and directors, where the leverage shifts from intervening in work to changing structure.
How do you get your first engineering management job without having managed anyone?
Internally, by taking the work before the title: run the hiring loop, own the incident review, mentor the new joiner, lead the project that crosses two teams. Externally it is harder, so bring evidence rather than enthusiasm. A panel will ask what you would measure in your first ninety days, so have the list ready, and expect to be asked what you will miss about writing code. A candidate who claims they will miss nothing reads as someone who has not thought about it.
Mid-Level
How much do engineering managers, directors and CTOs earn?
The federal anchor is computer and information systems managers at a May 2025 median of $175,140, against $135,980 for software developers, so the step from senior engineer into management is worth roughly $39,000 at the median. Chief executives, which is where company officers including many CTOs are counted, sit at $213,990. Industry moves the number more than most internal promotions do: the same management occupation pays a median of $200,510 in information and $182,510 in finance and insurance.
Which industries pay engineering leaders the most?
For computer and information systems managers, the Bureau of Labor Statistics records the highest medians in information at $200,510, then finance and insurance at $182,510, computer systems design and related services at $179,510, manufacturing at $178,110 and management of companies and enterprises at $176,950, against an overall median of $175,140. The spread between the top and the bottom of that list is larger than many promotions, which is why a sector move is a legitimate career step rather than a sideways one.
How do you measure whether an engineering team is performing well?
Use throughput and instability together. DORA's current model has five metrics: change lead time, deployment frequency and failed deployment recovery time for speed, and change fail rate and deployment rework rate for safety. Top performers do well across all five rather than trading one for the other, so a team whose deploy frequency is rising while its failure rate climbs is borrowing rather than improving. Pair them with retention and developer experience, because people problems show up in the delivery numbers two quarters late.
Should you build an internal developer platform, and how do you know it is working?
By 2025, 90 percent of organisations used an internal developer platform and 76 percent had a dedicated platform team, so the question is usually scope rather than whether. DORA's advice is a minimum viable platform for the single most common workflow, designed so other teams can extend it, and run as a product with real user research. Measure it on a balanced scorecard: lead time, deployment frequency, recovery time, change failure rate and rework alongside adoption and developer satisfaction. Expect a J-curve before the gains.
How should an engineering leader set policy on AI coding tools?
DORA calls this a clear and communicated AI stance, and treats it as one of the capabilities that amplify AI's benefits. The recommended shape is three buckets, prohibited, permitted with guardrails and allowed, written by a cross-functional group with executive sponsorship and published as a living document rather than a legal notice in a wiki. Its purpose is removing uncertainty, because uncertainty produces both excessive caution and quiet use of unvetted tools. DORA found a clear stance turns AI's usually neutral effect on developer friction into a decrease.
How do you decide between a monolith and microservices as an engineering leader?
Start from the deployment coupling you actually have rather than from the architecture you admire. DORA's test is that a service is only loosely coupled if it can be deployed independently of the services it depends on, and many systems described as service-oriented fail it. Architecture should fit scale: a monolith suits a small, fast-changing product, while hundreds of independent teams need decoupled services. Expect team structure to change with it, because a system comes to mirror the communication structure of the organisation that built it.
How do you prepare for an engineering leadership interview?
Expect three families of question. A first-ninety-days question, which needs named measurements rather than intentions. A judgement question about a decision that went wrong, which needs the rule you took from it. And a systems question, usually about platforms, microservices or AI policy, where panels are listening for a scoped answer with a stated test. Bring delivery numbers from your own teams, be ready to say what you would cut as well as what you would fund, and have one honest answer about an underperformer.
Senior-Level
What skills do companies expect from a VP of engineering or CTO in 2026?
Four, roughly. Translation, meaning the ability to put an engineering argument into cost, risk and optionality, which the FinOps Framework's principles describe well: business value drives technology decisions and everyone owns their usage. Governance, meaning a defensible process for which AI and third-party systems reach production. Culture, because DORA links a generative, high-trust culture to both delivery and organisational performance. And architecture judgement, because the structural choices are the ones that outlast every roadmap you will write.
How is AI changing the job of running an engineering organisation?
It moves the job from procurement to platform. DORA's framing is that AI amplifies an organisation's existing strengths and weaknesses: where platform quality is high its effect on organisational performance is strong and positive, and where platform quality is low the effect is negligible. So the defensible answer to a board is the state of testing, review and deployment rather than the number of seats purchased. The second change is evidential: throughput can rise while delivery stability falls, so the two have to be read together.
Should engineering leaders trust AI-generated code, and how should they govern it?
Trust it conditionally and govern it explicitly. Stack Overflow's 2025 survey found 84 percent of developers using or planning to use AI tools but only 32.7 percent trusting the accuracy of the output, with 66 percent naming almost-right answers as their biggest frustration and 45.2 percent saying debugging AI-generated code takes longer. The governance spine most organisations can defend is NIST's AI Risk Management Framework, AI 100-1, with its govern, map, measure and manage functions, plus the Generative AI Profile published in 2024.
How should a CTO handle security and secure development at an organisational level?
Build it in rather than inspect it at the end. DORA cites State of DevOps research finding high performers spend 50 percent less time remediating security issues, because security sits in design, in the pipeline and in everyone's daily work. For structure, NIST's Secure Software Development Framework, SP 800-218, organises practice into four groups: prepare the organisation, protect the software, produce well-secured software and respond to vulnerabilities. NIST is explicit that it is a risk-based starting point rather than a checklist, which is also how a board should hear it.
What career options exist for engineering leaders outside a standard CTO path?
More than the title ladder suggests. Staff-plus individual contribution, where the federal neighbours are computer and information research scientists at $140,300 growing 22 percent and computer network architects at $134,050. Platform, reliability and security leadership, which has the clearest executive case since platform quality now gates AI returns. Plus technical advisory and board work, venture and private equity technical diligence, consulting, and founding. A move between sectors counts too, given the medians run from $175,140 overall to $200,510 in information.
How do engineering leaders keep a technical pipeline when junior hiring has collapsed?
Deliberately, because the market will not supply it. Indeed's Hiring Lab found senior roles at 69.3 percent of software development postings in the first quarter of 2026, against a national mix of about 14 percent senior and 46 percent entry-level, with entry-level postings down 7.5 percent year on year by May 2026. The Hiring Lab also notes that entering during weak hiring can depress wages for up to a decade. Protecting a small, well-supervised junior intake is one of the few decisions only a headcount owner can make.
How do you advance from director to VP of engineering or chief technology officer?
Understand first that the arithmetic is unfavourable: chief executives are 291,600 jobs projected to grow 3 percent to 2035, while the management occupation below is 685,800 jobs growing 16 percent. The seats are few. What distinguishes candidates is external surface, meaning board, customer and partner conversations, plus a profit and loss you have genuinely owned and a technical strategy with falsifiable conditions attached. Scope and sector often pay better than the title does, which is worth weighing before organising a decade around it.
Get Tomorrow's Engineering Leadership Briefing
TLDR's homepage claims more than eight million readers, and Dark Reading is one of the most widely read enterprise-security sites anywhere. If the people you benchmark against already read these, the leaders who do not are the ones caught flat-footed in the next architecture or incident review.