MockStage exists for the accent tax.

Why I built this

I'm a Brazilian engineer, and I always dreamed of working at an international company — on a team that runs entirely in English. It's a dream I share with millions of non-native-English engineers, from Brazil to Eastern Europe, from India to Southeast Asia. Day to day, my English was never the problem. But the pressure of an interview was enough to make me freeze: I'd lose the exact technical terms, fumble to explain decisions I understood perfectly in my native language. I failed interview after interview — not for lack of technical knowledge, but for lack of fluency under pressure.

I tried other interview simulators, but they all ran into the same two problems. First, they were generic: they simulated "some technical interview," never the interview I was actually about to face — for that specific role, crossing what was in the job posting with what was on my résumé. Second — and this was the most frustrating — at the end I'd get only a number, or a "be more confident." That told me nothing. I couldn't point to what I'd actually said and see where, exactly, I had frozen.

I built MockStage to solve both: voice mock interviews with different personas — recruiter, technical, manager, director — generated from the real job posting and my own résumé. And at the end of every session, specific feedback that points to exactly where and how my communication broke down under pressure — not a generic score, but something I could actually use to do better on the next try.

Today it's the tool I wish I'd had before every interview I lost — not just to practice the conversation, but to understand, afterward, what really needed to change.

— Eduardo Souza, Founder of MockStage