This page needs a newer browser to run its tools. You can still read everything here.

Professional English for Developers Module 2

Clear writing foundations interview questions

Interview questions on clear writing foundations: short warm-ups, then what each harder question tests, the first step of a good answer and its follow-ups.

19 questions: 5 warm-ups and 14 with model answers · Levels: Fresher to staff

Warm-up questions

Short questions with short answers, each answered in full.

Fresher to mid

When is the passive voice the right choice in technical writing?

Answered in the lesson Plain English sentences: short, active, direct
Fresher to mid

Why do style guides tell you to delete words such as "simply" and "just" from instructions?

Answered in the lesson Concise and precise: words for technical writing
Fresher to mid

Why do global style guides say to avoid "since" and "while" in technical text?

Answered in the lesson Writing for a global audience in tech teams
Fresher to mid

When do you use a numbered list, and when a bulleted list?

Answered in the lesson Structure and formatting: text people can scan
Fresher to mid

Why ask a writing assistant for one narrow edit instead of "make this better"?

Answered in the lesson AI writing assistants and translation: used well

Questions with model answers

What each question tests, the first step of a good answer and the follow-ups to expect.

Fresher to mid

Your manager forwards a one-sentence incident notice of about 60 words that is about to go to customers, and asks you to fix it in ten minutes. Walk through what you change, in what order, and how you make sure nothing is lost.
What it tests

Breaking a long sentence into its ideas, leading with the news, choosing active verbs, and checking every fact before sending under time pressure.

First step

List the facts before you touch the wording: what is broken or changed for the customer, since when, the cause if it is confirmed, what is being done and when the next update comes. Then write the customer's news as the first sentence, with an actor and a verb.
Follow-ups
- The notice also goes to a partner who reads English as a second language. What else do you change?
- Legal asks you not to name the cause yet. How do you write the sentence about it?
- How do you check the rewrite in the minutes you have left?
From the lesson Plain English sentences: short, active, direct
Model answer, Pro. Model answers open with any pass; prices are in the notice on this page.
Opening the model answers with your pass…
Model answers open with any MySmartCoPilot pass.
Pro pass · 1 week₹79$2.99
30 days₹179$5.99
1 year₹1,699$45
One payment; a pass never renews. The price shown is the total you pay: no fees or charges are added at checkout.
Passes can’t be bought right now, so the model answers can’t be opened at the moment. If you have a pass, enter your licence key.
Choose a pass I have a licence key
It also opens every other in-depth part in Learn and every Pro tool. Sales are final, except where the law gives you a right to withdraw, for example in the EU and the UK (refund policy).
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Mid to senior

Two teammates comment on your postmortem draft. One says its passive sentences hide who did what. The other says active sentences would blame people. How do you rewrite it so that both concerns are met?
What it tests

Choosing the voice sentence by sentence: systems and roles as actors where readers need them, and the event as the subject where naming a person would blame them.

First step

Sort the sentences by what they report: actions of systems, decisions of roles and the actions of individuals during the incident. Systems and roles can be the actors of active sentences; for an individual's mistake, make the event the subject.
Follow-ups
- The timeline says "the config was changed" and nobody knows by whom. What do you write?
- How do you write the action items so that someone owns each one?
- A manager asks for the name of the engineer who ran the command. What do you do?
From the lesson Plain English sentences: short, active, direct
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Fresher to mid

A README's first paragraph runs to 140 words before the reader learns what the tool does. You are asked to halve it without losing a single fact. How do you go about it?
What it tests

Separating facts from padding, cutting wordy phrases, judgement words and unmeasured claims, and putting what the tool does first.

First step

Copy the paragraph and list its facts on their own lines first: what the tool does, how to install and start it, what it works with and its limits. Then rebuild the paragraph from that list, starting with what the tool does.
Follow-ups
- The team likes the friendly tone of the original. What do you keep?
- The paragraph calls the tool "the fastest", and nobody has measured it. What do you do?
- How do you check that nothing was lost?
From the lesson Concise and precise: words for technical writing
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Mid to senior

Your API documentation calls one thing a workspace, a project and a space. Users open support tickets because they think these are three features. What do you change, and how do you stop it from happening again?
What it tests

Choosing one term for one concept, fixing every place users meet it, and making the decision last beyond this one fix.

First step

Start from the reader: confirm that the three names really are one thing, then decide which single name the product, the API and the documentation will all use, with the cost of changing each in mind.
Follow-ups
- The API field is called project_id and cannot change. What do you write in the docs?
- How do you keep new pages from drifting again?
- Translators ask why the same feature has three names. What do you send them?
From the lesson Concise and precise: words for technical writing
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Mid to staff

An integration partner read "the client should retry" in your API specification as optional, and their client never retries. Your team says it was obviously required. Who is right, and how should the specification have been written?
What it tests

Knowing what requirement words mean in a specification and in a guide, and writing a requirement that implementers cannot read two ways.

First step

Before taking sides, check whether the specification declares how its requirement words are to be read, and how this sentence was written. Then decide what the behaviour really needs to be, required or recommended, and only then choose the word.
Follow-ups
- The specification declares nothing about its key words. What changes?
- Partners have already shipped clients that never retry. What do you do?
- How would you catch this before the specification is published?
From the lesson Concise and precise: words for technical writing
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Mid to senior

Your team lead's chat posts are full of idioms such as "let's circle back" and "low-hanging fruit", and they go to colleagues in three countries, some of whom read them through a translation tool. You are asked to help. What do you change, and how do you raise it?
What it tests

Rewriting idioms as their plain meaning plus the facts they hide, and raising a colleague's writing habit respectfully and usefully.

First step

Take one real post and rewrite it with the lead, phrase by phrase: say what each idiom means, and add the facts it hides, such as when the second discussion happens and which fixes count as the quick ones.
Follow-ups
- The lead says idioms make messages friendlier. What do you answer?
- How do you make the habit stick for the whole team?
- A colleague asks what "boil the ocean" means. How do you explain it?
From the lesson Writing for a global audience in tech teams
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Senior to staff

Your analytics show that a third of your documentation's readers use a browser's translation feature. Which changes to the writing make the biggest difference for them, and how would you check that they worked?
What it tests

Knowing which features of English break translation, putting fixes in order of impact, and testing without sending confidential text to third-party tools.

First step

Start with the patterns that cause wrong translations rather than awkward ones: words with two meanings, idioms, undefined abbreviations and very long sentences. Look for them first on the pages that most translated readers visit.
Follow-ups
- How do you test pages without reading every target language?
- The product team wants a casual, friendly tone. Is that a conflict?
- Which pages do you fix first, and why?
From the lesson Writing for a global audience in tech teams
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Fresher to mid

A new teammate says the team's docs and chat are full of abbreviations they cannot look up, such as a11y, RC and o11y. How do you handle abbreviations when you write for a global team?
What it tests

Deciding which abbreviations to keep, defining them where readers first meet them, and limiting how many a reader has to hold at once.

First step

Sort the abbreviations by your readers, not by yourself: which ones would a new colleague in another country already know?
Follow-ups
- Chat messages have no room for full forms. What then?
- Which abbreviations can stay undefined?
- How do you stop new ones from creeping back in?
From the lesson Writing for a global audience in tech teams
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Fresher to mid

Your 300-word onboarding email keeps getting replies that ask things it already answers. How would you restructure it, and how would you know that the new version works?
What it tests

Putting the request first, splitting topics into paragraphs, choosing the right kind of list for steps and for sets, and checking the result with evidence.

First step

Find what the email asks the reader to do, and by when, and move it to the first or second sentence. Then sort the rest into what the reader does in order and what they only need to look up.
Follow-ups
- The welcome paragraph matters to the sender. Where does it go?
- Many readers open the email on a phone. What changes?
- How do you measure whether fewer questions come back?
From the lesson Structure and formatting: text people can scan
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Mid to senior

A teammate removes the serial commas from your documentation to match another team's style guide. When does the comma change the meaning, and how do you settle the disagreement?
What it tests

Knowing when punctuation changes meaning, and settling a style dispute with a written rule rather than personal taste.

First step

Find a sentence in your own documentation whose meaning changes when its serial comma goes, and show both readings. Then agree which guide the documentation follows.
Follow-ups
- The other team's guide is the company standard. What then?
- Which other punctuation mark causes the same kind of problem?
- How do you stop the argument from coming back?
From the lesson Structure and formatting: text people can scan
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Fresher to senior

Half your team writes "colour" and half writes "color" in the same documentation, and the code samples use "color". How do you decide, and what do you change?
What it tests

Choosing one spelling variety for prose, keeping code in its platform's spelling, and making the decision last.

First step

List where each spelling appears: in prose, in code samples or in interface labels. Then check whether the company or the client already names a variety; if not, choose one for each type of document.
Follow-ups
- Your product's interface uses US spelling and your docs use UK spelling. Is that a problem?
- How do you make the spell checker enforce the choice?
- A customer complains about "American spelling". What do you answer?
From the lesson Structure and formatting: text people can scan
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Fresher to mid

You asked an AI writing assistant to polish an email to an important client, and it reads much better. Before you send it, what exactly do you check, and how?
What it tests

Treating fluent output as unchecked, and checking facts, commitments, certainty and tone against your own draft, change by change.

First step

Put your draft and the polished version side by side in a diff, so that every change is visible. Then check each change that touches something the client will act on, before you look at style.
Follow-ups
- The diff shows thirty changes. Where do you start?
- The new version is more polite than you would be. Do you keep it?
- Your manager says to trust the tool and save time. What do you answer?
From the lesson AI writing assistants and translation: used well
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes
Mid to senior

A colleague writes HR and client messages in their first language and sends the machine translation into English without reading it. Nothing has gone wrong yet. What do you advise, and why?
What it tests

Knowing where machine translation is safe and where it is not, and giving advice that is practical and respectful.

First step

Separate the messages by their weight: a chat message to a teammate is low risk, while a message that commits the company, refuses something or touches HR or legal matters is high risk. Start the advice there.
Follow-ups
- The colleague's English is weak, and writing in English takes them hours. What then?
- The messages contain employee names and salaries. Does that change anything?
- How would you check a translated message without speaking the source language?
From the lesson AI writing assistants and translation: used well
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 3 minutes
Fresher to mid

Your team asks contributors to disclose AI help in pull requests. An assistant rewrote your PR description and drafted two of the tests. What do you write in the PR, and why does the rule exist?
What it tests

Following a disclosure rule specifically and honestly, and understanding why a team asks for it.

First step

Start from the rule itself: read what the team asks contributors to disclose, and where. Then make sure that you can explain every line of the change without the tool.
Follow-ups
- The assistant's tests pass. Is that enough?
- The rule is not written down anywhere. What do you do?
- An interviewer asks whether you use AI at work. How do you answer?
From the lesson AI writing assistants and translation: used well
Model answer, Pro.
In the answer:
- Model answer
- Follow-up answers
- Common mistakes
- Rubric
- Variants
- about 2 minutes

The lessons of this module

Plain English sentences: short, active, direct Free lesson, Pro answers: 15 minutes
Concise and precise: words for technical writing Free core, Pro depth: 7 of 20 minutes free
Writing for a global audience in tech teams Free core, Pro depth: 7 of 20 minutes free
Structure and formatting: text people can scan Free core, Pro depth: 8 of 20 minutes free
AI writing assistants and translation: used well Free core, Pro depth: 9 of 25 minutes free

All Professional English for Developers interview questions · The Professional English for Developers track

Warm-up questions

When is the passive voice the right choice in technical writing?

Why do style guides tell you to delete words such as "simply" and "just" from instructions?

Why do global style guides say to avoid "since" and "while" in technical text?

When do you use a numbered list, and when a bulleted list?

Why ask a writing assistant for one narrow edit instead of "make this better"?

Questions with model answers

Your manager forwards a one-sentence incident notice of about 60 words that is about to go to customers, and asks you to fix it in ten minutes. Walk through what you change, in what order, and how you make sure nothing is lost.

Two teammates comment on your postmortem draft. One says its passive sentences hide who did what. The other says active sentences would blame people. How do you rewrite it so that both concerns are met?

A README's first paragraph runs to 140 words before the reader learns what the tool does. You are asked to halve it without losing a single fact. How do you go about it?

Your API documentation calls one thing a workspace, a project and a space. Users open support tickets because they think these are three features. What do you change, and how do you stop it from happening again?

An integration partner read "the client should retry" in your API specification as optional, and their client never retries. Your team says it was obviously required. Who is right, and how should the specification have been written?

Your team lead's chat posts are full of idioms such as "let's circle back" and "low-hanging fruit", and they go to colleagues in three countries, some of whom read them through a translation tool. You are asked to help. What do you change, and how do you raise it?

Your analytics show that a third of your documentation's readers use a browser's translation feature. Which changes to the writing make the biggest difference for them, and how would you check that they worked?

A new teammate says the team's docs and chat are full of abbreviations they cannot look up, such as a11y, RC and o11y. How do you handle abbreviations when you write for a global team?

Your 300-word onboarding email keeps getting replies that ask things it already answers. How would you restructure it, and how would you know that the new version works?

A teammate removes the serial commas from your documentation to match another team's style guide. When does the comma change the meaning, and how do you settle the disagreement?

Half your team writes "colour" and half writes "color" in the same documentation, and the code samples use "color". How do you decide, and what do you change?

You asked an AI writing assistant to polish an email to an important client, and it reads much better. Before you send it, what exactly do you check, and how?

A colleague writes HR and client messages in their first language and sends the machine translation into English without reading it. Nothing has gone wrong yet. What do you advise, and why?

Your team asks contributors to disclose AI help in pull requests. An assistant rewrote your PR description and drafted two of the tests. What do you write in the PR, and why does the rule exist?