Founding Full-Stack Engineer

The construction industry loses $1.6 trillion annually to inefficiencies — not because people are careless, but because critical knowledge is trapped in PDFs, transcripts, and scattered systems. Every new project starts from scratch.

We're building the opposite: an AI co-worker that extends the Projektsteuerer (the person who runs complex construction projects), while every project makes our system measurably better. The moat isn't the model — it's the compounding project memory no competitor can replicate.

Pre-seed led by Realyze Ventures — LPs include Zech and other major European construction groups. Co-investors: D11Z (the family office behind Aleph Alpha) and the CDTM Venture Fund (backed by 300+ CDTM alumni including founders of Personio, Alasco and the Technical Director of DeepMind).

Our software is running today on a major autobahn construction program and an S-Bahn transit program — multi-year timelines, hundreds of thousands of pages of specs, protocols, and communications. Real consequences when we get it wrong.

1. AI-native project management, not a chatbot on top of PDFs
   The construction industry doesn't need another chat wrapper around GPT. It needs project management software where AI runs in the background — through cronjobs, proactive alerts, and task dashboards — not in a sidebar chat window. The hard product question is how AI shows up: when as silent background automation, when as a surfaced recommendation the PM approves, when as a fully delegated task the user only reviews after the fact.
2. Extending harness engineering all the way to the UI
   Agent harnesses don't stop at the backend. A multi-step agent run that streams tokens, calls tools, hits failure modes, and recovers gracefully needs a frontend that makes all of that legible in real time. You'll plumb Vercel AI SDK streams from our agent layer straight into the component tree — streaming, tool-call traces, interrupts, partial renders, graceful failure — all as first-class UI concerns, not afterthoughts.

• Product sense: you reason from user pain → solution → measurable outcome. You can talk to non-technical customers and understand their workflows.
• Velocity + craft: prototype fast, measure everything, iterate on real feedback. But you care about reliability because the downside of wrong is real in construction.
• Comfort with the unknown: many of these problems don't have Stack Overflow answers. You read papers, prototype, and compare approaches.
• Bonus: strong open-source work, previous early-employee startup experience, domain depth in document understanding or agent systems, or shipped systems that replaced hours of human labor.
• Level is opportunistic: We've seen brilliant new grads outperform staff engineers and vice versa. If you're exceptional, we'll find the right scope.
• Language: We work in English. German is nice-to-have for customer conversations but not required — we have native speakers for that.

1. 90-minute first call with one of our engineers and then if you impress us, you will speak to one of the co-founders directly.
2. Onsite case study in Munich. We send you the materials in advance — plan on about 4 hours of preparation. You come to our office and we work through it together. This is where we see how you think, debug, and ship under real conditions.
3. Offer. Decision within 24 hours of the case study. Offer out within 48 hours.