Solutions Engineer / Field Engineer

About the Role

We’re deploying a measurement platform into real facilities—places where airflow has opinions, sensors get mounted “where it fit,” and the system gets blamed for physics. The Solutions / Field Engineer is the person who makes pilots succeed: installs done correctly, commissioning that produces trustworthy baselines, and troubleshooting that turns “it’s wrong” into a crisp explanation of what assumption broke and what to do next.

This role is the bridge between product promises and field reality. You translate bench-grade expectations into operator language, and you bring field failures back to engineering as actionable requirements.

What You’ll Do

• Run pilots end-to-end: plan and execute deployments, define success criteria with customers, manage timelines, and drive pilot readouts that lead to expansion.
• Installs & commissioning: oversee sensor placement, device setup, connectivity, calibration checks, and acceptance tests; ensure go-live happens with a clean receipt.
• Troubleshooting in the real world: diagnose issues across sensors, firmware, networking, and algorithms—drift, coherence collapse, interference, bad mounting, condensation risk, power quality, etc.
• “Bench mismatch” explanations for operators: translate failures into plain language: what the system assumed, what the site did instead, how we detected it, and what to change.
• Customer training: teach operators how to interpret alarms, validity/confidence indicators, and drilldowns; build trust without overselling.
• Field feedback loop: capture recurring failure patterns and propose product improvements (install guides, UI changes, diagnostics, acceptance tests).
• Partner & integration support: coordinate with facilities/BMS vendors, network/security teams, and site constraints so enterprise requirements don’t stall deployments.

Concrete Deliverables

• A pilot deployment plan template: site survey → install → baseline capture → acceptance tests → go-live → weekly readouts.
• A commissioning checklist: placement validation, calibration proof, telemetry health, contract validity gates, sign-off criteria.
• A troubleshooting playbook: symptom → likely causes → confirming checks → fix → prevention.
• Operator-facing explanation cards for top failure modes (“why the system abstained,” “why alarms spiked,” “why sensors disagree”).
• A field runbook / knowledge base that scales installs beyond a single hero.

Required Qualifications

• Hands-on experience deploying and supporting technical systems in the field (industrial, facilities, IoT, networking, instrumentation, or similar).
• Strong troubleshooting instincts across hardware/software boundaries: sensors, data acquisition, connectivity, and “what the signal is doing.”
• Ability to communicate clearly with non-technical operators and technical stakeholders (facilities, IT/security, engineering).
• Comfort traveling and operating independently on-site.

Preferred Qualifications

• Experience with data center or facilities environments (HVAC, humidity control, commissioning, BMS, containment).
• Familiarity with basic DSP/measurement concepts (noise floor, drift, coherence, sampling issues) to interpret diagnostics.
• Experience with enterprise deployment realities: network segmentation, security questionnaires, change control windows.
• Experience writing customer-facing documentation and internal runbooks.

How You’ll Be Measured (First 60–90 Days)

• You successfully execute at least one pilot install with clean commissioning and clear acceptance tests.
• Time-to-resolution for field issues drops because troubleshooting is structured and repeatable.
• Operators trust the system more because “bench mismatch” gets explained quickly and credibly.
• Engineering gets higher-quality bug reports and feature requests (repro steps, artifacts, receipts), accelerating fixes.

Working Style

• You’re calm in messy environments and good at separating “system bug” from “site reality.”
• You default to evidence: receipts, telemetry, and acceptance tests—not vibes.
• You’re comfortable saying: “Here’s what the system can promise, here’s what it cannot, and here’s how we know.”

Title & Level

Solutions Engineer / Field Engineer (mid-to-senior; can scale to Lead if owning deployment playbooks and partner motions), partnering with product, systems, and engineering.