Compliance Systems Engineer

You will own the system that encodes regulation. Every jurisdiction Wren serves has its own statutes, its own filing forms, its own cycles, its own quiet conventions that only a licensed practitioner picks up after years of work. Turning that into a tested, versioned system that licensed humans can rely on is the job.

This is not rules-as-configuration. It is a careful exercise in translating statute and practice into code, designed so that when the law changes or our reading of it changes, the history of that change is preserved and auditable. Someone, years from now, should be able to read why Wren filed something a particular way on a particular date and see the statute section, the commentary, and the engineering decision that produced it.

You will work across New York, London, and Toronto to start, with more to come. Each one has a personality. Part of the craft of this role is respecting those differences rather than smoothing them away.

You will work with our research lead, our compliance attorney, and the engineers building the agent runtime. You will also spend time with filing clerks at building departments and landmarks commissions, because the written rule and the enacted practice are not always the same thing, and a real compliance system has to account for both.

In your first year you will replace the current first-pass rules layer with a versioned regulatory model that tracks, per jurisdiction, the statutes in force, the forms required, the cycles that drive them, and the decisions our licensed reviewers have made about ambiguous cases. You will build the test harness that lets a statute change flow through the system without breaking the audit trail on prior filings. You will make it possible for a licensed reviewer to read a filing and see the specific rule that produced every section of it.

Beyond the core model, you will help shape the interfaces the agent uses to consult the regulatory state at draft time. That means designing tools that return not just a rule but the confidence and the provenance behind it, so the agent can decide when to proceed and when to ask. You will also own the quiet work of keeping the system current as laws change, which is a real engineering discipline rather than a housekeeping task.

Five or more years of software engineering, with meaningful experience in a domain where being wrong has real consequences: finance, law, healthcare, or regulated infrastructure. You write careful code and you write careful prose. You have built a system whose outputs were reviewed by licensed professionals, and you understand why that changes how you design.

In character, we want someone who enjoys reading statute and who is comfortable saying "this rule is genuinely ambiguous and our system needs to reflect that." Patience is a core trait here. So is the willingness to build the boring, correct version instead of the clever, fast one.

Write to careers@aedificeai.com with the subject line “Compliance Systems Engineer”. Include a resume and a one-page note on why this role and why Aedifice. A real letter gets a real reply. We read every inbound.