ACS Skills Assessment for Software Engineers: What Actually Gets Approved

#Which ANZSCO code should software engineers use for the ACS skills assessment?

The ACS recognises a wide family of ICT ANZSCO codes, but choosing the wrong one is one of the most common and costly mistakes applicants make. The code you select must genuinely reflect your day-to-day technical responsibilities — not just your job title.

Here is a quick reference for the most relevant codes software engineers encounter:

Many applicants apply for multiple codes in the same ACS submission. One community member shared their experience receiving positive assessments for three codes simultaneously — 261313 (Software Engineer), 261312 (Developer Programmer), and 261311 (Analyst Programmer) — in a single application, which took just over a month from submission to result.

Another important consideration: the code you get assessed under must align with the ANZSCO code you eventually nominate in your visa application. Getting assessed under the wrong code early can create mismatches that are expensive to fix later — one applicant in our community paid AUD 2,400 to submit three additional skills assessments after realising their original code selection was too narrow for the invite rounds they were targeting.

#What is the RPL pathway and when should software engineers use it?

RPL stands for Recognition of Prior Learning. It is ACS's mechanism for acknowledging that strong hands-on experience can substitute for — or supplement — formal academic credentials. For software engineers without a computing degree, it is often the only viable pathway to a positive skills assessment.

The two core ACS pathways for software engineers are:

The RPL pathway is commonly used by self-taught engineers, career changers from non-computing backgrounds (such as civil engineering or mathematics), and experienced professionals whose degree was in a non-ICT discipline. One applicant in our community — who held a Higher Secondary qualification and a civil engineering degree with outstanding papers — correctly identified RPL as their only realistic option for a software engineering assessment with nine-plus years of experience.

The RPL pathway demands significantly more documentation than the standard pathway. ACS requires a detailed written statement explaining your technical responsibilities, the projects you worked on, the specific technologies and tools you used, your individual contribution versus team contribution, and the scale and complexity of each project. Generic reference letters stating "John was a good developer" are routinely rejected.

That recovery story is instructive: ACS does have an appeals process, and a well-prepared statutory declaration can turn a negative outcome around quickly. But the better strategy is to get the documentation right the first time. At VJ Consulting and Education, we review RPL statements before submission specifically to identify gaps that ACS assessors commonly flag.

If your employer has closed down or your former manager is no longer reachable, a statutory declaration from the closest available person with direct knowledge of your work — even a client or a colleague — can substitute, though it must be highly specific about your technical duties.

#What work experience does ACS accept for a software engineer skills assessment?

Understanding exactly what ACS counts — and how it counts it — is essential before you assemble your application. The body is not simply verifying that you were employed; it is verifying that your actual daily work was genuinely ICT in nature and matches the ANZSCO code you are claiming.

Here is a breakdown of what ACS typically requires for each period of employment:

The reference letter is the document that most often causes delays or rejections. ACS assessors are looking for specificity: what programming languages and frameworks did you use, what was the scale of the system you built or maintained, what was your individual contribution as distinct from your team's contribution, and what was the business impact of the project. A letter that says "responsible for project development" fails on almost every one of those criteria.

Overseas work experience is fully accepted by ACS. If you worked in China, India, Malaysia, or any other country before coming to Australia, that experience counts — but the documentation requirements are identical. One community member raised a practical issue: a bank statement from their first year of overseas employment had a minor name discrepancy (one letter different). ACS can request clarification in these cases, and a brief explanatory statement with supporting ID is usually sufficient to resolve it.

If your former employer has ceased to exist, you are not automatically excluded. A statutory declaration from a former direct manager, even if they have since moved to another company, is acceptable. The declaration must be specific about your technical duties and should ideally reference the company's ABN or equivalent registration number, the dates of your employment, and the specific projects you worked on.

For software engineers navigating complex employment histories — multiple short contracts, overseas companies that are now closed, or roles where the job title did not match the actual technical work — the team at VJCE regularly assists clients in structuring their documentation to accurately represent genuine experience in a format ACS assessors find credible.

#How long does the ACS skills assessment take for software engineers?

The total elapsed time between submitting your application and receiving your result has two distinct components that applicants often conflate: the queue wait time and the actual assessment processing time. A complete, well-prepared application moves through the processing phase quickly. Incomplete applications or those requiring additional information can extend the total timeline significantly.

Real-world timelines shared by community members in 2025 confirm the published range. One applicant with two employment segments (six months as a Software Engineer and ten months as a Developer Programmer) submitted on 4 March 2025 and received their result on 10 April 2025 — approximately five and a half weeks total, with the actual processing taking nine days once the application entered the active assessment stage. They noted this was longer than the one-to-two-day processing times some others had reported, which they attributed to the complexity of having two separate employment periods.

The ACS assessment fee is approximately AUD 530 (always verify the current figure at the ACS website, as fees are subject to change). If you are applying for multiple ANZSCO codes in a single submission, this is generally covered under the same fee — but confirm this on the ACS portal before submitting.

Appeals, when handled correctly, can be resolved remarkably quickly. One community member received a positive appeal outcome in under 24 hours after resubmitting with a proper statutory declaration and detailed client statements. The ACS assessment fee for the appeal is not refunded on a successful appeal, but the alternative — a negative assessment on record — has far more serious downstream consequences for your visa application.

#Why do ACS software engineer applications get rejected or delayed?