The Tech Interview Process Explained: From Application to Offer

The big picture

Most tech hiring follows the same broad path, whether the company is a large IT services firm, a startup or a global product company. The details differ, but if you understand the stages, nothing will surprise you, and you can prepare specifically for each one.

Stage 1: finding and applying

What happens: you find an opening, apply through the company's careers page, a referral, a job site or your campus placement cell.

What to do:

• Read the full description: skills, eligibility, experience range and location.
• Apply through official channels. Genuine employers never charge for applications, interviews or offers (scam red flags).
• Tailor your resume to the role, with the right keywords (ATS-friendly resume checklist).
• If possible, get a referral; it often gets your resume read (referral message templates).

Browse live openings on our fresher, experienced and internship pages.

Stage 2: resume screening

What happens: a recruiter or an applicant tracking system (ATS) checks whether your skills and experience match. You may hear back in days or weeks, or not at all.

What to do: one clear page for freshers, achievements instead of duties, no spelling errors, links to GitHub and LinkedIn. Follow up politely once after a week if you have a contact.

Stage 3: online assessment

What happens: a timed test, usually proctored. It may include aptitude and reasoning, English, technical multiple-choice questions, and coding problems.

What to do: practise on similar platforms, check your camera, microphone and internet beforehand, and read each section's rules. See aptitude test preparation and online coding assessment tips.

Stage 4: technical interview(s)

What happens: one to four rounds, 30–60 minutes each. Typical content:

• Resume deep-dive: projects, technologies, your exact contribution
• Fundamentals: language, OOP, DBMS, OS, networks (core CS subjects)
• Coding: a problem on a shared editor or whiteboard (DSA plan)
• Design (experienced roles): system design or object-oriented design

What to do: think aloud, ask clarifying questions, start simple, test with examples. Use the technical interview checklist.

Stage 5: managerial or behavioural round

What happens: a hiring manager checks how you work: teamwork, ownership, handling deadlines and conflict, and learning from mistakes.

What to do: prepare six or so real stories and structure them with STAR (guide).

Stage 6: HR round

What happens: motivation, expectations, location, notice period or joining date, background and documents. For some companies this includes salary discussion.

What to do: answer honestly and clearly (HR questions and sample answers). Know your minimum acceptable salary and your joining flexibility.

Stage 7: offer, background check and joining

What happens: you receive an offer letter. Employers often run background and document verification (education, previous employment, ID). Joining can take weeks or months for campus hires.

What to do:

• Read the offer: role, location, salary components, probation, notice period, any service agreement or training bond.
• Negotiate politely when you have a competing offer or a clear case (salary negotiation guide).
• Provide truthful information; discrepancies found during verification can cancel offers.
• Keep communication professional until the joining date.

How long it takes

• Mass campus and off-campus drives: days to a few weeks for tests and interviews, then a long wait for onboarding
• Product companies and startups: two to six weeks from first call to offer is common
• Senior or specialised roles: sometimes longer

Delays are normal. Keep applying elsewhere while you wait.

Staying organised

Keep a simple spreadsheet: company, role, date applied, stage, next step, contacts and deadlines. Send a short thank-you message after interviews. If you are rejected, politely ask whether the recruiter can share feedback, then use it.

Common mistakes

• Applying everywhere with the same resume
• Preparing for one stage only (usually coding) and neglecting communication
• Not researching the company at all
• Accepting offers without reading the terms

Where to go next

If you are a fresher, start with how to crack your first tech interview in 30 days. If you already work, read the 30-day job-switch plan.