CAREERS
Enterprise AI is mostly a slide. The deployed fraction — production systems, regulated estates, evidence at every step — is small. That gap is the job.
We are a small team, founded in the USA, that deploys globally. Small means the person who scopes the problem ships the fix. There is no handoff to hide behind, and no deck to retreat into.
This page is written to filter, not to attract. Some readers should close the tab here. If instead you feel relief, keep reading.
/01 · SELECTION
We do not hire against a credential list. We hire against behavior we have watched survive the field. Three patterns recur.
You would rather put a rough v1 in front of a real user today than polish a demo for a month. Production is the only test environment you fully trust.
You can sit with a customer's ops team on Monday and be the person they call by Friday. Field work is a trust exercise conducted in someone else's building.
You record what you did and why before anyone asks — not for compliance, but because you want to know. Our products are built on that instinct. So is the team.
/02 · ROLES
These are the roles we would hire tomorrow. Founded in the USA. Deployment is global, and for field roles, frequent. There is no job board and no requisition count. Apply by writing to support@elixax.com with the subject 'Application — [Role]'. An engineer reads it, not a tracking system.
Embedded with customer teams, writing production code on their infrastructure. You scope the problem in their conference room and deploy the fix on their metal. Weeks on site, not quarters on calls. The deployment is the deliverable — there is no other artifact.
Core engineering on the infrastructure intelligence layer for regulated estates: the sealed, hash-chained Decision Replay evidence ledger, i-Trace change-to-impact correlation, maker-checker controls. On-prem software for Windows, RHEL, AIX, and Oracle estates. Patching is live; Automation is next. Founding means the architecture is yours to get right.
Retrieval and generation over real plan documents, in a domain where a wrong answer costs a member real money. Cited answers only. PHI-aware by design. You build the machinery that keeps a language model honest in a field that punishes improvisation.
/03 · PROCESS
Four steps. Weeks, not months. The process is small because the team is small — which means every step is with someone you would actually work with.
Send the thing you have built that you are proudest of — a repo, a deployment story, a system that survived contact with users. A working engineer reads it the week it arrives.
Two hours on a real problem from our queue. No leetcode theater, no take-home busywork. We want to watch you think, not recite.
All of it, because you will work with all of it. Ask anything. We answer plainly, including about the risks of joining an early company.
You get an answer in days. If it is yes, it comes with real scope attached — not a ramp-up period.
/04 · THE TRADE
No ping-pong tables appear in this section. Here is the actual trade.
What you get: scope that most companies gate behind a decade of tenure. Direct customer exposure — the people running your software know your name, and you know theirs. Field work that hardens into product: Holovyx is software that came back from the field, and your deployments feed it. A team small enough that the outcome is attributable to you, in both directions.
What it costs: field travel. Ambiguity. No department to escalate to — you are the department. We are an early company, and we will talk compensation plainly and early rather than gesture at a benefits wall we have not built.
If you need the machinery of a large employer around you, a large employer is the right call. We mean that without irony.
ENGAGE
Skip the cover letter. Send the thing you have shipped that you are proudest of — and what you would build here — to support@elixax.com with the subject 'Application'. If you want to know why we exist first, read the company page.