What makes Greenroom different from other AI mock interview tools?

Greenroom reads your actual GitHub repos before the session and asks questions specifically about your projects — your architecture decisions, your trade-offs, the libraries you chose. It is not a generic question bank. Every session is unique to your code and impossible to game with memorised answers.

Is Greenroom really free?

Yes. The free plan includes one full voice mock interview per month, AI feedback after every session, and a 14-day study plan. No credit card required. Pro ($10/mo) and Premium ($20/mo) unlock more sessions, history, and progress tracking.

How does the voice AI interviewer work?

You speak; Ari (our AI) listens, responds, and asks follow-up questions in real time — like a senior engineer across the table. The conversation is built from your GitHub repos, your target role, and your interview timeline. After the session you get specific written feedback on what you showed clearly, what was thin, and how you came across under pressure.

What companies do candidates prep for on Greenroom?

Engineers prepping for roles at Stripe, Vercel, Linear, Notion, Figma, Shopify, Atlassian, GitHub, Cloudflare, PlanetScale, Supabase, Railway, and similar mid-to-late-stage tech companies have used Greenroom to practice.

Do I need to connect GitHub to use Greenroom?

GitHub connection is what makes Greenroom personalised, so we strongly recommend it. You can also use Greenroom without GitHub for generic technical practice, but you'll miss the project-specific questions that make sessions feel like real interviews.

For engineers who know their craft but freeze when it counts

You're not scared of the
questions. You're scared of freezing.

Most interview prep teaches you facts. Greenroom teaches you to be yourself under pressure — by practicing with an AI that asks about your actual code, the projects you've shipped, the decisions you made. When they ask about your work, you should feel more confident than anyone in the room. Practice real interviews with an AI that reads your actual code, then tells you exactly what to fix. Free to start.

Start free mock interview No credit card · Takes 60 seconds Your first mock interview is on us — no card, no catch

Mock interview · AI Voice

Listening…

14:22

Coach Ari

Listening

Speak naturally — the interviewer is listening.

# LangGraph conditional routing from langgraph.graph import StateGraph def route(state): if state["task"] == "resume": return "generate_resume" return "scrape_jobs" graph = StateGraph(AgentState) graph.add_node("router", route_node) graph.add_conditional_edges( "router", route, { "generate_resume": "resume_node", "scrape_jobs": "job_node", }, )

Transcript

You are speaking…

Real conversation, not a quiz

Questions from your actual work

No credit card to start

Voice-based interview

GitHub-personalised questions

Accuracy score after every session

Free to start — no card needed

Real-time conversation with Ari

No generic Leetcode questions

Specific feedback on your gaps

Adaptive question difficulty

Voice-based interview

GitHub-personalised questions

Accuracy score after every session

Free to start — no card needed

Real-time conversation with Ari

No generic Leetcode questions

Specific feedback on your gaps

Adaptive question difficulty

The product

What an Ari session looks like

Real-time voice. Questions from your repos. Specific feedback after. Not a quiz — a conversation with a senior engineer.

Greenroom · Interview with Ari · redis-job-queue

redis-job-queue

Why did you choose at-least-once delivery over exactly-once in your job queue? Walk me through the trade-offs you considered.

Listening...

You

So the main reason we chose at-least-once was simplicity of the consumer logic. With exactly-once you need distributed transactions or an idempotency layer, and at our scale the duplicates were rare

Personalised

Questions built from your actual work

Ari reads your repos before the session starts. If you built a Redis-backed job queue, expect a question about your delivery strategy — not "explain Redis." Every session is unique to you and impossible to game with memorized answers.

// Your repo: redis-job-queue
+ "Why did you choose at-least-once delivery
   over exactly-once? Walk me through the trade-offs."
// Not the generic version:
– "Explain the difference between Redis and Memcached."

Voice-first

A real conversation, not a form

Real interviews are conversations. Ari listens, responds, and pushes back — like a senior engineer across the table. Typing answers into a box doesn't build the muscle that matters on the day.

Ari is listening

Ari: "Walk me through how you handle backpressure in your queue."

You: "So when the queue fills up, we..."

Honest feedback

Specific. Not a score.

Three sentences: what you showed, what was thin, how you came across. Nothing vague. No "great job." No arbitrary percentiles. Just what to fix before the real interview.

✓

Strong

Clear ownership of the caching layer. You explained the TTL trade-off without prompting.

Thin

Didn't address failure modes. A senior interviewer will follow up here — you need a sharper answer.

Watch out

"I think," "maybe," "kind of" — over-qualifying every answer reads as uncertainty even when you're right.

Pricing

Start free. No tricks.

One full session a month, free forever. Upgrade when you're ready.

Free

forever

✓ Max 1 mock interview/month

✓ Full voice session with Ari

✓ AI feedback after session

✓ 14-day study plan

Get started free

Pro

$10

per month

✓ 10 mock sessions/month

✓ GitHub repo analysis

✓ LinkedIn integration

✓ Session history + streaks

✓ Weak topic tracking

Start Pro — $10/mo

Premium

$20

per month

✓ 30 mock sessions/month

✓ Everything in Pro

✓ Advanced analytics

✓ Priority support

Start Premium — $20/mo

What candidates say

Real people. Real interviews.

★★★★★

"Finally an AI that actually reads my projects. It dug into my CAD optimization project and grilled me on tolerance stack-up and material trade-offs — exactly what a real interviewer would catch. Felt way more prepared after just two sessions."

Nikhil

Mechanical Engineer · Really helped with interview prep

★★★★★

"I come from a BBA background so I was nervous about case and HR rounds. Greenroom helped me structure my answers and speak confidently — made a real difference in how I showed up."

Shivam

BBA Graduate · Made a big difference

★★★★★

"The website looks really clean and well organized. It feels easy to use, and nothing seems unnecessarily crowded or confusing. The overall experience is smooth, and it gives a reliable and professional impression."

Rakesh

Full Stack Developer · Changed how I prepare

★★★★★

"Used it the night before my screening and it gave me a question almost identical to what I got asked. The GitHub analysis is genuinely impressive — questions about code I actually wrote."

Nithish Kumar

Software Engineer · Exactly what I needed

★★★★★

"Three failed interviews in a row, then I found Greenroom. The feedback after each session showed me exactly where I was losing marks. Passed my next two rounds back to back."

Shankar

ML Engineer · Would highly recommend

★★★★★

"I built Greenroom to solve my own problem — I kept blanking in interviews despite knowing the material. Practicing out loud with an AI that actually read my projects changed everything for me."

Mohammed Faheem

Founder · Built this for all of us

Share your feedback

Tried Greenroom? Tell us what worked, what didn't, or what you'd love to see next.
We read every message.

You're not scared of thequestions. You're scared of freezing.

What an Ari session looks like

Questions built from your actual work

A real conversation, not a form

Specific. Not a score.

Start free. No tricks.

Real people. Real interviews.

Share your feedback

You're not scared of the
questions. You're scared of freezing.