What Is Software Engineering? Definition, Degree and Jobs in 2027
- Knowledge areas the field’s reference guide defines
- 18
- SWEBOK Guide V4
- Bachelor’s programs titled software engineering
- 85
- IPEDS 2024, verified
- Median pay, software developers
- $135,980
- BLS OEWS May 2025
Engineering, Applied to Software
What is software engineering? It is the discipline of designing, building, testing and maintaining software with the methods of engineering. The definition the field’s own reference guide uses is “the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software.”
In plain terms: anyone can write a program, but a program that a bank, a hospital or an airline depends on has to be planned, reviewed, tested and kept working for years by people who did not write it. Software engineering is the body of practice that makes that possible. It covers the whole life of a piece of software, from working out what it must do to retiring it, and coding is one stage of many.
It is also a degree and a job. You can study it as a bachelor’s or master’s, and the people who do it for a living are counted in federal data as software developers. The sections below take each in turn: where the name came from, what the field covers, how it differs from computer science, the degree, and the jobs.
Where the Name Came From
Why is it called engineering at all? The name was a deliberate argument. In 1968, the NATO Science Committee held a working conference on the problems of software in Garmisch, Germany. Large systems were, in one participant’s words, “encountering great difficulties,” and the attendees debated what some of them called the software crisis. In the conference report, the organizers wrote that “The phrase ‘software engineering’ was deliberately chosen as being provocative,” implying that software should be built on the theory and discipline of the established branches of engineering.
That was an aspiration in 1968. Over the 58 years since, it has turned into a profession with its own body of knowledge, curriculum guidelines for degree programs, and accreditation for those programs. The questions the conference raised are still the core of the field: how to say clearly what a system must do, how to design it so it can change, how to know it works, and how to manage the people building it.
What Software Engineering Covers
What does the field actually include? The IEEE Computer Society maintains the Guide to the Software Engineering Body of Knowledge, known as SWEBOK. Its current version divides the field into 18 knowledge areas: 15 areas of software engineering practice, plus 3 foundations it rests on.
Practice (15 areas)
- Software requirements
- Software architecturenew in V4
- Software design
- Software construction
- Software testing
- Software engineering operationsnew in V4
- Software maintenance
- Software configuration management
- Software engineering management
- Software engineering process
- Software engineering models and methods
- Software quality
- Software securitynew in V4
- Software engineering professional practice
- Software engineering economics
Foundations (3 areas)
- Computing foundations
- Mathematical foundations
- Engineering foundations
The computing, math and engineering knowledge the practice areas draw on, the same groundwork every engineering discipline needs.
Two things stand out in that list. First, writing code is one area out of 18: it appears as software construction. Most of the list is about everything around the code, such as requirements, design, testing, maintenance, configuration management, quality and the management of the work. Second, the field keeps moving. The three areas added in the latest version, software architecture, software engineering operations and software security, reflect how software is built now: as large connected systems, under constant security pressure, and run continuously rather than shipped once.
The list even includes economics. Engineering means choosing the solution that works at a cost the project can bear, so the Guide treats cost and trade-off analysis as part of the discipline rather than something left to managers.
The Work, Stage by Stage
What does that look like on a real project? Follow one piece of software from start to finish and most of the knowledge areas show up in order. The stages overlap, and modern teams loop through them in short cycles rather than once, but the work in each stays the same.
Requirements
Before anyone designs anything, the team has to find out what the software must do and agree on it. The SWEBOK Guide breaks this into elicitation, analysis, specification and validation: drawing the needs out of users and other stakeholders, resolving conflicts between them, writing them down precisely, and checking that what was written is what people meant. Mistakes here are the expensive kind, because everything after is built on them.
Architecture and Design
Architecture sets the large structure: the main parts of the system, how they talk to each other, and which qualities, such as speed or security, the structure has to protect. Design works out each part in detail. Good design is mostly about change: arranging the code so a future change touches as little of it as possible.
Construction
This is the coding, along with code review, debugging and the tools that turn source code into running software. It is the stage most people picture, and it is one of 18 areas.
Testing
Testing happens at several levels, each aimed at a different target:
- Unit testing checks each module on its own, apart from the rest of the software; it is often automated, and typically the person who wrote the code runs it.
- Integration testing checks how the modules work together as they are combined.
- System testing checks the behavior of the whole system, and is where qualities such as security, privacy, speed, accuracy and reliability are usually assessed.
Operations and Maintenance
Once software is released, it has to be deployed, monitored and kept running, which is the operations area added in the latest version of the Guide. Then it has to be maintained, often for far longer than it took to build. The Guide lists five standardized categories of maintenance:
- Corrective: repairing problems found after delivery.
- Preventive: fixing latent faults before they occur in the live system.
- Adaptive: keeping the software usable as its environment changes, such as an operating system upgrade.
- Additive: adding new functions or features.
- Perfective: enhancements for users, better documentation and improvements to performance or maintainability.
Running through all of it are the areas that belong to no single stage: configuration management, which tracks every version of every file; project management; process; and quality. On a small team one person may handle all of these in a week. On a large one, each is a job title.
How It Differs From Computer Science
Isn’t this just computer science? The two overlap, but they have different aims. The SWEBOK Guide puts it this way: “Software engineering and computer science are related but distinct in the same way chemical engineering and chemistry are related but distinct.” Computer science studies computation itself and extends what we know about it. Software engineering applies that knowledge to build working systems for real users, within a budget and a schedule.
The degrees reflect the split. The national curriculum guideline for software engineering degrees puts about 50% of its minimum hours into engineering practice: design, testing, requirements, process and quality. A computer science curriculum spends far more of its time on math, algorithms and theory. Software engineering vs. computer science compares the two degrees area by area, with program counts and tuition.
Types of Software Engineering
What kinds of software engineering are there? There are two useful ways to divide it: by the kind of software you build, and by the stage of the work you focus on.
By the kind of software. The titles federal job data files under the same occupation show the main branches:
- Applications. The programs people use directly, from business systems to consumer apps. Titles like Applications Developer and Software Applications Engineer.
- Systems software. Operating systems, compilers, networking and the platforms other software runs on. Titles like Systems Software Developer and Computer Systems Software Engineer.
- Embedded software. Code inside devices such as cars, medical equipment and appliances, often with tight limits on memory, timing and safety. Embedded Systems Software Developer is one of the filed titles.
- Mobile. Apps for phones and tablets. Mobile Applications Developer is filed here too.
- Architecture. Senior engineers who set the structure of large systems. Software Applications Architect and Computer Systems Software Architect are both on the list.
By the stage of the work. Within any of those branches, engineers often specialize in one part of the life cycle: requirements and analysis, architecture and design, construction, testing and quality, or operations, the work of releasing software and keeping it running. On a small team one person covers most of these; on a large one they become separate roles.
Some neighboring jobs are counted separately: quality assurance analysts and testers, web developers, and computer programmers each have their own occupation in federal data. The pay section below shows how they compare.
What Is a Software Engineering Degree?
Can you study software engineering directly? Yes, but it is far less common than computer science. In federal data we list 85 bachelor’s programs titled software engineering, producing about 2,011 graduates a year, and 53 master’s programs. Computer science has about 9 times as many bachelor’s programs.
A software engineering bachelor’s covers the computing and math foundations of any computing degree, then adds the practice areas: software design, verification and validation, process, requirements and professional practice. Accredited programs go further. ABET’s engineering criteria require at least 30 credits of math and basic science, at least 45 credits of engineering topics, and a culminating major engineering design experience. Of the 85 bachelor’s programs, 39 (46%) are ABET-accredited, so accreditation is worth checking program by program rather than assuming.
The software engineering degree requirements guide lists the courses, the math sequence and the credits in detail.
Compare software engineering programs
Every bachelor’s titled software engineering, scored on completion, net price, ABET status and size.
Skills Software Engineers Need
What do you need to be good at? Three kinds of skill, roughly in the order you build them.
Technical skills. Programming comes first: one language well and several adequately. On top of that sit the practice areas accredited programs must cover: computing fundamentals, software design and construction, requirements analysis, security, verification and validation and software engineering processes and tools appropriate for the development of complex software systems. The math is real but specific. ABET’s software criteria name discrete mathematics, probability and statistics, which show up in algorithm analysis, testing and performance work.
Personal qualities. The federal career handbook lists the important qualities for the work as analytical skills, communication skills, creativity, attention to detail, interpersonal skills and problem-solving skills. Two of those are about people, which surprises students who expect a solitary job. Requirements come from conversations, designs get argued over in review, and most code is read by someone other than its author.
Professional judgment. The hardest skill to teach is knowing what not to build: when a simpler design is good enough, when a test is worth writing, when a deadline should move. That judgment comes mostly from experience, which is why degree programs put so much weight on team projects and a final capstone.
Licensing and Ethics
Is a software engineer a licensed engineer? Usually not. In the United States, professional engineering licenses are issued by the states, using exams written by NCEES. NCEES did offer a Principles and Practice of Engineering exam in software engineering, but it discontinued that exam after the April 2019 administration. In five sittings from 2013, it drew 81 candidates in total, in an occupation of about 1.7 million people. A licensed software engineer was always a rarity, and there is now no national exam to become one.
That does not mean the profession has no standards. ABET says accreditation supports entry to a technical profession through licensure, registration and certification, which matters to students who may later work on systems where safety is regulated. And the field has a formal code of ethics.
The Software Engineering Code of Ethics and Professional Practice, published by the IEEE Computer Society and ACM in 1999, sets out eight principles. In the code’s own words:
- Public. Software engineers shall act consistently with the public interest.
- Client and employer. Software engineers shall act in a manner that is in the best interests of their client and employer consistent with the public interest.
- Product. Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.
- Judgment. Software engineers shall maintain integrity and independence in their professional judgment.
- Management. Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance.
- Profession. Software engineers shall advance the integrity and reputation of the profession consistent with the public interest.
- Colleagues. Software engineers shall be fair to and supportive of their colleagues.
- Self. Software engineers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession.
The first principle puts the public ahead of everyone else, and two of the others repeat “consistent with the public interest.” That ordering is the engineering idea at the heart of the field: software that people depend on carries a responsibility to those people, not just to whoever paid for it.
What Software Engineers Earn
What does the work pay? The Bureau of Labor Statistics counts software engineers within the software developers occupation. Its median pay was $135,980 in May 2025, and BLS projects the occupation to grow 10.2% from 2025 to 2035, against 3.5% for all occupations, with about 95,300 openings a year.
| Occupation | Median pay, May 2025 | Projected change, 2025 to 2035 | Openings a year |
|---|---|---|---|
| Software Developers | $135,980 | +10.2% | 95,300 |
| Software Quality Assurance Analysts and Testers | $104,300 | +5.7% | 10,700 |
| Computer Systems Analysts | $105,850 | +7.9% | 32,900 |
| Web Developers | $92,650 | +3.8% | 5,300 |
| Computer Programmers | $100,390 | −7.3% | 4,400 |
BLS Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025-35). Software engineers are counted within software developers.
How do people get in? The typical entry route is a bachelor’s degree, with no prior work experience and no on-the-job training expected, and only 1.5% of software developers are self-employed. This is a field most people enter straight from a degree, as employees.
Where do they work? Among the 24 industries in the federal wage data we pulled, the largest employer by far is computer systems design and related services, with about 515,410 software developers, more than twice the next industry. The top five:
- Computer systems design and related services: 515,410 employed, median $132,050
- Software publishers: 173,080 employed, median $164,550
- Management of companies and enterprises: 103,450 employed, median $135,680
- Computing infrastructure providers, data processing and web hosting: 77,260 employed, median $156,950
- Banks and other credit intermediation: 67,350 employed, median $136,930
Banks and corporate head offices on that list are a reminder that many software engineers never work at a software company. By state, California employs the most, 284,390 or about 17% of the national total, followed by Texas, New York, Washington and Virginia.
Software developers are the largest and best-paid of these occupations. Computer programmers, whose work is narrower and centered on writing code to someone else’s design, are the one group projected to shrink. The software engineer salary guide breaks pay down by state, metro and experience.
Myths, Checked
You’ll often read that software engineering is just a fancy name for coding.
Coding is one of the 18 knowledge areas in the field’s reference guide, where it is called software construction. Requirements, design, testing, maintenance and the rest make up the other 17.
You’ll often read that software engineers are licensed like civil engineers.
The only US licensing exam for software engineering drew 81 candidates in five sittings and was discontinued after April 2019.
You’ll often read that most software engineers studied software engineering.
Computer science bachelor’s programs produce about 21 times as many graduates a year as software engineering programs, so most people with the job title studied computer science.
You’ll often read that software engineering is a solitary job.
The federal career handbook lists communication and interpersonal skills among the important qualities, and the profession’s code of ethics has a principle devoted to colleagues.
Is Software Engineering for You?
Who tends to do well in it? People who like building things that other people use, can stay with a hard problem, and do not mind that most of the job is reading, planning, reviewing and testing rather than writing new code. It is team work: almost nothing large is built by one person.
- You want the most direct route. A software engineering bachelor’s builds design, testing and a team project into the degree. Check ABET status when you compare programs.
- No software engineering program near you. A computer science degree leads to the same jobs. Add electives in software design, testing and requirements, and join a team project.
- You already have a degree in another field. A master’s in software engineering is one route in; check each program’s prerequisites before you apply.
- You want to know what the job is like day to day. The software engineer career guide covers the work, the path in and where the jobs are.
Frequently Asked Questions
What Is Software Engineering in Simple Words?
Software engineering is building software the way engineers build bridges: with a plan, agreed requirements, a design, systematic testing and maintenance for as long as the software is in use. It covers the whole life of a program, not just writing the code.
What Is the Official Definition of Software Engineering?
The international systems and software engineering vocabulary, quoted in the IEEE Computer Society’s SWEBOK Guide, defines it as “the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software.”
What Does a Software Engineer Do?
Software engineers work out what a system must do, design it, write and test the code, release it and keep it running. Day to day that means writing code, reviewing other people’s code, fixing defects and planning changes with a team.
Is Software Engineering the Same as Programming?
No. Programming, or construction, is one of the 18 knowledge areas in the SWEBOK Guide. Software engineering also covers requirements, architecture, design, testing, operations, maintenance, quality, security and the management of the whole process.
What Is a Software Engineering Degree?
A bachelor’s or master’s degree in software engineering itself, as opposed to computer science. We list 85 bachelor’s programs titled software engineering in federal data, and 39 of them are ABET-accredited. About 50% of the national curriculum guideline’s minimum hours go to engineering practice: design, testing, process and requirements.
What Are the Types of Software Engineering?
By the kind of software: applications, systems software, embedded software, mobile apps and web software. By the stage of work: requirements, architecture, design, construction, testing, operations and maintenance. Federal job data files most of these titles under one occupation, software developers.
Do You Need a Degree to Be a Software Engineer?
Usually. Software developers typically need a bachelor’s degree in computer and information technology or a related field, such as engineering or mathematics. Computer science is the most common route: there are about 9 times as many computer science bachelor’s programs as software engineering ones.
Is Software Engineering a Licensed Profession?
Not in the way civil engineering is. NCEES, which writes the US engineering licensing exams, discontinued its Principles and Practice of Engineering exam in software engineering after the April 2019 administration. In five sittings from 2013, it drew 81 candidates in total. The profession does have a code of ethics, published by the IEEE Computer Society and ACM.
Where Do Software Engineers Work?
Everywhere software is built, but the largest employer by far is computer systems design and related services, with about 515,410 software developers, followed by software publishers. California has the most of any state, about 17% of the national total.
What Skills Does a Software Engineer Need?
Programming is the baseline. Beyond it, the work calls for design, testing and requirements skills, the math accredited programs require (discrete mathematics, probability and statistics), and the qualities the federal career handbook lists: analytical skills, communication skills, creativity, attention to detail, interpersonal skills and problem-solving skills.
When Did Software Engineering Start?
The name dates from a 1968 NATO Science Committee conference in Garmisch, Germany. The organizers chose the phrase on purpose, to argue that building software should rest on the theory and discipline of established engineering.
References
Every figure on this page comes from one of these, read by the site’s data scripts and computed at build time, never typed in.
- 1 IEEE Computer Society, Guide to the Software Engineering Body of Knowledge (SWEBOK Guide), Version 4.0 The definition of software engineering, the chemistry analogy, and the 18 knowledge areas, three of them new in Version 4. Verified .
- 2 Naur and Randell (eds.), Software Engineering: Report on a Conference Sponsored by the NATO Science Committee, Garmisch, Germany, 7th to 11th October 1968 Why the phrase “software engineering” was chosen. Verified .
- 3 ACM and IEEE Computer Society, SE2014: Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering The software engineering knowledge areas and their minimum hours, 467 in all. Verified .
- 4 ABET, Criteria for Accrediting Engineering Programs, 2026-2027 (Criterion 5 and the Software program criteria) Curriculum minimums for accredited engineering programs, including software engineering. Verified .
- 5 ABET Accredited Program Search Software engineering bachelor’s programs on ABET’s list. Verified .
- 6 IEEE Computer Society and ACM, Software Engineering Code of Ethics and Professional Practice The eight principles, quoted from the short version. Verified .
- 7 NCEES, NCEES Discontinuing PE Software Engineering Exam The software engineering PE exam: 81 candidates in 5 sittings from 2013, ended after April 2019. Verified .
- 8 ABET, Why ABET Accreditation Matters Accreditation and entry to licensure, registration and certification. Verified .
- 9 BLS, Occupational Outlook Handbook: Software Developers, Quality Assurance Analysts, and Testers (How to Become One) The degree software developers typically need. Verified .
- 10 BLS, Occupational Outlook Handbook: Software Developers, Quality Assurance Analysts, and Testers (Job Outlook and Important Qualities) The important qualities for the work. Verified .
- 11 BLS Occupational Employment and Wage Statistics, May 2025, via api.bls.gov (national industry-specific, state and hourly series) Software developer employment and median pay by industry (24 industries checked). Verified .
- 12 BLS Employment Projections, occupation tables 1.2, 1.10 and 1.12, 2025-35: education and training The typical entry education, experience and training for software developers. Verified .
- 13 BLS, Employment Projections 2025-35: occupation data Projected change and openings, 2025 to 2035, and the job titles filed under each occupation. Verified .
- 14 BLS, Occupational Employment and Wage Statistics, May 2025 Median pay by occupation. Verified .
- 15 NCES IPEDS 2024 programs and completions Programs offered and graduates a year (three-year average). Verified .