A full-stack technology stack tells ACS what tools you use. It does not, by itself, tell ACS what occupation you perform. For a Full-Stack Developer ACS occupation decision, catalogue the deliverables and system responsibilities you owned instead of relying on a long list of front-end and back-end languages.
React, TypeScript, Node.js, Python, Java, .NET, PostgreSQL, AWS and Docker can appear in several professional ICT occupations. Two people can use almost the same stack and still have different responsibility, scope and evidence. That is why “I am a full-stack developer” is the beginning of occupation mapping, not the conclusion.
The current ACS IT occupation descriptions assess occupations by professional function and duties. For many full-stack careers, three codes deserve an evidence-led comparison: Web Developer 261212, Developer Programmer 261312 and Software Engineer 261313.
Start with the product boundary, not the framework list
A useful first question is: what are you professionally responsible for producing and maintaining?
A career can lean toward Web Developer when the work is primarily the planning, production and maintenance of websites or web applications, including web programming, web integration and web-specific operational concerns.
A career can lean toward Developer Programmer when the centre of gravity is translating specifications or designs into program code, testing and debugging that code, and maintaining applications at the program level.
A career can lean toward Software Engineer when the evidence shows broader responsibility for software-system needs, design, engineering decisions, complex implementation, quality and the behaviour of applications or systems beyond one website layer.
These are not prestige levels. They are different occupational stories.
The five-part full-stack occupation audit
1. Remove the job title
Write down the recurring duties from a normal month without using “full-stack developer”, “software engineer” or an ANZSCO title. If the occupation becomes impossible to identify once the title disappears, the evidence may be title-led rather than duty-led.
A useful companion rule is to understand why duties matter more than titles in an ACS assessment.
2. Separate tools from responsibility
“Used React, Node and AWS” is a technology inventory. It does not explain what you owned.
A stronger duty description answers questions such as:
- Did you design the application structure or mainly implement existing specifications?
- Were you responsible for a website/web application as a defined product boundary?
- Did you evaluate system limitations and make engineering trade-offs?
- Did you own testing strategy, reliability, integration or performance decisions?
- Were you maintaining program code under defined technical specifications?
3. Identify the dominant work across each employment period
A career does not have to be one occupation forever. A developer may begin in website production, move into application programming and later take broader software-engineering responsibility. Map each employment period separately before trying to force one code across the whole CV.
A simple duty ledger can help. For each major duty, record frequency, responsibility level, output and evidence. A weekly architecture decision with real accountability can carry more occupational signal than an occasional task that merely contains a fashionable technology name.
4. Check whether the employer reference can prove the choice
The occupation is only useful if your documents can support it. An employment reference that says “developed full-stack applications” is too compressed to show the boundary.
For a Web Developer direction, the reference should make the web product context visible. For a Developer Programmer direction, the program-code and specification relationship should be clear. For Software Engineer, the reference should show the broader system or engineering responsibility rather than just a longer list of languages.
ACS warns applicants to choose skills they have actually demonstrated and assesses whether education and/or work experience is at a professional ICT level and closely related to the nominated occupation. See the current ACS occupation guidance.
Three full-stack careers that should not be mapped the same way
Scenario A: commerce website specialist
The developer owns a large e-commerce web application. Most work concerns browser-facing functionality, server-side web features, CMS integration, web performance, hosting, web security and ongoing website maintenance. The developer writes substantial code, but the professional boundary remains the web application.
Web Developer deserves serious comparison here.
Scenario B: application programmer working from specifications
The developer receives functional and technical specifications, builds application modules, writes and maintains code, tests and debugs programs, and implements changes within an established architecture. The person is highly technical, but the evidence centres on program implementation rather than broad software-system design ownership.
Developer Programmer may be the better comparison.
For backend-focused work, mapping a Backend Developer role to ACS can require a separate evidence test.
Scenario C: product-platform engineer
The developer works across frontend and backend services but also owns service boundaries, integration choices, performance trade-offs, testing architecture, failure handling and broader application design. The web interface is only one part of the system.
Software Engineer becomes a stronger direction to investigate.
The stack can be identical across all three scenarios. The responsibility is not.
Full-stack does not mean you should nominate every plausible code
ACS currently allows applicants to choose up to three occupations in a migration skills assessment. That allowance should not be used as a substitute for occupation analysis. If more than one code is genuinely supportable, assess whether nominating multiple ACS occupations makes sense before submission.
If the more basic question is which ACS assessment pathway fits your profile, compare RPL with the General Skills Assessment before building the occupation strategy.
For this page, the rule is simpler: first decide which code the career supports most clearly. Add another code only when there is a substantial, separately provable professional pattern behind it.
RPL applicants should map the occupation before choosing projects
For an RPL application, project choice can magnify an occupational mismatch. If the nominated occupation is Software Engineer but both projects are mostly CMS configuration and interface maintenance, the reports may create a different occupational impression. If the career is genuinely Web Developer, there is no benefit in inflating the projects with enterprise-architecture language.
The project reports should expose the ICT knowledge that actually sits inside the nominated professional function. Occupation mapping therefore comes before project polishing.
A final evidence-first decision rule
Before selecting the ANZSCO code, ask four questions:
- What professional output dominates my recent career?
- What decisions am I personally accountable for?
- Which ACS occupation description requires the least rewriting of my real duties?
- Can my employment references and project evidence support that choice consistently?
A full-stack developer can be a strong ACS applicant under more than one plausible occupation. The defensible choice is not the code associated with the most impressive title. It is the code that the work, responsibility and documents already describe.
Full-stack is a work style, not an occupation code
A developer can build browser interfaces, APIs, databases and deployment pipelines without having an occupational label that simply reads ‘Full-Stack Developer’ in the relevant assessment framework. The challenge is to identify the central purpose of the role. Is the person primarily designing and developing software systems, working on web-specific applications, or performing a different specialist function? Examine projects over the entire claimed period, not just the latest sprint. A title chosen by a recruiter is useful background but the duties, complexity and outputs carry more weight for occupation mapping. The ACS General Skills guidance helps frame the evidentiary task.
Analyze the application’s center of gravity
Imagine a developer responsible for a React storefront, a Node.js ordering API, PostgreSQL data models and the release pipeline. If most responsibilities concerned the complete business application—data integrity, service orchestration, performance and production change—the occupational analysis may differ from a role almost entirely devoted to presentation-layer websites. Avoid the false equation that using React proves a web occupation or that using Java proves a software-engineering occupation. Assess the scale of system design, nature of technical decisions and the proportion of time spent across activities. The working title can remain ‘full-stack’ on the CV while the nominated occupation reflects the underlying work.
How to record blended duties credibly
A reference letter could describe three substantive project phases: implementing customer-facing components, designing backend services and operating production releases. Within each phase, indicate dates, accountability and outcomes. If team leadership emerged later, explain how hands-on development responsibilities changed. Avoid inserting every technology in the company’s stack if the employee never used it. A concise inventory of personally delivered features, testing responsibilities and design decisions will outperform a long list of brand names. Cross-check occupational eligibility against the official skilled occupation list independently of the skills assessment outcome.
Even a convincingly described full-stack project still needs a compliant employment reference under ACS employment-reference standard. Paid-work claims should reconcile with ACS payment documentation; where formal ICT qualifications are not suitable, RPL assessment alternative describes a distinct RPL route and its own conditions.
