Customer Engineer

eSentire

About The Position

As a Customer Engineer, you own the integration work that drives Atlas deeper into each account's environment, turning technical depth into platform stickiness and a harder-to-leave relationship. You write the integration code, build the data pipelines, and tune the detection logic a specific customer's environment actually needs. This is a hands-on engineering seat where every build should either close an adoption gap or make that account's renewal and expansion case stronger, not just solve an interesting technical problem.

Requirements

5+ years as a hands-on, customer-facing engineer, with concrete work you can show — an integration, workflow, or capability you built inside a real customer's environment, not just scoped or demoed.
Comfortable writing production code wiring up APIs and data pipelines, and getting all of it running on infrastructure someone else owns.
Comfortable operating without a rulebook: this is a new seat with no fixed process yet, and you'll help define what right looks like as you go.
Sharp enough technically to sit across from a customer's senior engineers and hold your own on architecture and design decisions, not just talking points.

Nice To Haves

Your accounts hit measurably faster time-to-value on Atlas than accounts running the standard path.
Coverage and integration depth in your accounts holds up as those environments change — because you're embedded enough to catch drift before it becomes a gap.
At least one thing you built for a single account gets adopted as a platform capability that ships broadly.
Your accounts renew and expand, and can point to specific work you did as part of why.

Responsibilities

Get assigned specific, account-level technical requests: a new integration, a new connection, a log source we've never pulled in before and turn them around with urgency, whatever the size of the actual ask.
Scope exactly what's being asked and ship it on the customer's timeline, not on a standard release or sprint cycle.
Handle the full range of requests that come in: new ticketing-system integrations, first-time log sources, one-off connections, treating each as its own assignment tied to one specific account.
Confirm the request is fully working with the customer before calling it done, no half-finished handoffs to someone else.
Notice when the same kind of request keeps showing up across different accounts, and flag it so it stops being repeat work and becomes something built once, for everyone.
Keep the customer's actual ask front and center every time: what they need, delivered the way and speed they need it.