Stand out for this role — generate a tailored resume and cover letter in about a minute.
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
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, 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.