Product engineering
JavaScript end to end across the web, the application and the server. Our own component library and a shared design system.
A small team that designs XEN from real operations: plants, fleets, counters and monthly closes. We are looking for people who want to build the same thing.

We do not post dated vacancies: when a profile fits, we open the conversation. Tell us what you have built, which operation you know up close and how you would like to contribute. We answer every message.
JavaScript end to end across the web, the application and the server. Our own component library and a shared design system.
Designing agents that act with permissions and approval, open protocols for external agents, and Xeni's conversation with every area.
Someone who walks into a plant, a store or a public entity, understands how it works and leaves XEN running with its team.
Invoicing, series and numbering, monthly close and payroll: processes tied to each company’s country and operation.
Five things that are already true on the team and that you notice on day one.
The monthly valuation of a water treatment plant, a fleet's inspection checklist and a counter's electronic invoicing exist because someone needed them. We do not build features from a catalog.
The web, the application and the server share one language. Anyone on the team can read any part of the system.
A new feature starts with Xeni writing the scope and the test cases. The team builds on that specification and deploys with the suite green. That is how XEN Overdrive works on the inside.
A screen is done when every block answers a question from the person who uses it and it exists in Spanish and in English. What does not reach that level is finished or withdrawn, never published halfway.
No filler grids, no decorative metrics, no gradients that mean nothing. Dense tables before cards, and the client's vocabulary rather than a presentation's.