Hesiod's tools run on one client's documents today and need to run on fifty. You own the architecture that gets them there: the governed data layer every engagement is built on, the standing project record, the integrations with the systems contractors already run, and a security posture a client's counsel can read before day one.

What you will do

• Set the platform architecture: multi-tenant project record, document and retrieval pipelines, model orchestration, and the audit and permission layer underneath all of it.
• Build the integration layer for construction ERPs and project platforms: Viewpoint, Sage, Procore, ProjectSight, Bluebeam, HCSS.
• Make the governed layer provable: read-only access, role permissions, logged queries, data that never leaves the project.
• Design for the field: offline-tolerant capture, dictation, mobile, and the realities of a job trailer's connectivity.
• Set the engineering standards and hire against them as the team grows.

Who does well here

• You have carried a product from a working version to one that many customers depend on, and you know which decisions have to be made early.
• You have shipped systems that handle documents, permissions, and integrations with legacy enterprise software.
• You have built with large language models in production and have opinions about retrieval, grounding, evaluation, and cost.
• Construction experience is welcome and not required. Curiosity about how a job actually runs is.