Private prep · for Gaz

Project Manager, Connectivity & Compute

Interviewing with the Director of Connectivity & Compute, Technology, Data & AI Group, Department of Home Affairs — for a PM role upgrading the Border Force passport-scanning systems. Everything below is built around one idea: walk in already understanding their real problem.

Jump to mock interviewTap any tile or term for detail · sources open in a new tab

The one thing to internalise

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

In 2024 the Australian Public Service Commission published a Capability Review of Home Affairs that said, bluntly, the department has no single, shared, executable plan for its ICT or data, is resourced for ‘maintenance’ rather than transformation, and runs an ageing estate where a large share of systems are already end-of-life. Connectivity & Compute is the infrastructure backbone they are now rebuilding — while it is still running national-security-critical services.

Every answer Gaz gives should implicitly speak to that problem: delivery certainty, under constraint, without dropping the ball on live services.

The actual program

Upgrading the border passport-scanning systems

This is the SmartGate / eGate and primary-line passport-reader estate the Australian Border Force runs at international airports and seaports. The Gen 3 biometric gates are being rolled out and expanded across the major airports, and the border is moving toward contactless, passport-free processing that matches a traveller’s face against their Advance Passenger Processing image. Under the hood, every gate parses the passport, reads the ePassport chip, validates its signature against the ICAO Public Key Directory, and checks the traveller against backend systems — in seconds.

Why this lands squarely in Connectivity & Compute: the gates are edge devices that are useless without rock-solid connectivity to backend compute. A gate that drops out becomes a queue at the border — which becomes a media story and a question at Senate Estimates. Gaz would be delivering availability, throughput and security at the most visible edge of the department.

Why you fit — make these explicit

You are not translating a generic CV. You are close to a bullseye.

Most candidates have to argue they could learn this domain. You have already done its two hardest halves — biometric facial recognition and airport network infrastructure — and you are already cleared. Lead with these connections; do not make the panel join the dots.

  • NV1 clearance — already held. Home Affairs roles need clearance. You hold NV1 now, so there is no vetting delay and no risk — a concrete reason to prefer you over an uncleared candidate.
  • Automated Facial Recognition experience. The exact biometric tech behind contactless, passport-free SmartGate processing. This is your single strongest, most specific differentiator.
  • Senior Infrastructure PM at Melbourne Airport (now). Network lifecycle / Cisco refresh in a live 24/7 airport — the same high-availability, can't-disrupt edge environment as the border gates.
  • ADF / government delivery. You already speak security, governance and classified-environment delivery — no public-to-public-sector translation needed.
  • Networks, Cloud, Cyber, Infrastructure + CCNA. Squarely the Connectivity & Compute domain, with genuine network depth most PMs lack.
  • Proven multi-site national rollouts. 111 sites (Team Global Express / Toll separation) and 18 cyber-security services (Bupa) — phased delivery at scale, exactly what airport-by-airport gate upgrades need.

Your one-liner: an NV1-cleared infrastructure PM who has delivered both facial-recognition and live airport-network programs — i.e. you have already done the two halves of this job.

Know the numbers

Four facts that frame the whole conversation

Tap any tile for the detail and the source.

The patch

What 'Connectivity & Compute' actually covers

Know the layer you would be building in — it is the physical and platform foundation everything else runs on.

Connectivity

Wide-area and local networks, SD-WAN, internet and secure gateways, telecommunications, links to overseas posts and to the border — airports and seaports — plus the resilience and redundancy of all of it.

Compute

Data centres, government hosting, hyperscale and sovereign cloud, the server and storage estate, end-user compute — and increasingly the compute capacity to run AI workloads on sensitive government data.

Likely ‘infrastructure build-out’ projects: data-centre migration and consolidation, network refresh, gateway consolidation, cloud migration, replacing end-of-life kit, and standing up compute for AI.

What the director will actually care about

Seven deliverables — in rough priority order

Directors are EL2s accountable upward to a Deputy Secretary and, ultimately, to Senate Estimates. They want a PM who removes risk and surprise from their world. Tap each for the detail and how to demonstrate it.

Sound plugged-in

Strategic objectives to weave in

He does not need to recite these. Landing two or three naturally is powerful.

ICT modernisation / retiring end-of-lifeDirectly answers the Capability Review's headline finding.
A single, prioritised technology roadmapThe exact thing the review said was missing.
Sovereign, secure, resilient compute & connectivityNational priorities — sovereignty and resilience are front of mind across government.
Enabling AI on sensitive government dataHome Affairs has openly said it wants this; it needs compute and connectivity underneath.
More value within constrained fundingEfficiency, prioritisation and value-for-money are constant APS pressures.

Context worth knowing: iTnews — Home Affairs to run AI on sensitive government data , National expectations for data centres & AI infrastructure (2026) and Microsoft — multibillion-dollar Australian AI infrastructure investment .

Vocab cheat-sheet

Speak the language — tap any term

Use these naturally and in context. Do not recite them as a list — that reads as memorised.

Stories locked and loaded

Six model STAR answers

Have these polished and ready; flex them across questions. Tap to open the full model answer, then swap in your real projects and numbers.

Rehearse against this

Mock interview

Each question: what the panel is really assessing, and how to attack it. Expand them one at a time and practise out loud.

Q1Why Home Affairs, and why this role?+

AssessingGenuine motivation + whether you understand their actual problem.

  • Mission: border, national security, keeping Australians safe — you want work that matters.
  • The challenge: rebuilding critical infrastructure while keeping it running. Say you want the hard problem.
  • Bridge to you: NV1-cleared, already delivering airport network infrastructure and facial recognition — this role is where your two specialties meet.
  • Avoid generic 'great culture' answers — anchor to the real delivery challenge.
Q2Tell us about a complex infrastructure project you delivered.+

AssessingDelivery certainty, scale of complexity, and a measurable result.

  • Lead with the constraint that made it hard (deadline tied to money, no-downtime, security).
  • Spend most of the answer on YOUR specific actions.
  • End with a number — % time/cost, systems migrated, uptime, $ value.
Q3A 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.
Q4How do you manage an SI underperforming against milestones?+

AssessingCommercial spine + relationship management.

  • Use the contract and make consequences explicit and unemotional.
  • Diagnose the real cause before demanding speed.
  • Escalate proportionately; preserve the relationship.
Q5Stakeholders all think they are the priority. How do you handle it?+

AssessingWorking across a siloed org (a known Home Affairs weak spot).

  • Transparent, criteria-based prioritisation over loudest-voice-wins.
  • Use governance forums for senior arbitration on contested calls.
  • Keep everyone informed of where they sit and why.
Q6How do you make sure security is built in, not retrofitted?+

AssessingWhether you understand the Home Affairs security context.

  • Security sign-off as a first-class milestone with lead time.
  • Engage assessors / IRAP at design stage.
  • Name PSPF, ISM, Essential Eight, HCF naturally — not as a list, in context.
Q7How do you bring structure to an ambiguous program?+

AssessingDirectly answers the Capability Review's 'no executable plan' finding.

  • Work breakdown, dependency mapping, single source of truth, honest RAG.
  • Transparent prioritisation across a messy portfolio.
  • Frame it as exactly the gap their public evidence points to.
Q8Tell us about delivering bad news to a senior leader.+

AssessingIntegrity and judgment under pressure.

  • No surprises; bring it early.
  • Lead with options and a recommendation, not just the problem.
  • Show you protect the leader's ability to make a good decision.
Q9How would you roll new gate software / hardware across airports without disrupting travellers?+

AssessingWhether you grasp the border's no-downtime, high-visibility reality.

  • Phased rollout — pilot at one airport/terminal, prove it, then scale.
  • Deploy in low-traffic windows; never during a peak-travel surge.
  • Keep manual/primary-line fallback ready so a gate fault never becomes a closed border.
  • Define rollback per site and a clear go/no-go before each wave.
Q10These systems handle biometric and passport data. How does that shape your delivery?+

AssessingAwareness of privacy, security and public trust at the border.

  • Privacy and security as designed-in gates: privacy impact assessment, APP/PSPF/ISM, IRAP early.
  • Data minimisation and clear handling of facial images and chip data.
  • Frame it as protecting public trust, not just ticking compliance.
Q11How do you manage the OEM / gate vendor and integration with systems like the ICAO PKD?+

AssessingVendor assurance in a specialised, standards-bound domain.

  • Hold the gate OEM to milestones, SLAs and interoperability standards (ICAO Doc 9303).
  • Treat external dependencies (PKD validation, backend checks) as managed risks with owners.
  • Test end-to-end — reader to backend to result — not just the box in isolation.

Turn it around

Sharp questions for Gaz to ask the panel

Good questions signal seniority and that he is assessing the role, not just hoping to pass.

  1. 01How does this branch's roadmap connect to the department's response to the 2024 Capability Review — particularly 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. 03How are you balancing hyperscale cloud against sovereign / PROTECTED hosting as compute demand grows for AI?
  4. 04What does delivery success look like for this role in the first 12 months?
  5. 05How mature is the program / portfolio governance the PM would be plugging into?
  6. 06For the passport-scanning upgrade, how do you balance throughput gains against availability risk during rollout across airports?
  7. 07Where is the gate estate heading — contactless / passport-free processing — and what does that mean for the connectivity and compute behind it?

The highest-leverage move

Open anchored to their real problem

“You’re upgrading the passport-scanning systems at the border — high-availability edge devices where a gate down becomes a queue, rolled out across airports without disrupting travellers, on an ageing estate a Capability 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 he understands their actual world — then he backs it with a CV that already fits. Bring the NV1 clearance up early (it removes real risk and delay for them). Mirror whichever methodology the ad names — he is covered (PMP, PRINCE2, PMBoK, ITIL, CSM) and CCNA gives him network credibility most PMs lack. The only watch-out: do not over-claim depth on the truncated pieces — speak confidently to what he actually delivered.

Do the homework

Sources

All public. Each opens in a new tab.