You'll ship agents that move money, and you'll keep the rhythm that gets them shipped. Accounts payable, accounts receivable, treasury: autonomous agents that read the invoice, match it, negotiate the discount, release the payment, and reconcile the cash. Every one of those actions runs in production with a customer's CFO watching the result.

Most of what the industry calls engineering culture was written for a world where humans typed every line. That world ended. We want to build the 2026 version: engineers who work with agents as a matter of course, where the unit of work is the loop (spec, generate, evaluate, correct, ship) rather than the ticket, where code review means reviewing the evals and prompts as hard as the diff, and where a regression suite over real customer invoices is what lets us move fast on systems that touch money. Nobody has a settled playbook for this. You'll help write ours, from inside a pod.

This is a player-coach role. You'll spend most of your week shipping code in one of our pods, and you'll manage the engineers day to day: 1:1s, feedback, growth, the hard conversation when it's needed. The rest goes to the delivery rhythm: pods commit to milestones in Linear, post progress daily, and review misses every Friday with the Head of Product and the CTO. You run that review and the follow-ups. The management share grows as we go from 8 engineers to 16 and beyond; this role is the natural path to Head of Engineering. You'll report to the CTO. Causa Prima is built by the team behind Taulia and backed by Creandum.

What you'll do

• Ship as a senior engineer, 70 to 80% of your week. Take the hardest work in your pod, unblock the integration nobody wants, and review the code that touches money personally. You set the bar by clearing it in front of the team.

• Manage the engineers day to day. Weekly 1:1s, direct feedback, growth plans, and the honest conversation about who's ready for more scope and who's in the wrong seat. The CTO owns hiring decisions and the technical direction; the people in the pods are yours.

• Run the delivery rhythm. Weekly milestone commitments, the Friday review, the dashboard of committed versus delivered, and the follow-ups when something slips. Misses are discussed to learn, not to blame; your job is that they get discussed at all, with an owner and a next step.

• Make the loop the way we work. Specs written so an agent can execute them, evals that run before merge, review practices that treat prompts as code. The CTO owns the architecture; you own that every pod actually works this way, including the change management when they don't.