About Software Engineer interviews in India
Software engineering interviews in India usually run across data structures and algorithms, system design, and a behavioural round, with the weighting shifting toward design as you become more senior. Interviewers care less about a memorised optimal solution and more about how you reason: clarifying the problem, talking through edge cases, stating time and space complexity, and improving a brute-force approach out loud. Bring one project you can defend deeply — its architecture, the trade-offs you chose, and what you would do differently — because that is where the strongest signal comes from.
🎯 Software Engineer Interview Tips
DSA DrillsPractise arrays, strings, trees, graphs and DP; state the complexity for each solution.
Think AloudTalk through your approach, edge cases and trade-offs before and while you code.
System DesignFor senior rounds, design scalable systems and justify each component.
Project DepthPick one project you can defend on architecture, decisions and what you would change.
🔧 Technical Questions
Technical Question 1
Explain the difference between a process and a thread.
💡 How to answer: Processes are independent memory spaces; threads share memory within a process. Threads are lighter but need synchronisation. Mention use cases for each.
Technical Question 2
What is time complexity and why does it matter?
💡 How to answer: Big-O notation measures how runtime grows with input size. O(1) is constant, O(n) is linear, O(n²) is quadratic. Always relate to real code — nested loops = O(n²).
Technical Question 3
Explain SOLID principles with examples.
💡 How to answer: Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, Dependency Inversion. Give a concrete code example for at least one.
Technical Question 4
What is the difference between SQL and NoSQL databases?
💡 How to answer: SQL: relational, ACID, fixed schema — good for transactions. NoSQL: flexible schema, scales horizontally — good for high-volume, unstructured data. Mention when to use each.
Technical Question 5
How does garbage collection work in Java/Python?
💡 How to answer: JVM uses generational GC — Young/Old/Perm Gen. Python uses reference counting + cyclic GC. Explain memory leaks and how to avoid them.
Technical Question 6
What is a REST API and what makes it RESTful?
💡 How to answer: Stateless, client-server, uniform interface, cacheable. REST constraints — HTTP verbs (GET/POST/PUT/DELETE), status codes, JSON payload. Contrast with SOAP.
Technical Question 7
Describe your approach to system design — design a URL shortener.
💡 How to answer: Clarify requirements → estimate scale → define APIs → choose DB → design components → handle edge cases. Show scalability thinking.
Technical Question 8
What is Docker and why do we use it?
💡 How to answer: Containerisation tool. Packages app with dependencies into isolated containers. Benefits: consistent environments, fast deploys, microservices isolation.
Technical Question 9
How do you optimise a slow database query?
💡 How to answer: Check execution plan (EXPLAIN), add indexes, avoid SELECT *, use JOINs efficiently, consider caching with Redis, denormalise where needed.
Technical Question 10
What is the CAP theorem?
💡 How to answer: Consistency, Availability, Partition tolerance — you can only guarantee 2 of 3. Cassandra favours AP; HBase favours CP. Real-world implications for distributed systems.
🧠 Behavioural Questions
Behavioural Question 1
Tell me about yourself as a software engineer.
💡 How to answer: Structure: Current role → 2–3 key technical achievements → core tech stack → why this role. Keep to 90 seconds. Lead with your strongest skill.
Behavioural Question 2
Describe a time you disagreed with a technical decision.
💡 How to answer: Use STAR. Show you raised concerns with data/evidence, were open to the team's reasoning, and could disagree and commit when needed.
Behavioural Question 3
Tell me about a project that failed. What did you learn?
💡 How to answer: Own the failure, show root cause analysis, demonstrate specific changes you made afterward. Growth mindset is what interviewers want to see.
Behavioural Question 4
How do you handle tight deadlines?
💡 How to answer: Prioritise ruthlessly, communicate early about risks, cut scope not quality, ask for help. Give a specific example where you delivered under pressure.
Behavioural Question 5
Where do you see yourself in 3 years?
💡 How to answer: Senior engineer / tech lead / architect. Tie your growth to the company's technical challenges. Show ambition with self-awareness.
💡 Situational Questions
Situational Question 1
A production bug is causing data loss. Walk me through your response.
💡 How to answer: Immediately alert stakeholders, stop the bleeding (rollback/feature flag), preserve logs, identify root cause, fix with tests, post-mortem documentation.
Situational Question 2
You are asked to estimate a feature with unclear requirements. What do you do?
💡 How to answer: Ask clarifying questions, break into known vs unknown, give a range estimate, identify risks early, propose a spike/prototype for unknowns.
Situational Question 3
Your code review finds 50 critical issues an hour before release. What do you do?
💡 How to answer: Triage by severity, fix P0 blockers, document P1/P2 as tracked debt, communicate to PM, do not release silently with known critical issues.
💰 Salary Questions
Salary Question 1
What salary are you expecting?
💡 How to answer: Never give first. Say: 'I'd like to understand the full role and responsibilities before discussing numbers. What is the budgeted range for this position?'
Salary Question 2
Your current salary is X. We can only offer X+10%.
💡 How to answer: Quantify your value: skills gap you fill, ramp-up cost saved, market rate data (cite Naukri salary insights). Negotiate on joining bonus or ESOPs if base is fixed.
🎤 Ask Interviewer Questions
Ask Interviewer Question 1
What does the technical stack look like and what influenced those choices?
💡 How to answer: Shows architectural curiosity. Great question to understand tech debt and modernisation roadmap.
Ask Interviewer Question 2
What is the team's biggest engineering challenge right now?
💡 How to answer: Shows you want to contribute, not just collect a salary. Listen carefully — the answer tells you about team health.
Ask Interviewer Question 3
How is on-call structured and how does the team handle incidents?
💡 How to answer: Critical for work-life balance. Shows operational maturity awareness.