Build the thing that kills ticket backlogs

Small team, real product, actual customers using it on production tickets every day. We move fast because we have to — and because we genuinely want to. No politics. No roadmap theater. Ship, measure, iterate.

3 open roles as of June 2026
Senior Backend Engineer
ML Engineer (NLP)
Customer Success
Remote-friendly. Austin offsite quarterly.

Open roles

Senior Backend Engineer
Remote — Austin preferred Full-time Python / Node.js

You'll work on the integration layer — the connectors that let Replixa talk to Zendesk, Stripe, HubSpot, and customer-specific APIs. You care about reliability, latency, and error handling in production. Experience with REST API integration, webhook systems, and background job processing required. Auth provider integration (OAuth, API keys, SAML) is a plus.

Apply
ML Engineer — NLP & Classification
Remote — Austin preferred Full-time Python / PyTorch

You'll work on intent classification, KB retrieval, and confidence scoring — the core of how Replixa decides what a ticket needs and whether it can resolve it. Comfort with retrieval-augmented generation, fine-tuning classification heads, and evaluating model performance on operational data. Prior experience in support automation or information retrieval is a strong plus.

Apply
Customer Success (First Hire)
Remote — Austin preferred Full-time Customer-facing

You'll own onboarding for new customers and be the person who helps them get to their first 200 resolutions. You'll see the product from the customer side and bring that signal directly back to the team. Support or CX background with some technical comfort (you don't need to write code, but you should be comfortable in a tool like Postman). Strong preference for someone who has worked in support operations themselves.

Apply

How we work

Remote-friendly, no async theater

We're distributed with an Austin anchor. Async is real — we write things down, decisions are documented, and nobody is required to be "always on." Weekly video sync is optional but happens. Quarterly Austin offsite for in-person work and food.

Weekly deploys, small diffs

We ship every week. PRs are small. Code review is fast. Nobody is waiting three sprints to see their work in production. If something breaks, we fix it same day — our customers' support tickets depend on us being reliable.

No ticket backlogs on our own tickets

Obviously. We use Replixa ourselves and we'd be embarrassed if we didn't. You'll also be expected to give honest feedback about the product — the "eat your own cooking" expectation is real and taken seriously.