Interview setup
The setup is what turns generic AI output into answers that sound like you and reference work you actually did. It is worth the two minutes.
What to fill in
Role
The position you are interviewing for. This shapes vocabulary and the kind of examples the assistant reaches for. Be specific — "Senior Backend Engineer" produces better output than "Engineer".
Job description
Paste the posting. The assistant mirrors the language the company uses, which matters more than people expect: interviewers tend to score answers higher when they hear their own framing reflected back.
Resume and personal profile
Optional attachments, and the single highest-leverage thing you can add. With your resume attached, behavioral answers cite projects you actually shipped instead of inventing plausible ones.
You do not have to fill the profile in by hand. Upload a resume (.pdf, .doc, .docx, .txt, .md, or .rtf) or paste it in and choose Extract with AI — the app reads it and fills your personal profile for you, which you can then edit.
Support types
Choose which surfaces this session needs — Chat, Coding, System design, or any combination. Only the ones you pick are prepared, so leaving out surfaces you will not use keeps the workspace uncluttered.
Programming language
Required when Coding is selected. Solutions come back idiomatic to the language you pick rather than translated out of Python.
Saving and reusing setups
Start an interview and the setup saves itself — there is no save button to remember. Each unique configuration appears once under Recent interview setup in the left sidebar; click the row and the form fills back in exactly as you had it. For a company loop with four rounds over two weeks, that is one row you click four times — while your interview history keeps every session separate so you can look back at what was asked.