The hardest APS6 interview feedback is often the feedback you never receive: your answer was relevant, polished and well structured, but it sounded one classification too low. This guide helps you identify and correct that problem before the panel does. It explains how APS6 questions are built from the selection criteria, what common questions are designed to uncover and why the Action section carries most of the evidence about your level. You will see a realistic candidate-style answer taken apart, learn exactly where it slips toward APS5 and compare it with a stronger version that makes the candidate’s judgement, influence, risk management and ownership clear. Further model answers, common pitfalls and a practical preparation checklist then show you how to apply the same standard to your own examples.
What are APS6 interview panels testing?
APS6 panels design interview questions by working backwards from the selection criteria.
The selection criteria are a focused view of what the panel is looking for in the ideal candidate: the specific capabilities they will assess your application against. The role description tells you the broader set of things you will be doing day to day; the selection criteria narrow that down to the capabilities that actually get scored.
The selection criteria usually sit in the position description or applicant pack, separate to the role duties, under a heading like Knowledge, Skills and Experience, focus capabilities, or key selection criteria. The quickest tell is the phrasing: criteria are written as capability statements ("Demonstrated ability to…", "Proven…", "Exceptional…"), while duties read as plain tasks.
To design the interview, the panel works from the same selection criteria. They take each capability the role needs and turn it into a question that draws out evidence of it. A criterion like "Demonstrated ability to plan, organise and prioritise competing work" becomes a question such as "Tell us about a time you had to manage several competing priorities with tight timeframes." The wording changes, but the question exists to test that exact capability.
The classification sets the level of behaviour the panel expects inside that evidence. The APS Work Level Standards help describe the complexity, autonomy and accountability associated with APS6 work, while the Integrated Leadership System describes how capabilities such as achieving results, working with others and communicating with influence develop at that level. Our guide to framing your experience at the right APS level explains how those two references work together.
For the broader interview process, including behavioural and hypothetical questions, STAR structure and general preparation, use our APS interview questions guide. This article stays focused on what makes an answer sound APS6.
Common APS6 interview questions
APS6 interview questions are simply the selection criterion rewritten as a prompt, and the panel uses your answer to judge whether you can perform the role at the required level. At an APS6 level, the most common selection criteria are stakeholder management, complex problem-solving, prioritising competing work, project or delivery ownership, clear written and verbal communication (including briefing decision-makers), and integrity and judgement under limited direction.
These capabilities also align with the five clusters in the Integrated Leadership System (ILS): Supports Strategic Direction, Achieves Results, Supports Productive Working Relationships, Displays Personal Drive and Integrity, and Communicates with Influence. The ILS helps you understand how behaviour changes by classification; the role's advertised criteria determine what the panel assesses in your interview.
These translate to common interview questions asked during APS6 interviews.
| Common APS6 interview question | What the panel is likely to assess |
|---|---|
| Tell us about a time you had to influence a resistant stakeholder while still delivering a required outcome. How did you approach the situation, and what was the outcome? | How you understand a stakeholder’s concerns, adapt your approach, negotiate a way forward and keep the work moving without giving in or escalating too quickly. |
| Tell us about a complex problem where the available information was incomplete or conflicting. How did you make sense of it and decide on a way forward? | How you make sense of incomplete or conflicting information, involve the right people, weigh your options and recommend a clear way forward without needing detailed direction. |
| Tell us about a time when you had to manage several competing priorities with tight timeframes. How did you decide what to focus on and ensure the quality of your work was maintained? | How you set priorities under pressure, explain your decisions and maintain quality while meeting tight deadlines. |
| Tell us about a significant project or piece of work you led or coordinated. How did you plan it, manage risks and dependencies, and keep it on track? | How you take ownership of the whole project, plan and monitor the work, manage risks and dependencies, and step in or escalate when needed. |
| Tell us about a time you identified an issue or opportunity and took the initiative to act. How did you decide what to do and when to involve others? | How you identify what needs attention, choose a practical response, act within your authority and know when to consult or escalate. |
| Tell us about a time you led an improvement that affected more than one team. How did you involve people and help the change stick? | How you use evidence and feedback, coordinate across teams, build support for change and make sure the improvement lasts. |
| Tell us about a time you turned a broad organisational priority or policy requirement into practical action. How did you decide what needed to happen? | How you connect day-to-day work to broader goals, anticipate the wider effects and turn high-level direction into a practical plan. |
| Tell us about a time you helped a colleague or team improve their capability or performance. What did you do, and how did you know it made a difference? | How you set expectations, delegate, coach and give useful feedback so others improve instead of taking over the work yourself. |
| Tell us about a time stakeholders disagreed about the best way forward. How did you help them work through it, and when did you decide to step in or escalate? | How you listen fairly, work through disagreement, maintain relationships and help people reach a clear decision, including when to intervene or escalate. |
| Tell us about a time when something you were responsible for did not go to plan. How did you respond, what did you change, and what did you learn? | How you take ownership without shifting blame, raise problems early, correct course and use what you learned to improve future work. |
| Tell us about a time you briefed a senior decision-maker on a complex issue or recommendation. How did you make the issue clear and tailor your advice? | How you make a complex issue clear, identify the decision needed, explain the options and risks, and respond confidently to questions. |
| Tell us about a time a project or priority changed unexpectedly. How did you adjust your approach and keep the work moving towards the right outcome? | How you reassess risks, resources and dependencies, explain what has changed and adjust your approach without losing sight of the outcome. |
| Tell us about a time you received constructive feedback that changed how you approached your work. What did you do differently, and what was the result? | How you respond to feedback, reflect honestly and make practical changes that improve how you work or lead others. |
You do not need a separate example for every question in this table. A small bank of strong examples can cover several capabilities, as long as you adjust the emphasis to answer the question being asked. The same project might demonstrate prioritisation in one answer, stakeholder influence in another and judgement under pressure in a third.
What matters is not how many examples you prepare, but whether each one gives the panel clear evidence of the capability and level it is testing.
What makes a strong APS6 interview answer?
A strong APS6 interview answer is not a memorised script. It comes down to two things: choosing an example that genuinely matches the capability being tested, and making sure the behaviour inside that example sounds like APS6, not a strong APS5 contribution.
The Integrated Leadership System helps explain that behavioural difference. It does not prescribe a fixed action for a stakeholder question or a delivery question. It describes the behaviour expected at each level, so you can check whether your example sounds proactive, considered and accountable enough for APS6. When your answer involves judgement, stakeholders, delivery or communication, the test is the same: does the behaviour match the level, or does it sit a step below?
That behaviour is heard most clearly in the Action section. Situation and Task set the context; Result shows what changed; but Action is where the panel hears the level: what you personally decided, how you weighed trade-offs, how you influenced people, and how much responsibility you carried. If the Action section only says you helped, supported, followed up or completed the work, it can sound too narrow for the level, even when the underlying experience was strong.
So the work of preparing is not memorising more questions. It is choosing examples that answer the selection criteria, then calibrating the Action section so the APS6-level behaviour already in your example is clear to the panel.
Worked APS6 interview answer example: weak vs strong
To demonstrate the difference between a strong and weak APS6 interview answer, we'll use a realistic practice response to an APS6 competing-priorities question.
The question was:
- Tell us about a time when you had to manage several competing priorities with tight timeframes. How did you decide what to focus on and ensure the quality of your work was maintained?
We'll look at the candidate-style answer, the coaching it would receive and how the same experience sounds when that feedback is applied.
In my last role, there was a week where we had a lot happening at once. I was helping with governance reporting, and we had committee papers due, the project tracker needed updating, and another team asked for some information about where a few deliverables were up to.
Coaching noteYou chose a relevant example with genuinely competing demands: committee papers, a project tracker, and an information request all landing in the same week. To make it stronger for APS 6, name the deadlines, who was relying on each product, and the risk if the papers or tracker were late or inaccurate.
My responsibility was to keep the three pieces of work moving and make sure the committee papers, tracker and response were finished accurately and on time.
Coaching noteYou made your responsibility clear: keeping three linked governance products accurate and on time. To make it stronger for APS 6, define the ownership you carried, including whether you coordinated inputs, set timeframes or were accountable for the overall workflow, so the task shows responsibility for the outcome, not just completion of the products.
I started by looking at what was due first and making a list so I could keep track of it. The committee papers were probably the main thing because the meeting was coming up, so I worked on getting those into the right format and checking the information we already had. I also checked in with my manager about what they wanted me to focus on first. After that I updated the tracker with the latest milestones and risks, and then used that to help answer the request from the other area. I tried to keep things moving by doing the most urgent things first and not leaving the spreadsheet until the end, because people were relying on it for the meeting. To keep the quality okay, I reread the papers before sending them through and checked the tracker against the information I had. If I was unsure about something, I asked my manager or checked with someone in the team.
Coaching noteYour actions were practical: you made a list, prioritised the committee papers, kept the tracker current, checked information, and asked for help when needed. To lift this to APS 6, explain the judgement behind those choices: how you weighed urgency against importance, managed dependencies between the tracker and the papers, and whether you negotiated timing or escalated risks that could affect quality.
In the end everything was finished on time, the papers went through, the tracker was updated, and the other team got the information they needed.
Coaching noteYou gave a clear finish point: everything was completed on time and the right people got what they needed. To make the result more convincing, say what your approach protected — for example, that the committee received accurate milestone and risk information, the other team got a consistent update, or no major corrections were needed after submission.
Taken together, the coaching notes show why this answer would fall short in an APS6 interview. The behaviour described demonstrates APS5-level delivery rather than APS6-level ownership. The panel does not hear the evidence it needs at the advertised level: setting priorities under limited direction, managing dependencies, negotiating timeframes, responding to risks and taking responsibility for the broader outcome. A clear STAR structure cannot make up for that level mismatch.
The easiest way to understand the feedback is to see it applied. The model answer below uses the same experience and shows how it could sound with the missing APS6-level judgement and ownership made clear. Interview Practice provides this kind of model answer alongside its coaching notes, helping candidates move from knowing what to improve to seeing how the improvement sounds.
The highlighted text shows the feedback being applied using the model’s best estimate of what likely happened. Treat these additions as prompts for facts to confirm or correct before using the answer in an interview.
In my last role, there was a week where we had a lot happening at once. I was helping with governance reporting, and we had committee papers due, the project tracker needed updating, and another team asked for some information about where a few deliverables were up to. The committee meeting date was fixed, so the papers had a hard deadline; the committee relied on them to make decisions, leadership relied on the tracker for a current view of milestones and risks, and the other team needed a status update they could act on. The main risk was that if the papers or tracker were late or inconsistent, the committee could make decisions on out-of-date information and the other team could act on a status update that did not match the governance reporting.
My responsibility was to coordinate the three linked deliverables, set the sequence and timeframes for the work, and make sure the committee and other team received accurate, consistent information when they needed it.
At the start of the week, I mapped the dependencies between the deliverables and proposed an order of priorities to my manager rather than waiting to be told. My view was that the committee papers had to come first, given the fixed deadline and the clearance time they needed, and that the other team’s request was better answered once the tracker was current so their update stayed consistent with the governance reporting. I then made a short task list so I could track what needed to be done, what information I already had, and what still needed checking. I worked on the committee papers first, getting them into the right format and checking the information we already had. I also made sure I did not leave the tracker until the end, because it was feeding both the meeting material and the response to the other team. I used the updated tracker as the single source of information: once the milestones and risks were current, I drew on it to answer the other team’s request. Where milestones or risks were unclear, I asked the relevant team members to confirm the details by a set cut-off time rather than guessing or leaving it until the final review. To maintain quality, I reread the papers before sending them through and checked the tracker against the information I had. If I was unsure, I asked my manager or checked with someone in the team so the final version was accurate.
In the end, the papers went through on time, the tracker was updated, and the other team received the information they needed. Because the papers and tracker were aligned, the committee had accurate, current milestone and risk information for its decisions, the material did not need major last-minute corrections, and the other team received a consistent status update. Ultimately, I received recognition from my branch manager for how I managed multiple competing priorities with tight deadlines.
What changed when the feedback was applied?
The candidate's underlying experience is the same. What changes is how the answer demonstrates the behaviour expected at the role's classification. The stronger version moves beyond organised task delivery and shows APS6-level judgement, ownership and accountability through the candidate's decisions, trade-offs and management of the broader outcome.
- The priorities are connected to deadlines, dependencies and risks instead of being presented as a task list.
- The candidate proposes an order of work and explains the trade-offs instead of waiting for their manager to set the priorities.
- The deliverables are managed as connected pieces of work, with a consistent source of information and clear cut-off times.
- The result explains what the candidate's approach protected, not merely that everything was finished.
This is what level calibration looks like in practice: the response does not just describe successful delivery; it demonstrates the behaviour expected of someone performing the role at APS6.
Find out whether your answers sound APS6
Practising a question is only useful if you can tell whether the panel will hear the evidence at the required level. APSPitchPro creates role-specific questions from the position you are applying for and reviews your response for evidence depth, STAR structure and level calibration.
Use it to identify vague or under-level evidence, strengthen your Action section and compare your response with a more clearly calibrated version.
Practise an APS6 interview →Further examples of strong APS6 interview answers
Here are four more common APS6 interview questions, with strong example answers that show the judgement, ownership and influence expected at this level.
APS6 example answer: managing a resistant stakeholder
Question: Give an example of a time you had to manage a challenging or resistant stakeholder. How did you build trust while still delivering the required outcome?
In a service delivery program, I was coordinating the introduction of a new referral process after an assurance review found inconsistent checks across regional teams. One regional manager resisted the change because they believed the extra quality step would delay urgent referrals and create more administration for staff.
My responsibility was to implement the required control across the program without weakening service standards. I needed to understand whether the stakeholder's concern reflected a genuine delivery risk, then find an approach that protected both timeliness and assurance.
I met with the manager and asked them to walk me through several recent referrals. That showed the proposed process treated every case the same, even though only higher-risk referrals required a second check. I separated the non-negotiable requirement, consistent assurance, from the part we could change, how the check operated. I reviewed four weeks of referral data with the assurance team and proposed a risk-based pathway: standard referrals would continue through the existing workflow, while higher-risk cases would receive the additional review. Because I expected the same workload concern to arise in other regions, I asked the other regional leads to test the proposed criteria during the four-week pilot and used their feedback to refine the guidance before the wider rollout. I set measures for timeliness, incomplete referrals and staff rework, and briefed the program lead on the revised approach and residual risk so the decision was transparent.
During the pilot, no urgent referral missed its service standard and incomplete referrals fell from eleven in the previous month to three. The regional manager supported the final process because their operational concern had been addressed, and the same risk-based approach was then adopted across the other regions.
Why this demonstrates APS6 behaviour:
- Anticipates stakeholder concerns: The candidate expects other regions to raise the same workload issue and involves them before the wider rollout, rather than waiting for resistance to emerge again.
- Uses different perspectives to improve the outcome: The manager's operational knowledge and the other regional leads' feedback directly shape the risk-based process and guidance.
- Adjusts delivery using specialist expertise: The candidate works with the assurance team, changes the original approach, sets measures for the pilot and makes the residual risk clear to the program lead.
- Negotiates without losing the outcome: They separate the assurance requirement that must remain from the implementation details that can change, then build support for a workable solution.
That is the APS5-to-APS6 shift in practical terms: the candidate does not only respond to an objection or keep stakeholders informed. They anticipate the wider concern, use different perspectives to improve the approach and steer the change through to adoption.
APS6 example answer: solving a complex problem
Question: Tell us about a complex problem you solved using analysis, judgement and consultation.
After a program introduced a new case-management process, monthly reporting showed a sharp increase in unresolved complaints. Senior leaders needed to know whether service performance had deteriorated or whether the new reporting method was distorting the result.
I was asked to analyse the increase and recommend a response before the next executive performance meeting. The risk was that a broad intervention would divert resources from other priorities if the diagnosis was wrong.
I began by defining the decision the analysis needed to support, then reconciled complaint records across the case-management system, regional logs and the previous monthly report. I found that a new status code accounted for part of the increase because transferred cases were being counted as unresolved twice. However, the data also showed a genuine concentration of aged cases in two regions. I tested those findings with the reporting team and the regional operations leads, checked whether staffing changes or seasonal demand explained the pattern, and documented the limits in the available data. I considered three options: a program-wide backlog response, correcting the reporting rule only, or a targeted case review in the two affected regions alongside the reporting fix. I recommended the third option because it addressed the real service issue without treating every region as if it had the same problem. To prevent the reporting distortion from recurring, I also proposed a validation rule for transferred cases and a common definition of an unresolved case across regional reports.
The executive accepted the recommendation and the reporting control. The duplicate counting rule was corrected before the next report, the validation check became part of the monthly reporting process, and the targeted review reduced cases older than 30 days from 94 to 61 over six weeks. Leaders had a more reliable performance picture and could direct support to the areas that needed it.
Why this demonstrates APS6 behaviour:
- Recognises how issues connect: The candidate separates a reporting distortion from a genuine service backlog and explains how both affect the executive's decision.
- Investigates diverse evidence and viewpoints: They reconcile several data sources, test the findings with reporting specialists and regional operations leads, and state the limits of the evidence.
- Frames analysis around consequences: The candidate compares three options and recommends the response that addresses the real problem without diverting resources across the whole program.
- Looks beyond the immediate fix: They introduce a validation rule and shared reporting definition so leaders can rely on future reports, not only the report in front of them.
That is the APS5-to-APS6 shift in practical terms: the candidate does not only analyse the information systematically and resolve the immediate problem. They recognise the connection between reporting and service delivery, consider the wider consequences of each option and establish a longer-term improvement.
APS6 example answer: leading a process improvement
Question: Tell us about a recurring inefficiency you identified and the improvement you led. How did you bring others into the change?
In my previous branch, executive briefs regularly reached the clearance team late. Authors were working from different templates, reviewers were repeating the same checks and no one had a clear view of where a brief was waiting. The delays created last-minute pressure and increased the risk of inconsistent advice reaching the executive.
I took responsibility for reviewing the workflow and introducing a more reliable process across the five teams that contributed to the briefs. I needed to improve timeliness without removing the specialist and quality checks the branch relied on.
I mapped the process from initial request to final clearance and reviewed three months of due dates, returns and rework. I then held short sessions with authors, subject-matter experts and the clearance team to test where the delays occurred. Two issues accounted for most of the lost time: teams were seeking specialist input too late, and reviewers were returning whole documents when only one section required correction. I proposed a single briefing template, named owners and cut-off times for each stage, and introduced a shared tracker that showed dependencies and decisions still required. We piloted the process with one reporting cycle. When authors said the first version of the tracker was too detailed, I removed fields that did not help a decision and added a simple escalation flag for risks that could affect the clearance date. I also ran a practical session with coordinators so they could use the process consistently rather than relying on me to manage every brief.
Over the next three reporting cycles, briefs cleared by the agreed date increased from 62 per cent to 91 per cent. The clearance team reported less repeated rework, and the branch adopted the template and tracker as its standard approach.
Why this demonstrates APS6 behaviour:
- Initiates the improvement: The candidate takes responsibility for reviewing a cross-team problem and develops the new workflow rather than only contributing to a change designed by someone else.
- Uses other people's expertise: Authors, subject-matter experts, reviewers and coordinators help identify the causes of delay and shape the solution.
- Adjusts the plan as evidence emerges: The candidate pilots the process, removes fields that do not support decisions and adds an escalation flag in response to user feedback.
- Helps others adopt the change: They run a practical session so coordinators can apply the process consistently without depending on them to manage every brief.
That is the APS5-to-APS6 shift in practical terms: the candidate does not only manage an improvement project from beginning to end. They steer the change as new information emerges and actively build the capability of the people who will sustain it.
APS6 example answer: integrity and confidential information
Question: Tell us about a time your integrity or judgement was tested when handling sensitive information.
I was preparing a briefing on a sensitive service issue for a cross-agency meeting. A senior colleague asked me to include several identifiable client examples because they believed the personal detail would make the case for action more persuasive. The draft was due to be circulated to a much wider group than the team that normally handled those records.
My responsibility was to give decision-makers enough evidence to understand the seriousness of the issue while ensuring personal information was only used and shared where it was necessary and authorised.
I paused circulation of the draft and checked the information-handling requirements and the purpose for which the examples had originally been collected. I then spoke with our privacy adviser to confirm the minimum information the meeting required. I explained to the colleague that the proposed version created an unnecessary disclosure risk and that urgency did not remove our obligation to handle the information properly. Rather than only rejecting the request, I prepared an alternative using aggregated data and de-identified case summaries that preserved the operational detail. For one issue where precise evidence might be needed later, I recommended a restricted annex that could be provided only to authorised decision-makers if requested. I recorded the handling decision and the source of the advice so there was a clear audit trail.
The briefing was cleared and circulated on time, and the meeting agreed to the proposed service review without identifiable client information being disclosed. The de-identified format was subsequently used for similar cross-agency briefs, giving the team a practical way to present sensitive evidence without creating avoidable privacy risk.
Why this demonstrates APS6 behaviour:
- Raises the concern proactively: The candidate pauses circulation before the information is disclosed rather than waiting for someone else to question the draft.
- Provides forthright, impartial advice: They explain the disclosure risk to a senior colleague even though the identifiable examples would make the briefing more persuasive.
- Takes responsibility for a workable outcome: The candidate does not simply reject the request or pass the problem upward. They prepare de-identified evidence, propose a restricted annex where necessary and document the decision.
- Improves the wider practice: The resulting format becomes a repeatable way to present sensitive evidence in later cross-agency briefs.
That is the APS5-to-APS6 shift in practical terms: the candidate does not only defend an ethical position when challenged. They identify the problem themselves, constructively challenge the proposed approach and establish a better way to handle similar work.
What mistakes weaken APS6 interview answers?
The most damaging APS6 interview mistakes are usually not failures of STAR structure. They are gaps in the evidence that prevent the panel from hearing APS6-level behaviour.
-
Giving a task list instead of a decision process: Listing emails, meetings and completed documents tells the panel you were busy. Explain what you noticed, what options or pressures you weighed, why you chose your approach and what you changed as the work developed.
-
Letting the manager own every important judgement: It is appropriate to consult or escalate, but "I asked my manager what to do" leaves little evidence of your own judgement. State the assessment or recommendation you took to them and why approval or escalation was needed.
-
Mentioning stakeholders without showing influence: Saying you kept stakeholders informed is not enough when the question is testing influence. Identify what they needed, where views differed, what you did to build support and which part of the outcome changed because of that engagement.
-
Naming a risk without managing it: Do not stop at "I identified a risk." Explain how you assessed its likelihood or consequence, what control or contingency you introduced, who needed to know and how you monitored whether the response worked.
-
Ending with completion rather than impact: "The work was delivered on time" is a finish point, not always a meaningful result. Tell the panel what the delivery protected, improved, enabled or changed for the team, stakeholder, decision-maker or service.
APS6 interview preparation checklist
Use this checklist to turn the job documents into a small bank of answers you can adapt under interview conditions.
-
Decode the role: Read the job ad and candidate pack, isolate the selection criteria and note the APS6 work-level expectations that give those criteria their required scope.
-
Map likely questions: Turn each criterion into a behavioural or hypothetical question, then group the questions under stakeholder influence, problem-solving, delivery, leadership, integrity or communication.
-
Choose 4 to 6 examples: Select examples with enough complexity to show APS6 behaviour. Build each as a flexible STAR outline, not a word-for-word script.
-
Test the level: Check whether the Action section shows your judgement, trade-offs, stakeholder influence, risk response and accountability. If those details did not happen, choose a stronger example rather than inflating the story.
-
Practise out loud: Practise a natural answer of two to three minutes, review where the evidence becomes vague and repeat the question with different wording so you learn the example rather than memorise a script.
Make your APS6 evidence clear
A strong APS6 answer does more than follow STAR. It shows the panel how you exercised judgement, influenced others, managed risk and took responsibility for the broader outcome. Choose examples where those behaviours genuinely happened, then practise explaining them clearly in your own words.
Prepare with APSPitchPro →FAQ
What questions are commonly asked in an APS6 interview?
Common APS6 questions test stakeholder influence, complex problem-solving, competing priorities, project or delivery ownership, integrity, judgement and communication with influence. The exact questions come from the selection criteria and responsibilities in the advertised role.
What makes an APS6 interview answer different from an APS5 answer?
An APS5 answer may show strong independent delivery and practical problem-solving. An APS6 answer needs to make broader judgement and ownership clear, such as steering connected work, anticipating stakeholder concerns, adjusting plans as risks emerge and taking responsibility for the wider outcome.
How many examples should I prepare for an APS6 interview?
Prepare four to six strong examples that collectively cover the main criteria in the job documents. A good example can answer more than one question, provided you change the emphasis and respond directly to the capability the panel is testing.
How long should an APS6 interview answer be?
Most behavioural answers should fit into roughly two to three minutes unless the panel gives different instructions. Keep Situation and Task concise, spend most of the time on your Action, then finish with a result that explains the outcome and why it mattered.
Should I mention the ILS in my interview answer?
You usually do not need to name the ILS. Use it during preparation to understand the behaviour expected at APS6, then demonstrate that behaviour through your real decisions, actions and results.
Can I use experience from outside the APS?
Yes. Private-sector, state government, community, defence and other experience can be relevant if it answers the criterion and shows comparable complexity, judgement and accountability. Translate the context clearly, but do not change or exaggerate what you did.