Walk me through your final-year or current project.

A two-minute structure for explaining your project in an interview: problem, your role, architecture, a hard problem you solved, results, plus a sample answer.

0 0
Read Time:2 Minute, 10 Second

This is the question you can prepare best, because it is about your own work. Most of the technical round often comes from it, so steer it towards what you know well.

A two-minute structure

  1. The problem (one or two sentences): who uses it and what it solves.
  2. Your role: team size and exactly what you built. Say “I”, not only “we”.
  3. Architecture and stack: front end, back end, database, hosting. Be ready to draw it.
  4. One hard problem: a bug, a performance issue or a design choice, and how you solved it.
  5. The result: a number if possible (users, speed, time saved), or what you learned and would change.

Sample answer (fresher)

“Our final-year project was a hostel complaint tracker for our college, used by about 400 students. There were four of us, and I built the back end in Spring Boot with MySQL and the role-based login. Students raise a complaint, the warden assigns it, and the student gets an email when it is closed. The hardest part was that the complaints list became slow once we loaded a year of test data; I found the query was doing a full table scan, added an index on status and created date, and added pagination, which brought it from several seconds to well under a second. If I did it again I would add automated tests from the start.”

Sample answer (experienced)

“I work on the claims platform for an insurance client, a team of twelve. I own the claim-intake APIs in .NET 8 on Azure, with SQL Server and a Service Bus queue to the fraud-check service. Last quarter, duplicate claims were being created when the mobile app retried on timeout; I added idempotency keys on the create endpoint, which removed the duplicates. I also moved our deployments to blue-green slots, so releases no longer need downtime.”

Prepare for these follow-ups

  • Draw the architecture and walk through one request end to end.
  • Why that database, framework or design?
  • How did you test it? How is it deployed?
  • What would you change if it had 100 times the users?
  • What was the hardest bug?

Mistakes to avoid

  • Listing technologies without saying what you did with them.
  • Claiming parts you cannot explain in depth.
  • Going over three minutes before the interviewer asks a question.

This answer was written by Debugger’s Space as practice material. It is asked in most Indian IT services interviews (TCS, Infosys, Wipro, HCLTech, Tech Mahindra, LTIMindtree, Accenture, Cognizant, Capgemini, IBM). See each company’s hiring steps and practice questions on Debugger’s Space.

Previous post Explain a CI/CD pipeline you have used.
Next post Tell me about yourself.
Subscribe
Notify of
guest

0 Comments
Oldest
Newest Most Voted
Close
0
Would love your thoughts, please comment.x
()
x