// prepare, then crack it
How to prepare for a tech interview
Start with the company: engineers share the rounds and the questions they were asked on each company page. Then use the plan below.
The usual interview rounds
- Online testAptitude, coding (1 to 3 problems) or a MCQ on your stack. Practise timed problems; read every question fully before coding.
- Technical 1Your core stack and the projects on your resume. Be ready to explain every line on your resume and why you chose that design.
- Technical 2 / codingLive coding or a deeper dive: data structures, SQL, debugging a snippet, or a small design. Think aloud and test your code with an example.
- System design (3+ years)Design a service end to end: requirements, APIs, data model, scaling, failures. Start simple, then grow it.
- Manager roundHow you work: a hard bug you fixed, a conflict, an estimate that went wrong, how you mentor. Use real stories with numbers.
- Client round (services)For a client project: communication, domain knowledge and confidence. Ask about the project; it shows interest.
- HR roundNotice period, current and expected salary, offers in hand, joining date, relocation. Have clear, honest answers ready.
Every company is different. See real rounds from people who interviewed there on Companies.
A 4-week plan
Week 1: basicsRevise your main language and framework from the ground up. Write small programs; don't only read.
Week 2: problem solvingOne or two coding problems a day: arrays, strings, hashing, two pointers, trees, SQL joins and group by.
Week 3: projects and designWrite a one-page story for each project: problem, your part, tech, result. Practise one system design a day if you have 3+ years.
Week 4: mock and polishTwo mock interviews with a friend, timed. Prepare HR answers. Read the company's rounds and questions on its company page.
What to revise for your role
Java / .NET backendOOP, collections, multithreading, Spring Boot or ASP.NET Core, REST, SQL, transactions, microservices, caching.
FrontendJavaScript (closures, promises, event loop), React or Angular state and rendering, CSS layout, performance, accessibility.
Data engineeringSQL (window functions), Python, Spark, data modelling, pipelines (ADF, Airflow), file formats, slowly changing dimensions.
Cloud / DevOpsNetworking basics, Linux, Docker, Kubernetes, Terraform, CI/CD, monitoring, one cloud (AWS, Azure or GCP) in depth.
QA automationTest design, Selenium or Playwright, API testing, a framework you built, CI runs, flaky test fixes.
Architect / leadTrade-offs, non-functional requirements, migrations, cost, security, team practices; real decisions you made and why.
On interview day
- Share your Digital Resume link so everyone sees the latest version.
- Test your camera, mic and internet 15 minutes before an online round.
- Keep a notebook for design rounds, and water.
- Ask one good question at the end: the team, the project, how success is measured.
- Write down the questions you were asked the same day, while you remember them.
After the interview
Help the next engineer: share your rounds and questions on the company page. It stays anonymous and is checked before it shows.