Field Sales Engineer

Role Overview

• 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 design, open the laptop and implement.
• You decide where Airwave connects in each customer's stack and how the data flows, and you own that recommendation as the technical expert in front of the customer.
• At kickoff you take the customer's document repository and get it loaded into Airwave so the product is grounded in their equipment, their procedures, and their standards.
• Everything downstream depends on this being right.
• You build the reports each customer needs.

Requirements

• Deep fluency in how field service actually runs and how the systems behind it fit together, FSM, ERP, CMMS, compliance and safety systems, and the homegrown middleware that stitches them. You've seen enough real stacks to know they're never clean, and you can find the right insertion point in a messy one.
• A builder with an architect's judgment. You can make the call on where a product fits in a tangled stack, and you're the one who then builds it, not someone who hands it off.
• AI-forward, and here it's survival. Pattern-matching across very different stacks is what lets one person cover many accounts.
• Field instinct and scrappiness. You care whether the workflow works for the tech, and you're comfortable doing your own grunt work at a seed-stage company instead of waiting for scale and process.
• You get real data to production in messy environments, and you can stand in a customer's system and prove it works, not just assume it does.

Tech Stack

• ERP