Technical practice
How would you map a client's building hierarchy, point names and tags to an internal standard?
What to coverSuggested preparation: Explain how you would establish what each point represents, check its relationship to equipment and flag ambiguous or inconsistent names before mapping them. Describe how you would document decisions so another team can review them.
How would you interpret an HVAC design before digitalizing a building?
What to coverSuggested preparation: Discuss how equipment, served areas and control relationships help you understand the building hierarchy. Explain what design information you would document and what you would clarify rather than assume.
What control concepts matter when integrating AI-enabled optimization with an existing HVAC control system?
What to coverSuggested preparation: Draw on DDC, PLC or similar building-automation experience to explain control sequences, operating limits and how a proposed change interacts with existing controls. Discuss the trade-off between energy efficiency and maintaining appropriate building operation without assuming a particular site design.
How would you use Python scripts and a front-end interface to support building digitalization?
What to coverSuggested preparation: Describe a plausible division of work between repeatable data checks or transformations in scripts and review or correction in the interface. Explain how you would verify outputs against source building information; Python is used in the role, while proficiency is listed as an asset.
How would familiarity with BACnet, Modbus or LonWorks help you investigate building-management-system data?
What to coverSuggested preparation: Explain at a practical level how protocol familiarity can help you identify available points and investigate discrepancies between a displayed value and its intended meaning. These protocols are listed as nice-to-have familiarity, so avoid implying expertise in any one is mandatory.
How would you test an algorithm before deploying it to a building?
What to coverSuggested preparation: Outline checks for the mapped inputs, expected control behavior and unexpected results, then explain what evidence you would share with stakeholders. Treat energy-efficiency outcomes and safe operation as evaluation considerations, not as a claim that the posting specifies a particular test method.
How would you assess a request to update a building configuration or control setting?
What to coverSuggested preparation: Explain how you would establish the requested change, check its relationship to the documented HVAC design and existing controls, and verify the result. Discuss the trade-off between resolving the request promptly and avoiding unintended effects.
What would you check when a building's point data does not behave as expected during onboarding?
What to coverSuggested preparation: Work through possible issues with hierarchy, names, tags, configuration or the underlying control system, separating evidence from assumptions. Explain how you would record findings and coordinate with the relevant team to resolve the discrepancy.
What information would you include in a post-deployment technical handoff?
What to coverSuggested preparation: Cover the building mapping, documented HVAC design, deployed algorithm or control changes, test results and unresolved issues where applicable. Explain how clear process documentation supports the posting's standardized procedures and post-deployment support.
Behavioural practice
Tell me about a time you coordinated a technical handoff across teams.
What to coverSuggested preparation: Use a real situation involving shared responsibilities, explain the actions you took to establish ownership and communicate dependencies, and state the result. Connect the example to the role's cross-functional building onboarding or deployment handoffs without claiming the situations were identical.
Describe a time you resolved ambiguous or inconsistent technical information.
What to coverSuggested preparation: Give the situation, how you investigated and documented the ambiguity, and the resulting decision or correction. A building-data example is especially relevant to the posting's point-name, tag and mapping work, if you have one.
Tell me about a time you reported technical test results to different stakeholders.
What to coverSuggested preparation: Describe the test context, how you distinguished findings from uncertainties, and how you adapted your explanation to the audience. State what decision or next step followed rather than inventing a quantified impact.
Describe a time you kept a deployment or technical project moving despite a dependency.
What to coverSuggested preparation: Set out the deadline or dependency, the actions you took with other teams, and the outcome. Explain any trade-off between timeliness and completing necessary checks, since the role calls for timely deployment.
Tell me about a time you improved documentation or supported a team after handoff.
What to coverSuggested preparation: Use a real example to explain the initial gap, what you documented or clarified, and how the receiving team used it. Relate the result to the role's process documentation and post-deployment handoff duties without implying a particular employer process.