What Amritsar hiring managers actually ask in a first technical interview
Fewer algorithm puzzles than you would expect, more questions about a project you can explain end to end. Our placement desk sat in on a quarter's worth of interviews and wrote down what actually got asked.
Our placement desk sits in on first-round interviews whenever the company allows it. Over a quarter of drives — product companies in Mohali and the Tricity, service firms hiring in bulk, a few remote-first startups — one pattern held almost without exception: the first round is not a test of your syllabus. It is a test of whether you can talk about something you built.
That is good news if you have built something, and it is the whole problem if you have not. Here is what actually came up.
The first ten minutes decide the rest
Nearly every interview opened the same way: tell me about a project you have worked on. Not a puzzle, not a definition. The candidates who did well treated that as the main question rather than a warm-up, because that is what it is — the interviewer picks their follow-ups out of your answer, so you are effectively choosing the topic of your own interview.
What separated a good answer from a weak one was rarely the project's ambition. It was whether the candidate could say what the thing does, who it was for, and what they personally wrote. Three sentences, in plain language, before any technology is named. The people who started with "I used React, Node, MongoDB and JWT" almost always got asked, a minute later, what the project actually did — and had to start again.
The follow-ups, in the order they usually come
- "Why did you choose that over the alternative?" — Any defensible reason works. "It was what the trainer used" does not. If you genuinely picked it because it was familiar, say that and add what you would evaluate differently now.
- "What broke, and how did you find it?" — The single most revealing question in a first round. It is asking whether you have ever debugged something, or only ever followed working instructions. Have one real bug ready: the symptom, how you narrowed it down, what it turned out to be.
- "What would you change if you rebuilt it?" — Interviewers are checking that you can criticise your own work. "Nothing, it works fine" reads as inexperience, not confidence.
- "Which part did someone else write?" — Asked more often than students expect, and answered badly more often than anything else. Claiming a teammate's module is the fastest way to fail a round, because the next question goes into it.
The technical questions are narrower than you fear
First rounds are screens. They are looking for a floor, not a ceiling, and the questions stay close to the work the role actually involves.
Full-stack and web roles
State management and what re-renders when. The difference between authentication and authorisation, usually via "how did you handle login?". Why an API call is in one place rather than another. One or two questions on the database: what your schema looked like, and whether you would still model it that way. Almost nobody asked for an algorithm on a whiteboard; several asked candidates to read a short piece of their own code aloud and explain it.
Data and analytics roles
SQL, and then more SQL. Joins, grouping, and one question that requires a window function or a subquery — asked conversationally rather than as a written test. Then: how did you handle missing data, and how did you know your result was right? The statistics questions stayed practical, with "what does this p-value mean in the context of your chart" far more common than a derivation.
Cybersecurity roles
A scoped scenario — here is a target, what do you do first — followed by questions about the report. What did you write, who was it for, how did you rank severity. Candidates who had written findings documents during training had a visible advantage, because that document is most of the junior job.
Digital marketing roles
A campaign you ran, the budget it ran on, and what you changed after the first week. Then attribution: how did you know the conversion came from that channel? Screenshots of a course dashboard get spotted immediately; a small live budget you actually managed does not.
What loses people the offer
Very little of it is technical.
- A CV listing skills the candidate cannot discuss. If Docker is on the CV, expect one question about Docker. Remove anything you have only watched a video about.
- A project everyone else in the batch also submitted. Interviewers in this region see the same four or five tutorial clones every season and recognise them instantly. Change the domain, add a feature the tutorial did not have, and be able to say which part is yours.
- No questions at the end. Two is enough. Ask what the first three months look like, or what the team is currently struggling with.
- Guessing instead of saying "I don't know". Every interviewer we spoke to said the same thing: a candidate who says "I have not worked with that, but here is how I would approach it" scores better than one who bluffs and gets unwound over the following two minutes.
How to prepare in the two weeks before a drive
- Write your project story down. Three sentences on what it does, then a version you can stretch to five minutes. Say it out loud until it stops sounding rehearsed.
- Re-read your own code. Open the repository and look at the parts you wrote in week two. You will not remember them, and the interviewer will ask about exactly those.
- Prepare one bug and one trade-off. Both come up almost every time. Having them ready converts two hard questions into two prepared answers.
- Trim the CV to what you can defend. One page. Project first, skills second, certificates last.
- Do one mock interview with someone who will interrupt you. The pressure is in the follow-ups, not the first answer, and that is the part practising alone does not simulate.
The thing almost nobody asked about
Certificates. In an entire quarter, we did not see a single interviewer ask a candidate to produce one, and only a handful referred to a course name at all. The certificate gets you through the CV screen; the project gets you through the interview. That is the whole hierarchy, and it is worth knowing before you choose where to put your effort during training.
If you are preparing for a drive and want a mock interview with someone who will push back on your answers, the placement desk runs them for current students and alumni — get in touch and we will put one in the calendar.
