eGigSoftware developer interview questions and answers
General developer interviews mix your projects, problem solving and fundamentals like the web, databases and Git. Be ready to explain your code and your decisions.
12 questions. Read each one, start the timer and answer out loud as if you were in the room, then open the tip. Nothing is recorded.
Walk me through a project you built.
What a good answer covers
The problem, your part, the stack, one hard decision and the result. Have the code or link ready.
How do you debug a bug you can’t reproduce?
What a good answer covers
Logs, monitoring, recent changes, user details, then narrow down with small experiments.
What happens when you type a URL and press Enter?
What a good answer covers
DNS lookup, TCP and TLS, HTTP request, server response, then the browser parses, loads assets and renders.
What is the difference between SQL and NoSQL databases?
What a good answer covers
SQL databases use tables, fixed schemas and joins. NoSQL stores documents, key-values or graphs with flexible schemas and scales out easily.
Explain REST APIs and the HTTP methods.
What a good answer covers
Resources at URLs. GET reads, POST creates, PUT or PATCH updates, DELETE removes. Status codes say what happened.
How do you resolve a merge conflict in Git?
What a good answer covers
Pull the latest, open the conflicting files, keep the right changes, test, then commit the merge.
What is the difference between a process and a thread?
What a good answer covers
A process has its own memory. Threads run inside a process and share its memory, so they need care with shared data.
How do you make a slow page or query faster?
What a good answer covers
Measure first, then add indexes, cache, cut round trips and paginate large results.
Explain time complexity with an example.
What a good answer covers
Big O describes how work grows with input. Linear search is O(n); binary search on sorted data is O(log n).
How do you keep a web app secure?
What a good answer covers
Validate input, use parameterised queries, escape output, hash passwords, use HTTPS and least privilege.
How do you handle a deadline you can’t meet?
What a good answer covers
Tell the team early, explain why, and offer options: smaller scope, more time or help.
How do you review someone else’s code?
What a good answer covers
Check correctness first, then clarity and tests. Be specific and kind, and suggest instead of order.
All 12 questions with answers
1. Walk me through a project you built.
The problem, your part, the stack, one hard decision and the result. Have the code or link ready.
2. How do you debug a bug you can’t reproduce?
Logs, monitoring, recent changes, user details, then narrow down with small experiments.
3. What happens when you type a URL and press Enter?
DNS lookup, TCP and TLS, HTTP request, server response, then the browser parses, loads assets and renders.
4. What is the difference between SQL and NoSQL databases?
SQL databases use tables, fixed schemas and joins. NoSQL stores documents, key-values or graphs with flexible schemas and scales out easily.
5. Explain REST APIs and the HTTP methods.
Resources at URLs. GET reads, POST creates, PUT or PATCH updates, DELETE removes. Status codes say what happened.
6. How do you resolve a merge conflict in Git?
Pull the latest, open the conflicting files, keep the right changes, test, then commit the merge.
7. What is the difference between a process and a thread?
A process has its own memory. Threads run inside a process and share its memory, so they need care with shared data.
8. How do you make a slow page or query faster?
Measure first, then add indexes, cache, cut round trips and paginate large results.
9. Explain time complexity with an example.
Big O describes how work grows with input. Linear search is O(n); binary search on sorted data is O(log n).
10. How do you keep a web app secure?
Validate input, use parameterised queries, escape output, hash passwords, use HTTPS and least privilege.
11. How do you handle a deadline you can’t meet?
Tell the team early, explain why, and offer options: smaller scope, more time or help.
12. How do you review someone else’s code?
Check correctness first, then clarity and tests. Be specific and kind, and suggest instead of order.
Before the interview
- Read the job description twice and match two of your examples to what it asks for.
- Keep printed copies of your resume, ID proof and certificates ready, even for online rounds.
- Know your current CTC, expected salary and notice period. Check typical pay in our salary guide, and compare offers with the in-hand salary calculator.
- Genuine employers never ask you to pay for an interview, training kit or joining. Report anyone who does.