How we work here.

The product refuses to guess, and so does the work

Every number CommitControl puts on a screen is derived from the customer's own data by a fixed calculation. Run it twice on the same pipeline and you get the same answer twice. The language layer reads that arithmetic back in plain English. It cannot produce a figure, change one, or alter how anything is weighted.

That constraint is not a marketing position, it is a standard that reaches every role. We do not ship a number we cannot trace to its inputs. We do not describe a capability we have not built. We do not put a claim on the website that the code does not support. If you have worked somewhere that shipped a confident number over thin data, you will find this either a relief or an irritation. It is worth knowing which before you apply.

The work runs in the EU

Production and customer data run on AWS in Frankfurt (eu-central-1). The Salesforce connection only reads; nothing writes back. GDPR access and erasure are tested endpoints rather than a manual process, and the model provider never receives a customer name, an opportunity name, or a person's name. Data governance here is a design constraint that shapes the architecture, not a compliance exercise applied afterwards.

The company is ZeusGlobal Nexus Limited, registered in Dublin. The roles we are hiring now are fully remote to start with. We are saying "to start with" rather than "remote forever" because we have not yet had the conversation about what this looks like at twenty people, and we would rather tell you that than promise something we might revisit.

Support is answered by the person who wrote the code

There is no tier one queue. A customer who reports a problem reaches somebody who can read the stack trace and change the thing. That keeps the distance between using the product and fixing it very short, and it means everyone here carries some direct contact with the people who pay us. If you want a role sealed off from customers, this is not it.

You own a surface end to end

Roles are scoped by surface rather than by layer. You take a piece of the product or the business and you own it from the decision through to what the customer experiences. You will not wait on a committee and you will not receive somebody else's half of the work late. The trade is that the scope is wide and the structure around it is thin. That suits senior people who would rather hold the whole problem. It does not suit somebody who wants a defined lane and a visible ladder, because neither of those exists yet.

What we will not pretend

• We are early. V1 is in production and the company is at the start of its commercial life. The risk profile is a startup's, not an established employer's.
• There is no ladder yet. A title here describes what you own, not where you sit in a hierarchy that has not been built.
• The scope is wide and the support around it is thin. You will do work that a larger company would have a whole function for.
• We are Salesforce only today. HubSpot is not built. If you are expecting a broad integration surface on day one, that is not where the product is.

What happens to what you send us

Applications go to a mailbox we control and are read by the people you would be working with. We do not load candidate details into any marketing or sales system. We keep what you send for twelve months so we can come back to you when something opens, and then we delete it. Ask us to delete it sooner and we will. How we handle personal data generally is set out in our privacy policy.