Airwave
See how your profile stacks up against this role.
We compared the job requirements to your profile to show where you're strong and where you fall short.
We sell AI smart glasses to industrial field-service companies. The people who fix HVAC systems, service elevators, maintain refrigeration, keep heavy equipment running. The people everyone comes running to when something breaks. And everyone is pulling at them - the customer needs the machine back up, the dispatcher wants an update and the office wants the report.
No two customer stacks are the same. You're the person who walks into that, understands how data flows through their business systems, and decides where Airwave fits so operations doesnβt halt. You're the systems expert in the room when we're in front of a customer.
You read a customer's stack for what it is, not what it should be. You find where the field data has to land so it's trustworthy and usable, and you recommend the configuration that gets it there with the least work on the customer's side. Sometimes that's a clean integration into an existing system of record. Sometimes the system of record barely exists, and you're recommending solutions. Frictionless is the standard. If the design leans on the customer to do a pile of work, it's the wrong design.
This is the seat that decides whether Airwave is a point tool or the front door to a customer's modernized stack. Asset data, work history, field readings that used to live on paper or in a bad batch upload now get captured at the source through the glasses. You're the one who makes that land in a way the rest of their business can access.
You implement the integrations, load the documentation, build the reports, and validate the data integrity. This is not an advisory role. The people whoβll thrive in this role designs, opens the laptop and implements.
A clean schema isn't the job. The tech using what you built is the job. You care whether the report and the data flow actually fit how the work happens in the field, not just whether they're technically correct, because a clean integration nobody uses is a failed one. You read a customer's systems for where the data breaks and where the workflow will fight you, and you build around both.
You propose the design, the reports, and the data-flow. The CSM and the field expert confirm it fits how techs actually work before it's final. You own the build, the field keeps a veto. That's what keeps a technically elegant integration from being the kind nobody uses.
$80-100K
After you apply, unlock the direct contact details of the people who actually make the call. A quick follow-up makes you 5x more likely to land an interview.
Marcus Rivera
Chief Revenue Officer

Hitachi

CrowdStrike

Rubrik, Inc.

Samsara

ZOLL Cardiac Management Solutions

Airwave