Senior Software Engineer, Integrations

Job Description

Job Description

About Ruxlo

LinkedIn is your professional network. Facebook and Instagram are your social networks.

Ruxlo is your Home's Network.

Your Home. Your Neighborhood. Your Town.

We're building a profile page for every one of America's 150M+ properties — and the people tied to each one.

Most of what happens to a house is forgotten, scattered across a county filing, a shoebox of receipts, and the memory of whoever owned the place three families ago. We're replacing that with one durable record attached to the parcel itself: work recorded by the contractor who did it, confirmed by the owner who paid for it, and it stays with the house when it sells. Think CARFAX for homes.

On a public-record foundation, we're building crowdsourced layers competitors can't license — verified contractor work history, deal documents, and real neighborhood connections. Every layer feeds a Property Graph that gets richer, ranks higher in search and AI answer engines, and pulls in the next user for free. One AI-native app — map-based web and mobile, AI-assisted search, freemium — serves homeowners, contractors, investors, builders, and agents.

We're early-stage, backed by an experienced SaaS founder — a unique opportunity to help define a category at the intersection of AI, data, and the largest asset class in the country.

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.

Position Requirements

Data Aggregation Expertise (the core of this role)

• You've lived aggregating messy, fragmented data into a single system. Real estate data is scattered across public records, permits, MLS feeds, county sites, contractor and agent tools — inconsistent formats, missing fields, duplicates, no shared IDs — and you've done the unglamorous work of pulling it all in and making it coherent.
• A strong track record of ingesting from many disparate, low-quality sources at once and reconciling them into one trustworthy model — matching, deduping, normalizing, and resolving conflicts across sources that disagree.
• Comfortable getting data when there's no clean API: web scraping and crawling, parsing HTML/PDF/scanned documents, headless browsers, and handling anti-bot measures, pagination, and rate limits — because much of this data isn't behind a tidy endpoint.
• Deep, hands-on experience building two-way integrations — REST/GraphQL, webhooks, batch and streaming, OAuth and other auth flows — not just calling an endpoint once.
• Fluency with sync and aggregation fundamentals: idempotency, retries, rate limiting, pagination, incremental sync, entity resolution, and reconciliation of divergent state across systems.
• You know where your job ends: your mandate is getting clean, reliable data inside our walls and landing it into the pipeline — from there our Data team models, transforms, and serves it. You build and feed the front door, not the whole warehouse.
• Comfortable working in an existing orchestration and ingestion stack (workflow schedulers, layered/ELT-style pipelines) rather than needing to invent one — you plug into what's there and raise the bar on it.
• An "integrations as code" philosophy: connectors, schemas, and contracts live in version control, get code-reviewed, and are built for maintainability and observability.

Partner-Facing & Relationship Management

• This is a partner-facing role, not a heads-down eng seat — you're comfortable owning external relationships and being the human on the other end, not just the code.
• Proven ability to manage third-party relationships end to end: sourcing and reaching out to data providers, negotiating and maintaining access, and navigating data-sharing agreements and terms.
• Comfortable interacting with all types of stakeholders — towns and municipalities, contractors, service providers, agents, and platform partners — to unblock access, resolve data issues, and keep integrations healthy.
• Strong written and verbal communication; you can represent Ruxlo professionally to outside partners and translate between their world and ours.

Engineering Craft

• 5+ years as a software engineer with a backend/fullstack mindset — comfortable moving across the stack, not living in 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.

Ownership & AI-Native

• Able to own an area end-to-end with limited guidance and establish patterns from scratch.
• AI-native by default: you use AI tools to multiply your output — and verify what they produce.

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 public records, permits, MLS, or contractor/service networks.
• Data / ETL / pipeline engineering and data-quality validation.
• Experience with iPaaS or connector frameworks, or building a custom integration platform.
• Message queues, event-driven architecture, and change-data-capture (CDC).
• Contract testing, observability, and using production signals to catch sync drift early.
• SaaS data-product or multi-tenant integration experience.

*This position is hybrid Manasquan, NJ. Must be willing to be onsite 4 days/week*

Ruxlo LLC is an Equal Opportunity Employer. 

AI disclosure: As part of our recruiting process, Ruxlo may use AI-assisted tools to help screen, review, and organize applications, as well as to support scheduling and communication. These tools assist our team and all final hiring decisions are made by humans. We work to ensure these tools are used fairly and without unlawful bias. If you have questions about how AI is used in your application, would like to request a reasonable accommodation or an alternative review process, please contact us at View phone number on ziprecruiter.com.