Job Description

Engine is the travel and spend management platform used by thousands of businesses to manage travel, expenses, and card programs. and as customers put it to work, they need it to plug into the systems they already run: their HRIS, ERP, CRM, accounting stack, and data warehouse. Right now, that integration layer lands on Product and Engineering. It shouldn't.

As Solutions Engineer, you'll own the technical implementation layer between go-to-market and the product. You're the person who knows whether a Dayforce sync is misconfigured or unsupported, can walk a customer through a Reporting API setup without pulling in an engineer, and can tell an AM exactly how to position Engine's Open API before a deal closes. You'll cut the avg 5-7 escalations per week, build the playbooks that prevent the next wave, and make sure high-value deals never stall because someone didn't know how a connector worked.

Note: this role requires that you work 3 days/week from our Chicago office at 500 W Madison St, Chicago, IL 60661

Your Mission:

Own the integration request queue

• Be the first technical responder on all inbound integration requests - HRIS (UKG, Dayforce, BambooHR), ERP/accounting (Sage, Business Central, Dynamics 365, Xero, Acumatica, Workday), Reporting API, Open API, and iPaaS (Workato, Zapier).
• Run setup and debugging calls that currently pull in Product or Engineering; resolve or escalate with a clear written summary, not a new meeting request.
• Own the intake process: define a triage template (system, use case, deal value, destination, schedule) and a routing framework by complexity tier.
• Track request volume by system type and feed the data directly into roadmap prioritization.

Build the implementation knowledge base

• Create and maintain a connector compatibility matrix - what's supported, what's in flight, what's a workaround, and what's a hard no.
• Write per-connector one-pagers for the five most-requested systems, covering setup steps, common failure modes, and known limitations.
• Record setup and debugging calls; turn the most common ones into reusable Looms and setup guides that AMs and customers can use without scheduling a call.
• Maintain a sandbox/demo environment AMs can use to walk customers through integration capabilities before they commit.

Enable the field team

• Train IMs/AMs to qualify integration feasibility and run first-level setup for the most common connectors, so they're not skipping straight to Product on every "can we connect to X?" question.
• Build quick-reference collateral for common ERP, HRIS, and API objections: what's supported today, what's coming, and how to handle a connector gap without losing the deal.
• Partner with Product Marketing on technical readiness for integration-related product launches.

Protect engineering time

• Set and hold a clear escalation bar: define what requires Engineering vs. what you can resolve independently.
• Surface repeat escalation patterns to Product as structured feedback — with volume, deal value, and customer impact attached.
• Reduce integration-related Product and Engineering call time week-over-week; own the metric.

How Success Is Measured

• Deflection rate: % of integration requests resolved without Engineering escalation
• Time-to-resolution and time-to-first-successful-sync
• Product/Engineering integration call time, week-over-week
• Repeat question volume (tracked through the intake queue)
• Request volume by connector type (fed into roadmap)
• Revenue at risk resolved: deal value unblocked by your involvement
• HRIS sync reliability: failed-sync rate across active integrations

Cross-Functional Partners

• Product
• Engineering
• Sales (New Business)
• Expansion (Account Management)
• Implementation
• Revenue Enablement
• Product Marketing

What You’ll Bring to Engine:

• 3-5+ years in a Solutions Engineering, Technical Account Management, or Implementation Engineering role at a B2B SaaS company.
• Hands-on experience with HRIS integrations (UKG, Workday, BambooHR, Dayforce, or similar) and/or ERP/accounting connectors (NetSuite, Dynamics, Xero, Acumatica, or similar).
• Comfort working directly with REST APIs — you can read documentation, write a test call, and diagnose a sync failure without an engineer in the room.
• Strong written communication: you can turn a debugging session into a reusable guide, and a customer escalation into a structured product brief.
• Experience working across Sales and Account Management teams — you know how to translate "can we connect to X?" into a scoped, honest answer the field can use.
• Comfort using AI tools to document, diagnose, and scale enablement content without sacrificing accuracy or depth.

Bonus points

• Experience with iPaaS platforms (Workato, Zapier, Boomi, or similar)
• Background in travel technology, fintech, or SMB-focused SaaS
• Experience building or maintaining a sandbox/demo environment
• Familiarity with data warehouse integrations (Snowflake, BigQuery, S3)
• Prior experience writing connector documentation or API one-pagers for a go-to-market audience

Applications for this role will be accepted through November 5, 2026 or until the role is filled. We encourage you to apply early, as we may begin reviewing applications before the deadline.