# What is your favorite subject? Campus interview answers

Name a core subject related to the job that you genuinely understand, give one specific reason you like it, and mention a project or problem where you used it. Then be ready: interviewers often treat your answer as permission to ask technical questions on that subject. Never pick a subject you can't defend for ten minutes.

By the Speaking Coach team at Sodhera Intelligence. Updated 2026-10-22. Source: https://www.orecci.com/speaking-coach/interview-questions/what-is-your-favorite-subject/

## This is a technical question in disguise

In campus interviews, "What's your favourite subject?" sounds friendly. Often it is the start of the technical round. Whatever you name, the interviewer can say, "Great, then tell me about..." and spend the next ten minutes there.

That's actually good news. You get to choose the topic of your [technical round](/speaking-coach/interviews/technical-interview/). The only mistake is choosing badly.

## How to choose your subject

| Choose it if | Avoid it if |
| --- | --- |
| It is a core subject for the job you're applying to | It is an elective unrelated to the role, unless you can link it |
| You scored well or understood it deeply | You liked the teacher but don't remember the content |
| You used it in a project, internship or competition | It was purely theory you memorised for the exam |
| You can explain its basic concepts without notes | You'd need to revise it from scratch |
| You can say something about where it's used today | It's a general subject like English or environmental studies, for a technical role |

If two subjects fit, pick the one most closely tied to the role. For a software role, data structures, operating systems, databases or networks are safer than a niche elective. For a core mechanical role, thermodynamics or manufacturing processes. For finance, financial accounting or corporate finance.

## How to prepare

Give yourself a few evenings for this. It pays off in more than one round.

1. **List the five to eight core concepts** in that subject. The ones every textbook chapter starts with.
2. **Explain each out loud in under a minute,** without notes. If you can't, revise it.
3. **Prepare one application.** A project, lab, internship task or real-world system where the subject is used. Your [final year project](/speaking-coach/interview-questions/tell-me-about-your-final-year-project/) is often the best one.
4. **Prepare one "beyond the syllabus" point.** Something you read or tried that wasn't in the exam.
5. **Expect the classic follow-ups** in the table below and answer each out loud.

## Follow-ups to expect by subject

| Subject | Likely follow-ups |
| --- | --- |
| Data structures | "Difference between an array and a linked list? When would you use a hash map? Reverse a linked list." |
| Operating systems | "What is a deadlock and how do you prevent it? Process vs thread? What is virtual memory?" |
| Database management | "What is normalisation? Explain joins. What's an index and when does it slow things down?" |
| Computer networks | "What happens when you type a URL in a browser? TCP vs UDP?" |
| Thermodynamics | "State the laws. What is entropy in simple terms? Explain a refrigeration cycle." |
| Strength of materials | "Stress vs strain? What is a factor of safety? Draw a stress-strain curve." |
| Financial accounting | "Walk me through the three financial statements. What's depreciation and why does it matter?" |
| Marketing management | "Explain the 4 Ps with a product you know. How would you segment the market for a new snack?" |

## A simple answer structure

1. **The subject.** One line.
2. **Why you like it.** One specific reason, not "it's interesting."
3. **Where you used it.** A project, lab or internship.
4. **Optional hook.** Something you'd be glad to talk about.

About 30 to 45 seconds. Then let them choose where to go.

## Example answers

These are examples with made-up details. Use your own subject and project.

### Computer science student

> "Database management systems. I like that it's very practical: a badly designed schema shows up immediately as slow queries or wrong data. In my final-year project I designed the database for a hostel management app, and I had to rethink the schema twice when we added room transfers. I've also been reading about how indexes work internally, which wasn't really covered in class."

### Mechanical engineering student

> "Heat transfer. I liked it because you can see it everywhere, from a phone heating up to how a car radiator works. In our third-year lab we tested different fin designs on a heat sink, and my design dissipated heat noticeably better than the standard one in our trials. That got me interested in thermal design for electronics, which is part of why I applied here."

### Commerce student

> "Cost accounting. Financial accounting tells you what happened, but cost accounting tells you why one product makes money and another doesn't. In my internship at a small textile firm I helped work out the cost per metre for two fabric lines, and found one was priced below cost once overheads were included. That's the kind of analysis I'd like to keep doing."

## If you get stuck on a follow-up

You won't know everything. When a question goes past what you know:

- Say so honestly: "I haven't studied that in depth."
- Reason from what you do know: "But based on how X works, I'd expect..."
- Don't bluff. Interviewers in your subject will notice immediately.

See [how to answer a question you don't know](/speaking-coach/guides/answer-question-you-dont-know/) for more ways to handle this calmly.

## Mistakes to avoid

| Mistake | Why it hurts |
| --- | --- |
| "I like all subjects equally" | Avoids the question and suggests no depth anywhere |
| Picking a subject to sound impressive | The follow-ups expose it fast |
| Naming a non-technical subject for a technical role | Looks like you're avoiding the core |
| Saying "Maths" when maths was your weakest grade | They can see your transcript |
| Reasons like "the teacher was good" or "it was easy" | Says nothing about your interest |

## Rehearse under questioning

The real practice for this question is being grilled on your subject. Ask a friend in your branch to fire five questions at you, or use Speaking Coach: tell its interviewer your subject and it will ask follow-ups on what you said, then show you where you paused for long stretches or rushed.

## Questions people ask

### Is it okay to choose a subject not related to the job?

Only if you can link it clearly to the role. For technical roles, a core subject is safer because the follow-up becomes a fair technical round.

### What if they ask about my least favourite subject?

Name one honestly, but not a core subject for the job. Say briefly why, and what you did to get through it. Keep it short and neutral.

### Should I revise my favourite subject before the interview?

Yes. Revise its core concepts and practise explaining them out loud. It's one of the highest-value hours of preparation for a campus interview.

### Can my favourite subject be from school?

For a campus interview, a college subject is better. A school subject only works if you followed it further in college.

### What if I freeze on a basic question?

Take a breath, ask to restate it in your own words, then start from the definition. Freezing is common; recovering calmly is what interviewers remember.

---
Speaking Coach on the App Store: https://apps.apple.com/app/id6767124039
Speaking Coach on Google Play: https://play.google.com/store/apps/details?id=com.sodhera.speakingcoach