The work happens inside other people’s boundaries.

The same four chips appear on product status. We hire against this packaging, not against a future one.

• We build Reign the way we ask customers to let us build for them. Nearly all of our own implementation runs through the Factory. Agents and models write. A named iTmethods engineer approves. That is not a slogan. It is how the product is made.
• Engineers operate what they build. There is no wall between the team that ships and the team that gets paged. If you would not want to be woken by it, that is information about the design.
• Decisions are written down. The writing is part of the job rather than an afterthought, because a decision nobody recorded is a decision the next person has to make again from nothing.
• Work is reviewed by people who will have to run it. Review here is not a gate applied by a separate function. It is the person who will hold the pager reading what you propose to hand them.
• Evidence is produced as the work happens. The record of what changed, who approved it and what state it left behind is generated by the work rather than reconstructed for a reviewer afterwards.
• Model calls go through Reign Gateway. Identity, policy and a record before a provider is reached. That applies to the tools we build with, not only the ones we sell.
• Scope is agreed before work starts. Eligibility, the approval gate and the measures are written down first. Nobody here is asked to hit a date that was quoted before anyone looked.

None of that is unusual in a well run engineering organization. It is unusual to describe it accurately at the point of hiring, which is what this page is trying to do.

• Platform and product engineering. Building Factory, Gateway and Assurance, and what ships into a customer instance. The Factory we productize is the Factory we already run on our own work.
• Operations engineering. Running Reign Ops: single-tenant dedicated instances, the toolchain estate, upgrades, the hardened baseline, backups with a restore that has been exercised, and the response when a platform stops.
• Security and compliance. Owning the documented process behind every question a customer asks, and the record of what was answered. This function says no in writing and is supported when it does.
• Field engineering. Named engineers who sit with the teams doing the work rather than reporting on it, inside the engagement and under the customer’s change process.
• Commercial and delivery. Owning the contract, the scope, and the point where a briefing becomes work. Including the part where we tell somebody there is no fit.

We hire slowly, and we describe a role accurately at the point of hiring rather than after an offer. If the description you were given does not match this page, tell us, because one of the two is wrong.