Program Manager

Walk me through a program you managed that touched multiple teams, like traders, developers, and quants. How did you pull those groups into one plan?

whether they have real experience coordinating cross-functional stakeholders with different priorities, not just running a single team's backlog

Tell me about a time a project's scope or requirements changed midstream. How did you handle it and what did you do to keep everyone aligned?

comfort with ambiguity and change management in a fast-moving environment, since trading firms shift priorities often

Describe a project where you had to build the requirements, milestones, and resource plan basically from scratch. What was your process?

whether they can actually construct a program plan independently versus just executing a plan someone else built

What's a time you had to deliver bad news, like a slipped deadline, to senior stakeholders? How did you frame it?

transparency and communication skill under pressure, since credibility with traders depends on honest status reporting

Tell me about the most technically complex project you've managed, even if you weren't the one writing code. How did you stay credible with the engineers?

ability to earn trust with technical teams without needing to be an engineer themselves

Tell me about a time your analysis or problem-solving changed the direction of a project rather than just kept it on schedule.

evidence of the analytical, problem-solving contribution the posting emphasizes beyond pure coordination and scheduling

How do you run Agile with a group that includes quants and traders who may not be used to sprint ceremonies?

practical fluency with Agile methodology and the ability to adapt process to a non-traditional engineering culture

How do you track dependencies across teams when a delay on one team, like the tech team, could hold up a trader-facing product?

practical project tracking skills and whether they think in terms of critical path and risk, not just task lists

What tools or methods have you used to keep visibility into a program's health, and how do you decide what to escalate versus handle yourself?

operational maturity around reporting and judgment about when to involve leadership

Say a trading desk wants a new feature live before an upcoming product launch, but the dev team says the timeline is unrealistic given other commitments. What do you do?

how they mediate conflicting priorities between business urgency and technical capacity without just deferring to whoever is loudest

If two stakeholders, say a trader and a quant, disagree on what 'done' looks like for a new feature, how do you resolve that before it becomes a delivery problem?

skill at surfacing and resolving ambiguous requirements early rather than letting disagreements surface late in delivery

Picture a launch date is fixed because of a market or regulatory deadline, but a key feature isn't ready. Walk me through how you'd handle that.

judgment under hard external constraints and ability to prioritize scope versus timeline versus quality

How do you decide what level of process is enough for a given project here, given this is described as an entrepreneurial, fast-moving environment?

whether they can right-size process instead of imposing heavy overhead on a lean, fast culture