Senior Integrations Engineer

Eve

About The Position

Youâll own the end-to-end integration experience for Eveâs customers, from contract signed to integration live and usable. Eve integrates with multiple major case management platforms, each with its own API patterns, authentication models, deployment quirks, and edge cases. Some are cloud-native with clean REST APIs. Others are self-hosted on-prem systems behind firewalls that require weeks of configuration. Your job is to figure out the right integration path for each customer and drive it to completion. This is not a project management role, but itâs not a pure engineering role either. Youâll split your time between hands-on technical work (configuration, validation, debugging, scripting) and customer-facing delivery (implementation planning, expectation setting, vendor coordination, internal handoffs). You need to be comfortable on a customer call walking through auth setup and equally comfortable tracing an OAuth token refresh failure through three layers of a distributed system. You sit on the Customer Success team and partner daily with Engineering. Youâre the bridge: you own the customer-facing integration experience, determine what the integration path should look like, and feed requirements back to Engineering for productization. You define what needs to be built; Engineering builds it at scale.

Requirements

3-5+ years building, configuring, and debugging production API integrations (REST APIs, pagination, rate limiting, retry logic)
Experience owning implementation delivery end-to-end, not just building integrations but driving them to completion with customers
Proficiency in Python or Node.js (Python preferred) for scripting, data transformation, and API orchestration
Hands-on experience with OAuth 2.0, JWT, token refresh cycles, and permission/scoping troubleshooting
Comfortable working with webhooks and debugging common failure modes (expiry, missed events, configuration drift)
Experience mapping data across systems that represent the same concepts differently
Strong communication skills for customer calls, vendor negotiations, and internal coordination
Interest in legal technology and how law firms operate

Nice To Haves

Direct experience with legal tech platforms (Clio, Filevine, SmartAdvocate, Litify)
iPaaS or integration platform experience (Workato, Celigo, Mulesoft, Tray.io)
A track record of creating implementation documentation, runbooks, or process guides that other teams use
SQL familiarity and ability to reason about how integration data flows into a data warehouse
On-prem and hybrid deployment experience with self-hosted systems, firewall rules, and VPNs
Multi-tenant integration management across hundreds of customer accounts
Experience building observability and alerting for integrations at scale

Responsibilities

Own integration delivery for customers from post-sale through go-live: scoping the integration path, validating configuration (auth setup, tenant and environment validation, allowlisting, callback/redirect setup, granular permissions, document store configuration), testing in sandbox and live environments, and driving to completion
Scope integration approaches for new CMS partners, prototype solutions, and deliver technical requirements to Engineering for productization
Manage strategic vendor relationships: pressuring vendors for API access, proving whether issues are on their side or ours, identifying unsupported or undocumented API behavior, and negotiating workarounds when standard paths donât exist
Debug and resolve production integration issues by tracing through logs, isolating the layer (our side, vendor side, or customer config), and resolving or routing to Engineering with a clear diagnosis
Build the assets required to scale integration delivery: implementation playbooks, vendor-specific setup guides, troubleshooting matrices, customer readiness checklists, known limitation documentation, escalation criteria, and handoff notes for the CS team
Identify patterns across customer integrations and feed productization requirements back to Engineering, without duplicating the platform Engineering owns