Features

Six things have to work for an answer to be usable.

Hearing the question, deciding it was one, knowing enough about you to answer it, and getting the words on screen before the pause becomes awkward. Each has its own page, because each is where a different competitor falls over.

In detail

One page per capability

In the order they happen during a call.

What each thing costs

Charged for work, not for time

Listening is free however long the call runs. Everything else is a fixed number of credits, so the bill is predictable before you start.

What happensCreditsWhen
A live answer1Fast or Balanced model
An advanced answer3The Advanced model, thinking harder
A screenshot answered4A coding problem or a slide on screen
A practice question2Asked, then your answer marked
Notes after the call2Summary, questions asked, what to revise
A job description analysed1Measured against your CV
Listening to the callFreeHowever long it runs
Reading your CVFreeWhen you add or update it

Packs, plans and worked examples →

After the call

What you are left with

Processing runs when a session ends. It is the part that makes the next interview easier rather than just this one.

When something is down

It falls back rather than failing

An interview is the worst possible moment for a provider outage, so an answer is not tied to one model or one company.

If the model that should write an answer is unavailable or overloaded, the next one writes it, and you are charged once. An answer that fails altogether is not charged for at all. The same applies to a dropped connection: a session waits five minutes, and reopening it — in the same tab, a new one, or the Windows app — carries on with the credits already held.

See it on a question only you could answer.

Add a CV and a job description, and run the first one in your browser.

Create your account