About a year ago I started actively participating in technical interviews at my company as an interviewer. I'm a DevOps engineer, not an HR person — so I had zero process going in.
And honestly? Neither did anyone else.
Not my teammates. Not even my manager — he was literally googling "top DevOps interview questions" right before calls. I did the same thing.
The Google Sheet phase
I cobbled together a checklist from colleagues and random "top interview questions" sites, dumped it into a Google Sheet, and called it a system. Rows for questions, columns for scores, and a notes cell at the end where I was supposed to write some comment about how the candidate did.
The idea was fine. The execution was painful.
Here's the thing — during a technical interview you're already doing a lot:
- Listening carefully to what the candidate says
- Thinking about follow-up questions on the fly
- Evaluating their answer in real time
- Keeping track of time
And on top of all that I was supposed to type structured notes into a spreadsheet? Half the time I'd finish the call and have three words written down.
Then my company started asking for written feedback reports after each interview. A proper structured writeup per candidate.
The thing that finally pushed me over the edge
Candidates started showing up using AI assistants to help them answer questions in real time. And interviewers — myself included — were still juggling Google Sheets and personal notes.
That asymmetry felt absurd. After 3-4 interviews I just thought: this is dumb, I can fix this.
What I built
I opened up my editor and started building Interview Helper — a smart organizer for people who conduct technical interviews regularly.
The core features:
Question Bank — ready-made question templates organized by role (DevOps, Backend, Frontend, Data Science, HR, System Design) and level (Junior / Middle / Senior). No more googling. Just open the bank, pick a template, copy it into your session.
My Templates — save your own custom question sets and reuse them across interviews. If you have a go-to set for DevOps Middles, you create it once and it's always there.
Sessions — each candidate gets their own session with their name, role, date, and status. No more mixing up "the DevOps guy from Tuesday" with "the other DevOps guy from Thursday."
AI assistant — helps analyze candidate answers during or after the interview, and assists with writing the feedback report afterward.
Honest disclaimer
I'm a DevOps engineer, not a fullstack developer. This is a genuine side project built out of frustration with my own workflow. It's not polished to perfection — but it already makes my interviews noticeably less chaotic.
Would love your thoughts
Do other people who conduct interviews regularly feel this pain? Is your process actually better than mine was, or are you also secretly running on Google Sheets and vibes?
And if this sounds useful — I'd love to hear what features would actually matter to you. Happy to share more details or a demo in the comments.
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.