Senior Integrations & Platform Engineer

Attorneyassistant β€” Philippines Β· Posted ~3 hours ago

Senior Full-time

Skills

API development Event-driven architecture CRM integrations Webhooks Authentication API security Retries Idempotency API versioning Technical discovery APIs CRM Event-driven services

πŸ”“ Log in to save this job, tailor your resume & track your apply process β€” 7 days free, no card needed.

Log in to add to target list

Summary ✨ AI‑Generated

A senior engineering role focused on building a reliable integration platform that connects a core application with customer systems and external lead sources. You will design secure, documented APIs and event delivery services, establish standards for authentication, signing, retries, idempotency, replay and versioning, and turn recurring integration needs into scalable reusable capabilities. The position involves significant technical discovery and end-to-end ownership.

Highlights

Lead the design of a modern integration platform with ownership of production APIs, event-driven services, CRM connectors, and reusable integration capabilities. The role offers substantial technical ownership and the opportunity to establish API standards, reliability practices, documentation, and self-service tooling.

Description

About the Role We are building an AI-enabled intake and conversion platform for law firms. Our human and AI agents engage prospective clients, complete intake workflows, and help firms convert qualified prospects into signed clients. That only works if information moves reliably between our platform, our clients' systems, and the partners that supply leads. You will design and build that integration platform β€” production APIs, event-driven services, and CRM connectors β€” leading technical discovery yourself and turning recurring requirements into reusable capabilities rather than one-off scripts. What You Will Build Client APIs and Event Delivery Build secure, documented APIs and a reliable webhook platform that deliver intake, lead, and conversion outcomes to client systems.Own delivery mechanics and API standards: subscriptions, authentication, webhook signing, retries, idempotency, replay, versioning, and the documentation and testing tools customers need to self-serve.Inbound Lead and Partner Integrations Build services that securely accept leads and potential cases from external vendors on behalf of hundreds of law-firm clients, built on a canonical intake model and an adapter framework that normalizes new partners without duplicating core logic.Handle validation, deduplication, attribution, consent and source tracking, and tenant routing, and build monitoring and reconciliation tools that make missing or misrouted leads visible and recoverable.CRM Connectors and Custom Client Work Turn recurring client requirements into reusable, configurable connectors β€” installable packages, managed integrations, and embedded workflows β€” with secure OAuth or API-key onboarding.Design configurable field mapping, routing rules, and synchronization behavior so a new firm can be connected without an engineer, and own connector deployment, versioning, and support.Lead technical discovery with law firms, CRM administrators, and vendors; deliver custom integrations as paid engagements when a connector is not appropriate; and fold reusable components back into the platform.Platform, Reliability, and Security Design multi-tenant, event-driven services with strong isolation of customer data and credentials, and own them from design through deployment, monitoring, and incident response.Design for third-party rate limits, outages, schema changes, and duplicate events, backed by structured observability, automated contract and integration testing, and replay tools.Protect sensitive lead, caller, and case data through least-privilege access, secure secret storage, credential rotation, tenant-aware authorization, and configurable retention. First 90 Days Days 1–30: Understand and Design Map the current client-delivery and inbound-lead workflows, define the canonical data models, and recommend the integration architecture, security model, and API standards as a prioritized plan. Days 31–60: Ship the Foundation Ship the first production client API and webhook capabilities with signing, retries, idempotency, replay, and alerting; automate the existing inbound lead source; and validate with early clients. Days 61–90: Productize and Scale Harden the services for production volume and third-party failures, launch the first productized CRM connector, and present the roadmap for additional connectors and self-service capabilities. Required Experience Typically 5 or more years of software engineering experience, including ownership of backend, platform, or integration systems.Hands-on experience designing and operating customer-facing APIs, webhooks, or integration platforms in production.Strong proficiency in a modern backend language (TypeScript/Node.js, Python, Java, Go, or C#) plus strong SQL and relational data modeling.Deep understanding of event-driven systems, distributed-system failure modes, and API authentication patterns including OAuth 2.0, API keys, JWTs, and signed requests.Experience designing reliable integration behavior β€” retries, idempotency, rate limiting, replay, reconciliation, and schema evolution β€” backed by automated contract and integration testing.Experience with multi-tenant SaaS and operating services in AWS, Azure, or GCP using containers, CI/CD, and infrastructure as code.Experience working directly with customers and partners on discovery and launch, translating messy business processes into maintainable software, and a self-directed approach to ambiguous problems. Preferred Experience Integrations with CRM, case-management, or lead-management platforms such as Salesforce, Litify, HubSpot, Filevine, Clio, or Lawmatics.Salesforce work involving Apex, REST APIs, Platform Events, Flow, or managed packages, or publishing installable apps, marketplace connectors, or SDKs.Legal technology, law-firm operations, legal intake, or professional-services delivery, including billable client engagements.SFTP, batch imports, change-data capture, or streaming platforms, and familiarity with MCP or secure data interfaces for AI agents.Depth in one or two platforms, plus the ability to learn unfamiliar APIs and data models quickly, matters more than familiarity with all of them. What Success Looks Like Clients and partners exchange standardized outcomes and leads through reliable, documented interfaces instead of manual work.Integration failures are visible, diagnosable, and recoverable.New vendors and CRM systems are added through reusable adapters and configuration, so onboarding each new client, CRM, or lead source takes less time.