Company
Interview guides for the companies people prepare for most. Each guide explains how hiring works, what every level is expected to show, how the rounds differ by role, and gives practice questions with strong answers that you can filter by role and level. Use them alongside the role roadmaps and the practice workspaces on this site.
These are independent guides written by CodingInterview.net. We are not affiliated with any company listed. Processes change and vary by team and country, so confirm details with your recruiter.
Choose a company
How the loops compare
| Company | Typical length | Rounds | What stands out |
|---|---|---|---|
| 4–8 weeks to a hiring decision, plus 1–6 weeks of team matching | Recruiter call, 1–2 technical screens, 4–5 interviews in the final loop | Interviewers do not decide; a hiring committee reviews written feedback. Code is often written without running it. |
Find guides for your role
Every company guide has a section for each role it hires for. Jump straight to yours.
| Role | Company guides | Roadmap |
|---|---|---|
| Software Engineer | Software Engineer roadmap | |
| Front End Engineer | Front End Engineer roadmap | |
| Machine Learning Engineer | Machine Learning Engineer roadmap | |
| Data Scientist | Data Scientist roadmap | |
| DevOps and SRE Engineer | DevOps and SRE Engineer roadmap | |
| Product Manager | Product Manager roadmap | |
| Engineering Manager | Engineering Manager roadmap |
Levels across companies
Level names differ, but the expectations line up roughly. Use this to work out which level to target and which interview bar you will meet. Mapping is approximate; offers depend on how you perform, not only on years of experience.
| Company | Entry level | Mid level | Senior | Staff and above |
|---|---|---|---|---|
| L3 · Software Engineer II | L4 · Software Engineer III | L5 · Senior Software Engineer | L6 · Staff Software Engineer, L7 · Senior Staff Software Engineer |
How to prepare for a specific company
- Build the base first. Every company tests the same core skills. Follow the roadmap for your role and practise every day in the coding, SQL and system design workspaces.
- Learn the loop. Read the company's hiring process and the round list for your role, so nothing on the day is a surprise.
- Target the right level. Read what your level must show. Senior loops weigh design and ownership far more than entry-level loops.
- Prepare stories for the company's values. Most companies score behaviour against a written set of principles. Prepare two or three stories for each one.
- Rehearse under real conditions. Answer the questions in the guide out loud with a timer, then run full mock interviews in the last two weeks.
- Track progress. Use the study plan and progress page to keep a daily habit and review weak topics.
FAQ
Do companies really ask different questions?
Less than most people think. Coding rounds everywhere test the same data structures and patterns, and system design rounds test the same building blocks. What differs is the format, the weight given to each round, the level bar and the behavioural framework. Learn the shared skills first, then spend the last two or three weeks on company-specific preparation.
Should I memorise questions reported by other candidates?
No. Interviewers rotate questions and change details, and they notice rehearsed answers. Questions in these guides are written to show the style and difficulty of each round, so that you practise the thinking rather than the answer.
How many companies should I interview with at once?
Three to six at a time works well for most people. Start with one or two companies you care less about, to warm up, and schedule the ones you want most for when you are at your sharpest. Running loops close together also helps when comparing offers.
Which level should I apply for?
Look at the level descriptions in each guide and match them to what you do today, not only your years of experience. If you already lead designs and mentor others, aim for senior. A recruiter will usually suggest a level after the first call; you can ask how it was decided.