Most of what UDX bills is websites that matter to the business that owns them: a museum's gala and ticketing site, a live music venue launching in a new city, a beverage group's brand sites and ordering portal, a promoter's event calendar that sells out in minutes. You will build and maintain those.
Every site runs on Rabbit, our Kubernetes delivery platform, which means every branch gets an environment, every deploy is a merged pull request, and the infrastructure is already handled. Your focus is the site itself: theme, templates, custom plugins, headless front ends, performance, and the integrations that make the site useful.
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 WordPress sites from design: custom themes, block patterns, custom post types, Tailwind, and the plugins a client actually needs.
- Build headless and hybrid front ends in Next.js and React against WordPress or Strapi, with server-side rendering and CDN caching that survives real traffic.
- Launch sites on Rabbit: repository setup, branch environments, CloudFront and certificate configuration, go-live checklists, and the post-launch fixes.
- Maintain a portfolio of live sites: WordPress core and plugin updates, performance regressions, editorial requests, and the small changes that arrive every week.
- Integrate the services clients depend on: HubSpot forms and workflows, ticketing platforms, server-side Google Tag Manager, Meta and Google conversion APIs, email deliverability.
- Write and maintain Ghost Inspector and end-to-end test suites so releases do not break checkout or forms.
- Track every task to a GitHub issue and leave a comment and a PR link for every day worked.
- Four or more years building WordPress professionally, including custom theme and plugin development in modern PHP.
- Strong JavaScript and TypeScript; production experience with Next.js or React and server-side rendering.
- Tailwind CSS and responsive layout work that matches a design file to the pixel.
- Comfort with Git workflows, pull requests, CI checks and containerized development. You do not need to run Kubernetes, but you need to work inside a platform that does.
- Experience with WooCommerce, event or ticketing integrations, or CRM and marketing integrations.
- Written English that clients can read in issue threads.
- Overlap with US Eastern hours.
- Contract engagement, hourly, with a steady multi-client backlog.
- Infrastructure handled by the platform, so you spend your time on the site, not the server.
- Clients whose sites are central to their revenue, which means your work gets used and noticed.
- Direct access to the founders. No layers, no ticket queue between you and the decision.
- Remote, flexible hours outside the US Eastern overlap.
| Specialization | WordPress theme and plugin development, Next.js and React front ends, site launches |
|---|---|
| Commitment | 20 to 40 hours a week; the backlog is steady across several clients |
| 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 access on day one; production deploys go through pull requests and the platform |
| 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 |
Send the answers below through the contact form with the role name in the subject line. Short answers are fine; links are better than descriptions. We reply to everyone who answers all four.
- Link to two live sites you built or substantially rebuilt, and say what you owned on each.
- Link to a pull request that shows your WordPress or Next.js work, and what it fixed.
- Describe a launch you ran: what was on the go-live checklist, and what broke afterwards.
- Your availability in hours per week, the US Eastern hours you can overlap, and your hourly rate.