Staff Analytics Engineer - Energy & Building Systems

About this role

About R-Zero

R-Zero offers smart building technology that delivers real-time occupancy and energy insights, which ultimately helps buildings reduce energy costs, improve net operating income and increase asset value. R-Zero’s occupancy based demand control ventilation solutions include IAQ and comfort monitoring, high-efficiency HVAC filtration, space utilization sensors, occupancy-based building controls, and real estate performance analytics. R-Zero’s intuitive, secure and scalable platform enables owners, operators, and their tenants to cut building operating expenses and carbon emissions, with zero upfront costs. Learn more at www.rzero.com.

About the role

R-Zero is hiring a Staff Analytics Engineer to be the engineering judgment behind our building analytics: the findings we surface, the rules that generate them, the savings we claim, and the decision to move from insight to control. R-Zero's Physical AI platform combines occupancy sensing with BMS data to cut HVAC energy in commercial buildings, and every finding we put in front of a customer has to hold up to an engineer's scrutiny.

You will decide whether a finding is real, whether a savings number is defensible, and whether a control action is safe to turn on. You'll also make that review process scale as our rule library and fleet grow.

This is a startup role. Much of what you'll work on has no established playbook yet. You'll help define the M&V methods, review practices, and rule standards the Solutions team runs on.

The ideal candidate is a mechanical, controls, or energy engineer who lives in trend data. You can open a building's point list and drawings, pull a week of trends, and tell us within a day whether a finding is right, how confident you are, and what you'd need to be sure. You know the BACnet priority array well enough to know what happens when our write meets an operator override.

What you'll do

• Make every finding defensible: Decide whether each finding is real, and own the quality of the rules that produce it.

• Grow the rule library where it matters: Turn open-ended charters, such as central plant coverage, into validated rules, prioritized by impact.

• Discovery: Find savings beyond the rule library: investigate each building like an energy auditor, vet leads against data quality and real-world constraints (e.g., lease terms), and turn validated findings into portfolio rules.

• Qualify and scope new buildings: decide fit, and which equipment and points to trend, ranked by savings value.

• Stand behind our savings: Build M&V methods that hold up for each building and measure, including where standard IPMVP options don't fit.

• Gate and implement control: Decide when insight is ready to become control, then implement it safely through the BACnet priority array.

• Be the engineering voice with customers: Lead findings reviews with customer engineering and facilities teams, and feed what you learn back to Product and Engineering.

Required qualifications

These are skills we expect you to bring on day one.

• Evidence grading and system characterization: You judge how far to trust each building fact by its source. The range runs from a reasoned assumption to a public dataset, a document, a single trend, several trends together, or on-site or customer confirmation. You can say what evidence would raise that rating. You extract system configuration from drawings, submittals, nameplate photos, and test-and-balance reports, resolve conflicts between them, and state plainly whether the result is good enough to act on.

• Finding validation: You can review a finding against trend and building data and make a defensible call. That includes telling a failed sensor or offline controller from a real equipment fault, confirming what a BACnet point is from how it behaves, and proving from trends which unit serves which zone.

• Hands-on data analysis: You pull and analyze time-series data directly through AI agents (such as Claude), analytics platforms, or code. You’re skeptical enough to catch when a query, result, or agent is wrong.

• Priority-array control: You can implement control through the BACnet priority array, including write priority, relinquish defaults, and operator override collisions, not only through BMS programming.

• Sequences of operations: You can write a sequence of operations or control strategy grounded in ASHRAE Guideline 36.

• Airside depth: You have working depth in AHUs, VAV, and terminal units, plus working knowledge of central plant and hydronic systems.

• M&V fundamentals: You apply IPMVP in real buildings and can map BACnet points to the variables an M&V calculation needs.

• Customer technical leadership: You have led technical reviews with customer engineering or facilities staff.

• Experience and education: 8+ years of hands-on experience in HVAC design, controls or BMS engineering, energy engineering, commissioning, or building analytics. A bachelor’s degree in Mechanical Engineering, Building Science, Controls Engineering, Energy Engineering, or a related field, or equivalent demonstrated practice.

Preferred qualifications

We weigh these heavily, but they won’t rule you out.

• Central plant depth: You go beyond working knowledge of chillers, boilers, towers, and hydronic distribution, enough to own plant rules and plant savings.

• Standards in the field: You have applied ASHRAE 62.1 and 90.1 in real buildings, not just cited them.

What you'll own within 30–90 days

After onboarding on R-Zero's platform, rules, and tooling, we expect you to own the following.

• Grading playbook: Write down the judgment calls and methods behind your grades, and update the playbook whenever our software grades something wrong.

• Rule review and improvement: Review rules and improvement proposals, judge them, and improve the rules.

• Actionable defect reports: Write up defects in current rules or features so engineering can act on them: reproducible, point-referenced, with root…