LIKELY QUESTIONS
- Can you walk us through your experience in hydrological data compilation, cleaning, quality control, analysis, and reporting, and the tools you have used?
- Describe a hydrological modelling project you have led or significantly contributed to. What model did you use, what inputs were required, and how did the outputs influence decisions?
- How would you approach designing or reviewing a hydrological monitoring network for a catchment with limited historical data and budget constraints?
- Tell us about your experience updating river rating curves or rating equations. How did you deal with changing channel conditions, backwater effects, or inconsistent gauging data?
- How have you used GIS and spatial analysis to support water availability assessments, flood vulnerability mapping, or permit evaluation?
- What factors would you consider when evaluating hydrological reports submitted for water use projects, and how would you identify weak assumptions or risks?
- How would you prepare flood advisories and seasonal outlook reports for both technical and non-technical stakeholders in Kenya?
- This role involves collaboration across technical teams and stakeholders. How have you worked with engineers, planners, field officers, counties, or community stakeholders to deliver hydrology-related outcomes?

BEHAVIOURAL QUESTIONS
- Tell us about a time you found major errors or gaps in hydrological data that could have led to a wrong conclusion.
Model approach: Situation: A basin assessment relied on long-term river flow and rainfall data with inconsistencies. Task: Validate the dataset and produce a defensible analysis within a tight reporting deadline. Action: Explain how you audited metadata, checked outliers and missing values, compared station records with nearby gauges and rainfall-runoff relationships, documented assumptions, and rebuilt the cleaned dataset. Result: Show improved confidence in the analysis, correction of the water availability estimate, and acceptance of the report by decision-makers.

- Describe a time you had to explain complex hydrological findings to non-technical stakeholders.
Model approach: Situation: Flood risk or water allocation findings needed to be shared with managers, county officials, or permit applicants. Task: Make technical results understandable and actionable. Action: Describe how you translated model outputs into maps, simple scenarios, risk categories, and clear recommendations, while anticipating questions and addressing uncertainty honestly. Result: Stakeholders understood the implications, made timely decisions, and there was less misunderstanding or pushback.

- Give an example of when you had to work with a multidisciplinary team to solve a water resources problem.
Model approach: Situation: A project involved hydrologists, GIS staff, engineers, environmental specialists, and field teams. Task: Integrate inputs into one coherent assessment or recommendation. Action: Explain how you clarified roles, aligned datasets and assumptions, set review checkpoints, resolved technical disagreements using evidence, and kept outputs decision-focused. Result: The team delivered a robust product on time, and your contribution improved technical quality and coordination.

- Tell us about a time you managed competing deadlines or urgent field and reporting demands.
Model approach: Situation: You had simultaneous demands such as permit reviews, flood reporting, modelling updates, and field data verification. Task: Prioritize high-risk, high-impact work without compromising quality. Action: Describe how you triaged tasks, delegated where possible, used workplans and milestones, communicated trade-offs early, and maintained quality assurance on critical outputs. Result: Deadlines were met, urgent risks were addressed first, and there were no major quality issues or stakeholder complaints.

SMART QUESTIONS TO ASK
- How does WRA currently prioritize hydrological work across water allocation, flood risk management, and monitoring network development, and where would this role add the most value in the first 12 months?
- What hydrological models, GIS platforms, databases, and telemetry or monitoring systems are currently in use, and are there plans to modernize or integrate them further?
- What are the biggest technical challenges WRA is facing right now in relation to data quality, ungauged catchments, flood forecasting, or climate variability?
- How is success measured for this role - for example through quality of technical reviews, improvement in monitoring coverage, turnaround time for permit support, or impact on planning decisions?
- How does the Authority coordinate with counties, disaster management agencies, meteorological services, and other water sector institutions during flood advisories and seasonal outlook preparation?

RED FLAGS TO WATCH FOR
- Vague answers about data systems, modelling tools, station maintenance, or quality assurance may indicate weak technical infrastructure or unclear expectations for the role.
- If they cannot explain decision authority, reporting lines, or how hydrology supports permit evaluation and planning, it may suggest role ambiguity and potential bottlenecks.
- If they downplay field realities, budget constraints, staff capacity, or inter-agency coordination challenges, that may signal unrealistic expectations or limited operational support.