Startups & finance interview prep
These two sit together because they are the two most commonly misread. Candidates bring a big-tech script to a startup and sound theoretical; they bring startup informality to a bank and sound unreliable. The preparation that works is close to opposite in each.
Jump to: Early-Stage Startup Β· JPMorgan Chase
π€ Run a mock interview free βWhat preparation actually looks like here
Startups hire for range and autonomy, and they are testing it live
The process is faster, less structured and often includes a paid or unpaid take-home. What they are really asking is whether you can operate without scaffolding: no dedicated QA, no platform team, ambiguous requirements. Evidence of shipping something end to end β including the unglamorous parts, the deployment, the on-call, the bug you fixed at midnight β outweighs algorithmic polish.
At a startup, your questions are half the interview
Runway, current revenue, why the last person left, what the first ninety days look like. Founders read good questions as commercial judgement, and the absence of them as someone who has not thought about whether the company will exist in two years. This is also genuinely for your benefit: you are the one taking the risk.
Banks screen for rigour and for what happens when you are wrong
Expect structured competency questions, sharp attention to accuracy, and questions about controls, auditability and regulation. Saying you moved fast and fixed it later is a red flag rather than a virtue. Precision about what you did and did not personally verify matters more than enthusiasm.
Finance rounds test composure deliberately
Being pressed on a number, asked to defend an assumption, or interrupted mid-answer is often the assessment itself β the job involves defending your work to people who are sceptical and senior. Staying calm, conceding a fair point and holding a defensible one is the behaviour being measured.
Both care intensely about why you, why here, why now
In neither case will a generic answer survive. At a startup it signals you are treating them as a fallback. At a bank it signals you have not thought about a long-horizon commitment. Name something specific and true about the company and connect it to what you want next.
The take-home is where startup processes are won and lost
Most early-stage processes include one, and most candidates treat it as a coding test. It is closer to a work sample: they are reading how you scope something underspecified, what you chose not to build, and whether you left the codebase in a state someone else could pick up. Include a short README saying what you deliberately skipped and why, and what you would do with another day. That single file routinely separates two otherwise identical submissions, because it is the only evidence of judgement in the whole package.
Ask a startup about runway before you ask about equity
Equity is the thing candidates fixate on and the thing least likely to be worth anything. Runway, burn and the path to the next raise determine whether your options ever vest, and asking about them reads as commercial literacy rather than distrust. If the answer is evasive, that is itself the answer. Get the strike price, the total outstanding shares and the vesting schedule in writing β a percentage with no denominator is not information.
In finance, expect your CV to be verified line by line
Background checks are genuinely thorough and regulated: dates, titles, qualifications, sometimes credit history. An embellishment that would go unnoticed elsewhere becomes a withdrawn offer here, often after you have resigned from your current job. Anything you cannot substantiate should come off the CV before you apply, not after someone asks.
The pace question is the real fit question, in both directions
Startups ask about ambiguity tolerance because the job has no map; banks ask about process because the job has a great deal of it. Answer honestly rather than strategically. Someone who needs structure will be miserable at a fourteen-person company however well they interview, and someone who resents sign-off chains will not last in a regulated environment. This is the rare interview question where the candidate has more to lose from a persuasive answer than a true one.
Preparing for a startup and preparing for a bank pull in different directions β proof you can operate unsupervised, versus proof you are rigorous and predictable under scrutiny. Decide which you are actually interviewing for before you write a single answer.
Company by company
Early-Stage Startup
Startup interviews move fast and value range: can you build, own ambiguity, and wear multiple hats? Expect practical exercises over trivia.
The process
- βΊFounder/HM screen
- βΊA practical take-home or live build
- βΊTeam / culture-fit conversations
Question types
- βPractical build (close to real work)
- βProduct & ownership thinking
- βCulture / motivation fit
How to prepare
- π‘Show you can ship end-to-end and own ambiguity.
- π‘Ask sharp questions about the product and market β curiosity signals fit.
- π‘Be honest about what you'd need to learn; startups value self-awareness.
JPMorgan Chase
JPMorgan interviews are rigorous, testing coding fundamentals, financial-domain knowledge (for finance roles), and risk awareness. Expect algorithmic coding, system design for financial systems, and behavioral questions on ownership.
The process
- βΊOnline coding assessment (1-2 problems)
- βΊPhone screen (coding + domain)
- βΊOnsite: hard coding + system design
- βΊDomain interview (financial products, risk)
- βΊBehavioral / culture round
Question types
- βCoding (hard: trees, graphs, DP, design patterns)
- βSystem design (trading, payments, fraud detection)
- βFinancial domain (trading logic, risk β varies by role)
- βBehavioral (ownership, risk awareness, precision)
How to prepare
- π‘Prepare hard-level algorithms and fault-tolerant system design.
- π‘Learn financial-domain basics even from a non-finance background.
- π‘Emphasize correctness and edge-case handling β in finance, bugs cost money.
Based on publicly documented formats; interviews change over time. This is preparation guidance, not leaked questions.