One candidate reports four rounds for Palo Alto Networks' Cloud & Platform Engineer role: a hiring manager screen, a technical round on infrastructure as code, a stakeholder conversation, and a director round. Another report describes a single, high-level hiring manager discussion.
Candidate reports for this role differ, so prepare for two possible tones. One candidate who received an offer describes four rounds: a hiring manager resume screen, a technical round with team members, a conversation with stakeholders, and a final round with a director. The standout moment was being asked to open a GitHub repo of their own work and walk through the code in detail. The night before, they reread the project and noted what each module did and why it was structured that way. Interviewers pushed on the reasoning behind choices, so naming tools was not enough. They wanted tradeoffs.
The technical round in that account centered on infrastructure as code, because the team does a lot of cloud automation. It also touched on Azure and AWS and on concepts such as service mesh. The stakeholder round felt more like a check on whether the candidate would be easy to work with day to day.
A second candidate, who did not receive an offer, describes a single hiring manager conversation. It stayed high level and focused on past experience, work management and responsibilities rather than technical depth. The team then chose other candidates for its current needs. The two reports don't show which experience is typical, so prepare for both. Have one project you can explain line by line, and have concise stories about ownership and impact ready.
Synthesized from 2 candidate reports by our editorial team.
Candidates report starting with the hiring manager, who goes through the resume and screens for fit. One account describes this as a high-level talk about past experience, work management and responsibilities, with little technical probing. Prepare concise examples of ownership and impact.
2
Technical round with the team
Infrastructure as code, cloud platforms, project code walkthrough
One candidate who received an offer describes a technical round with team members that leaned on infrastructure as code, given the team's cloud automation. It also covered Azure and AWS and service mesh concepts. That candidate was also asked to present a GitHub project and walk through the code in depth, explaining design choices and tradeoffs.
3
Stakeholder conversation
Working-style and collaboration fit
The same candidate describes a third round with stakeholders and people they would work alongside. It felt aimed at judging whether they would be easy to work with day to day. Expect collaboration-focused questions and prepare examples of working across teams.
4
Director round
Final conversation
That candidate's last round was with a director, after which they received an offer. The report gives no detail on the questions asked. Be ready to discuss your projects, decisions and impact at a senior level.
