You know that feeling — walking out of an interview, and by the time you hit the elevator, your brain already starts replaying that one question.
The one where you said something… fine. Acceptable. Professional.
But deep down, you know you had a killer answer in you. The honest one. The clever one. The one that would've made the interviewer lean in and say, "Tell me more."
Instead, you played it safe. You gave the textbook response. You talked about "process improvement" and "team collaboration" like a LinkedIn post come to life.
And now, days later, you're still thinking about what you should have said.
Not because you lied. But because you held back.
Here's mine.
I was interviewing for a Flutter role. Everything was flowing — architecture, state management, animations. Then came the question:
"What do you use for the backend?"
What I said:
"Dart."
Just… Dart. Like it's a backend. Like that's a normal thing a reasonable person would say.
What I should have said:
"Firebase. Or if I need more control, a custom API with Node or Go. But Dart? Only if I'm using Serverpod or Dart Frog — and even then, I'd clarify that's not the same as 'Dart by itself.'"
The interviewer paused. Typed something. Moved on.
And me? I sat there, smile frozen, already replaying the horror in slow motion.
So here's where I leave you hanging:
Did I get the job?
…That's for Dev Confessions #3.
Now your turn — drop in the comments:
What's one thing you said in an interview that still makes you cringe? And what should you have said instead?
Top comments (0)