R-Zero - Staff Analytics Engineer - Energy & Building Systems

• 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. • Evidence grading and system characterization: • 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. • Finding validation: • 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. • Hands-on data analysis: • 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. • Priority-array control: • Sequences of operations: You can write a sequence of operations or control strategy grounded in ASHRAE Guideline 36. • Sequences of operations: • Airside depth: You have working depth in AHUs, VAV, and terminal units, plus working knowledge of central plant and hydronic systems. • Airside depth: • M&V fundamentals: You apply IPMVP in real buildings and can map BACnet points to the variables an M&V calculation needs. • M&V fundamentals: • Customer technical leadership: You have led technical reviews with customer engineering or facilities staff. • Customer technical leadership: • 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. • 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. • Central plant depth: • Standards in the field: You have applied ASHRAE 62.1 and 90.1 in real buildings, not just cited them. • Standards in the field: • 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. • Grading playbook: • Rule review and improvement: Review rules and improvement proposals, judge them, and improve the rules. • Rule review and improvement: • Actionable defect reports: Write up defects in current rules or features so engineering can act on them: reproducible, point-referenced, with root cause separated from symptoms. • Actionable defect reports: • Multi-method savings estimates: Quantify savings several ways, including a rule of thumb when data blocks the preferred method, reviewed and signed off with our principal engineer. • Multi-method savings estimates: • New M&V methodologies: Define new M&V methodologies when existing approaches don’t fit. • New M&V methodologies: • Control readiness calls: Judge when findings are on solid enough ground that control is plausible and prudent. • Control readiness calls: • Ambiguous charters: Take an open instruction such as “add central plant rules,” pick what has the most impact, build it, and validate it. • Ambiguous charters: • Scalable review: Make review scale through rule-level review, sampling, clustering, and AI-assisted grading, so review time grows with rules rather than findings. Spot-check the software grader against your own grades and track where you disagree. • Scalable review: • Findings reviews: Lead R-Zero findings reviews and engineering deep-dives with prospects and customers. • Findings reviews: • Nice-to-haves • Nice-to-haves • Background at an MEP or energy consultancy, a commissioning or retro-commissioning firm, a fault detection and diagnostics (FDD) or building analytics company, or an early-stage startup. • Hands-on experience with BACnet integrations and Niagara/Tridium supervisors. • Experience building or tuning FDD rules at fleet scale. • Familiarity with Python, SQL, or similar tools for time-series analysis. • Exposure to DCV, IAQ, or smart building product categories, and familiarity with Title 24. • Industry credentials such as PE, CEM, CMVP, CCP, or CEA. • Travel • Travel • Up to 15% travel for customer technical reviews, site validation, and occasional deployment support. Travel may include overnight trips or physical site tasks such as walkdowns and mechanical room access. • Rarely • (0 – 12%) • Occasionally • (13 – 33%) • Frequently • (34 – 64%) • Regularly • (65 – 100%) • Seeing: Must be able to read reports & computer monitors. • Seeing: • Hearing: Must be able to hear well enough to communicate with others. • Hearing: • Sitting: Must be able to sit for prolonged periods of time. • Sitting: • Standing: Must be able to stand for prolonged periods of time. • Standing • Reaching/Climbing/Stooping/Kneeling: • Grasping/Feeling: Must be able to write & use a keyboard, tablet or phone system. • Grasping/Feeling: • Lifting/Pulling/Pushing: Must be able to lift, push and pull at least 75 lbs. • Lifting/Pulling/Pushing: • Rarely • (0 – 12%) • Occasionally • (13 – 33%) • Frequently • (34 – 64%) • Regularly • (65 – 100%)