Define the role before the interview
A useful interview begins with a clear decision about the work. Write down the essential outcomes, tools, working pattern, reporting relationship and level of autonomy. Separate requirements from skills that can be learned. This gives every candidate a fairer and more consistent conversation.
Review evidence before forming conclusions
Look for experience connected to the role: comparable responsibilities, relevant projects, portfolios, code or writing samples, systems used and outcomes achieved. Ask what the candidate personally owned when an example involved a team. Do not request confidential material from a former employer or client.
Use a structured interview
Ask all candidates the same core questions, with follow-ups based on their answers. A simple scorecard can cover role knowledge, problem solving, communication, remote-working readiness and availability. Structure does not remove judgement; it makes the basis of that judgement clearer.
Plan the interview sequence
Open by explaining the role and the format of the conversation. Move from comparable core questions to evidence from the candidate’s experience, then leave time for their questions. If several interviewers participate, assign topics and agree who records the final evidence so candidates do not repeat the same conversation unnecessarily.
Useful example questions
- Which past responsibility is most similar to this role, and what did you personally deliver?
- Describe a problem you could not resolve alone. How did you communicate it and what happened next?
- How do you plan work and make progress visible when your manager is offline?
- Tell us about a time requirements changed. How did you clarify priorities?
- Which tools in this role have you used in real work, and what did you use them to achieve?
- What working hours can you reliably maintain, and where do you need flexibility?
- What information or support would help you perform well in the first month?
Assess communication in context
Communication requirements vary. A customer-facing role may need concise written responses under pressure; a developer may need to explain a technical trade-off; an accountant may need to flag a reconciliation issue accurately. Evaluate the form of communication the work actually requires rather than applying a vague standard.
Discuss remote-working readiness
Ask how the candidate manages priorities, interruptions, documentation and blockers. Explain your own meeting rhythm, channels and response expectations. Where equipment, connectivity or a private workspace are material, discuss them specifically and agree who provides what.
Confirm working hours and time-zone overlap directly. Kenya’s relationship to your working day will depend on where your team is based and whether the role needs real-time coverage. Do not infer availability from location.
Choose a proportionate practical assessment
A short, role-relevant exercise can test judgement more directly than abstract questions. Use fictional or sanitised material and define what you are assessing. Examples include drafting a customer reply, reviewing a small code sample, reconciling a sample ledger, organising a diary conflict or editing a short passage.
Keep the task bounded. Consider payment when an assessment is lengthy or produces useful commercial work. Candidates should not be asked to disclose confidential information or complete an active business project without appropriate terms.
Compare candidates fairly
Record evidence shortly after each interview and compare it with the criteria established at the start. Avoid nationality-based assumptions and vague “culture fit” judgements. If collaboration style matters, describe the behaviour you need—for example documenting decisions or raising risks early.
References may be appropriate for some roles, but obtain permission and decide what relevant information you need to verify. Qualifications should also be checked when they are important to the responsibilities.
Avoid common interview errors
Do not let a relaxed conversation replace evidence, or change standards midway because one candidate has an interesting background. Avoid questions unrelated to the work and do not infer capability from confidence alone. Give candidates enough information to understand what a good answer requires.
When language or communication is important, assess it through realistic role activity rather than assumptions about Kenyan professionals as a group. Record what was demonstrated and where further verification is needed.
Make the working relationship clear
Before a final decision, ensure the candidate understands the scope, compensation, currency, payment timing, manager, tools and expected start. Be honest about challenges and invite questions. A candidate is also deciding whether your organisation can support good remote work.
Continue with the guide to onboarding a remote professional in Kenya, or return to the complete remote hiring guide.
Find the right professional for your team
Browse public profiles to compare skills, experience, availability and working preferences before you begin a conversation.