Shape Australia. Create your future - A guest post from the APSC

Nathan Watson

The Department of Finance Archive

The content on this page and other Finance archive pages is provided to assist research and may contain references to activities or policies that have no current application. See the full archive disclaimer.


The Australian Public Service Commission (the Commission) is responsible for the APSjobs website which includes the Public Service Gazette (the Gazette) published in electronic form.

Our Problem

1. Agencies only use the Gazette to advertise what they must. The Gazette notifies some, not all, types of job opportunities that are available, as well as appointments or promotions to the APS. This means we are not exposing all public service job opportunities on APSjobs - people in the Public Service know this but does everyone else?

Google Analytics data tells us there are around 3 million APSjobs page views per year with 33% (approx. 1/3 or 1 million) belonging to new users. We know that people are looking at our site and we need to improve what we offer.

2. Our website is dated - a recent review of APS workforce management practices identified that the APS must better position itself to attract and compete for the best people. The review also identified that the current APSjobs website is dated and does not provide a user experience expected by potential candidates.

Our Solution

Make APSjobs the go to site for all career and job opportunities across government. It should provide access to all types of vacancies advertised across the Public Service – permanent, non-ongoing, contract, specialist.

What we have done so far

The APSC are working with experienced UX designers sourced through the Digital Marketplace. We have finished our Discovery Phase and are part way through our Alpha phase covering both UX and Creative Design. Expected completion date of Alpha is late April/early May 2017.

In anticipation of our technical needs at the end of Alpha we want to find out what is on offer and who may be interested in partnering with us on the build.

Just so you know, we’ve looked at govCMS PaaS but no firm decision has been made to use govCMS. We’ve also looked at IworkforNSW and think it’s pretty good. This discussion paper is to make sure we are informed about options to select optimal technology and obtain value for money.

Next steps

You would need to work with our wireframes and layered PSD files and deliver a system that includes but is not limited to:

• An easy to use, efficient and seamless experience for both agency and candidate users;
• No duplicate data entry – take the date from agency careers site (API’s or RSS feeds?);
• A simple automated option for agencies who may want to advertise short term or specialist roles directly on APSjobs (or have no e-recruit system and currently ask applicants to email an application to <name>;
• Is mobile optimised and WCAG compliant;
• Requires minimal support/human intervention, is secure, offers simple self-service if needed, is easy to use;
• Some reporting capability;
• Is ready for Beta (private) by September 2017 (yes! this year):

Now you know our problem, what we are up to and what we envisage for the next stage. We don’t need you to repeat the work already done on design but we are realistic if changes are needed. We want to partner with you to deliver a great product.

Over to you and tell us what you can offer before we do our formal ATM. We want to know what you can offer and your experience in similar work. No more than 5 pages would be great and pictures always help. We encourage responses from SME's and you do not need to be based in Canberra. We may contact you to discuss further or to meet based on your response to this discussion paper.

Send response to by cob 27 March 2017.


Simon Spencer

A/g CIO, Australian Public Service Commission

Add new comment


  • Allowed HTML tags: <a> <strong> <em>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Last updated: 25 January 2018