Software engineering is the most contested fresher role in India's campus placement season. TCS, Infosys, Wipro, and Cognizant collectively hire over one lakh freshers annually for software engineer and systems engineer roles, while Amazon, Google, Microsoft, and Flipkart hire a smaller, highly selective batch through campus drives at top-tier colleges. Understanding the difference in interview patterns between service companies and product companies is the first step in planning your preparation.
Service company drives usually start with an aptitude, reasoning, and verbal round (on platforms like AMCAT, CoCubes, or Mettl), then a group discussion, then a technical and HR round. Here you are tested on C fundamentals, data structures (linked lists, trees, sorting), and basic OOP concepts. You do not need competitive programming for TCS NQT or Infosys InfyTQ. You do need to solve medium problems in under 20 minutes.
Product company and startup drives are entirely different. Amazon, for example, runs two to three coding rounds where you are expected to solve LeetCode-medium problems in Java or Python, followed by a system design round (even for freshers, especially at SDE-1 level) and a behavioural round structured around their Leadership Principles. Google's fresher process includes data structures and algorithms rounds that require strong command over graphs, dynamic programming, and bit manipulation.
Most Software Engineer fresher drives in Indian campus placements move through a fixed sequence of stages. Knowing the order lets you prepare each stage in turn instead of cramming everything at once. The typical round flow is: Aptitude -> Technical Interview(s) -> HR -> [System Design for product companies].
Each stage shortlists candidates for the next. Treat the early stages as filters to clear cleanly, then invest your deepest preparation in the technical and role specific rounds where offers are actually decided.
Interviewers for Software Engineer roles look for a consistent core of skills. Use this checklist to audit where you are strong and where you need more practice before the drive.
We are verifying more Software Engineer questions from recent drives and add them as students report them. In the meantime, use the round pattern and skills checklist above to structure your preparation, and browse company specific question sets for the recruiters you are targeting.
Preparation for a Software Engineer role works best when it mirrors the round pattern above. Work through these steps in order rather than trying to cover everything at once.
For service companies like TCS, Infosys, and Wipro, no. Their coding rounds test basic DSA at an easy to medium level. For product companies and FAANG, yes. You should be comfortable with LeetCode medium problems and know graphs, dynamic programming, and heaps.
Python is the most flexible choice. It is readable, short, and accepted everywhere. Java suits enterprise heavy companies. C++ is common in competitive programming. Pick one and stay fluent in it. Do not switch languages mid preparation.
Yes, but it requires more deliberate preparation. EC, EEE, and mechanical engineering students regularly crack software engineer drives at service companies if they have strong DSA fundamentals and a couple of well-explained projects. Product companies are more selective but not impossible.
Reading questions is not the same as answering them under pressure. Start a free AI mock interview tuned to the Software Engineer round you are preparing for and get a scored verdict on every answer. No credit card required.