19 nov
|
Bifrost Studios
|
España
19 nov
Bifrost Studios
España
Harba. Permanent. Remote, based in Spain. English as the working language.
Why this role exists
Harba runs marinas. Slip bookings, billing, guest self-service, power metering, access control, payments: one platform, used every day by harbour masters across Europe.
Now we are rebuilding it. The goal is to become the number one marina and sailor app in the world: the platform marinas run on, and the app sailors open before, during and after every trip. Built AI-native from the first commit.
We need one person to lead that build. You will not pick tickets off a queue. You will shape the new platform, make the product and technical calls, and ship it. If you have been waiting for a role where you own the whole thing, this is it.
Where we are
Harba is used by more than 160 marinas in 9 countries, from small Danish clubs to municipal harbours and a port in the US. That gives us real customers on day one, ten years of knowing how a marina actually works, and a market to win.
We are backed by Bifrost, one of Europe's leading venture studios. You will build the new platform in close collaboration with Bifrost's CTO, who gives you oversight and a sparring partner on architecture, while you own the build.
There is more ambition than people. What you own will be bigger than your title, and as the team grows around you, you will be the person with the most context in it.
What you will do
- Lead the build of the new Harba platform, end to end: the UI, the Postgres schema, the edge functions in between, the deploy, and what happens after it.
- Build the sailor side. Booking a berth, paying for power, getting into the harbour, finding the next stop: make it the app sailors actually want on their phone.
- Decide what gets built first. Turn a harbour master's complaint, a sailor's review or a support ticket into shipped product, and make the judgement calls in the middle yourself.
- Put AI to real work in the product, for harbour masters and for sailors. Less admin, better trips, not a chatbot in the corner.
- Build with coding agents as your normal working method, and take responsibility for what they produce.
- Plan the move from the current platform to the new one, so 160+ marinas switch without noticing anything except that it got better.
- Set the engineering standard: rules, skills and gates that make the codebase easy for the next person and the next agent.
- Talk to the people using it. Harbour masters and sailors will tell you exactly what is broken, usually in the middle of the season.
Our stack TypeScript and React, Postgres on Supabase, Next.js, deployed on Vercel, tracked in Linear.
Stripe for payments. LLMs doing real work in the product. You will have a big say in the rest, including how we build for mobile.
Coding agents are part of how we build. Claude Code and Codex are in the daily loop across the Bifrost companies, and you will set that up for Harba rather than just use it.
The current platform runs on an older stack. You do not need to know it, and we are not hiring for it. With agents, reading and moving off old code is a solvable problem. We are hiring for where the platform is going.
Two things we do gate on: strong TypeScript and React fundamentals, and having written and shipped real code yourself, not only prompted for it.
Who you are
We do not filter on years. We have hired people early in their career who ship more than people with twice their experience. The difference is always hunger.
- You are exceptional at agentic development. You can show us how you prompt, review and validate what comes back, and you have opinions on how to set up a repo so agents do good work in it.
- You have strong product sense. You can sit with a customer, work out what they actually need, and decide what not to build.
- You have shipped full-stack products and run them in production: migrations, auth, payments, deploys, and the 2am debugging.
- You have worked in a real engineering pipeline with standards: branches, review, CI, releases. You know what good looks like.
- You can read and reason about code you did not write. When an agent produces something plausible and wrong, you catch it.
- You drive yourself. You work well remote, you do not need to be told what is next, and when something is missing, a key, a decision, an account, you ask straight away.
- You want to lead something. You want more responsibility than you have been given so far. That is the vigente offer.
Bonus points
- Consumer apps people love, especially mobile: React Native, Expo or a strong PWA.
- Supabase in production, especially RLS and edge functions.
- Payments: Stripe Connect, payouts, reconciliation.
- Multi-tenant B2B SaaS, and migrating customers between platforms.
- LLM feature work: retrieval, evals, cost and latency, validating output you cannot fully trust.
- Security and GDPR: auth, tenant isolation, secrets.
- Hardware integrations: metering, access control, IoT.
- You have built your own agents, skills or tooling.
- You sail, or you have spent a summer in a harbour.
Your first months We are specific about this because most companies are not.
Week one: you know the product, you have talked to harbour masters and sailors, and you have a real change merged.
Month one: you have a plan for the new platform: what we build first, what we migrate, what we drop. You agree it with Bifrost's CTO.
Month three: the first part of the new platform is live with real marinas and real sailors.
Month six: you are the person everyone asks about Harba's product, and you are hiring the next engineer.
How we work
- Small team, fast decisions. You will be in the room where they get made.
- Linear tracks reality, updated as work happens.
- Feature branches, PR review, squash merge. main is protected and deploys on merge.
- Agents draft, humans approve, the system logs it.
- Remote and async by default, with regular time together in person.
How we hire Four stages, usually about three weeks.
1. A 30-minute call.
2. A technical conversation where you walk us through something you built and we read code together.
3. A case. A real problem from our world: a harbour master's request or a sailor's problem, and a slice of the product. How you would approach it, what you would build first, and what you would refuse to build. We discuss it together. It is not an exam.
4. A conversation with Bifrost's CTO and Harba's co-founder, references, and an offer.
Use Claude Code, Codex, Cursor, whatever you actually work with. We are not testing whether you can code without AI. We want to see how you scope a problem, how you review what the agent gives you, what you reject, and what you are willing to ship. Practicalities The role is remote, based in Spain. Our working language is English.
Compensation is competitive and includes equity.
You need an existing right to work in Spain. This is a requirement, and applications without it will not be considered.
How to apply
Send us a CV or a profile, and one paragraph on something you built and owned: what you decided, what you got wrong, and what you would do differently. If some of it was built with agents, say so and say what you changed.
We only consider applications sent through this posting.
We use AI tools to help review applications. They support the decision, they do not make it. A human reads every application.
📌 AI Product Engineer (España)
🏢 Bifrost Studios
📍 España