Founding Engineer (Tech Lead)

The Context

Banks still run their most critical, regulated work by hand; reading letters and emails, re-keying data between systems, chasing down missing info. It's the kind of work that's too important to get wrong and too tedious for anyone to want to do.

Porters fixes this. Our AI agents run these regulated processes end to end, with the audit trails and security banks actually require, so the work moves at the speed customers expect instead of the speed a backlog allows.

We're just over a year old and already live with real customers, growing the product quickly, and were named Fintech of the Year 2026. The goal is to build the operating system for autonomous banking. We're backed by Earlybird, one of Europe's oldest venture firms, and Seedcamp, who wrote first checks into Revolut, Wise, and UiPath.

The Mission

You'll own the outcomes. You take an ambiguous business problem and turn it into clear requirements, a design with clear business rationale, sequenced work, and a realistic estimate, build the hardest parts yourself, and multiply a team of mid-level engineers with well-defined, extensible work and the reviews that keep quality high. You stay an IC at heart while making the work legible, sized, and worth doing.

This job is in person in Zurich, or remote in Barcelona or Berlin.

Your responsibilities

• Deliver the highest-risk work yourself: Be the IC where it matters. Personally engineer the most complex, business-critical components, from cross-service logic to the boundary where AI outputs become deterministic, auditable actions, and set the technical bar for the team as you go.

• Turn business goals into shipped projects: Take an ambiguous problem and own it through to delivery, defining requirements, a design that starts from customer impact and takes the highest-ROI path whether it's make or buy, sequenced work, estimates, and clear engineering acceptance criteria a team can execute with minimal churn.

• Design complex systems that don’t break down in 12 months: Architect entire systems so the likely next requirement plugs in cleanly through configuration or a new adapter, keeping components reusable and loosely coupled, separating business logic from shared services, and maintaining a single authoritative, append-only source of truth for critical data - including consideration of make-or-buy options.

• Scale the team's autonomy and quality: Set decision thresholds so engineers self-serve low-stakes calls, define sanctioned paths for experimenting with regulated data, and spread understanding of our systems to cut key-person risk. Settle design in review, then build the road to production: CI/CD with quality gates, automated migrations, and systems that report their own health.