For hiring teams
Interview writing, editing and translation candidates with one link
Send a writing, editing or translation candidate one link. An AI interviewer asks about their real work, and you decide from the quoted scores.
Free while Aethel is in early access: one interview link, up to 25 interviews a month, about 3 of them with a video interviewer, the rest by voice. No card needed.
Hiring for writing, editing and languages
What makes this hard to screen
Writing samples may have been edited by someone else, and a polished sample does not show how the writer checks facts or takes feedback. Translators are hard to judge if you do not read both languages. You want to hear how they make choices and catch errors.
Roles this field covers: content writer, copywriter, technical writer, editor, content strategist, translator, localization specialist, journalist.
Listen for these in a transcript
- Checks facts and terms against primary sources and can say where.
- Explains how a specific edit helped the reader.
- Changes tone and structure on purpose for a brand, audience or culture.
Warning signs
- Does no research or fact-checking.
- Rewrites until the client stops asking, without knowing what was wrong.
- Cannot explain any choice they made in a piece.
Fit
Which writing roles it fits, and which it does not
The interview hears how a writer makes and defends choices. That makes it a good first conversation where judgment and process matter, and the wrong tool where the job is the craft on the page itself.
A good fit
- Technical writers and documentation leads. They can talk through getting facts out of engineers, testing steps against the product, and deciding what a reader needs first.
- Editors and content strategists. Questions turn to edits they made and why, notes a writer pushed back on, and keeping a piece accurate on deadline.
- Content writers and copywriters. Research on a subject they did not know, working from a brief, and changing tone for a brand or a new audience.
- Translators and localization specialists, for their process. How they handle a phrase with no direct equivalent, glossaries and style guides, and the review before delivery. Judge the translation itself separately.
- Grant writers. Researching funders, getting facts from busy program staff, and what made a funded proposal stronger than the drafts before it.
Not the right tool
- Judging the writing itself. Nothing in a conversation shows how well someone writes. Ask for a sample or set a short writing task as its own step.
- Checking a translation or a second language. The interview does not test a second language. A translator can describe their checks, but only a reviewer who reads both languages can judge the result.
- Live interpreting. Interpreting happens in real time. Describing past assignments does not show whether someone can keep up with a speaker.
- Interviews in other languages. Interviews run in English or Spanish. It is not a fit for roles that need an interview in a language other than English or Spanish.
- Medical and regulatory writers. Healthcare and life sciences lists medical writer among its roles and scores clinical or scientific reasoning. Interview healthcare candidates
Example questions
Questions a writer, editor or translator may hear
In the interview, the AI writes its own questions from the field's topics, fits them to the role on your link, and follows up on each answer. The examples below come from the product: practice questions for this field and must-ask questions that come filled in on the starter templates.
- From this field's practice questions
“Imagine a client sends back your draft saying it doesn't sound like them, with no other notes. What do you do first?”
What to listen for: Questions before a rewrite: what felt wrong, a look at pages the client wrote themselves or at their style guide, and a fix tried on one section before the whole draft is redone.
- From this field's practice questions
“Tell me about one piece you checked for accuracy before it went out. What did you check, and what did you catch?”
What to listen for: The piece, the facts that could have gone wrong in it (names, figures, dates, product terms) and the source each one was checked against. The best answers say what the check caught.
- Must-ask on the Translator starter template
“Tell me about a phrase that had no direct equivalent. How did you decide on your translation?”
What to listen for: The phrase described closely, two or three options (a literal version, a local idiom, a plain rewording) and why one served this reader. Also who confirmed the choice: a client glossary, a second reviewer or the subject expert.
- Must-ask on the Technical writer starter template
“Tell me about a document you rewrote. How did you know the new version was better?”
What to listen for: "Better" shown, not felt: fewer support tickets on that topic, a task new users could finish on their own, a review that passed sooner. An answer that stops at "it read more clearly" is thin.
- Must-ask on the Editor starter template
“Tell me about a piece you edited heavily. What was wrong with it, and how did the writer respond?”
What to listen for: The diagnosis before the fix: the structure, missing evidence, or the wrong reader in mind. Then the writer: how the notes were framed, what the writer fought for, and what stayed.
How it works
How to interview with a link
Step 1: Create a link for the role
Choose the field "Writing, editing and languages", the level, and a specialty such as content writer or copywriter.
Step 2: Send it to your candidates
Share it wherever you already find writing, editing and translation candidates.
Step 3: Candidates interview on their own time
It takes about 15 minutes, and they know the interviewer is an AI.
Step 4: Review and decide
Mark each one Advance, Not a fit, or Undecided.
The interview
What the interviewer covers
It follows up on each answer and picks the writing, editing and translation topics that fit the role.
- A piece they are proud of and what made it work
- A major edit or rewrite and why it was needed
- Writing for readers who knew less than they did
- Researching an unfamiliar subject and checking facts or terms with sources or experts
- A factual error or mistranslation and how it was caught
- Adapting tone and style for a brand, audience or culture
- Editor or client feedback they disagreed with
- Working to a tight deadline without losing accuracy
What the scoring looks for
Strong work: the candidate checks facts and terminology against primary sources, explains how each edit serves the reader, adapts tone and structure on purpose, and can show the work was accurate and understood.
Warning signs: the candidate does no research or fact-checking, rewrites until a client is satisfied without knowing what was wrong, or cannot explain any choice they made. The scoring AI is told to score an area below 60 when its answers show one of these.
Your questions
Sample must-ask questions
Up to three per link. The interviewer is told to ask each one as written, and every result shows whether it was asked word for word, asked in other words, or not asked. Examples:
- Tell me about a piece you rewrote heavily. What was wrong with the first version?
- How do you check facts, names and terminology before something is published?
- Describe a time an editor or client disagreed with a choice you made. How was it settled?
Starter templates
Start from a common role
Start a link from one of these and edit anything.
Content writer
Focus: Articles and web pages, research, editing, meeting deadlines
Editor
Focus: Structural and line editing, fact-checking, style guides, feedback writers can use
Grant writer
Focus: Researching funders, writing proposals, budget narratives, reporting to funders, working with program staff
Technical writer
Focus: Product documentation, working with engineers, writing for different readers
Translator
Focus: Accurate translation, terminology and style guides, adapting tone for the audience, review and quality checks
Reading the answers
What a strong answer looks like in writing work
Every scored area is read for the same three things, and your team sees them under each score. In writing, editing and translation they sound like this.
A specific case
One named piece, with its reader and its size: a 40-page setup guide for a home medical device, a product page rewritten for a new market, a chapter translated from Portuguese. Without a case like that, the area scores at most 60, however polished the answer sounds.
A trade-off weighed
Why this structure, word or cut, and what else they considered: a term taken from the client glossary over a more natural one, a section moved up because readers skipped it. Comparing two or more options, and saying why each one lost, is the top level.
A measured result
How they knew it worked: fewer reader questions, an error caught before print, a reviewer who signed off, a funder who said yes. A style rule that other writers now follow is the top level.
A score of 90 or more needs a complete quote of at least 20 words about the area. "I always check my sources" is read as a habit, not a case.
Setting up the link
Mistakes to avoid with a writing link
Putting a writing test inside the interview.
A must-ask such as "Rewrite this sentence" gets a reply in conversation, not a sample you can judge. Keep must-asks to "Tell me about a time" or "Walk me through how you", and send the writing task on its own.
One link for every kind of writer.
The questions follow the role on the link. Make one link per role and set its specialty and focus areas, such as API docs or product copy, so a technical writer and a copywriter each hear about their own kind of work.
Leaving out the language pair.
For a translator, put the languages and the kind of text in the focus areas, for example "Spanish to English, legal contracts". The interviewer starts from the focus areas.
Reading a high score as proof of skill.
A high Craft and accuracy score means the candidate described careful, checked work in detail. It does not check that the story is true, so confirm it with samples and references.
Results
What you see for each candidate
Editorial judgment and accuracy, with quotes
Each of the four scored areas gets a score out of 100 with the candidate's own sentences beside it, or "Not enough evidence" when no answer reached it. The full transcript sits under them, so you can read every answer in order.
Three checks under every score
A specific case, a trade-off weighed, a measured result. A writer who said "I always check my sources" and never named one piece shows "Not yet" on the first check.
Which answers were pasted
A typed answer with pasted text in it is marked "Typed, pasted". For writing roles that is worth knowing: pasted prose shows what someone can prepare, not how they reason on the spot. The mark is not part of the score.
Answers in Spanish, kept in Spanish
A result from an interview held in Spanish is labelled "Interview language: Spanish". Its quotes stay in the candidate's Spanish words, so a bilingual reviewer can read them as said.
The four scored areas
Each out of 100, with quotes.
- Editorial judgment (problems found, edits made)
- Counts as evidence when the candidate describes a specific writing, editing or translation problem: what was wrong, the options, the choice they made, or how they knew it worked.
- Craft and accuracy (structure, sourcing, tone, terminology)
- Counts as evidence when the candidate describes how they produce accurate, well-structured work: research, sourcing, fact-checking, structure, style guides, tone, terminology or translation choices.
- Communication (briefs, edit notes, pitches)
- Counts as evidence when the candidate describes explaining their work or decisions to other people: briefs, edit notes, pitches, style guidance, or walking a client through changes. Answers that respond to the question asked, in a clear order, with a concrete example, also count, but only up to 80 on their own. Grammar, word choice and fluency are never judged.
- Collaboration (editors, clients, subject experts)
- Counts as evidence when the candidate describes working with editors, authors, clients, subject experts, designers or reviewers, including handling feedback and disagreement. Saying "we" is not, by itself, collaboration evidence.
Aethel never scores faces, voices or accents, and does not verify degrees, licenses or work history. How Aethel uses AI
FAQ
Questions hiring teams ask
Does the interview test their writing?
No. It is a conversation, so it hears how they talk about their writing and editing choices. Use a writing sample or a short paid test for the craft itself.
Can it check translation quality?
No. It does not test a second language. It can ask a translator how they handle terms, tone and errors, which you can weigh next to a sample.
Can we focus it on technical or UX writing?
Yes. Pick technical writer as the specialty, or add docs or product copy as a focus area, and the questions move to that kind of work.
See also the questions companies ask and the pricing page.
Send your first writing, editing or translation interview link
Want to show candidates what to expect? What the interview covers for writers, editors and translators
Interview candidates in other fields
- Software engineering
- Data and machine learning
- Design
- Product management
- Finance and accounting
- Law and compliance
- Healthcare and life sciences
- Healthcare support and caregiving
- Science and research
- Education and training
- Childcare and early education
- Sales and customer success
- Customer service and support
- Retail, food and hospitality
- Administration and office support
- Government and public service
- Nonprofit, church and community work
- Skilled trades and facilities
- Operations and other fields