You can write faultless production code and still fail your ACS skills assessment software engineer application, because the assessor never sees your code. They read your employment reference letters, and the most common reason a 261313 application is knocked back is a reference that describes testing, support, or spec-following work instead of the end-to-end software design that ANZSCO 261313 actually requires. This guide maps the real thresholds, the code boundaries, and the reference-letter language that passes, so you can self-audit before you lodge.
What ANZSCO 261313 covers and when to use a different code
ANZSCO defines Software Engineer 261313 as an occupation that "designs, develops, modifies, documents, tests, implements, installs and supports software applications and systems." Read that list as a lifecycle, not a menu you can pick one item from. ACS wants evidence that you own the arc from a design decision to a running system, not that you touched a single stage of someone else's plan.
The phrase that trips people up is "installs and supports." In a reference letter, that has to mean supporting software you helped build, not administering servers or staffing a help desk. If your duties read as infrastructure or end-user support, an assessor will push you toward a different unit group before they consider your qualifying experience.
Software Engineer vs Developer Programmer 261312: where each role sits
First, a correction worth making up front: 261312 is Developer Programmer, not Analyst Programmer. Analyst Programmer is 261311, a distinction several competitor guides get wrong. ANZSCO describes the Developer Programmer as someone who "interprets specifications, technical designs and flow charts, builds, maintains and modifies the code for software applications, constructs technical specifications from a business functional model, and tests and writes technical documentation."
Who owns the design is the whole game. A Developer Programmer builds from specifications that already exist; a Software Engineer produces those specifications and the architecture behind them. If your letter shows you receiving designs and turning them into code, that reads as 261312. If it shows you deciding the structure, the interfaces, and the system behaviour, that reads as 261313.
The full unit group 2613 boundary, which no current SERP page operationalises:
Code | Occupation | Distinguishing task criterion |
|---|---|---|
261311 | Analyst Programmer | Analyses user needs, produces requirements documentation, then encodes and tests: requirements-to-code scope |
261312 | Developer Programmer | Interprets existing specs, flowcharts and designs, then builds and modifies application code: spec-to-code scope |
261313 | Software Engineer | Designs, develops, installs and supports whole systems end to end: broadest architectural and lifecycle scope |
261314 | Software Tester | Writes test plans and scripts, produces test cases, runs regression tests, logs defects: test-only scope |
Software Engineer vs Software Tester 261314: the duty overlap that causes rejections
Every software engineer tests their own work, and the 261313 duty statement even lists "tests" explicitly, so the overlap with 261314 feels harmless. It is not. ANZSCO defines Software Tester 261314 around writing test plans and scripts, producing test cases, running regression testing, using automated test tools, and documenting results in defect reports.
The assessor applies a straightforward filter: does the reference show you designing and building software that you also test, or does it show you testing software other people built? A letter that describes only test execution, defect logging, and QA sign-off maps cleanly to 261314, and it is the most documented rejection trigger for people who nominate 261313. Where testing is genuinely a slice of a broader design-and-build role, make sure the design-and-build duties lead the letter and the testing sits where it belongs, as one task among several.
Check your eligibility before you pay the ACS fee
Every ACS skills assessment software engineer candidate is routed through one of two pathways, each carrying its own fee. The General Skills pathway costs AUD $1,498 excluding GST, and the RPL pathway costs AUD $625 excluding GST, both effective 3 November 2025. Confirm the live rate on acs.org.au or on our ACS fee 2026 guide before you pay. Which pathway you belong in comes down to your qualification, not your confidence, so work that out first.
Formal qualifications pathway: what ACS means by an ICT-major degree
The General Skills pathway is for applicants with a recognised tertiary ICT qualification. "ICT-major" means a Bachelor's degree or higher where ICT content dominates the program, and "closely related" means that major aligns with the 261313 occupation you are nominating. That closely-related status drives your experience requirement, and almost no competitor page tells you this.
An ICT-major degree closely related to Software Engineer needs 2 years of work in the last 10 years, or 4 years at any point. An ICT-major degree that is not closely related needs 4 years at any point. An IT-minor degree closely related to the role needs 5 years in the last 10, or 6 years at any point. The matrix below is the artifact worth screenshotting before you lodge:
Qualification | Closely related to 261313? | Experience (last 10 yrs) | Experience (anytime) | Pathway |
|---|---|---|---|---|
ICT-major Bachelor's or higher | Yes | 2 years | 4 years | General Skills |
ICT-major Bachelor's or higher | No | not applicable | 4 years | General Skills |
IT-minor Bachelor's or higher | Yes | 5 years | 6 years | General Skills |
No degree or trade certificate | not applicable | not applicable | 6 years | RPL |
RPL pathway: experience thresholds for non-ICT degree holders and applicants with no degree
The RPL pathway exists for people without an ICT-major tertiary qualification. ACS requires 6 years of relevant ICT work for applicants with no degree or a trade certificate. For applicants who hold a non-ICT degree but want to claim their experience under RPL rather than General Skills, the operative threshold depends on how ACS classifies the qualification; in practice, most non-ICT degree holders with 4 or more years of closely related experience are directed to the General Skills route once their degree is assessed, with RPL applying where a qualification falls outside ICT entirely. If your degree sits in an ambiguous field, confirm your pathway before paying.
There is a recency rule that catches applicants off guard: your most recent work experience must be active or fall within the 2 years before you submit. Six strong years mean nothing if your last ICT role ended three years ago; you need to re-enter ICT work before the RPL route reopens. All experience must run at a minimum of 20 hours per week. Our pathways explained page walks the RPL knowledge areas in more depth.
Work experience ACS accepts as closely related to 261313 duties
ACS counts only professional ICT employment undertaken from age 18 onward, at 20 hours a week or more, with duties that align to the 261313 task list. Claiming years spent in support, systems administration, or QA-only roles is a common misjudgement; those hours are real work, but they map to other codes and dilute the design-and-development picture the assessor is looking for. Claim the years where you were building software, and describe them in the language of the duty statement.
Prepare your documents in the format ACS actually accepts
Most rejections come down to paperwork that fails a stated format rule. ACS enforces those rules mechanically, the way a compiler rejects a type mismatch without caring how good your intent was.
Academic transcripts: originals, certified copies, and translation rules
ACS is specific about scans. Transcripts and award certificates must be high-quality colour scans at a minimum of 300 dpi, consolidated into one PDF per qualification, with every edge of the page visible and the completion date clearly identifiable. A cropped corner or a missing completion date is grounds for rejection on its own. Documents not in English need a certified translation alongside the original, and if you hold a postgraduate degree, you must also submit your undergraduate qualification documents. The full list lives on our eligibility and documents guide.
Employment references: the fields ACS requires for every position you claim
Every position you claim needs a reference carrying a fixed set of fields, and a letter missing any one of them is a documented rejection trigger. On company letterhead, the reference must state your full name as it appears on your other documents, your job title, your start and end dates, your employment type, your hours per week (at or above 20), the city and country of the role, and a description of your ICT duties naming the actual tools and technologies you worked with. It must then close with the signer's name, position, direct work email, phone number, and signature. A generic HR letter that confirms your dates but not your duties is not sufficient to support a claim; the duties are the part the assessor grades against 261313.
Statutory declarations: when a reference letter on its own is not enough
When a former employer has closed, refuses to sign, or cannot be reached, you are not stuck. ACS accepts a third-party statutory declaration or affidavit from a work colleague who can attest to your duties, provided it comes with supporting documentation such as employment certificates or leaving certificates. The colleague swears to what they witnessed you doing; the supporting paperwork corroborates the dates and the role. Treat it as a substitute for the signature, not a substitute for the evidence.
Submit your 261313 application through the ACS Portal
Lodgement happens entirely online through the ACS Portal at portal.acs.org.au. The mechanics are straightforward once your documents are prepared; the sequence below is the one that avoids re-work.
Create your account and select ANZSCO 261313 in the application form
Register on the portal, then start a new application and nominate Software Engineer 261313 as your occupation and the correct pathway (General Skills or RPL) as determined by your qualification. The occupation you pick here drives which duty statement your references are read against, so confirm it matches the boundary analysis above before you go further.
Upload documents, pay the fee, and confirm your lodgement
Upload each transcript as its own PDF, attach your reference letters and any statutory declarations, and pay the pathway fee to submit. The application is not in the queue until payment clears and the portal confirms lodgement, so watch for that confirmation rather than assuming the upload was enough.
What happens during the processing window
ACS assesses complete applications inside a published window and offers priority handling for applicants facing a near-term visa deadline. Rather than treat any single figure as current, check the live estimate on our processing time 2026 page before you plan around a date. An application that triggers a request for more documents resets your clock, which is the strongest argument for getting the paperwork right the first time.
How ACS reads your ACS skills assessment software engineer application and what fails it
This is where most applications are won or lost. The assessor is not judging whether you are a good engineer; they are checking whether the words in your references satisfy the 261313 duty statement, on the evidence in front of them.
Mapping your daily duties to the ANZSCO 261313 unit group tasks
Take the duty statement apart and match your own work to it, phrase by phrase. "Designs" wants architecture and interface decisions you made. "Develops" wants the build. "Implements" and "installs" want the system going live. "Supports" wants you maintaining software you helped create. Where a reference letter uses your employer's internal job title instead of this vocabulary, the assessor has to bridge the gap without your help. Rewrite the duties in ANZSCO's own terms, truthfully, so no interpretation is required.
Three rejection patterns specific to software engineer applicants
Failures cluster into three shapes. The first is a duties mismatch: references describing testing, support, or spec-following work rather than software design and development, which is the leading cause for this code. The second is a non-compliant reference format, where a mandatory field is missing or the letter is not on letterhead. The third is a qualification not assessed as comparable to an Australian Bachelor's degree, which downgrades you into a longer experience requirement or out of the General Skills pathway entirely. Our rejection self-audit guide breaks each pattern down further.
Pre-submission audit: five things to verify before you pay
Before you spend the fee, confirm all five of these:
1. Your nominated code matches your actual duties on the 2613 boundary table, not just your job title.
2. Every reference letter carries all required fields, on letterhead, with duties in ANZSCO language.
3. Each transcript is a 300 dpi colour scan, one PDF per qualification, edges visible, completion date shown.
4. Your qualification's ICT-major status and closely-related status place you in the pathway you selected.
5. If you are on the RPL route, your most recent ICT role is active or ended within the last 2 years.
Using your outcome letter for Australian visa applications
The result letter is the object every earlier step exists to produce. What you can do with it depends on the outcome and on the clock attached to it.
Positive assessment: linking your result to visa subclass 189, 190, or 491
A positive 261313 assessment sits on the MLTSSL and supports the skilled independent (189), state-nominated (190), and regional (491) subclasses. Read your outcome letter for the Skill Level Requirement Met Date, because it affects your points calculation. ACS sets that date at the point you had completed both your qualification and the required experience; only employment after it counts as skilled employment for the Department's points test. Experience that predates it still qualifies you for assessment, but applicants who overlook the Skill Level Requirement Met Date overstate their points score.
Negative assessment: when to appeal versus when to reapply
A negative result is not the end, but the right response depends on why it failed. If the assessor misread evidence you already supplied, appeal. If the problem was a genuine gap, a non-compliant reference, a duties mismatch, or too few qualifying years, reapplying with corrected documents is usually faster and cheaper than contesting the original decision. Our guide on whether to appeal or reapply walks the decision in detail.
Assessment validity is 2 years: build your visa timeline around it
Many migration blogs and agency pages quote 3 years. The ACS service agreement states 2 years from issuance. Plan your expression of interest, your English test, and your state nomination inside that two-year window. If your invitation is slow to arrive and the clock runs out, you reassess and pay again, so time the assessment to sit close to your visa lodgement, not years ahead of it.
Questions software engineers ask about the 261313 skills assessment
Can a software developer or programmer apply under ANZSCO 261313, or should they use a different code?
Yes, but only if your day-to-day work is genuinely software design and full-lifecycle development. A developer who builds from specifications written by others fits Developer Programmer 261312, and someone who gathers requirements and then encodes them fits Analyst Programmer 261311. Nominate 261313 only when your references show independent design and architecture decisions across the software lifecycle.
What counts as closely related work experience for an ANZSCO 261313 assessment?
Closely related means duties that align with the 261313 task list: designing, developing, implementing, and supporting software systems, at a minimum of 20 hours per week, undertaken from age 18 onward. Infrastructure administration, help-desk support, or pure testing work maps to other codes, not to Software Engineer.
Does ACS accept freelance or contract work as employment evidence for software engineers?
Yes, provided you document it to the same standard as salaried work. You need a reference on letterhead, or a statutory declaration where no client can sign, stating the engagement dates, hours per week, and your ICT-specific duties, ideally backed by contracts and invoices that corroborate the period claimed.
What happens if my former employer no longer exists and I cannot get an official reference letter?
ACS accepts a third-party statutory declaration or affidavit from a work colleague who can attest to your duties, supported by documents such as employment certificates or leaving certificates. The colleague states what they witnessed, and the supporting paperwork corroborates the dates and the role.
How long is an ACS skills assessment for ANZSCO 261313 valid, and can I use it for more than one visa subclass?
The ACS service agreement sets validity at 2 years from issuance, not the 3 years quoted across many migration blogs. Within that window, you can use the same positive result for multiple MLTSSL subclasses, including 189, 190, and 491.
Before you pay the fee, read our ACS document checklist for 261313 applicants and confirm you have every field and file ready, so your application clears on the first read.