D J

Platform Engineer | Fullstack Engineer. Built AI voice interview practice for developers. The AI talks back and asks follow up questions.

[D J @DevPrep_app]

I built https://t.co/xkb3fRBdc3 because I kept knowing the answer but falling apart when someone asked me out loud.

This is what a practice session looks like. The AI asks a real question, listens to your answer, and pushes back just like a real interviewer would.

Free to try. https://t.co/l1KEtYvTFR

[D J @DevPrep_app]

@Hiteshdotcom Built https://t.co/7M9cf6LdX8 for exactly this reason. The AI pushes back on your answers out loud, not in a text box. https://t.co/7M9cf6LdX8

[D J @DevPrep_app]

@Hiteshdotcom Exactly this. The scarce skill now is being able to explain what you shipped, why you made those decisions, and defend them when someone pushes back. That cannot be AI generated. That has to be practiced out loud.

[D J @DevPrep_app]

@KrishnaBuildsAI Marketing and getting customers.

[D J @DevPrep_app]

@NanouuSymeon Prompt. Everyone thinks it's just asking a question. Once you've tried to get an AI to behave consistently as a technical interviewer, you realise how much craft goes into it.

[D J @DevPrep_app]

@NanouuSymeon The hardest part is explaining it simply to someone non-technical. Git tracks changes. GitHub is where you store and share them. Once you can explain it clearly to a non-dev, you actually understand it.

[D J @DevPrep_app]

@NanouuSymeon Good list. The one nobody practises is explaining it out loud. Describing your branching strategy or how you resolved a merge conflict in an interview is a completely different skill to actually doing it.

[D J @DevPrep_app]

@kelvinbuildss The best developers also know HOW to use AI without depending on it.

[D J @DevPrep_app]

@himani_0507 Front-end developer. Done a bit of everything since.

[D J @DevPrep_app]

@NanouuSymeon Only when the code works first time. Which is never.

[D J @DevPrep_app]

@NanouuSymeon Good morning Nanou. Constantly improving https://t.co/7M9cf6KG7A. AI voice interview practice for developers. The AI talks back, pushes back and asks follow-up questions. Free to try for anyone with interviews coming up.

[D J @DevPrep_app]

Be honest. Have you ever completely blanked in a technical interview? Knew the answer five minutes after leaving. Happens to the best of us.

[D J @DevPrep_app]

@NanouuSymeon Of course, first thing for any dev worth their salt. Even vibe coders end up copying and pasting terminal commands eventually. You can't avoid it forever.

[D J @DevPrep_app]

@nikkuv5787 I've developed https://t.co/qfE6CnNuiM for just such a thing. Hope it might help.

[D J @DevPrep_app]

@NanouuSymeon Failing isn't the problem. Not knowing why you failed is. Every bad interview tells you exactly what to practice next if you're willing to listen.

[D J @DevPrep_app]

@IamAroke Azure Key Vault on everything. The number of times I've seen connection strings hardcoded in config files that end up in source control is genuinely frightening.

[D J @DevPrep_app]

@NanouuSymeon Ctrl + Shift + P in VS Code command palette.

[D J @DevPrep_app]

@singhaditya4333 Use it as a learning experience. The interview exposed the gap. The fix is practicing the actual doing writing it out, not just prompting it. Rough lesson but useful one in the long run. You will get there!

[D J @DevPrep_app]

Just added Google and GitHub sign-in to https://t.co/qfE6CnNuiM. If you're working through a full stack learning path and want to practice technical interviews out loud, it's free to try. https://t.co/7M9cf6KG7A

[D J @DevPrep_app]

@NanouuSymeon 7. Build something real with each one before moving to the next. Tutorial projects don't count.