You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Causa Prima

Engineering Lead

  • Office
  • 6+ years
  • English (C1)

Salary

Not stated

Similar roles pay €80K - 115K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company builds autonomous agents for accounts payable, accounts receivable and treasury. An agent reads an invoice, matches it, negotiates the discount, releases the payment and reconciles the cash, and each step runs in production where a customer's CFO sees the result.

Traditional engineering practice was built for a time when people wrote every line by hand. The team is working out how to build with agents as the default, where the basic unit is a loop of spec, generate, evaluate, correct and ship. Code review covers evals and prompts with the same rigour as the diff, and a regression suite built on real customer invoices lets the team move quickly on money-moving systems. No established playbook exists yet, and you will help write it from inside a pod.

This is a player-coach role. You will write code in one of the pods most of the week and manage its engineers day to day, including 1:1s, feedback, growth and difficult conversations. The company is growing from 8 engineers to 16 and beyond, and the management share of this role will grow with it. This role is a natural route to Head of Engineering. You report to the CTO. The company was founded by the team that built Taulia and is backed by Creandum.

Responsibilities

  • Spend 70 to 80% of your week as a senior engineer: take on the hardest work in your pod, clear blocked integrations, and personally review code that touches money.
  • Hold weekly 1:1s, give direct feedback, write growth plans, and decide, with honesty, who is ready for more scope and who is in the wrong seat. The CTO makes hiring and technical direction decisions, while you lead the people in the pods.
  • Run the delivery rhythm: weekly milestone commitments in Linear, the Friday review with the Head of Product and the CTO, a dashboard of committed versus delivered work, and follow-up on any slippage. Misses are reviewed to learn from, and each one must have an owner and a next step.
  • Establish the loop across every pod, including specs an agent can execute, evals that run before merge, and treating prompts as code. The CTO owns architecture; you ensure each pod follows these practices and lead the change when one does not.
  • Flag risk early, so that anything that will miss Friday is known by Tuesday to you and to everyone who depends on it.
  • Spend time with customers, such as controllers who need the agent's technically correct but operationally wrong matches explained, or AP leads who walk you through undocumented SAP extensions. Their feedback shapes the next milestone.

Requirements

  • You are a senior engineer who enjoys the operational side, with production experience where mistakes cost money in fintech, payments, ERP-adjacent work or enterprise B2B.
  • You have managed engineers, run their 1:1s and a delivery cadence, and wanted to keep doing that while still writing code.
  • You build with agents and have shipped something in the last month using an agentic coding tool that saved you a week. You can show it.
  • You write Python or TypeScript well and know PostgreSQL well enough to review a migration without help.
  • You have kept commitments reliable, measured with numbers such as committed versus shipped or cycle time. When work slipped, you followed up without turning it into blame.
  • You add rituals only when they earn their place and drop them when they do not. A weekly review should take 30 minutes rather than 90.
  • You can disagree with a founder and remain in the discussion. Trust comes first, then challenge.
  • Fluent English is required. German or Spanish is a plus. Munich is preferred, and Madrid is acceptable. You will work regularly from both offices.
  • Nice to have: experience with AI agents in production, where agents are the product rather than a feature.
  • Nice to have: depth in purchase-to-pay or order-to-cash, or hard-won experience from an SAP integration.
  • Nice to have: experience growing with a team through a Series A or B.
  • Nice to have: experience as a former founder or founding engineer.
  • This list is a wishlist rather than a checklist. Apply even if you do not match every item, as long as the role excites you.

Conditions

Based in Munich or Madrid, with regular travel between both offices.

Reports to the CTO.

Equal opportunity applies to all candidates.

Where you’d work

From the office

About the company

Causa Prima

  • Industry: FinTech

Office in Munich, Germany

Also hiring in Madrid, Spain

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 19 checks run
  • 0 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Employment, Company, Requirements
Tech stack
  • TypeScript
  • Python
  • PostgreSQL
Seniority
Lead
Type
Full-time
Industry
FinTech
Specialty
Backend
Region
Europe
Show 7 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Lead
Experience
6+ years
Tech stack
  • TypeScript
  • Python
  • PostgreSQL

Location

Work model
Office
Region
Europe
Office
  • Munich, Germany

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Company

Industry
FinTech

Requirements

Languages
  • English (C1)

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason