Home Court Prep
Illustrative sampleAn anonymised, composite example of what Home Court Prep produces — built to show the format. Not a real person, employer, or interview.

Sample dossier

Project Manager, Network & Compute Infrastructure

A senior PM interviewing with the director of an infrastructure team at a federal-government agency — for a role rebuilding the network and compute behind the country’s automated border gates. Everything below is built around one idea: walk in already understanding their real problem.

The one thing to internalise

This is a burning-platform rebuild, not a greenfield project

Anchor every answer to delivery certainty, under constraint, without dropping live services.

Ageing estate

Much of the technology estate is already past end-of-life, with replacement funding not yet fully secured.

Maintenance, not transformation

The agency is resourced to keep services running, not to radically modernise — that gap is the job.

No single executable plan

Its own capability review flagged the lack of one shared, prioritised roadmap. Imposing order is directly valued.

A newly stood-up function

The technology group is itself finding its delivery rhythm — a PM who creates structure stands out.

Why you fit — make these explicit

Close to a bullseye, not translating a generic CV

The candidate has already done this job's two hardest halves — and is already cleared. Lead with these; don't make the panel join the dots.

  • An existing security clearance. Roles like this need clearance. Already holding one means no vetting delay and no risk — a concrete reason to prefer this candidate over an uncleared one.
  • Biometric-matching delivery. The exact technology behind the contactless border gates. The single strongest, most specific differentiator.
  • Live-airport network experience. A network refresh in a running 24/7 airport — the same high-availability, can't-disrupt edge environment as the gates.
  • Government / regulated delivery. Already fluent in security, governance and accreditation — no public-sector translation needed.
  • Multi-site national rollouts. Phased delivery across many sites at once — exactly what site-by-site gate upgrades demand.

Speak the language

Vocab cheat-sheet

Use these naturally and in context — not recited as a list.

Security accreditation

Independent sign-off that a system meets the required controls at its classification — engage assessors early, not late.

Controls assessment

The catalogue of cyber controls a government system is measured against; name it naturally in delivery talk.

Essential cyber baseline

The baseline mitigations (patching, application control, MFA, backups) used as shorthand for cyber maturity.

Sovereign hosting

Hosting under domestic control and data residency — the counterweight to public cloud for sensitive workloads.

Gateway reviews

Independent assurance checkpoints at key project stages; knowing where you sit signals delivery maturity.

Systems integrator (SI)

The external partner that delivers much of the build; your day-to-day is assuring and holding them to milestones.

Work-level standards

How a role's level is defined by complexity and accountability — pitch answers at the advertised level.

Benefits realisation

Tracking that a project delivers its promised outcomes, not just outputs — a strong closing note.

Stories locked and loaded

Model STAR answers, built from the candidate's own roles

Polished and ready to flex across questions. Real numbers drop into the [brackets] — the panel scores the Result, so always close with a quantified outcome.

No-downtime delivery

Network refresh in a live 24/7 airport

Likely prompt: Tell us about a complex infrastructure project you delivered.

SituationI owned end-to-end delivery of a network lifecycle refresh across a running international airport that cannot tolerate disruption to live operations.

TaskDeliver the refresh on schedule and budget with zero impact to operations, coordinating multiple vendors and operational stakeholders.

Action
  • Phased the work site-by-site and into low-impact windows so no live operation was ever exposed.
  • Built a rollback path for every device change and a clear go/no-go before each cutover.
  • Drove vendors to milestones and SLAs with regular delivery-assurance checkpoints.

ResultRefreshed [N sites] with [zero] unplanned operational impact, on schedule — [add your metric]. The closest possible analogue to the border-gate estate: edge devices, no tolerance for downtime.

Scale rollout

Separating IT across a national multi-site program

Likely prompt: Describe delivering change across many sites without disruption.

SituationI project-managed the IT separation of a large multi-site organisation as it stood up independently — a time-boxed, national program.

TaskStand up / migrate IT across every site on a hard timeline while keeping each site operational.

Action
  • Ran a wave-based rollout with a repeatable runbook so each site followed a proven pattern.
  • Sequenced dependencies and held site-level go/no-go decisions.
  • Managed vendors and provided project leadership across a dispersed program.

ResultSeparated [all sites] within the program window with continuity maintained — [add your metric]. Proof of phased delivery at national scale, exactly what site-by-site gate upgrades demand.

Secure delivery

Transitioning managed security services with no coverage gap

Likely prompt: How do you make sure security is built in, not retrofitted?

SituationI managed the transition of a portfolio of managed cyber-security services, where any gap in coverage was unacceptable.

TaskTransition every service with no break in security coverage and no service disruption.

Action
  • Treated security continuity as the primary constraint, not a downstream check.
  • Mapped controls and engaged security teams early so requirements shaped the transition.
  • Staged the cutover with assurance at each step.

ResultTransitioned [all services] with no coverage gap — [add your metric]. Shows security delivered as a designed-in outcome, which is the bar here.

Rehearse against this

Mock interview

Each question: what the panel is really assessing, and how to attack it.

Q1Why this agency, and why this role?+

AssessingGenuine motivation + whether you understand their actual problem.

  • Anchor to the mission and to the real delivery challenge — rebuilding critical infrastructure while keeping it running.
  • Bridge to you: cleared, and already delivering both the edge-network and biometric halves of this job.
  • Avoid generic 'great culture' answers.
Q2A project is heading for a slip. What do you do?+

AssessingEarly-warning instinct, integrity, no-surprises reporting.

  • Catch it from leading indicators before it lands.
  • Bring options, not just a problem; re-baseline transparently.
  • Communicate upward early — that is what builds director-level trust.
Q3How do you make sure security is built in, not retrofitted?+

AssessingWhether you understand the regulated, high-assurance context.

  • Security sign-off as a first-class milestone with lead time.
  • Engage assessors at design stage.
  • Name the relevant frameworks naturally, in context — not as a list.
Q4How do you bring structure to an ambiguous program?+

AssessingDirectly answers the review's 'no executable plan' finding.

  • Work breakdown, dependency mapping, a single source of truth, honest status.
  • Transparent prioritisation across a messy portfolio.
  • Frame it as exactly the gap their public evidence points to.

Turn it around

Sharp questions to ask the panel

Good questions signal seniority — that you're assessing the role, not just hoping to pass.

  1. 01How does this team's roadmap connect to the response to the capability review — the end-of-life systems and the push for a single executable plan?
  2. 02Where does this role sit on the keep-the-lights-on vs transformation spectrum, and how is that balance changing?
  3. 03What does delivery success look like for this role in the first 12 months?
  4. 04How mature is the program / portfolio governance the PM would be plugging into?
  5. 05For the gate upgrade, how do you balance throughput gains against availability risk during rollout?

The highest-leverage move

Open anchored to their real problem

“You’re rebuilding the network and compute behind the border gates — high-availability edge systems where an outage becomes a queue, rolled out without disrupting travellers, on an ageing estate your own review said needs a single executable plan. Delivering that kind of change under constraint, without dropping live services, is exactly what I do.”

That framing tells the director you understand their actual world — then you back it with a CV that already fits.

← Back to Home Court Prep