Senior Software Engineer, Integrations

About the role

Ruxlo is a data-driven real estate platform — map-based web and mobile, AI-assisted search, freemium — built by a small, high-pace, AI-native team. 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.

Responsibilities

• Build resilient, reusable connectors for a wide range of data sources, including public records, permits, MLS feeds, county sites, contractor and agent tools, accounting platforms, and dispatch software.
• Reconcile messy, inconsistent data from disparate sources into a coherent, trustworthy model through matching, deduplication, normalization, and conflict resolution.
• Handle data extraction when no clean API exists, using web scraping, crawling, parsing of HTML/PDF/scanned documents, headless browsers, and techniques to bypass anti-bot measures.
• Develop and maintain two-way integrations using REST/GraphQL, webhooks, batch and streaming processes, OAuth, and other authentication flows.
• Implement sync and aggregation fundamentals: idempotency, retries, rate limiting, pagination, incremental sync, entity resolution, and reconciliation of divergent state across systems.
• Integrate with existing orchestration and ingestion stack (workflow schedulers, layered/ELT-style pipelines) to raise the bar on data reliability and observability.
• Own third-party relationships end-to-end: source and reach out to data providers, negotiate access, and navigate data-sharing agreements.
• Act as the primary point of contact for external stakeholders (towns, municipalities, contractors, service providers, agents, platform partners) to unblock access and resolve data issues.
• Establish connector patterns, two-way sync conventions, and data contracts that the rest of engineering will adopt as the number of sources scales.
• Ensure integrations are built with an "as code" philosophy: connectors, schemas, and contracts live in version control, are code-reviewed, and are maintainable and observable.

Requirements

• 5+ years as a software engineer with a backend/fullstack mindset — comfortable moving across the stack, not confined to one layer.
• Strong coding ability in at least one of TypeScript/JavaScript, C#/.NET, or Python, and productive in the others.
• Experience building and operating production integrations against third-party and internal APIs.
• Hands-on experience aggregating messy, fragmented data into a single system, particularly in domains like real estate, public records, permits, or contractor/service networks.
• Track record of ingesting from many disparate, low-quality sources and reconciling them into one trustworthy model.
• Comfortable extracting data when no clean API exists: web scraping, parsing HTML/PDF/scanned documents, using headless browsers, and handling anti-bot measures.
• Deep experience building two-way integrations: REST/GraphQL, webhooks, batch and streaming, OAuth, and other auth flows.
• Fluency with sync and aggregation fundamentals: idempotency, retries, rate limiting, pagination, incremental sync, entity resolution, and reconciliation.
• Ability to work within an existing orchestration and ingestion stack (e.g., workflow schedulers, layered/ELT-style pipelines).
• Partner-facing mindset: comfortable owning external relationships and representing Ruxlo professionally to outside partners.
• Proven ability to manage third-party relationships end-to-end, including sourcing, negotiating access, and maintaining data-sharing agreements.
• Strong written and verbal communication skills to translate between external stakeholders and internal teams.
• Able to own an area end-to-end with limited guidance and establish patterns from scratch.
• AI-native by default: proficient in using AI tools to multiply output while verifying their results.

Preferred Skills

• Founding-team or early-stage experience building an integrations or data-ingestion function from zero on a lean team.
• Direct experience integrating with QuickBooks or other accounting systems, dispatching/field-service software, or CRM platforms.
• Proptech, real estate, fintech, or geospatial data experience, especially with public records, permits, MLS, or contractor/service networks.
• Data/ETL/pipeline engineering and data-quality validation expertise.
• Experience with iPaaS or connector frameworks, or building a custom integration platform.
• Familiarity with message queues, event-driven architecture, and change-data-capture (CDC).
• Experience with contract testing, observability, and using production signals to catch sync drift early.
• SaaS data-product or multi-tenant integration experience.