Remote Backend Integration Engineer: Data Feeds & CRM

UDX; Durham (NC); Hybrid; USD 55,000 - 110,000; Full time

Job summary

UDX Inc. is seeking an Integration Engineer to build and maintain backend services that connect clients' systems: data feeds, ticketing and CRM automations, and conversion APIs. You will work with PHP and Node.js, Firebase and Cloud Run functions, Elasticsearch, and HubSpot/Salesforce APIs, deployed on Kubernetes across multiple clouds.

This is a remote contract role with overlap for US Eastern hours. We expect strong API design, data modeling, and reliable deployment practices, with a focus on

Qualifications

• Four or more years building backend services.
• Real experience with HubSpot, Salesforce or similar CRM APIs.
• Experience with serverless runtimes and Elasticsearch.
• SQL and data modeling that hold up when a feed changes shape.
• Git, pull requests, CI; Docker for local development.
• Written English readable by clients.
• Overlap with US Eastern hours.

Responsibilities

• Build and maintain data feed pipelines: ingestion, normalization, validation, scheduling, and the alerting that tells us when a feed is stale before the client does.
• Build CRM and marketing integrations on HubSpot, Salesforce and Meta: webhooks, private apps, property mapping, conversion APIs, and the reconciliation jobs that catch drift.
• Build ticketing and event automations: order and refund webhooks, count aggregation, partial refund handling, and dashboards clients check during a presale.
• Write and operate cloud functions on Firebase and Cloud Run: pollers, cron jobs, endpoint protection, cost and error monitoring.
• Expose and consume WordPress REST endpoints for headless front ends and third-party systems.
• Harden what you build: input validation, secret handling, rate limits, least-privilege service accounts.
• Track every task to a GitHub issue with a same-day comment and a PR link.

Skills

Backend development

CRM APIs

Serverless runtimes

SQL data modeling

Git & CI

English writing

Tools

Docker

Elasticsearch

Firebase Functions

Cloud Run

Job description

ENGINEERING CAREERS

Software | Integration Engineer

UDX is looking for a backend engineer to build the services that connect our clients' systems: data feeds, ticketing and CRM automations, conversion APIs, and the small cloud functions that keep them in sync.

Apply Other Careers

Integration Engineer

Behind every UDX website is a set of integrations that do the real work: a real estate listings feed that has to be right every morning, a ticket count pipeline that updates a promoter's CRM as sales come in, a conversion API that reports purchases to Meta and Google, an ERP that pushes product data to four brand sites. You will build and maintain those.

The stack is pragmatic: PHP and Node.js services, Firebase and Cloud Run functions, Elasticsearch, HubSpot and Salesforce APIs, WordPress REST endpoints, webhooks in both directions. Everything runs on Rabbit and deploys from a pull request.

This is a contract role, remote, with overlap for US Eastern hours.

UDX is a service-disabled veteran-owned small business (SDVOSB) founded in 2011 and headquartered in Durham, North Carolina, with a distributed engineering team. We build and run cloud infrastructure and web platforms for organizations that cannot afford downtime: cultural institutions, live event promoters, consumer brands, real estate and professional certification bodies. Our delivery platform, Rabbit, turns a Git repository into a fully provisioned, monitored, secured environment on Kubernetes across GCP, AWS and Azure. We also ship Kubernetes operators to the Azure Marketplace.

Every hour we work maps to a GitHub issue. Every change is a pull request. Every day of work leaves a comment. That is how we bill, how we prove work to clients, and how we know what happened six months later.

What you'll do

• Build and maintain data feed pipelines: ingestion, normalization, validation, scheduling, and the alerting that tells us when a feed is stale before the client does.
• Build CRM and marketing integrations on HubSpot, Salesforce and Meta: webhooks, private apps, property mapping, conversion APIs, and the reconciliation jobs that catch drift.
• Build ticketing and event automations: order and refund webhooks, count aggregation, partial refund handling, and dashboards clients check during a presale.
• Write and operate cloud functions on Firebase and Cloud Run: pollers, cron jobs, endpoint protection, cost and error monitoring.
• Expose and consume WordPress REST endpoints for headless front ends and third-party systems.
• Harden what you build: input validation, secret handling, rate limits, least-privilege service accounts.
• Track every task to a GitHub issue with a same-day comment and a PR link.

What you'll need

• Four or more years building backend services in Node.js or PHP, with at least one in production at a client's expense.
• Real experience with HubSpot, Salesforce or a comparable CRM API, including webhooks and OAuth private apps.
• Familiarity with serverless runtimes (Firebase Functions, Cloud Run, Lambda) and with Elasticsearch or a comparable search and analytics store.
• SQL and data modeling that hold up when a feed changes shape.
• Comfort with Git, pull requests and CI. Docker for local development.
• Written English that clients can read in issue threads.
• Overlap with US Eastern hours.

What we offer

• Contract engagement, hourly, with a defined backlog of integration work across several clients.
• Systems that clients depend on daily, so correctness is noticed and rewarded.
• Multi-cloud infrastructure (GCP, AWS, Azure) handled by the platform.
• Direct access to the founders. No layers, no ticket queue between you and the decision.
• Remote, flexible hours outside the US Eastern overlap.

Engagement

Specialization Backend services, data feeds, CRM and ticketing integrations, cloud functions Commitment 20 to 30 hours a week to start Engagement Contract, hourly, invoiced monthly against GitHub issues Work setup Remote Overlap At least 4 hours a day inside US Eastern business hours Access Repository and service-account access scoped per client; secrets through the platform, never in code Location No restriction Language English, written and spoken; you will write in client repositories Start As soon as the references clear How we work Issue per task, pull request per change, comment per day

How to apply

Send the answers below through the contact form and begin your message with the role name. Short answers are fine; links are better than descriptions. We reply to everyone who answers all four.

Link to an integration you built that runs unattended in production, and say how you know when it fails.

Which CRM, ticketing or advertising APIs have you shipped against, and what was the hardest part of each?

Describe a data feed that changed shape under you: how you noticed, and what you changed.

Your availability in hours per week, the US Eastern hours you can overlap, and your hourly rate.

Apply for Software | Integration Engineer

Answer the four questions above and send them through the contact form. If the fit is there, the first conversation is with the founders, not a recruiter.

Apply Other Careers word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1