FieldFlo Tech Lead, Integrations Remote · Full time Company website

Apply for Tech Lead, Integrations

FieldFlō is a management platform purpose-built for specialty subcontractors in construction and field services. We help trade contractors streamline operations, strengthen safety, and gain real-time project visibility. We are rapidly scaling, and our customers are at the heart of what we do.

About the Role

FieldFlo is building the operating system for demolition, abatement, and remediation contractors, replacing paper timesheets, manual safety forms, and disconnected payroll with a single digital platform. Our integration layer syncs employees, projects, and payroll data between FieldFlo and the diverse ERP and accounting systems our clients use, while connecting our internal tools to automate onboarding.

We are looking for a Tech Lead, Integrations to own the technical direction and hands-on development of our integration platform. You will be the technical authority on how data flows in and out of FieldFlo — from ERP and payroll syncs to CSV imports to reconciliation logic. You’ll work alongside our current integration partner, providing architectural direction and technical oversight, while personally building new integrations, proofs of concept, and API endpoints. This is a deeply hands-on role: we need someone who writes code every day, not someone who directs from above.

You will also be client-facing — joining calls with contractors and their teams to troubleshoot sync issues, explain integration behavior, and build confidence in our platform.

What You’ll Do

Hands-On Integration Development

•      Build, maintain, and debug sync connectors alongside our current integration partner — stepping in directly when capacity is limited or urgent issues arise.

•      Develop new API endpoints and customizations as integration needs evolve, reducing dependency on any single team or partner.

•      Lead new integration proofs of concept independently, establishing patterns for the next generation of connectors.

Integration Architecture & Vision

•      Own the integration-layer architecture and long-term vision for FieldFlo’s integration platform, aligned with the broader platform architecture set by the Lead Architect.

•      Design and evolve the platform toward a scalable, productized framework that enables new connectors to be stood up in weeks, not months.

•      Evaluate integration strategies (build vs. partner vs. iPaaS) and make recommendations to the Lead Architect and engineering leadership.

Client-Facing ERP & Payroll Connectors

•      Own the sync pipelines between FieldFlo and clients’ ERP, payroll, and accounting systems — including QuickBooks Online, QuickBooks Desktop, Sage 100, Sage 300, Sage Intacct, Foundation, Vista Viewpoint, COINS, Acumatica, Procore, Trimble, Paycor, and Plexxis.

•      Provide architectural direction and technical oversight to our current integration partner, defining standards, reviewing implementations, and owning the technical quality of all connectors.

•      Design reconciliation logic that surfaces payroll/position mismatches automatically and guides clients through alignment.

API Advocacy & Documentation

•      Serve as the internal advocate for integration concerns in API design — ensuring that API changes across teams account for downstream integration impact.

•      Collaborate closely with product and engineering teams to influence API development with integration use cases in mind, as integrations are the largest consumer of the FieldFlo API.

•      Own and maintain API documentation for integration consumers — including endpoint specifications, versioning, response schemas, and usage guides — ensuring documentation stays current with every release.

Sync Health, Monitoring & Operations

•      Build the real-time sync health dashboard for CS — sync status, error counts, lag, and entity counts across all connector types.

•      Implement alerting (sync errors → immediate CS notification; delay > 24h → escalation) and surface sync state in the client-facing portal.

•      Develop runbooks per connector, own monitoring metrics, and lead the on-call rotation for sync issues.

Documentation & Knowledge Management

•      Maintain a structured integration registry documenting each client’s ERP system, ERP version, sync tool, sync tool version, and connector configuration.

•      Create and maintain runbooks, onboarding guides, and troubleshooting documentation for each connector type.

Technical Escalation & Client Communication

•      Serve as the primary technical escalation point for all integration issues — whether surfaced by the integration partner, CS, or internal teams.

•      Join client calls as needed to explain sync behavior, troubleshoot issues, and build confidence in the integration layer. Must communicate clearly and professionally with non-technical stakeholders.

•      Partner with Product, CS, and Engineering on integration specs; work directly with ERP vendor technical contacts.

•      Be available for critical sync issues that require rapid response — sync failures, CVEs, and production incidents that impact client operations may need resolution within minutes, not hours.

What Success Looks Like

•      New sync clients reach first payroll export in under 20 days, regardless of ERP system.

•      Integration partner relationship has clear architectural ownership and technical direction from FieldFlo’s side, with well-defined quality standards.

•      A clear technical roadmap exists for evolving the integration platform toward a productized, scalable architecture.

•      Sync dashboard shows 99%+ uptime with < 5 min lag; CS self-serves status without engineering.

•      New connectors can be stood up in weeks, not months, via a productized framework.

•      All integrations are fully documented — client registry, connector runbooks, and API documentation are current and reliable.

•      Critical sync issues are resolved within minutes during US business hours; clients trust the integration layer enough to retire their paper processes.

Required Qualifications

•      7+ years of software development with significant hands-on integration architecture experience.

•      Production integration experience with multiple ERP, payroll, or accounting systems (e.g., QuickBooks, Sage, Foundation, Viewpoint, COINS, Acumatica, or similar).

•      Experience designing sync architectures with state management, conflict resolution, and partial-failure recovery across cloud and on-prem environments.

•      Proven ability to provide architectural oversight and technical direction to external development teams or partners.

•      Strong hands-on coding ability — comfortable building new integrations, API endpoints, and proofs of concept daily, not just directing from above.

•      Excellent English communication (C1/C2) — must be comfortable in customer-facing conversations with non-technical stakeholders.

•      Available during US business hours (Central or Eastern time overlap required) with flexibility for urgent issues outside standard hours.

•      Comfortable operating as a domain expert within a broader architectural framework — strong opinions, loosely held, with the ability to align to platform-wide standards.

Preferred Qualifications

•      Direct experience with two or more of: QuickBooks Online/Desktop, Sage 100/300/Intacct, Foundation, Vista Viewpoint, COINS, Acumatica, Procore, or Trimble.

•      Experience with on-prem sync architectures (desktop sync agents, .NET connectors, RDP environments).

•      Experience evolving an integration platform from professional-services-based delivery toward a productized, scalable model.

•      Familiarity with the demolition, abatement, remediation, or broader construction trades vertical.

•      Experience with integration platforms (MuleSoft, Workato, Dell Boomi) or CRM integrations (HubSpot, Salesforce).

Core Competencies

•      Hands-on builder — writes code every day, builds proofs of concept, and experiments with new integration approaches

•      Integration platform thinking — ability to architect a scalable sync platform across a diverse ERP/payroll landscape

•      Technical oversight — providing clear architectural direction and quality standards to development partners

•      Client empathy — sync reliability directly impacts whether contractors trust digital over paper

•      Urgency and ownership — treats sync failures as production incidents that demand immediate attention

•      Strong troubleshooting across system boundaries and mixed on-prem/cloud environments

•      API advocacy — championing integration concerns in internal platform and API design decisions

•      Documentation discipline — keeps integration registry, runbooks, and API docs current and reliable