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
I've been looking at https://t.co/V1BjsQ8bQ6. If you're job hunting in tech, try https://t.co/PyZREdg0Uu. You apply directly to the person hiring, not an HR black hole. Makes a massive difference when you actually get a response from the person who will be your manager.
@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
@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.
@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.
@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.
@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.
@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.
@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.
@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.
@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.