In-depth guides for top tech company interviews. Each guide covers the interview process, question types, preparation tips, and includes real practice questions.
9,429 guides across 7,316 companies · page 69 of 158
SQL practice for Air France data scientist candidates: window functions, funnel and retention queries, joins that quietly drop rows.
Practice explaining analysis before a Ally Financial data scientist interview: the recommendation, the uncertainty, the follow-ups.
Abzooba data scientist prep: probability, sampling distributions, and stating the assumption behind every test you run.
SQL practice for Accor data scientist candidates: window functions, funnel and retention queries, joins that quietly drop rows.
Diagnose a metric move for adjoe data scientist prep: split by segment, rule out a logging change, separate mix shift from behaviour.
Code reading practice for Electric Power Engineers software engineer prep: work out what unfamiliar code does before judging it.
Testing practice for MHP - A Porsche software engineer candidates: the boundaries worth covering, and why flakiness is a real defect.
System design practice for Samyak Infotech software engineer candidates: reach a data model and an API contract, not a box diagram.
Software engineer prep for Sodales Solutions: design exercises weighted toward the constraints of product and business analytics work.
Timed coding practice for State of Illinois software engineer candidates: full attempts under a clock, then scored against a rubric.
Software engineer interview prep for Internshala: original coding, system design and debugging practice, each with a worked solution.
Corbins software engineer prep on partial failure: a timed-out request has an unknown outcome, not a failed one.
Mobicule software engineer prep: algorithm drills where every complexity claim has to name the assumption under it.
Take-home style practice for Nova Ltd. software engineer candidates: a small service, a fixed budget, a written tradeoff.
Alorica software engineer prep on partial failure: a timed-out request has an unknown outcome, not a failed one.
Timed coding practice for Lionbridge software engineer candidates: full attempts under a clock, then scored against a rubric.
Take-home style practice for STEMCELL Technologies software engineer candidates: a small service, a fixed budget, a written tradeoff.
Ehvert Mission Critical software engineer prep on databases: indexes, query plans, and the anomalies an isolation level still permits.
Testing practice for Beroe Inc. software engineer candidates: the boundaries worth covering, and why flakiness is a real defect.
Info Edge software engineer prep on operations: decide what you would need to see to know a release is going wrong.
Amica Insurance software engineer prep on operations: decide what you would need to see to know a release is going wrong.
Debugging practice for Alberta Blue Cross software engineer candidates: reproduce it, narrow it, then change one thing per run.
Testing practice for Axos Business Center software engineer candidates: the boundaries worth covering, and why flakiness is a real defect.
Concurrency drills for Entegris software engineer prep: races, lock ordering, and what a check-then-act sequence assumes.
Software engineer interview prep for Ardagh Group: original coding, system design and debugging practice, each with a worked solution.
Eni Spa software engineer prep: algorithm drills where every complexity claim has to name the assumption under it.
Asahi Kasei software engineer prep on partial failure: a timed-out request has an unknown outcome, not a failed one.
Early Warning Services software engineer prep on partial failure: a timed-out request has an unknown outcome, not a failed one.
Concurrency drills for S&C Electric software engineer prep: races, lock ordering, and what a check-then-act sequence assumes.
Timed coding practice for RATP Dev software engineer candidates: full attempts under a clock, then scored against a rubric.
Concurrency drills for Merck KGaA software engineer prep: races, lock ordering, and what a check-then-act sequence assumes.
Debugging practice for Canadian Tire software engineer candidates: reproduce it, narrow it, then change one thing per run.
Software engineer prep for City of Philadelphia: design exercises weighted toward the constraints of B2B software and infrastructure work.
System design practice for Bombardier software engineer candidates: reach a data model and an API contract, not a box diagram.
Brown Brothers Harriman software engineer prep: algorithm drills where every complexity claim has to name the assumption under it.
Caching practice for Benchmark Electronics software engineer prep: settle the staleness budget before choosing an invalidation strategy.
Debugging practice for IRIS Business Services software engineer candidates: reproduce it, narrow it, then change one thing per run.
Debugging practice for Energy Transfer software engineer candidates: reproduce it, narrow it, then change one thing per run.
Software engineer interview prep for AutoStore (Norway): original coding, system design and debugging practice, each with a worked solution.
Take-home style practice for WeWork software engineer candidates: a small service, a fixed budget, a written tradeoff.
Testing practice for Nala software engineer candidates: the boundaries worth covering, and why flakiness is a real defect.
A prep plan for Riva International software engineer candidates: answer first, read the solution second, repeat the misses later.
Timed coding practice for KGISL software engineer candidates: full attempts under a clock, then scored against a rubric.
Take-home style practice for Maropost software engineer candidates: a small service, a fixed budget, a written tradeoff.
Timed coding practice for Intuitive Machines software engineer candidates: full attempts under a clock, then scored against a rubric.
Concurrency drills for Rev software engineer prep: races, lock ordering, and what a check-then-act sequence assumes.
Take-home style practice for Benifex software engineer candidates: a small service, a fixed budget, a written tradeoff.
Engine software engineer prep on operations: decide what you would need to see to know a release is going wrong.
Code reading practice for Judi Health software engineer prep: work out what unfamiliar code does before judging it.
Debugging practice for Prove software engineer candidates: reproduce it, narrow it, then change one thing per run.
Timed coding practice for Worldpay software engineer candidates: full attempts under a clock, then scored against a rubric.
System design practice for D-Wave Quantum software engineer candidates: reach a data model and an API contract, not a box diagram.
Take-home style practice for Darktrace software engineer candidates: a small service, a fixed budget, a written tradeoff.
Caching practice for Sagesure insurance managers software engineer prep: settle the staleness budget before choosing an invalidation strategy.
Code reading practice for NextEra Energy, Inc. software engineer prep: work out what unfamiliar code does before judging it.
Code reading practice for Bank of Canada software engineer prep: work out what unfamiliar code does before judging it.
Timed coding practice for Bauer Media Group software engineer candidates: full attempts under a clock, then scored against a rubric.
Software engineer interview prep for ARX Robotics: original coding, system design and debugging practice, each with a worked solution.
Take-home style practice for Samsung Semiconductor Inc (US) software engineer candidates: a small service, a fixed budget, a written tradeoff.
API design practice for GM Financial software engineer candidates: compatibility, versioning, and changes you cannot take back.