Web Developer and Software Engineer can use the same languages, the same cloud platform and even the same code repository. The occupational difference appears when you ask a harder question: what system boundary and engineering responsibility does the work actually show? In a Web Developer versus Software Engineer ACS comparison, ask whether the documented work primarily concerns website delivery or broader software-system design, engineering and maintenance.
ACS currently describes Web Developer 261212 around planning, producing and maintaining websites using web programming languages, applications, technologies and databases. Software Engineer 261313 is described more broadly around designing, developing, modifying, documenting, testing, implementing, installing and supporting software applications and systems. See the current ACS IT occupation descriptions.
That does not mean “small website = Web Developer” and “complex website = Software Engineer”. Complexity matters, but scope and professional accountability matter more.
The broader occupation-mapping principle is that duties matter more than titles in an ACS assessment.
Boundary 1: what is the primary product?
A Web Developer profile becomes clearer when the professional output is a website or web application as the central product: its web functionality, interfaces, integrations, content or browser-facing behaviour, hosting and continuity.
A Software Engineer profile becomes clearer when the applicant’s responsibility extends across software systems or application architecture: system needs, component design, application behaviour, technical limitations, broader integration, engineering quality and lifecycle decisions.
A sophisticated SaaS product can be delivered through a browser and still involve software-engineering work. “It runs on the web” is not enough to make 261212 the automatic answer.
Boundary 2: what decisions are you trusted to make?
The strongest occupational signal often sits in the decisions, not the languages.
Web Developer signals
- selecting or implementing web-specific development approaches;
- building and maintaining website or web-application functionality;
- integrating web code with content, media, databases or web services;
- working with hosting, web server, access, backup or continuity concerns;
- maintaining a web property as the primary system boundary.
Software Engineer signals
- analysing broader software or system needs and limitations;
- making or owning software-design decisions across components;
- defining technical behaviour beyond one website layer;
- engineering testing, reliability, performance or maintainability across an application or system;
- producing or implementing technical specifications in a wider software lifecycle.
These are signals, not a substitute for the full ACS description.
Boundary 3: if the browser disappeared, would the occupation story survive?
This is a useful thought experiment.
If most of the role still makes sense because you are engineering services, domain logic, distributed components, application architecture and broader system behaviour, Software Engineer deserves close comparison.
If the role is fundamentally defined by building and maintaining the website or web application — even with substantial backend code — Web Developer may remain coherent.
The test is imperfect, but it stops “frontend = Web Developer, backend = Software Engineer” thinking.
Three examples where the title can mislead
Example 1: senior frontend engineer on a product platform
The person owns component architecture, state management, performance budgets, automated testing, design-system infrastructure and integrations across a large product. Although the work is frontend-heavy, the evidence may show software-engineering responsibility rather than ordinary website production.
Example 2: backend-heavy web developer
The person builds server-side features, database integrations and APIs for a group of websites, manages web deployment and resolves hosting/security issues. The work is technical and backend-heavy, but the professional boundary is still web development.
Example 3: agency “software engineer”
The employer uses Software Engineer as the title, but the work is mostly building client websites, CMS themes, web integrations, landing pages and ongoing site maintenance. The title alone should not control the ACS occupation choice.
The employer reference has to reveal the boundary
A generic reference saying “developed, maintained and tested applications” can be compatible with both occupations and therefore proves little about the distinction.
A useful reference should make visible:
- what kind of system or product the person worked on;
- the scale and boundaries of responsibility;
- what design or implementation decisions belonged to the applicant;
- what technical outputs were produced;
- how testing, integration, reliability or maintenance fit the role.
Do not copy ACS duty wording into the letter. ACS explicitly tells applicants to select skills they have actually demonstrated and assesses the evidence against the nominated occupation.
If the evidence genuinely supports more than one code, decide whether nominating multiple ACS occupations adds clarity or only more ambiguity.
Where Full-Stack Developer fits
If your actual title is Full-Stack Developer and Developer Programmer is also a plausible option, widen the comparison beyond this two-code question. Here, the focus remains narrow: 261212 or 261313?
RPL makes vague occupation mapping harder to hide
For RPL applicants, the project reports add another layer of evidence. Two reports focused almost entirely on website content, CMS behaviour and web maintenance can weaken a Software Engineer narrative. Two reports showing broader software architecture, system constraints and engineering decisions can create a different picture.
The project report should not be rewritten to fit the code. The code should be chosen after the project and employment evidence show what the career actually is.
RPL applicants should also confirm whether RPL or the General Skills Assessment is the right ACS pathway for their qualification and experience profile.
A five-question final check
Before choosing between Web Developer and Software Engineer, ask:
- Is my primary professional product a website/web application, or a broader software system?
- What design and engineering decisions am I personally accountable for?
- Are my most important responsibilities web-specific or system-wide?
- Would my employer reference make the same occupation clear without my job title?
- Do my projects and recent work reinforce that same professional identity?
The safer ACS occupation is the one your evidence explains naturally. Technology stack is context. Professional scope is the deciding story.
Web work spans more than one occupational function
A company may call its engineer a ‘Web Developer’ while the person spends most of the week designing distributed backend services. Another employee with the title ‘Software Engineer’ may primarily implement content-driven websites and maintain front-end templates. Occupation mapping should not follow titles mechanically. Compare the kinds of systems built, degree of software design, development lifecycle ownership and whether web delivery is the main purpose of the role. An application with a browser interface is not automatically web-development work in the occupational sense; nearly every modern software platform has a web component.
Consider two projects with similar tools but different responsibilities
Project A involves improving a small business website, integrating forms and maintaining content and front-end behavior. Project B involves designing transaction processing, defining service interfaces, developing persistence logic and engineering deployment safeguards for a complex application. Both might use JavaScript, Git and automated tests, yet the central occupational activity differs. Describe what the employee was responsible for delivering and how architectural decisions were made. If a role spans both examples, make the split visible over time rather than highlighting only the part aligned to a desired ANZSCO number.
Avoid manufacturing an occupation from keywords
Job descriptions stuffed with terms such as ‘software architecture’, ‘web solutions’ and ‘enterprise design’ are often less credible than ordinary descriptions of genuine work. Explain how requirements arrived, what technical problem the employee solved, which code or components they owned and how successful delivery was established. Assessing authorities may look beyond employment references to education and relevant professional history. Check the ACS requirements and the government occupation list for the applicable assessment and visa context rather than extrapolating from marketing job titles.
Separate current occupation from an entire career
A senior professional might have begun as a website implementer and later shifted to full-stack product engineering. Those periods may merit different descriptions in a skills assessment, even with the same employer. Ask what changed in the technical decision-making, codebase responsibilities and level of autonomy. If the nominated occupation better matches only recent work, do not silently assign it to every early career year. A timeline with role-specific evidence may be more persuasive than a single generic five-year software-developer reference.
Read the official ICT occupations at ACS code information before mapping a software title to an ANZSCO code. The ACS supporting evidence standards govern the employment narrative, and assessment pathways helps determine which ACS pathway is actually being used to assess that work.
