Unknown - Founding Engineer

• The problem is genuinely hard. When a structural engineer changes Column C7 in their analysis model, the same column exists in drawings, schedules, specs and emails under different names, in different formats, with no shared identifier. Resolving those references into one canonical entity, and telling the engineer exactly what just went out of date, is the core of our product. You'll build on and extend that foundation. • The problem is genuinely hard. • Your work ships to people who pay. The platform is in production with signed design partners including some of the UK's leading structural engineering firms. Features go from your branch into the hands of working engineers within days, and you'll hear directly what landed and what didn't. • Your work ships to people who pay. • You'll work on the whole product, not a slice of it. We're a small team and we run one focused thing at a time. You'll take features from a conversation with a customer through design, implementation, tests and deployment. No ticket factory, no waiting on three other teams. • You'll work on the whole product, not a slice of it. • What we're building • What we're building • Structural engineers work across a fragmented set of tools with no shared source of truth: ETABS models, SAFE analyses, Autodesk drawings, Excel specs, PDFs, emails. When a design changes, propagating that change across files is manual, slow and error-prone, and the errors are expensive. • Bite is the change management and audit trail layer for structural engineering. The platform does two things that today take weeks of manual work: natural-language search across a project's entire file ecosystem, and cross-file impact detection. Both run on a single engineering knowledge graph built on content-addressed file storage, per-file structured extraction, and a canonical entity resolver that unifies concepts across file formats. • The timing matters too. The Building Safety Act now requires firms to evidence their design decisions, and directors carry personal liability for it. We are building the system of record for that. • What a typical week looks like • Ship a feature end to end: a Node/TypeScript API change, the React frontend that exposes it, and the tests that prove it works. • Pair with El-Amin (our CTO, a former practising structural engineer) on how engineers actually think about a column, a load path, or a revision, then encode that into the data model. • Improve extraction or retrieval quality in the Python ML/RAG workers and measure whether it actually got better. • Sit in on a design partner call and watch a structural engineer use what you built last week. • Make a pragmatic call on tech debt with the team: what we fix now, what we log, and why. • You don't need to be expert in every layer. The stack is polyglot by design (TypeScript, Python, React, C#/WPF, Azure) and we care about strong core engineering far more than specific tools. • Product sense is not optional • AI now writes a meaningful share of the code. What it can't do is decide what's worth building, notice that a feature solves the wrong problem, or sense that a structural engineer will never click that button. We don't have a layer of product managers between you and the customer, and we don't plan to. Every engineer here exercises product judgement daily. If you've ever been frustrated that nobody asked you what should be built, this is the antidote. • How you'll grow • How you'll grow • You'll learn an entire vertical: how structural engineering firms work, how AEC data formats behave, and how to build LLM/RAG systems that hold up in production. You'll work directly with our VP of Engineering and CTO, and as the team grows around you there's a clear path to owning a domain, leading projects, and eventually mentoring the engineers who come after you.