APS 5 Interview Questions and Sample Answers

Situation: I was given the annual review of our internal guidance material, about sixty documents, with a six-week window. Task: I owned the review and the sign-off pathway. Action: I triaged the sixty by whether the underlying policy had changed, which cut the substantive rewrites to eleven. I set my own checkpoint at week two and raised early with my director that two of the eleven touched a policy still under consideration, so I proposed holding those and completing the other nine. Result: nine were updated and published inside the window, the two held items were completed a fortnight later once the policy settled, and nothing was published against superseded policy.

Situation: a request came in that fell between two categories in our guidance, and each category carried a different processing timeframe. Task: the file was mine to progress. Action: I set out both readings in a short note, including which facts pointed each way, and identified that the narrower reading was defensible while the broader one would have set a precedent for a class of requests we had not considered. I took the note to my EL1 with a recommendation rather than a question. Result: she agreed with the narrower reading, we recorded the reasoning on file, and the note was later used as the reference point when two similar requests arrived.

Situation: I was co-ordinating a quarterly report that needed figures from three business areas, and one area consistently supplied late. Task: I owned the report deadline. Action: rather than escalating first, I asked to see how their extract was produced and found their data was not available until after their own monthly close — the deadline we had set was never achievable for them. I rebuilt the report sequence around their actual close date, asked for a partial extract earlier so I could start, and confirmed the new arrangement in writing. Result: the report went out on time for the next three quarters, and the change removed a recurring escalation rather than repeating it.

Situation: I drafted a brief for our first assistant secretary on options for a small program change. Task: it had to be short enough to be read before a meeting the next morning. Action: I put the recommendation and the two-line reason at the top, kept the background to a paragraph, and moved the detail to an attachment. I asked a colleague outside the program to read it for whether the recommendation was obvious, and she pointed out I had not stated the cost of doing nothing, so I added it. Result: the brief went up unamended and the recommendation was agreed at that meeting. The structure became the pattern I used for later briefs.

"Our policy team wanted a report in two weeks; the data team said six. I met both leads separately to understand what each actually needed. Policy needed three headline figures for a briefing, not the full report. I proposed a two-week interim brief with those figures, flagged clearly as preliminary, and the full report at week six. Both agreed, the briefing went ahead on time, and the final figures changed by less than 2%."

"While preparing a grants round, I noticed the online form let applicants submit without the eligibility declaration. I tested it, documented the gap and raised it with my manager the same day, with a fix the IT team could make in an hour. We paused the launch by one day. Without it, we'd have had to chase declarations from every applicant, roughly 400 of them."