Requirement → your example → follow-up → rehearsal notes.
1. Turn the job requirements into questions
Read the job description for responsibilities and evidence, rather than collecting generic interview answers. A requirement such as “lead cross-functional projects” could invite a question about aligning people who did not report to you. Write the question in ordinary language and note the requirement it relates to.
Use the current CV you submitted, the job description and your own project notes. Add public company material only where it helps you understand the role. Do not include another person's confidential information without permission. Start with five important requirements; you can expand the map once each has an honest example.
2. Attach an example you can defend
For each requirement, choose a real situation. Record the context, your individual action and the result you can substantiate. Separate what you did from what the team did. If the outcome was not measured, describe the change without inventing a percentage. If you have no example, note the gap and prepare an honest explanation of related experience.
| Field | What to write |
|---|---|
| Requirement | The skill or responsibility in this job description. |
| Example and source | A real project, plus the CV line or your own note that supports it. |
| Your action | The decision or contribution you personally made. |
| Result | A supported outcome, with uncertainty clearly stated. |
| Follow-up | What went wrong, what you changed, or what you would do differently. |
This is a preparation template, not a script to memorise. Keep enough detail to check your facts, then practise explaining them naturally.
3. Practise the second question
A prepared opening can hide a weak example. Ask a practice partner to follow up: “What was your contribution?”, “Why did you choose that option?”, “What evidence showed it worked?” and “What would you change?” Answer from your record, rather than adding a more impressive detail to satisfy the question.
Opening: Tell me about a project that went off track.
Follow-up: Which decision was yours, and what did you change afterwards?
Review: Can you distinguish the team's outcome from your own contribution?
There is no need to guess the employer's exact questions. The aim is to make your evidence easier to explain across several reasonable questions.
4. Write a short review after each rehearsal
Note three things: where the answer was clear, where a claim needed stronger evidence and where you lost the thread. Choose one improvement for the next rehearsal. Read the job requirement again before changing an answer, so you do not become more fluent at answering a different question.
Thalassa Assistant can use the material you add to its local knowledge base to play an interviewer, in a typed or spoken rehearsal, and generate a written debrief. Check the suggestions against your actual experience. Debriefing is available with meeting credits and eligible plans; Standard does not include it. Rehearsal and generation use the applicable meeting-time allowance.
5. Use a preparation schedule that fits your time
If you have two weeks, use the first few days to map requirements, the middle days to test examples and follow-ups, and the final days to rehearse the weakest answers. If the interview is tomorrow, narrow the same method to the three most important requirements. A schedule is a way to allocate attention, not a guarantee of readiness or a job offer.
Prepare practical questions for the employer as well: the role's priorities, how success is evaluated and what remains unclear in the description. For salary discussions, research the role and region separately, choose your own range and prepare the reason. The assistant does not decide that range or provide personalised financial advice.
6. Check the interview's rules before using assistance
Rehearsal before an interview is distinct from assistance during a selection process. Follow the employer's rules and obtain the permissions required for transcription or other assistance. If aids are forbidden, do the preparation beforehand and take the interview without them. Do not use the product to conceal prohibited help or to claim experience you do not have.
In permitted interviews, Thalassa can draft an answer from your documents and show the source. You remain responsible for checking it and for what you say. Read the data and privacy information before adding personal material: document search is local, while transcription and answers use cloud services. Audio is not archived and the transcript is deleted after the meeting; saved notes, debriefs and metadata are separate.
Questions about trying the workflow
Can I practise without paying first?
The free first meeting includes up to 15 minutes of live answers, five preparations and about 100 pages, without a card. Check the current trial and interview features before deciding.
Do I need a subscription for one interview?
One meeting credit is €29.90 including VAT, valid for 365 days. It includes a 500-page knowledge base and 30 meeting minutes plus 30 minutes' grace. Rehearsal and briefing/debrief generation consume the same available minutes; they are not unlimited extras. Credits are one-time purchases and do not renew. Current bundles and terms are on the meeting-credit section.
Practise with the experience you already have.
Explore rehearsal, written feedback and meeting credits for occasional use.
Explore interview preparation