Jane Street · Primly Community

Jane Street technical program manager (TPM) interview: notes from a non-US candidate

intl_isla · 4 replies

wrote this up mostly because i'm uk-based and the jane street tpm process for london roles is a bit different. but the structure translates, so hopefully useful even if you're applying to the ny office.

what the role is: jane street's tpm function is real program management, not watered-down project coordination. you're managing complex technical programs across engineering teams, often with hard delivery constraints and stakeholders who are very technically sophisticated. if you come from a PM background without strong eng depth, the technical expectations will be a stretch.

the interview loop (london, 2026):

first round: 60-minute conversation with a hiring manager. split between background and two behavioral-style questions. the behavioral questions were specific and they followed up hard. "you said you escalated to leadership, what specifically did you say, what was the response, and what would you do differently." no surface-level STAR accepted here.

second round: technical program management case. they gave me a scenario involving a multi-team engineering project with a dependency problem and a deadline. questions: how do you structure the program, how do you surface and manage the dependency, what do you do when team b misses their milestone and team c is now blocked. 45 min exercise, then 15 min debrief.

third round: two back-to-back interviews with senior engineers. they asked about technical architecture decisions i'd overseen, how i handled engineers who disagreed with a timeline, and one round that was mostly about how i'd learn a new technical domain quickly. they were probing whether i could hold my own in a room of smart engineers.

what they seem to want: someone who can figure out what "done" means when it isn't well-defined genuine comfort with technical ambiguity, not just tolerance communication style that is direct and precise. not the consultancy version of "clear communication."

what surprised me: no slide presentation, no formal take-home. everything conversational. they did not ask "where do you see yourself in 5 years" or any variant they asked me what i found genuinely hard about my current job. felt honest, not a trap.

still in process so can't share outcome. but the rounds themselves felt like talking to people who were good at what they do, which is honestly rarer than it should be.

4 replies

jordan_pm

the "what do you find hard" question is one of my favorites as an interviewer and so rare to see. it tells you so much more than the standard strength/weakness framing. sounds like a thoughtful loop. good luck.

returner_ren

the dependency / blocked team scenario is basically what real TPM work looks like every week. if you can handle that exercise well it probably means you'll handle the actual job. did they give you time to ask clarifying questions before the case started?

intl_isla

yes, they encouraged it actually. i asked about team sizes, which teams had done this kind of integration before, and whether there was a fixed external deadline or internal. those questions changed my approach meaningfully. i think not asking would have been a bad signal.

careerveteran

london JS is underrated as an option. compensation is different obviously but the work is the same caliber and the visa situation is cleaner for non-us candidates.