LIKELY QUESTIONS
- What interests you about the Engineer II role at the Water Resources Authority, and why do you want to work on dams, water pans, and flood mitigation structures?
- How would you approach inspecting a proposed site for a water infrastructure project?
- What key factors would you check when assessing dam safety compliance as an entry-level engineer supporting a senior team?
- Describe how you would compile, analyze, and present engineering or flood-related data in a clear technical report.
- Tell us about your experience with survey work, site measurements, or interpreting drawings, maps, or topographic information.
- Which computer applications or engineering tools are you comfortable using, and how would they help you in this role?
- Field work can involve remote locations, difficult weather, and tight timelines. How would you manage safety, accuracy, and productivity in such conditions?
- This role requires maintaining repositories of water infrastructure information. How would you ensure data is accurate, organized, and easy to retrieve?

BEHAVIOURAL QUESTIONS
- Tell us about a time you worked on a technical project with incomplete or inconsistent data.
Model approach: Situation - Briefly describe the project or assignment and the missing data problem. Task - Explain what analysis or output you were responsible for. Action - Show how you verified sources, organized available data, noted assumptions, consulted supervisors or teammates, and used a structured method to avoid errors. Result - Quantify the outcome, such as a completed report, improved accuracy, or timely submission, and mention what you learned about engineering judgment.
- Describe a time you worked effectively in the field or under difficult site conditions.
Model approach: Situation - Give an example involving weather, access issues, terrain, or limited resources. Task - State your role in collecting measurements, observations, or inspections. Action - Explain how you prepared equipment, followed safety procedures, coordinated with others, adapted the plan, and maintained data quality. Result - Highlight successful completion of the task, safe execution, and any useful findings or recommendations produced.
- Give an example of when you had to communicate technical information to someone who was not an engineer.
Model approach: Situation - Identify the context such as a class project, attachment, internship, or community setting. Task - State what needed to be explained and to whom. Action - Describe how you simplified terms, used visuals or examples, focused on practical implications, and checked understanding. Result - Show that the audience understood, approved, or acted on the information, demonstrating clear communication.
- Tell us about a time you noticed a potential risk, error, or compliance issue and took action.
Model approach: Situation - Describe the technical or procedural issue you observed. Task - Clarify your responsibility and why it mattered. Action - Explain how you checked the facts, documented the issue, escalated appropriately, and suggested a practical solution while respecting reporting lines. Result - Share how the risk was reduced, rework was avoided, or safety/compliance improved.

SMART QUESTIONS TO ASK
- How is the Engineer II role structured between office-based analysis, report writing, and field inspection work?
- What technical standards, dam safety guidelines, or inspection frameworks does the Authority use most often for this team?
- What would success look like in the first 6 to 12 months for someone joining at Engineer II level?
- What kind of mentorship, training, or supervised exposure is provided to help junior engineers build competence in dam safety and flood monitoring?
- How does the Authority coordinate engineering assessments with environmental, hydrological, and enforcement teams during infrastructure inspections?

RED FLAGS TO WATCH FOR
- Vague answers about field safety procedures, transport, protective equipment, or supervision during site inspections.
- No clear onboarding, mentorship, or review process for entry-level engineers handling technical assessments and reports.
- Unclear workload expectations, for example frequent emergency field demands without sufficient staffing, tools, or prioritization systems.