Senior Integration Engineer

Job Description

Senior Integrations Engineer

\n

\n

Engineering | Denver, CO (preferred) or US Remote | Full-time

\n

Reports to: Piers Symons, COO & Co-Founder

\n

\n

About Earlytrade

\n

\n

Earlytrade is a B2B fintech company built for the construction industry. We help general contractors and subcontractors improve cash flow through a platform that gives subcontractors more control over when they get paid and on what terms. The result is a fairer, more transparent way to manage working capital across the construction supply chain.

\n

\n

Earlytrade sits in the middle of messy, fragmented ERP, project-management, and payment ecosystems. This role is for someone who wants to turn that complexity into an advantage: building reliable integration infrastructure, handling ugly edge cases, and making connectivity and embedded workflow support part of how Earlytrade wins.

\n

\n

The Role

\n

\n

We’re hiring a Senior Integrations Engineer to design, build, and own the technical integration layer that connects Earlytrade to the broader construction and financial software ecosystem. This is a backend-heavy engineering role focused on reliability, partner complexity, and operational correctness: you’ll work across APIs, webhooks, file and batch workflows, and embedded integration patterns to make Earlytrade easier to adopt and harder to displace.

\n

\n

You’re not primarily building isolated product features, you’re building the connective tissue between Earlytrade and a complex, fragmented partner landscape. You’ll own both greenfield integration builds and the extension of existing infrastructure, and you’ll work directly with Piers Symons (COO & Co-Founder), our Integrations Product Manager, and our partner and revenue teams to translate business requirements into reliable, scalable technical connections.

\n

\n

Some integration infrastructure is already in place. You’ll inherit a Java, Spring Boot, and Apache Camel-based platform, evaluate it honestly, and improve it, while also building net-new integrations from scratch as Earlytrade’s partner ecosystem grows. You’ll also work directly with external partner technical teams as the day-to-day engineering counterpart during discovery, build, testing, and go-live.

\n

\n

What You’ll Build

\n

\n

\n
• Reliable integration services that connect Earlytrade to ERP, project-management, AP, and payment platforms across APIs, webhooks, and file or batch workflows
\n
• Data transformation and reconciliation layers that translate messy external partner formats into dependable internal workflows and vice versa
\n
• Embedded integration touchpoints that let Earlytrade appear inside partner systems where that creates a better customer workflow and a stronger product moat
\n
• Authentication and authorization flows for third-party API connections, including OAuth2, API key management, and token lifecycle handling
\n
• Data transformation and mapping layers that translate partner data schemas into Earlytrade’s internal data model, and vice versa, across JSON, XML, CSV, spreadsheet, and partner-specific formats
\n
• Embedded integration touchpoints that allow customers to initiate or manage Earlytrade workflows from within their ERP, project-management, or AP tooling where the partner surface supports it
\n
• Error handling, retry logic, reconciliation flows, dead-letter patterns, and alerting infrastructure to ensure integration failures are caught, logged, and recoverable
\n
• Internal developer tooling and documentation that makes it easier to onboard new integrations and maintain existing ones
\n
• Partner-facing technical documentation and implementation support that help external teams integrate with Earlytrade effectively
\n

\n

\n

Responsibilities

\n

\n

\n
• Own the full lifecycle of integrations: discovery, design, build, testing, deployment, monitoring, and ongoing maintenance
\n
• Evaluate existing integration infrastructure and lead improvements to reliability, observability, scalability, and maintainability
\n
• Design integration architectures that are robust by default, with idempotency, graceful degradation, and auditability built in from the start
\n
• Work with product, revenue, and partner teams to scope new integration requirements and translate them into accurate technical specifications
\n
• Build and maintain Apache Camel routes and integration services across REST APIs, webhooks, and file or batch-based partner workflows with varying levels of technical maturity
\n
• Implement and manage async and scheduled processing patterns for high-volume, latency-sensitive, or operationally constrained partner data flows
\n
• Design embedded integration touchpoints where Earlytrade functionality or status needs to appear inside partner systems, while keeping the source-of-truth workflow architecture clean
\n
• Write thorough integration tests, contract tests, and end-to-end validation suites covering both happy paths and failure modes
\n
• Define and enforce data integrity standards for all data crossing integration boundaries, particularly financial and transactional records
\n
• Maintain clear, accurate technical documentation for every integration: data flows, field mappings, delivery modes, error codes, and escalation paths
\n
• Act as the internal technical authority on third-party platform capabilities, integration limitations, and best practices across API, webhook, and file-based delivery models
\n
• Act as the day-to-day technical counterpart for partner engineering and solutions teams during discovery, implementation, testing, and go-live
\n
• Contribute to architecture decisions that affect how integrations interact with Earlytrade’s core backend services
\n

\n

\n

Required Qualifications

\n

\n

\n
• Direct experience integrating with ERP platforms commonly used in construction or mid-market enterprise environments (e.g. accounting, project management, or cost management systems)
\n
• 5+ years of professional software engineering experience, with at least 3 years focused on integrations, platform engineering, or systems connectivity
\n
• Deep, production-tested experience building and maintaining integrations with third-party platforms across REST APIs, webhooks, and file or batch-based delivery patterns; familiarity with other partner styles such as SOAP is a plus
\n
• Strong backend engineering skills in Java and Spring Boot; experience with Apache Camel or a comparable integration framework is strongly preferred
\n
• Hands-on experience with OAuth2, API key management, and token-based authentication flows for third-party API connections
\n
• Proven ability to design reliable async and batch-oriented data pipelines: retry logic, idempotency, reconciliation, scheduling, and failure recovery
\n
• Experience with PostgreSQL: data modeling, query writing, and maintaining transactional integrity across integration boundaries
\n
• Strong understanding of data transformation patterns: field mapping, schema normalization, format conversion (JSON, XML, CSV, spreadsheets, EDI, or similar)
\n
• Track record of building integrations that handle financial or transactional data where correctness and auditability are non-negotiable
\n
• Experience writing integration tests, contract tests, and monitoring/alerting setups that catch failures before customers do
\n
• Excellent technical communication skills: you can write clear specs, field mapping docs, and implementation guidance for internal and external teams
\n
• Experience working directly with external partner technical teams through discovery, implementation, testing, and production rollout
\n
• Comfortable working across engineering, product, revenue, and external partner teams simultaneously
\n

\n

\n

Preferred Qualifications

\n

\n

\n
• Familiarity with construction project management, cost management, or document management platform APIs
\n
• Experience with AP automation, payment processing, or accounts payable workflow platforms
\n
• Knowledge of EDI standards (X12, EDIFACT) or construction-specific data formats used in invoice and contract exchange
\n
• Experience building embedded integration experiences inside ERP, project-management, or AP tooling, such as surfacing status or enabling action-taking from within third-party systems
\n
• Experience building or consuming GraphQL APIs where they support partner or product-facing integration use cases
\n
• Familiarity with iPaaS platforms (MuleSoft, Boomi, Workato, or equivalent), even if your preference is native code
\n
• Exposure to event streaming platforms (Kafka, AWS EventBridge, or equivalent) for high-throughput partner data ingestion
\n
• Experience with cloud infrastructure (AWS or GCP) including managed queues, secrets management, and integration monitoring tools
\n
• Prior experience in a fintech, payments, or B2B SaaS company where integration reliability directly affected revenue
\n

\n

\n

Technical Context Today

\n

\n

\n
• Primary Stack: Java 17 + Spring Boot + Apache Camel
\n
• Persistence: PostgreSQL, shared domain concepts, and migration-aware schema evolution
\n
• Integration Styles: REST APIs, webhooks, file and batch exchange patterns including CSV, XML, Excel, and partner-specific workflows
\n
• Embedded Opportunities: Integration patterns that let customers trigger or view Earlytrade workflows from within ERP, project-management, or AP platforms
\n
• Authentication: OAuth2 / API key / token-based auth
\n
• Platform Context: AWS-hosted services, secrets management, monitoring, retries, and scheduled or sync-driven workflows
\n
• Adjacent Product Surfaces: Some coordination with Earlytrade’s Node.js + TypeScript GraphQL service and React + TypeScript frontend where integrations surface into customer experiences
\n
• CI/CD: Bitbucket Pipelines or equivalent
\n

\n

\n

What We Offer

\n

\n

\n
• Competitive compensation dependent on experience
\n
• Meaningful equity in a fast-growing fintech with a clear path to scale
\n
• Direct access to founders and leadership, you’ll shape the integration strategy, not just execute it
\n
• A technically complex, high-stakes domain: construction and fintech have some of the messiest, most fragmented API ecosystems in enterprise software, and that’s what makes it interesting
\n
• A collaborative, low-ego team that takes the craft seriously
\n

\n

\n

\n