Engineering has been the engine of tech hiring for a decade. The latest data shows that engine idling. Openings have stopped growing, U.S. hiring is well below its peak, and inside engineering the mix of roles is shifting fast. For tech companies, the question for 2027 is less "how many engineers" and more "which kind".
This article reads the engineering numbers in Lenny Rachitsky's State of the tech job market: late 2026 and turns them into decisions for CTOs, engineering leaders and talent acquisition teams. Our view: tech companies should plan engineering by capability rather than by technology silo, and update their job architecture before they write another specialist requisition. It expands one part of our guide to the tech job market in 2027.
What the data shows
The report uses global openings at more than 9,000 tech companies (TrueUp) and U.S. hiring data (Live Data Technologies).
| Signal | Number | Scope |
|---|---|---|
| Growth in open engineering roles | 29% through 2024, 15% through 2025, 2.5% over the past year | Global openings |
| Software engineers hired | About 113,000 in the 12 months to April 2026, less than half the 2022 peak of 239,000 | U.S. hires |
| Engineers hired in 2025 | More than 120,000 | U.S. hires |
| Open engineering roles | More than 65,000 | As counted in the report |
| Mobile and front-end demand | Nearly halved in the past year | Openings |
| Forward deployed engineer (FDE) openings | Up 4.6x in a year, to about 1,500 | Global openings |
| Security engineering | One of the fastest-growing specialties, right behind FDE | Openings |
For the first time in the history of the report, engineering openings have stalled. But the absolute numbers remain large: engineering is still the biggest category of tech hiring by far.
What is driving the shift
The report's author explains the mobile and front-end decline as "the collapse of specialized/siloed engineering disciplines, with smaller eng teams having broader ownership (thanks to AI)."
The job description data supports that reading. Python has been the most-mentioned engineering skill for years and is still growing. "LLM" has just passed Java in engineering postings, Java is declining, and Kubernetes is holding its ground. The pattern: general-purpose and AI skills up, narrow language specialisms down, core infrastructure steady.
Two growing roles fit the same story:
- Forward deployed engineers work directly with customers to make a product work in their environment. The author notes that part of the 4.6x growth is likely other roles, such as sales engineer, being renamed FDE. Either way, companies want engineers who combine building with customer-facing problem solving.
- Security engineers are in demand as AI features and broader access raise the stakes of mistakes.
What this means for your engineering roles
Review specialist requisitions first
If your 2027 plan includes requisitions defined by a single platform, such as "iOS engineer" or "front-end engineer", ask whether the work really needs a specialist or whether a product engineer who can work across the stack would serve better. We expect fewer narrow specialist requisitions in 2027 and broader scope in the roles that remain.
This does not mean specialists have no future. Complex mobile apps, design systems and performance-critical front ends still need deep expertise. The point is to decide deliberately, role by role.
Update the job architecture
Most engineering career frameworks were written when teams were organised by platform. A framework for 2027 might organise around capabilities instead:
| Capability | What it looks like in practice |
|---|---|
| Product engineering | Takes a feature from spec to production across front end, back end and data |
| Platform and infrastructure | Keeps systems reliable, secure and cost-efficient |
| AI engineering | Builds, evaluates and maintains features that use LLMs |
| Customer-facing engineering | Deploys and adapts the product for specific customers |
| Security | Protects systems, data and AI features |
Each engineer has a primary capability and growing breadth in others. Requisitions then describe the capability and the level, not just the language.
Decide between reskilling and rehiring
If you have mobile or front-end specialists whose work is shrinking, retraining them as product engineers can be faster than hiring, because they already know your product, codebase and customers. Plan it explicitly: a learning budget, a mentor, a first cross-stack project and a review after a quarter.
Hire externally where you need capability you do not have. For many tech companies in 2027, that will be AI engineering, as "LLM" climbs the engineering skill rankings, and security, one of the fastest-growing specialties in the report.
How to hire for broader engineering roles
Broader roles make screening harder. Keyword matches on a language or framework tell you less when the job spans several. Three adjustments help:
- Write outcomes in the job description. For example: "has owned a feature end to end, including the API, the interface and the monitoring after launch."
- Use a work sample that crosses layers. A short task that touches both back end and front end, or a code review across the stack, shows breadth better than a single-language test.
- Score judgment about AI tools. Ask candidates to complete part of the task with AI assistance and score how they check the output, not how quickly they produce it.
Our guide to assessing tech candidates when every CV says LLM covers assessment design in more depth.
What this means for APAC engineering teams
The report's hiring numbers are U.S. figures; its openings data covers tech companies globally. It has no breakdown for Singapore, Malaysia, Indonesia or Hong Kong. The cause the author points to, AI letting smaller teams own more, does not depend on location, so we expect the same shift in role mix to reach regional engineering teams.
Engineering talent pools also differ in size from city to city across the region. A broad product engineer role may fill quickly in one city and slowly in another. To check, track your engineering requisitions over the past four quarters by city, and the share that were defined by a single platform. If specialist roles stay open longer, that is a sign to broaden them.
Explain engineering headcount to leadership
Flat engineering openings make a convenient headline for finance teams: hire less. The data supports a more precise message. Engineering is still the largest category of tech hiring, and the report's author notes that open recruiter roles are rising sharply, which may be a leading indicator that engineering hiring picks up again. A useful way to present your 2027 plan:
- Fewer specialist roles, with the roles you will broaden or not refill.
- Targeted new capability, such as AI engineering and security, with the business reason for each.
- Reskilling, with the number of engineers moving into broader roles and the cost of the programme.
- A trigger for hiring more, such as a product launch or a customer commitment, so the plan can scale quickly if demand returns.
This turns "flat headcount" into a plan for a different kind of team.
FDE and security roles: hire carefully
Rising roles attract rebranded titles. Before opening an FDE or security requisition, define the work:
- For FDE roles: what share of time is spent building versus in customer meetings? Who owns the customer relationship?
- For security roles: application security, cloud security or AI security? Each needs a different profile.
Clear definitions prevent a requisition that attracts everyone with the title and few with the skills. Agree the definition with the hiring manager and write it into the first paragraph of the job description, so candidates can judge the fit before they apply.
Next step
List every engineering requisition in your 2027 plan and tag each one as specialist or broad. For each specialist role, write one sentence on why it cannot be broader. Then decide where you will reskill and where you will hire. For the full picture of the 2027 tech job market, read our guide to the tech job market in 2027. For finding engineers who are not applying, see sourcing automation software.

Author
Moka AI Editorial Team
The Moka AI Editorial Team creates insightful, practical, and engaging content on HR, recruitment, and AI innovation. We explore emerging trends, share industry insights, and turn complex ideas into actionable knowledge to help HR professionals navigate the evolving world of work.



