--- title: Why Did You Choose This Branch? Interview Answer description: How to answer why did you choose this branch in an interview — honest scripts for CSE, ECE, mechanical and civil, including when you did not choose it at all. url: https://usegreenroom.app/blog/why-did-you-choose-this-branch-interview-answer last_updated: 2026-08-01 --- ← Back to blog India · Campus # "Why did you choose this branch?" How to answer August 1, 2026 · 11 min read ![Why did you choose this branch interview answer — guide cover from Greenroom, the AI mock interviewer](/assets/blog/why-did-you-choose-this-branch-interview-answer-hero.webp) "Why did you choose computer science?" She said she had been fascinated by computers since childhood. The interviewer asked what she used to build back then. There was nothing back then. There had been a rank, a counselling round, and a seat, which is how the overwhelming majority of Indian engineering branches get chosen, and which is a completely acceptable answer that almost nobody gives. **"Why did you choose this branch?"** is one of the most common HR questions in Indian campus and fresher interviews, and it is asked in an unusual spirit: the interviewer knows how counselling works. They are not testing whether you had a calling at fourteen. They are checking whether you engaged with what you ended up doing, and whether you can talk about your own decisions without inventing a story. Here is how to answer honestly, by situation. ## What the interviewer is really checking - **Did you engage?** Four years of a subject, and whether anything in it caught you. This is the actual question. - **Can you be honest about a mundane origin?** Candidates who invent a childhood passion get caught by one follow-up, and the invention costs more than the mundane truth ever would. - **Does the branch connect to the role?** Especially when it does not — an ECE graduate applying for a software role gets this question with a sharper edge, and needs a real bridge. - **Do you make decisions or drift?** A branch you did not choose is fine. Four years of not noticing what you were studying is less fine. ![Diagram of the answer structure for why did you choose this branch — the honest origin, what you actually found interesting once inside, and the evidence that you engaged with it](/assets/blog/why-did-you-choose-this-branch-interview-answer-diagram.webp) The origin story matters far less than what you did once you were there. Most candidates spend the whole answer on the first part. ## The three-part structure **Part one: the honest origin, in one sentence.** Including the mundane version. "Honestly, it was the branch my rank got me at that college." That sentence is fine. It is also disarming in a good way, because interviewers hear the fabricated version constantly. **Part two: what actually caught your interest once you were inside.** This is where the answer lives. Name a specific subject, lab, project or moment. "The data structures course in the third semester was the first time a subject felt like solving something rather than memorising it." Specific beats general by a wide margin. **Part three: the evidence.** What you did because of that interest. A project, an internship, a specialisation, a certification, hours spent on something nobody assigned you. "That's why I picked the machine learning elective and built the recommendation project on my resume." Then optionally a clause bridging to the role. Thirty seconds total. **The core rule:** answer the origin in one sentence and spend the rest on what you did afterwards. The interviewer is asking about you now, not about a counselling portal in 2022. ## Scripts by situation **CSE or IT, and you genuinely like it.** Easy, but avoid the generic. "I was reasonably sure I wanted CSE, mostly because a cousin was doing it and it looked interesting rather than from any deep insight. What actually held me was the algorithms course — I ended up doing competitive programming for a year and that's still the part of the work I enjoy most." **You did not choose it; the rank did.** "I'll be honest — mechanical was the seat I got, and I did not choose it in any meaningful sense. What surprised me is that the thermodynamics and design courses were genuinely interesting, and the CAD work is where I first enjoyed being precise about something. The reason I'm here is that I found the same thing in programming during my third year, which is when I started building properly." **You switched fields — ECE, mechanical, civil applying to software.** This is the version that gets probed hardest, so lead with the evidence rather than the apology. "I studied electronics, and I liked the embedded side of it. Around the third year I started writing more software than hardware for our projects, and it became clear that was the part I was actually good at. Since then I've built three projects, done a six-month internship in backend development, and my final-year project was entirely software. The electronics background is not wasted — it's why I'm comfortable at the low level — but software is a deliberate choice, not a fallback." Note the structure: honest origin, the turning point, concrete evidence, and one sentence pre-empting the real concern, which is whether you will leave for a core role later. **You dislike your branch.** Do not say that, but do not fake enthusiasm either. Focus entirely on part three. "The branch itself was not the part I connected with, but the programming courses inside it were, and that's what I built on — here's what I did with it." Honest without being negative. Our [how to explain your project in an interview](/blog/how-to-explain-your-project-in-an-interview) guide covers presenting that evidence. **You are a non-engineering graduate in tech.** Same shape, more evidence required. Name the transition point, what you have built, and what you have completed. Certifications help at the resume stage; a deployed project helps in the room. Our [how to get a job without experience](/blog/how-to-get-a-job-without-experience) guide covers building that evidence. ## The related questions in the same family Prepare these together, because they come as a set in Indian HR rounds: - **"Why did you choose this college?"** Same shape: honest, brief, then what you did there. - **"Why are you moving away from your core branch?"** Answered above — evidence first, and pre-empt the retention concern. - **"Would you go back to your core field if you got a chance?"** Be honest but decisive. Hedging here creates the exact doubt the interviewer is probing. If you would not, say so plainly and briefly. - **"Why should we hire someone from a different branch?"** Turn it into what the background gives you, with one concrete example rather than a claim about being a fast learner. Our [why should we hire you](/blog/why-should-we-hire-you-answer) guide covers the framing. ## What not to say - **A childhood-passion story you cannot support.** One follow-up — "what did you build then?" — and the answer collapses. - **"Because it has good scope and placements."** True for many people and dead honest, but it says nothing about you and it is the answer everyone gives. If money and stability genuinely drove the choice, say it once and move quickly to what you found interesting. - **Criticising your college or the counselling system.** It reads as blame, and it takes time away from part three. - **Reciting the branch's syllabus.** They have read it. - **A long answer.** Thirty seconds. This is not the question that decides the interview, and treating it as though it is makes you sound anxious. ## Where each prep option actually helps - **Your own transcript and project list** — the raw material for part three is already there. Pick the two things you did that were not assigned to you. - **Your seniors and placement cell** — for knowing which companies ask this with a sharper edge, particularly for cross-branch applicants. - **ChatGPT** — will produce a fluent childhood-passion narrative, which is the single wrong answer for this question. Use it to structure your real one instead. - **Greenroom** — the spoken layer. [Ari, the AI interviewer](/) runs HR rounds and asks the follow-up — "so what did you build then?" — which is exactly where the invented version breaks. Honest tradeoff: this is a thirty-second question, so weight your practice accordingly. Our [campus placement interview guide for India](/blog/campus-placement-interview-guide-india) covers the full HR round and our [fresher interview questions and answers](/blog/fresher-interview-questions-and-answers) guide covers the ones with more weight. ## Frequently asked questions ### How do you answer why did you choose this branch? Give the honest origin in one sentence, then spend the rest of the answer on what actually caught your interest once you were studying it, and finish with concrete evidence of that interest such as a project, an elective or an internship. Thirty seconds is the right length. The interviewer knows how counselling works and is checking whether you engaged with the subject, not whether you had a calling at fourteen. ### What if you did not choose your branch and got it through counselling? Say so plainly — it is a completely acceptable answer and interviewers hear the fabricated alternative constantly. Follow it immediately with the specific subject, lab or project inside the branch that did hold your interest, and what you did because of it. Honesty about a mundane origin plus evidence of engagement outperforms an invented passion that collapses at the first follow-up. ### How do you explain switching from ECE or mechanical to software? Lead with evidence rather than apology. State the origin briefly, name the turning point where you started writing more software than hardware, then list what you have actually built — projects, an internship, a final-year project — and close with one sentence pre-empting the real concern, which is whether you will leave for a core role later. Framing the original background as useful rather than wasted also helps. ### Is it OK to say you chose your branch for scope and placements? It is honest and it is true for a great many people, but it says nothing about you and it is the most common answer, so it should take one sentence at most. Say it once and move quickly to what you found genuinely interesting during the degree and what you did about it, because that second part is what the question is actually for. ### What should you not say when asked why you chose your branch? Avoid a childhood-passion story you cannot support with anything you built, criticism of your college or the counselling system, reciting the syllabus back to someone who has read it, and answers longer than about thirty seconds. The single most damaging option is an invented origin, because the follow-up asking what you built at that time is standard and immediate. ### Will they ask if you would return to your core branch later? Cross-branch candidates are frequently asked this, and hedging creates exactly the doubt the interviewer is probing. Answer decisively and briefly — if you would not go back, say so plainly and point at the evidence that you have already committed, such as the projects and internships you chose in the direction you are moving towards. The follow-up is always "so what did you build then?" — and that is where rehearsed origin stories fall over. [Greenroom](https://usegreenroom.app/) runs HR rounds out loud with Ari, follow-ups included. Free to start. Curious how it works? See [how AI mock interviews work](/blog/ai-mock-interview).