Senior Software Engineer, Integrations

The Role

Our product is only as good as the data flowing through it. We already have a working data platform — an orchestrated pipeline with a layered data model and several source ingestions live in production — owned by our Data team. But the world of property data is far bigger than what we pull today: permits, contractor and service networks, agent tools, accounting platforms, and dispatch software all live in disconnected systems that don't talk to us or each other. You'll be our first dedicated integrations hire, here to dramatically expand the breadth of sources we aggregate and make two-way data flow a first-class part of how we build.

This is a software engineer first, with an integrations mindset — someone genuinely comfortable getting data across every kind of source and making it flow both ways. You'd rather build a resilient, reusable connector than hand-massage another one-off export. You know how to reconcile messy, inconsistent data from public and private sources, and you think in terms of syncs, webhooks, idempotency, and reconciliation — not just "pull the file."

This is not a pure engineering role. Much of the data lives behind relationships, not APIs — so you'll be partner-facing, owning third-party relationships end to end: reaching out to towns, data providers, contractors, and platform partners, negotiating access, working through data-sharing terms, and being the person who keeps those connections alive as they change. You're as comfortable on a call with a county clerk or a partner's ops team as you are in the codebase.

It's a senior IC role building on real foundations. You're not starting from zero — there's a monorepo, an orchestration layer, and a medallion pipeline to build on and feed. But there's no dedicated integrations function yet: you'll set the connector patterns, the two-way sync conventions, the data contracts into the pipeline, and the partner relationships that the rest of engineering adopts. The standards you set early become how we integrate as the number of sources and systems scales.

What You'll Do

Expand what we aggregate. Establish our first real two-way integrations and stand up connectors for the many sources we don't yet pull — prioritizing the sources and syncs that matter, not connectors for their own sake.

Wire up everything around a property. Integrate data for everything tied to a property — permits, contractors, services, agents, and public and private records — normalizing inconsistent sources into a coherent, trustworthy model.

Connect the operational stack. Build two-way integrations with QuickBooks and other accounting systems, dispatching software, and the third-party platforms our users and partners already run on.
Make data flow both ways, reliably. Own sync as code: ingestion, outbound writes, webhooks, retries, idempotency, and reconciliation — so data stays consistent across systems and failures are caught, not silently dropped.

Design durable contracts. Define the data models, schemas, and API contracts that keep integrations stable as sources change, and version them like production code.

Focus on trust, not busywork. Decide what to integrate and why, then build the automation and monitoring that keep it healthy. Lean on AI-assisted tooling so the work stays about data quality and coverage strategy, not babysitting brittle scripts.

Work directly with the source. Partner with the people and organizations behind the data — town and municipal offices, contractors, service providers, agents, and platform partners — to get access, understand their systems, and keep integrations working as they change.

Set the standard. Make the build-vs-buy-vs-partner calls, and let the connectors and patterns you establish become the team's default.