I Decided to Apply to My Own Company. I Didn’t Get the Job.

Vamsi — Thu, 23 Jul 2026 13:00:00 +0000

Yesterday, I did something a bit unusual.
I opened our website, clicked "Apply," and sat down to take Sreevaai's automated technical screening.
I’m the founder. I know the vision, I know the product inside out, and I built the early version of the business from scratch. I figured I would spend ten minutes sailing through the screening, get a perfect scorecard, and call it a day.
It didn't go that way.
The Interview Begins
The AI interviewer popped up. The voice was calm, conversational, and friendly.
It started with a simple, standard question:
"Welcome. Let’s start by looking at your background. Can you walk me through Sreevaai's primary database architecture?"
I smiled. This was my home turf. I launched into a smooth, high-level founder pitch about our scalability, our database clusters, and our data pipeline speed. I sounded confident. I felt good.
Then Sreevaai did what it was designed to do.
It listened. And then it went deeper.
"You mentioned scaling the session cache to handle heavy read loads. What specific caching patterns did you implement to prevent cache stampedes under high concurrency?"
I blinked. I knew we used caching, but the exact code implementation was handled by our lead engineer.
"Well, we leverage Redis for session storage to keep things fast," I replied, trying to keep my tone steady.
The AI didn't move on to a new topic. It stayed right there.
"Redis is a solid choice. But under concurrency, if the cache expires, multiple server nodes might query the database simultaneously. How did you design your lock key eviction policy to prevent that database spike?"
Complete silence on my end.
I fumbled. I talked about generic locking mechanisms.
Sreevaai listened, paused, and asked one final follow-up:
"Could you write the pseudo-code for how you acquire that lock in the cache handler?"
I couldn't.
The Scorecard
Ten minutes later, the interview finished, and Sreevaai's evaluation report was emailed to my inbox.
I opened it.
Summary: Excellent communication. High structural confidence. Shows strong business alignment. However, technical execution depth is missing. Candidate was unable to detail eviction logic or write the requested concurrency lock structure under probing.
Recommendation: Do not advance to technical rounds. Candidate is better suited for Go-To-Market (GTM) or sales roles.
I sat back in my chair and laughed.
My own product had just rejected me.
What I Learned from Failing My Own Interview
Most first-round technical interviews are checklists.
They ask a question, the candidate recites a memorized answer from a study guide, and the interviewer checks a box and moves on. This is why resumes look amazing, but codebases break.
When we built Sreevaai, we didn't want to build another checkbox bot. We wanted to build a conversation.
A conversation that probes when a response is vague. That challenges assumptions. That listens to the details of what you say, rather than just waiting for its turn to speak.
Failing my own screening proved that it works. It didn't care that my name was on the logo. It didn't care about my confidence. It only cared about my actual technical depth.
If you’re hiring, you don't need invasive tools or complex tracking to find the right people. You just need to have a real conversation.
Even if, occasionally, that conversation tells the founder he should stick to his day job.
👉 Try a mock technical interview on yourself
👉 Explore how Sreevaai automates first-round screening

How Candidates Cheat on Coding Interviews in 2026 (And How to Catch It)

Vamsi — Tue, 21 Jul 2026 10:28:34 +0000

If you're hiring remote developers, here's a hard truth: standard take-home tests and live screeners are broken.

Candidates are using dual monitors, screen-sharing workarounds, and LLMs running in the background to bypass traditional screening. We evaluated over 1,000 technical interviews and identified the three most common cheating methods:

The Clipboard Bypass — Copy-pasting solutions generated on another device.
The "Ghost" Interviewer — Having a senior friend whisper answers off-camera.
Tab-Switching Automation — Rapidly switching tabs to query code templates.

How to Protect Your Technical Funnel

Beating AI-assisted cheating requires context-aware evaluation, not just memory tests:

Copy-Paste Restrictions — Prevent code blocks from being pasted directly into the IDE.
Focus Tracking — Flag when a candidate shifts focus away from the test window.
Behavioral Signal Correlation — Monitor speech patterns and eye contact to confirm candidate presence.

Try it yourself: We built Sreevaai to automate technical screening with built-in anti-cheating mechanisms.

👉 Take a Free Mock AI Interview to see the anti-plagiarism system in action.
👉 Sign up for a Free Trial or Book a Quick Tech Demo to protect your pipeline.

DEV Community: Vamsi

I Decided to Apply to My Own Company. I Didn’t Get the Job.

How Candidates Cheat on Coding Interviews in 2026 (And How to Catch It)

How to Protect Your Technical Funnel