Get questioned on the skills you claim

Your resume lists what you know. This works through it skill by skill — what an interviewer asks to test each one, what a good answer covers, and the follow-up that catches people out. Including the skills nothing in your experience backs up.

How it works

1. Upload the resume you are applying with It is read in your browser and the skills section is pulled out of it. The file never leaves your device — only the text, and only when you press the button.
2. Tick the skills you want questioning on Every skill the resume lists, as a checkbox. Take the lot or pick the three the job actually turns on. Paste the posting too if you have one, and the questions lean towards how that employer says the skill will be used.
3. Work through the questions and the answers For each skill: the questions it is most often asked about, what a good answer covers, and the follow-up that separates having used something from having read about it. Print it or save it as a PDF to revise from.

Why these questions and not a list off the internet

• They come from your resume A generic list asks what dependency injection is. This asks about the DI container in the service you actually shipped, because that is what the person across the table will have read before walking in.
• Pitched at your level The same skill is a different interview at two years and at ten. Seniority is read from the dates on your roles, not from the word "Senior" in a title, and the page tells you what it pitched at so you can see if it guessed wrong.
• It finds the claims nothing backs A skill on your list with nothing in your work history behind it is the first thing an interviewer finds and the hardest to talk your way out of. Almost nobody spots those in their own resume. This names them.
• The answers do not invent your experience How a technology works is explained properly — that is public knowledge. What you did with it comes only from your resume, and where an answer needs a detail you have not written down it leaves a marked gap for you to fill.

Preparing for a technical interview without memorising answers

The questions in a technical interview are rarely surprising. They come from the resume on the table, and most of them are the same handful per technology — which is why preparation works at all. What catches people out is the second question: not "what is a message queue" but "your consumer throws halfway through a batch, now what".

So the useful preparation is not learning answers by heart. It is going through your own claims one at a time, saying out loud what you actually did with each, and noticing the ones where the sentence runs out. Those are the ones to think about before somebody asks. An answer you have thought about sounds nothing like an answer you have memorised, and an interviewer can tell the difference immediately.

Common questions

Is it free?

Yes. Upload a resume, pick your skills and read the questions and answers without paying. An account is needed because the questions are produced by an AI model and the requests are counted per account.

Do I need a job description?

No — it is optional. Without one the questions come from what your resume puts forward on its own, which is what you want before a screening call. With one, they lean towards how that posting says the skill will be used.

How many questions will I get?

Eight per skill by default, across warm-up, core and deep. Tick three skills and you get twenty-four; the page shows the running total before you start so you know what you are asking for.

What does "not evidenced" mean next to a skill?

Your skills section claims it but nothing in your work history demonstrates it — for example a recent major version listed when the only project shown used an older one. It is flagged because an interviewer will find it, and the questions for that skill are the ones they would use to find out.

Are the answers something I should memorise?

No. They are what a good answer covers, so you can check whether yours does. Reciting one is obvious from across a table, and the follow-up question is designed to land exactly where a memorised answer stops.

Is my resume stored or used to train anything?

The file is parsed in your browser and never uploaded. The text goes to the configured AI provider to produce the questions, and is not used to train a model.