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 93 of 158
A two-week prep plan for Atos data scientist candidates: write your answer before reading the solution, revisit misses three days later.
Diagnose a metric move for Barbaricum data scientist prep: split by segment, rule out a logging change, separate mix shift from behaviour.
Avid Bioservices Data Scientist interview guide: reported rounds, practice questions with worked solutions and a 7-day prep plan.
Data scientist prep for Attadale Partners: practice defining a product and business analytics metric, picking its guardrails and defending the tradeoff.
Modeling drills for a Atlas Air data scientist interview: baselines, regression interpretation, class imbalance, model defense.
Timed data scientist practice for AXA: short SQL and probability sets run end to end, then scored against a rubric.
Data scientist prep for ASTEK candidates: drill A/B design, power and minimum detectable effect on original exercises.
Timed data scientist practice for Artificial Intelligence Australia: short SQL and probability sets run end to end, then scored against a rubric.
API design practice for SCIEX software engineer candidates: compatibility, versioning, and changes you cannot take back.
Timed coding practice for Atruvia AG software engineer candidates: full attempts under a clock, then scored against a rubric.
PDF Solutions software engineer prep: algorithm drills where every complexity claim has to name the assumption under it.
Causal inference drills for Airwallex data scientist prep: diff-in-diff, matching, instruments, and the limits of observed data.
Diagnose a metric move for adsquare data scientist prep: split by segment, rule out a logging change, separate mix shift from behaviour.
Data scientist prep for Affinius Capital: practice defining a product and business analytics metric, picking its guardrails and defending the tradeoff.
API design practice for MiTek software engineer candidates: compatibility, versioning, and changes you cannot take back.
Levy Professionals software engineer prep: algorithm drills where every complexity claim has to name the assumption under it.
Take-home style practice for PRADCO software engineer candidates: a small service, a fixed budget, a written tradeoff.
Concurrency drills for Knack Consulting Services software engineer prep: races, lock ordering, and what a check-then-act sequence assumes.
MicroTech Systems software engineer prep on operations: decide what you would need to see to know a release is going wrong.
Timed coding practice for Smith + Andersen software engineer candidates: full attempts under a clock, then scored against a rubric.
Debugging practice for Vantive software engineer candidates: reproduce it, narrow it, then change one thing per run.
Debugging practice for TechHighBrows software engineer candidates: reproduce it, narrow it, then change one thing per run.
Leuwint Technologies, software engineer prep on databases: indexes, query plans, and the anomalies an isolation level still permits.
Caching practice for GAO Research software engineer prep: settle the staleness budget before choosing an invalidation strategy.
API design practice for One Big Circle software engineer candidates: compatibility, versioning, and changes you cannot take back.
Timed coding practice for Exponential-e software engineer candidates: full attempts under a clock, then scored against a rubric.
A prep plan for CodeClouds software engineer candidates: answer first, read the solution second, repeat the misses later.
Timed coding practice for Evince Development software engineer candidates: full attempts under a clock, then scored against a rubric.
Everestek software engineer prep on databases: indexes, query plans, and the anomalies an isolation level still permits.
Concurrency drills for DMI software engineer prep: races, lock ordering, and what a check-then-act sequence assumes.
Testing practice for DX Factor software engineer candidates: the boundaries worth covering, and why flakiness is a real defect.
Software engineer prep for Cibirix: design exercises weighted toward the constraints of product and business analytics work.
Testing practice for FCT software engineer candidates: the boundaries worth covering, and why flakiness is a real defect.
API design practice for The Options Clearing Corporation software engineer candidates: compatibility, versioning, and changes you cannot take back.
Software engineer interview prep for Stratpoint: original coding, system design and debugging practice, each with a worked solution.
Debugging practice for Smartodds software engineer candidates: reproduce it, narrow it, then change one thing per run.
API design practice for Covista software engineer candidates: compatibility, versioning, and changes you cannot take back.
Timed coding practice for Delta Energy Systems software engineer candidates: full attempts under a clock, then scored against a rubric.
Code reading practice for Flow software engineer prep: work out what unfamiliar code does before judging it.
Testing practice for Amnet Digital software engineer candidates: the boundaries worth covering, and why flakiness is a real defect.
Software engineer prep for National Bank of Kuwait: design exercises weighted toward the constraints of payments and lending work.
Software engineer interview prep for MedImpact: original coding, system design and debugging practice, each with a worked solution.
Debugging practice for Apps Associates software engineer candidates: reproduce it, narrow it, then change one thing per run.
Caching practice for Impact software engineer prep: settle the staleness budget before choosing an invalidation strategy.
System design practice for Altron Automation software engineer candidates: reach a data model and an API contract, not a box diagram.
Software engineer prep for Ensolum: design exercises weighted toward the constraints of product and business analytics work.
Debugging practice for Doma Technology software engineer candidates: reproduce it, narrow it, then change one thing per run.
Caching practice for Astos Solutions software engineer prep: settle the staleness budget before choosing an invalidation strategy.
API design practice for Annalect software engineer candidates: compatibility, versioning, and changes you cannot take back.
Software engineer prep for AmTrust: design exercises weighted toward the constraints of B2B software and infrastructure work.
Software engineer prep for GEI Consultants: design exercises weighted toward the constraints of product and business analytics work.
Arvind software engineer prep on databases: indexes, query plans, and the anomalies an isolation level still permits.
Caching practice for Collabera software engineer prep: settle the staleness budget before choosing an invalidation strategy.
Teknion software engineer prep on partial failure: a timed-out request has an unknown outcome, not a failed one.
System design practice for LVMH Perfumes & Cosmetics software engineer candidates: reach a data model and an API contract, not a box diagram.
Hargrove Engineers + Constructors software engineer prep on databases: indexes, query plans, and the anomalies an isolation level still permits.
Testing practice for Connection software engineer candidates: the boundaries worth covering, and why flakiness is a real defect.
CapeStart software engineer prep on databases: indexes, query plans, and the anomalies an isolation level still permits.
Timed coding practice for ATG Entertainment software engineer candidates: full attempts under a clock, then scored against a rubric.
Software engineer prep for RTP Company: design exercises weighted toward the constraints of supply chain and logistics work.