Software Engineer · Writes, tests and maintains the code that runs modern life — and is one of the first professions watching AI automate its own daily work.
Darker cells mean a higher score for this topic on that metric.
LessMore
Last reviewed Sources & creditsMedia creditsMethodology
Most days split between writing new code, reading other people's code during review, fixing bugs, and talking to teammates about what to build next. Meetings, planning and mentoring take up more time than newcomers expect. A senior engineer often writes less code personally than a junior one, spending more time on design decisions, reviews and unblocking others.
No, but it remains the most common and lowest-friction route. A four-year degree teaches algorithms, data structures and systems concepts that are expensive to learn on the job. Bootcamp graduates and self-taught engineers do get hired, especially by smaller companies, but usually need a strong portfolio or open-source work to substitute for the credential.
Parts of it already are. Tools built into modern code editors now write a large share of routine code — boilerplate, first-draft tests, translations between languages — for engineers who use them regularly. What is much harder to automate is deciding what to build, why, and how a system should be shaped so it survives contact with real users and failure.
It varies enormously by country and company. In the United States the median is around $133,000 a year; in Germany roughly €69,000; in India, where the industry employs the most people, a national average is closer to ₹900,000. Senior and staff engineers at large technology companies can earn several times the national median once stock compensation is included.
In practice, little — the titles overlap and companies use them inconsistently. 'Programmer' is the oldest term and emphasises writing code; 'developer' is common in web and product companies; 'software engineer' leans on the idea of applying disciplined process, testing and design, borrowed from older engineering fields, to building software. Job descriptions rarely distinguish them consistently.
At most established technology companies, yes: a live or take-home technical interview, often involving algorithm problems on a shared document or whiteboard, remains the standard filter, alongside a system-design round for more senior roles. Smaller companies and startups are more likely to substitute a paid trial project, a portfolio review, or a conversation about past work.
How society sees the software engineer has swung between clerical and glamorous more than once. Early programming was coded, quite literally, as women's work — detail-oriented and low-status, like typing — before the same job was rebranded as a high-status, world-changing pursuit once the money and power involved became obvious.
That whiplash still shows up in the culture: hacker mythology and Silicon Valley wealth on one side, basement-dwelling IT-support comedy on the other, and a real, well-documented drop in the share of women in the field since the 1980s in between.
How much status the profession carried in each era, on a 0–100 scale.
Programming was widely seen as clerical support work, comparable to typing, and was disproportionately staffed by women for exactly that reason; a widely read 1967 magazine article pitched it as a career suited to people who were good at planning a dinner party.
The 'software crisis' narrative around the 1968 NATO conference made clear how expensive and difficult good programming actually was, slowly raising the field's standing among engineers and managers even as pay stayed modest outside a few specialist firms.
Personal computing created its first celebrity engineers and self-made millionaires — Gates, Jobs, Wozniak — and hacker culture gained a countercultural cool, even as the broader public image stayed closer to the socially awkward nerd stereotype.
Google, Facebook and their peers made 'software engineer' one of the most sought-after graduate jobs in the world, with campuses designed to be aspirational workplaces and stock compensation that created real wealth well below the executive level.
Status has cooled from its peak: repeated rounds of layoffs at major technology companies, a tougher entry-level hiring market, and public skepticism about the industry's social effects have all landed on a profession that spent the 2010s feeling untouchable.
Dramatizes the founding of Facebook and the lawsuits that followed; less about code than about the ambition and betrayal of the people who write it, but hugely influential in shaping the public image of the founder-engineer.
A satirical HBO comedy about a startup building a compression algorithm, mocking pitch decks, brogrammer culture and big-tech excess with enough specificity that many engineers treated it as a documentary.
A British sitcom set in a fictional company's basement IT department, built around the gap between how technical staff see themselves and how the rest of the office treats them.
A drama following hardware and software engineers through the PC clone wars, the online-services era and the early web, praised by many working engineers for how accurately it renders the feel of the work.
Follows Black women mathematicians at NASA, including Dorothy Vaughan teaching herself and her team FORTRAN to keep their jobs as the agency installs an IBM mainframe — a direct dramatization of the human-computer-to-programmer transition.
A German thriller about a young hacker collective, built around genuinely researched hacking and social-engineering techniques rather than Hollywood's usual fictional interfaces.
A live or virtual session solving algorithm problems on a whiteboard or shared document under time pressure — a genuine rite of passage into the profession that most working engineers have opinions about and few defend as pleasant.
A team builds a working prototype in a single overnight or 48-hour push, fueled by free food and branded T-shirts, then demos it to judges; equal parts bonding ritual, recruiting tool and genuine occasion for fast, scrappy learning.
Being added to a service's on-call rotation — literally a pager in the 1990s, now a phone app that can wake someone at 3 a.m. — marks the moment a company trusts an engineer with a production system's failures, not just its features.
None of this settles whether software engineering is really 'engineering' in the old sense, a craft, or something new that borrowed the name for credibility. The field itself has never fully agreed, and the argument shows up again in the debate over its own legends.
What has changed least is the gap between the job's image and its daily reality: neither the lone hacker genius nor the buttoned-up engineer in a hard hat looks much like a person reading a stack trace at 11 p.m., which is where most of the actual work happens.
Closest neighbours on the six-score profile — not the same field only.
Finds patterns and builds predictive models from data — a 2008 job title built on three centuries of counting, testing and visualizing evidence.
AI-resistant 38 📦Builds the systems that train, deploy, monitor and govern machine-learning models in production.
AI-resistant 54 🗺️Decides what a company should build next, and why — turning customer needs, business goals and engineering limits into one shared plan nobody else fully owns.
AI-resistant 50 🔐Protects systems, data and people by finding, preventing and responding to digital attacks.
AI-resistant 63 🌿Leads the strategy, measurement and reporting that helps organizations reduce environmental and social harm while meeting business obligations.
AI-resistant 66 🧾The keeper of the books: heir to a craft so old it invented writing itself, now negotiating with the software built to automate it.
AI-resistant 35Designs and tests the algorithms behind machine intelligence, in a field now racing to automate a growing share of its own research process.
AI-resistant 50 🛰️Designs, analyzes and certifies the aircraft, rockets and spacecraft that leave the ground, working to safety margins that leave no room for guessing.
AI-resistant 74 🌉The profession that turns rivers, rock and gravity into bridges, roads and clean water — civilization's quiet load-bearing trade since Imhotep.
AI-resistant 72 🔌Designs and fabricates the transistors inside every computer, phone and weapon, using machines precise enough that only a few factories on Earth can run them.
AI-resistant 60 🦾Designs the machines that sense, decide and act in the physical world, where the hard problem was never intelligence but the world itself.
AI-resistant 65 🔐Protects systems, data and people by finding, preventing and responding to digital attacks.
AI-resistant 63 📦Builds the systems that train, deploy, monitor and govern machine-learning models in production.
AI-resistant 54 🌬️Designs, builds and improves wind, solar, storage and grid systems that turn renewable resources into dependable electricity.
AI-resistant 72