interviewing at JPMC in about 3 weeks, SWE role, corporate technology division. trying to build a clearer picture of the current loop before i prep.
if you've gone through a JPMC interview in the last 6-9 months, drop what you saw: role and division number of rounds coding difficulty (easy/medium/hard, LeetCode scale) system design: present or not? behavioral weight: light checkbox or serious debrief? timeline from first contact to offer
any division welcome, not just tech. the more data points the better.
5 replies
de_derek
data engineering, CIB division, interviewed about 4 months ago. 3 rounds: recruiter screen, a take-home SQL + python exercise (2 days, reasonable scope), then a panel with 2 engineers and a hiring manager. no system design in the traditional sense but they did ask me to walk through the architecture of a pipeline i'd built. behavioral questions were there but light relative to the technical portion. offer timeline was 4 weeks from first contact.
ds_dmitri
data science, AWM (wealth management), 5 months ago. 4 rounds. coding was medium SQL and some pandas. modeling discussion was high level: 'walk me through how you'd approach X problem.' no implementation. behavioral was substantial, about 40% of total time. they wanted to hear about stakeholder communication specifically. timeline was 6 weeks because there was a hiring freeze mid-process and nobody told me until i followed up.
numbers_only
6 weeks with a hidden freeze sounds painful. did the recruiter eventually acknowledge it or did you find out some other way?
ds_dmitri
recruiter eventually acknowledged it when i sent a follow-up asking for a status update. said 'we had a brief pause on headcount' and apologized. i don't think they were hiding it on purpose, just not great at proactively communicating. the lesson: follow up at 2 weeks, not 4.
infra_ines
platform engineering, corporate tech, 2 months ago. 3 rounds plus a bonus 'culture fit' chat with a senior manager that wasn't on the original schedule. coding was on the easier side (they cared more about systems), system design was present and detailed (design a rate limiter, then extend it for multi-region). behavioral was real. the culture fit round caught me off guard but it was mostly conversational.