Engineering managers use this question to judge self-awareness and how you are likely to respond to code review. In Indian tech interviews a rehearsed weakness gets probed quickly, so pick a real gap outside core coding, such as estimation or communication, and describe how you are measurably fixing it.
My biggest strength is patient debugging. During my internship at a fintech startup in Chennai, a report export kept failing for only some users, and after two days of reading logs I traced it to a timezone conversion in the date filter. The fix was one line, but I also added a test so the bug could not quietly return. My weakness is estimating how long tasks will take. In my first sprint I said a form would take one day and it took three, because I hadn’t counted validation, edge cases and review comments. Now I split every task into smaller steps before giving an estimate, and I record my actual time in a simple sheet. Over the last two months my estimates have come much closer, and my lead now lets me size my own tickets.
Calling yourself a perfectionist is a disguised strength that panels see through. The rewrite names a real habit that slows delivery, a simple rule to fix it and feedback confirming the change.
For students, interns and your first job.
My biggest strength is patient debugging. During my internship at a fintech startup in Chennai, a report export kept failing for only some users, and after two days of reading logs I traced it to a timezone conversion in the date filter. The fix was one line, but I also added a test so the bug could not quietly return. My weakness is estimating how long tasks will take. In my first sprint I said a form would take one day and it took three, because I hadn’t counted validation, edge cases and review comments. Now I split every task into smaller steps before giving an estimate, and I record my actual time in a simple sheet. Over the last two months my estimates have come much closer, and my lead now lets me size my own tickets.
One strength I can prove is writing readable code. A senior developer from our alumni network reviewed my college project, a library management system in Python, and his main comment was that he could follow every function without asking me anything. I name variables carefully and keep functions short. The weakness I’m working on is speaking up in group discussions. In team meetings I used to stay quiet even when I disagreed, and once our group spent a week on an approach I suspected would not scale. Since then I write down at least one point before every meeting and make sure I raise it. I also volunteered to present our final project demo to the department, which went well, and I now contribute in meetings without much hesitation.
For roughly 3 to 8 years in the field.
My strength is making systems observable before they break. At a healthtech company in Hyderabad, I added structured logs, dashboards and alerts to our appointment service, and when the database slowed down one evening we caught it within minutes instead of hearing about it from patients the next morning. My weakness has been delegation. Because I knew the service best, I kept taking the hardest bugs myself, which left two newer engineers without the chance to learn it, and my manager raised this in my review. Now I pair with them on tricky issues instead of solving them alone, and I hand at least one challenging ticket to someone else every sprint. One of them led our last production incident, with me only as backup.
A strength I’d highlight is working closely with product and design. On a B2B invoicing product in Pune I sit in on discovery calls, and more than once I’ve suggested a simpler technical route that gave users the same result in half the time, such as reusing our existing PDF engine instead of building a new one. My weakness is that my frontend skills lag behind my backend skills. I can read React code and fix small issues, but I’m slow with complex state management. For the last few months I’ve been taking small UI tickets deliberately and pairing with our frontend lead every Friday afternoon. I recently built a filter panel on my own that passed review with only minor comments, which I could not have done earlier.
For 10+ years, specialists and leaders.
My strength is turning a vague business goal into a technical plan a team can execute. When our leadership decided to enter SME lending, I broke that goal into an eight-month roadmap of services, integrations and compliance checks, and we launched the first product within that window. My weakness is that I’ve drifted away from hands-on coding, and in design reviews I sometimes depend on my team for the details of newer tools. I don’t want to be an architect who cannot read the code being reviewed. So I now pick up one small ticket every sprint, and I’ve completed a Kubernetes course with practical labs. Last month I debugged a deployment issue on our staging cluster myself, which also earned me some credibility with the platform team.
One strength I bring is calm incident leadership. I’ve led the response to several serious production outages, including one where a bad configuration took our payments API down for forty minutes; I kept the call focused, assigned clear roles and published a blameless review within two days listing five fixes, all of which we completed. My weakness is speaking to large audiences. I’m comfortable in small design reviews, but at company town halls I used to over-prepare and read from my slides. I joined an internal speakers’ group and now present at our monthly engineering forum. My most recent talk, on incident practices, drew plenty of questions, and I spoke mostly without notes.
Written by the DigitalCVMaker team for developers applying in India. Every example is original — none is copied from a real person’s profile — and each is built around what employers and clients in this field look for: the role, a specialism, and proof you can back up. We revise the page when that changes; the date at the top shows the last update.
These are examples to adapt, not real people. Swap in your own numbers, specialisation, city and achievements — it only works when every word is true for you.
Only if that language is not central to the role. Saying you are still learning Kotlin for a backend Java role is fine, but the same answer for an Android role is not. Explain how you are learning it, for example through a side project.
One well-proven strength usually beats three unsupported ones. Choose the one most relevant to the job description, give a concrete example, and leave enough time to discuss your weakness properly, since that is the part interviewers listen to most closely.
Add your headline, summary and skills to a personal website with your photo, work and contact form — free to start.
● Live in 5 minutes · free to start · no auto-renew
One strength I bring is calm incident leadership. I’ve led the response to several serious production outages, including one where a bad configuration took our payments API down for forty minutes; I kept the call focused, assigned clear roles and published a blameless review within two days listing five fixes, all of which we completed. My weakness is speaking to large audiences. I’m comfortable in small design reviews, but at company town halls I used to over-prepare and read from my slides. I joined an internal speakers’ group and now present at our monthly engineering forum. My most recent talk, on incident practices, drew plenty of questions, and I spoke mostly without notes.