Software Engineer Skills Report — Week of 2026-04-12
Half of all software engineering job postings analyzed this week — 51% of 2,265 listings — require AWS experience. That single number tells you a lot about where the market sits right now: cloud infrastructure fluency isn't a differentiator anymore, it's a baseline expectation. What's more interesting is what sits alongside it.
The Core Stack Employers Are Hiring For
System Design appears in 41% of postings, making it the second most-demanded skill after AWS. This isn't a coincidence. As engineering organizations grow more distributed and infrastructure more complex, employers are screening for engineers who can reason about architecture — not just write functional code. The ability to design scalable, fault-tolerant systems is being treated as a senior-level prerequisite across a wide range of roles, not just staff or principal positions.
Python (31%) and SQL (21%) round out the foundational technical layer. These two have been workhorses of the industry for years, and the data confirms they remain deeply embedded in employer expectations. ETL/ELT appearing in 20% of postings signals continued demand for engineers who can move and transform data — a skill set that bridges software engineering and data engineering roles.
On the frontend and backend language side, TypeScript and JavaScript each appear in 18% of postings, while Go/Golang shows up in 17%. Go's near-parity with TypeScript is notable — its adoption in cloud-native and high-performance backend systems is clearly reflected in what hiring teams are asking for.
Two Signals That Deserve Attention
Cross-functional leadership is showing up earlier in the pipeline than expected. At 29% of postings, this isn't just a Director-level requirement — it's being asked of individual contributors and mid-level engineers. Employers are looking for engineers who can coordinate across product, design, and data teams, not just ship features within one. If your resume doesn't demonstrate some version of this, you're leaving signal on the table.
HIPAA Compliance appears in 25% of postings — a striking figure that reflects how heavily health tech has penetrated software engineering hiring. One in four listings expects familiarity with healthcare data regulations. Engineers without this exposure may find themselves filtered out of a significant portion of the market without realizing it. This is especially relevant for backend and infrastructure roles where data handling is central.
Kubernetes and Machine Learning: Infrastructure and Intelligence
Kubernetes appears in 22% of postings, reinforcing that container orchestration is now a standard skill for engineers working in cloud environments. Machine Learning follows at 16% — meaningful but not dominant. The ML number suggests employers want engineers who can work adjacent to or integrate ML systems, rather than a wholesale demand for ML specialists across all software engineering roles.
Emerging Signals Worth Watching
Beyond the structured taxonomy, several patterns are surfacing in job descriptions that haven't yet been codified into standard skill categories. These emerging signals point to where engineering demand is heading:
- AI-native problem solving and AI-powered personalization engines are appearing in roles that previously wouldn't have touched ML — particularly in marketing technology and product engineering.
- Real-time threat detection systems and SOC analytics are showing up in security-adjacent engineering roles, indicating that security operations is becoming an engineering domain, not just an IT one.
- Cross-channel unified analytics — spanning SMS, RCS, email, and push — reflects the technical complexity behind modern customer engagement platforms, where engineers are expected to reason across multiple data streams simultaneously.
- Cloudflare global network analytics and RCS messaging analytics suggest employers are hiring engineers with experience in edge computing contexts and next-generation messaging infrastructure.
None of these have hit threshold frequency in standard job posting data yet, but their concentration across specific verticals makes them worth tracking closely.
Three Actionable Takeaways
- Get fluent in System Design, not just implementation. With 41% of postings citing it explicitly, the ability to articulate architectural decisions — trade-offs, scalability choices, failure modes — is being tested at interview. Treat it as a primary skill, not an afterthought.
- Understand HIPAA at a working level, even if you're not in health tech yet. One in four postings expects it. A basic working knowledge of how PHI is handled, stored, and transmitted opens a substantial portion of the market that would otherwise screen you out.
- Position cross-functional experience concretely on your resume. Listing "collaborated with stakeholders" isn't enough. Quantify what you coordinated, across which teams, and what shipped as a result. Employers citing this skill at 29% frequency are looking for evidence, not language.