LIKELY QUESTIONS
- Can you walk us through your academic background and explain how it prepares you for a Water Resources Officer II (Permitting) role?
- What do you understand about the purpose of water permitting under the Water Act 2016 and the Water Resources Regulations 2025?
- How would you receive, verify, and document a permit application to ensure it is complete and ready for technical evaluation?
- This role requires maintaining permit registers, databases, and filing systems. What systems or methods would you use to keep records accurate, current, and easy to retrieve?
- Suppose an applicant submits incomplete or unclear information. How would you handle the situation while maintaining professionalism and regulatory compliance?
- How would you prioritize multiple permit applications and coordinate their distribution to the relevant technical officers without delays?
- What is your experience with computer applications, data entry, spreadsheets, databases, or GIS-related tools, and how could you apply those skills in this role?
- Why do you want to work for the Water Resources Authority, and how do you see yourself contributing to equitable and sustainable water resource management in Kenya?

BEHAVIOURAL QUESTIONS
- Tell us about a time you had to manage a large volume of records, data, or documents accurately under time pressure.
Model approach: Situation - Briefly describe the task, such as managing project files, lab data, or student research records. Task - Explain the need for accuracy and deadlines. Action - Describe how you created a checklist, used spreadsheets or folders, verified entries, and tracked progress. Result - Quantify the outcome, such as zero missing records, faster retrieval, or on-time completion.

- Describe a situation where you had to explain a technical or procedural issue to someone who was unfamiliar with it.
Model approach: Situation - Identify a case involving a class project, attachment, internship, or customer-facing task. Task - State that your goal was to help the person understand the process clearly. Action - Explain how you used simple language, broke the process into steps, checked understanding, and remained patient. Result - Show that the person completed the process correctly or that confusion was reduced.

- Give an example of a time you worked with others to complete a task that required coordination and attention to detail.
Model approach: Situation - Mention a group assignment, field exercise, internship task, or departmental activity. Task - Explain your role in ensuring information moved correctly between team members. Action - Describe how you assigned responsibilities, shared updates, followed up, and checked details before submission. Result - Highlight successful completion, improved teamwork, or reduced errors.

- Tell us about a time you identified an error or inconsistency in information and what you did about it.
Model approach: Situation - Describe a case involving data entry, lab results, mapping data, forms, or reports. Task - Explain that you needed to protect accuracy and avoid downstream problems. Action - Show that you reviewed the source documents, confirmed the discrepancy, informed the right person, corrected it, and improved the checking process. Result - Emphasize prevented mistakes, improved quality, or smoother processing.

SMART QUESTIONS TO ASK
- How is the permitting unit structured, and how does this role interact with technical evaluators, compliance teams, and regional offices?
- What does success look like in the first 6 to 12 months for someone joining as a Water Resources Officer II (Permitting)?
- What systems or platforms does the Authority currently use for permit registers, records management, and application tracking?
- What are the most common challenges the permitting team faces, for example incomplete applications, turnaround times, or data quality, and how can a new officer help address them?
- What training and mentorship are provided on the Water Act 2016, the Water Resources Regulations 2025, and internal permitting procedures?

RED FLAGS TO WATCH FOR
- Vague answers about training, onboarding, or supervision for an entry-level role, which may suggest limited support despite the technical and regulatory demands.
- No clear explanation of workload, turnaround expectations, or systems for tracking applications, which may indicate process gaps or operational disorder.
- Signals that applicants or external stakeholders are handled inconsistently or informally rather than through clear procedures, which can point to compliance and governance risks.