5 exercises — choose the most professional response to real freelance client communication scenarios: scope creep, delays, rate negotiation, deliverable alignment, and payment follow-up.
Professional communication principles for freelancers
Acknowledge before redirecting: validate the client's idea before explaining why it changes scope
Be specific: name the invoice number, exact date, concrete impact — vagueness reads as unprofessional
Offer a path forward: every difficult message should end with a next step or question
Consequences, not threats: state what happens next as a business fact, not a warning
0 / 10 completed
1 / 10
A client emails mid-project: "Can we also add a mobile app to the website redesign? It shouldn't take long." Which response handles scope creep most professionally?
Option A is the best response: it opens by validating the idea (not rejecting it), explains clearly why it's a separate project (different platforms, technologies, testing), redirects to the current project value, proposes a clear next step (a follow-on proposal), and ends with a question to maintain collaboration. Option D is correct in content but uses contractual/transactional language ("revise the contract," "change request") which can feel adversarial. Option C implies willingness to add scope before any budget discussion — a risk. Option B is too blunt. Key freelance communication principle: never say "that's out of scope" as your opening line. Acknowledge the idea, explain the implications, propose a path forward.
2 / 10
You are 3 days behind schedule on a client project due to an unexpected technical issue. How do you communicate this?
Option A is the strongest: it names the specific issue (not vague "technical problems"), states the exact impact (3 days), gives the revised date clearly, reports that the core issue is resolved (reducing client anxiety), explains the communication timing rationale (as soon as I had a clear picture), and offers a collaborative next step (prioritising deliverables). Option D is good — names the feature, gives a specific new date, and promises updates — but doesn't mention that the issue was already resolved. Option C is accurate but terse and ends negatively (apologising for inconvenience). Option B is too vague — "a bit late" and "a few more days" signals unprofessionalism. Delay communication formula: specific cause + exact impact + new date + current status + offer to collaborate.
3 / 10
A prospective client asks: "What's your daily rate?" How do you respond professionally?
Option A is the strongest: it names the rate directly (not evasive), explains the basis for it (specialisation, level, what's included), then pivots to a qualifying question — showing you understand that rate structure choice (day rate vs fixed vs retainer) depends on project type — and ends with a collaborative step. Option D is a legitimate positioning choice (fixed-price preference) but doesn't answer the question and may frustrate the client. Option C avoids answering entirely — a common freelancer mistake that signals either lack of confidence or no established pricing. Option B answers with nothing but the number — valid but misses the opportunity to justify the rate and understand the client. Key principle: name your number, justify it briefly, then reframe toward understanding the project.
4 / 10
At the start of a project, how do you establish clear agreement on deliverables to avoid disagreements later?
Option A is the strongest: it lists all the components of a proper scope document (inclusions, explicit exclusions, revision rounds, delivery format, milestones with sign-off), explains why each matters, and adds the proactive practice of progress updates mid-project — a technique specifically designed to prevent the final-delivery surprise that causes most scope disputes. The meta-insight ("that's not what I imagined" moment) shows experience. Option C mentions the change order clause — a critical contractual protection. Option B covers the basics (brief, confirmation, revision rounds). Option D focuses on alignment through conversation — useful but relies on a verbal process that leaves too much room for misremembering. Most important protection: explicitly list what is NOT included — exclusions prevent as many disputes as inclusions.
5 / 10
A client is late on payment. Which message is most likely to get paid while preserving the relationship?
Option A is the strongest: professional opening ("following up"), specific invoice details, offers to help (resend, documentation — removing client friction), and includes a concrete consequence (work pauses at next milestone) without threats. This makes the cost of non-payment clear without being aggressive. Option D is good — specific, assumes good faith ("sure this is just an oversight"), and asks for a date rather than immediate payment — a softer first chase. Option C's immediate threat ("forced to pause work," "charge late fees") is appropriate for a third chase but not a first follow-up — it damages the relationship unnecessarily. Option B lacks invoice details and has no consequence. Chase email framework: specific details → offer to help → clear consequence → professional close. The key difference between Option A and C: Option A states a business consequence; Option C makes a threat. Both are valid but appropriate at different stages.
6 / 10
Sarah, the client project manager, sends you this Slack message: 'Hey Devs, just a quick reminder – the new user authentication flow needs to be *super* responsive. Users are complaining about delays.' What's the most appropriate response to acknowledge the feedback and request clarification?
This question tests your ability to handle vague client feedback. Option 1 demonstrates a proactive approach by seeking concrete metrics. Options 2 and 3 are insufficiently detailed, failing to address the core issue of 'super responsive'. Option 4 is passive and doesn't move towards a solution.
7 / 10
You're reviewing a pull request submitted by a junior developer. The PR contains several new features but the code is poorly documented and uses overly complex logic. You leave this comment on the PR: 'This feature looks great, but it's difficult to understand without more context. Could you add comments explaining the key steps?' Which of the following best reflects the tone of this feedback?
This assesses constructive feedback skills. Option 1 is overly enthusiastic and doesn't offer guidance. Option 2 provides direct criticism with clear expectations for improvement. Options 3 and 4 are too vague or prioritize the wrong aspect (performance) over fundamental code quality.
8 / 10
During a daily standup meeting, you need to inform your team about a potential delay on a project. The primary cause is a dependency on an external API that's experiencing intermittent downtime. What's the most effective way to communicate this update?
This focuses on transparency and proactive communication. Option 1 downplays the issue, potentially misleading the team. Option 2 clearly explains the problem, its impact, and your actions. Options 3 and 4 are evasive and fail to inform the team about a critical dependency.
9 / 10
You're starting a new project with a client. To ensure clarity, you draft this PR description for your initial commit: 'Implemented user registration functionality using React and Node.js.' Which of the following additions would most improve this description?
This tests your ability to write effective PR descriptions. Option 1 is too technical and doesn't explain the purpose. Option 2 provides context about the user experience. Options 3 and 4 focus on implementation details rather than the overall functionality.
10 / 10
A client is three weeks overdue on their payment. You send them this email: 'Hi [Client Name], We're writing to follow up on invoice #INV-2023-10 regarding the project deliverables completed as per our agreement. We understand that unforeseen circumstances can arise, but timely payments are crucial for maintaining a strong working relationship.' Which of the following would be the best next step after sending this email?
This assesses handling difficult client conversations. Option 1 is unprofessional and risks damaging the relationship. Option 3 demonstrates a proactive approach by attempting to resolve the issue directly. Options 4 represents repeating the same ineffective communication strategy.
What does "Freelance Developer Interview Questions — Client Communication Practice" cover?
Practice professional English for freelance client communication: scope creep, delays, rate negotiation, deliverables, and payment follow-up in 5 structured exercises.
How many questions are in this interview set?
This set has 10 exercises, each with a full explanation.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do these exercises include model answers?
Yes. Each interview question gives you several possible responses and asks you to pick the one that communicates most clearly and completely — the explanation then breaks down exactly why that answer works, including the specific vocabulary a strong candidate would use.
What if I choose an answer that isn't the strongest one?
You'll see which option was correct and read a full explanation of why it's stronger than the alternatives, plus the key vocabulary and phrasing worth reusing in a real interview.
Can I retry the questions?
Yes — use the "Try again" button on the results screen to reset and go through the set again.
Is this the same as a real technical or behavioural interview?
No — it's focused practice for the language side of interviewing: recognising which phrasing sounds precise and confident versus vague, and knowing the vocabulary interviewers expect for this role. It won't replace mock interviews, but it builds the vocabulary you'll need in one.
Where can I find interview prep for other roles?
Browse the full Interview exercises hub for 170+ modules covering behavioural, technical, and system design rounds across dozens of IT roles, or check the "Next up" link below to continue.
Do I need an account, and is my progress saved?
No account is needed. Progress is tracked only for your current visit — reloading or leaving the page resets the counter.
Who writes these interview questions?
Every question is written by the CoderSlingo team based on real technical interview patterns for this role, then reviewed for accuracy and clarity.