QUICK FACTS:

<aside> 🌎

LOCATION: Munich, Germany - hybrid

</aside>

<aside> 🛠

OUR TECH STACK: ”Classic” Software Stack: TypeScript, react, Python, PostgreSQL, Terraform ”Modern” AI Stack: Leading LLM models, observability/evaluation tooling (Langsmith), graph RAG & vector databases

</aside>

<aside> 💼

EMPLOYMENT TYPE: Full-Time

</aside>

<aside> 📅

START DATE: asap

</aside>

🚀 What WE do at Tendos

We are Tendos, a Munich-based startup, offering agentic workforce for white-collar jobs in construction. Our AI-first solution streamlines and automates tendering and quoting related workflows in the construction industry. Tendos is freeing inside sales teams from tedious manual tasks while unlocking new revenue potential. Take the unique opportunity and join one of the hottest early-stage start-ups to redefine workflows with AI in the biggest industry in the world!

🚀 The role

Most ads like this one say the founder wants out of the technology. Here it is the other way round, and it is the most important sentence on the page: our CTO is deeply involved in the technology and will stay that way.

This is a purely technical leadership role: no reports, no people management. What you take on is the architecture and technical direction of a platform that has outgrown one person, and of a team building on it every day. You stay hands-on: you design, and you write code that goes to production.

🥇 What YOU will do at Tendos

• Set technical direction across the platform. You own the architecture and the technical standards of the platform, beyond a single feature and beyond the current quarter. You make the technology calls (patterns, frameworks, tooling, build or buy), lead design reviews, and balance what we need to ship now against what the system has to carry in two years.
• Take the hardest problems, design through production. The ones where after two weeks it still isn't clear whether the approach holds, and where getting it wrong is expensive to undo.
• Raise the standard. Not line by line in code review, but in how technical work gets done here: how a problem is framed, which options are weighed, and which solution fits the job at hand. You set that bar, and you set it by example.
• Mentor and sponsor. Hand over the visible, career-making piece of work rather than keeping it, and argue for that person in rooms they are not in.
• Turn open debates into decisions. A technical argument that has run for three weeks is a cost. You write the options down, make the call legible and get the team moving again.
• Bring the engineering view into product and customer decisions. What is cheap, what is expensive, and what a promise to a customer costs the platform later.
• Do the unglamorous work too. The migration, the flaky test suite, the maintenance a team this size has nobody spare to absorb. Unprompted, and in your first quarter rather than once you have settled in.

💪🏼 What we are looking for