Software | Integration Engineer

ENGINEERING CAREERSSoftware | 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.

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, Hub Spot and Salesforce APIs, Word Press 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 Git Hub 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.

• 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 Hub Spot, 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 Word Press 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 Git Hub issue with a same-day comment and a PR link.

• 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 Hub Spot, 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.

• 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.

• 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 Git Hub 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