Backend Engineer, Building Record

You will build the system of record. Every building Wren touches has a record that begins when we first engage and that is designed to remain legible long after the team that started it has moved on. Drawings, filings, conditions, inspections, material histories, correspondence. That record is the backbone of the product and of the company.

The standard for this system is unusual. We are not building a CRUD application. We are building something that needs to be readable, queryable, and trustworthy in twenty years, by people who are not us. That changes how you design. You will think about schema migrations as events with provenance, not as one-off scripts. You will think about the shape of the data as a legal artifact, not as a convenience for today's feature.

Most of the week is backend engineering in TypeScript and Postgres with occasional Python for data work. Some of the week is reading: filings, drawings, statutes, so that the schema you design actually matches the thing it is meant to represent.

You will work with the research lead, the compliance systems engineer, and the agent-runtime team. Your work sits underneath all of theirs. You will also occasionally work directly with the licensed professionals who read these records, because the only real test of legibility is whether a stranger can make sense of a building's file in ten minutes.

In your first six months you will take ownership of the record model: what a building is to us, what a filing is, what a condition is, how a document attaches to all three, and how provenance flows through the system. You will migrate the current early-stage schema into the versioned, event-sourced model that can support the next decade of product, and you will do it without losing the audit trail on any existing engagement. You will write the internal documentation that lets someone joining in three years understand the model without asking you.

Beyond the core schema you will build the retrieval primitives the agent runtime uses to read a building. That means thoughtful query surfaces, careful handling of partial or contested data, and the small interfaces that let the rest of the team build features without breaking the archival guarantees. Expect to spend real time on correctness and comparatively less time on novelty.

Seven or more years of backend engineering with deep Postgres or equivalent relational experience. You have designed a schema that lived longer than you worked on it. You have run migrations against real data without incident. You think about event sourcing, provenance, and audit trails as first-class concerns, not as compliance checkboxes.

In character, we want someone who is unusually comfortable with the idea that their work will outlast their tenure. Someone who writes schema documentation as carefully as they write code. Someone who would rather produce one durable system than five clever ones. If the idea of working on the same model for three years sounds dull, this is the wrong role.

Write to careers@aedificeai.com with the subject line “Backend Engineer, Building Record”. 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.