EngineeringFully remote
Senior Product Engineer
Own features end to end in the codebase 400 boatyards use to run haul-outs, invoices, and winter storage.
Apply by email
Opens a pre-filled email. Applications go straight to a human at hiring@slipway.example.
What you'd actually do
- Ship one meaningful thing most weeks — a clearer schedule view, a billing fix, faster search — and watch real yards use it within days.
- Work the whole stack: Rails, Postgres, and a React front end, plus the occasional gnarly CSV import from a twenty-year-old yard system.
- Talk to customers directly. A few times a month you'll get on a call with a yard manager and see your feature running in their shed office.
- Review teammates' work kindly and get the same back — two engineers look at everything before it ships.
- Take a real on-call rotation: roughly one week in six, almost always quiet, paid extra when it isn't.
- Spend your first month shipping small fixes with a buddy, not sitting through onboarding decks.
What you won't be doing
- No sprint theater. We plan in six-week cycles with slack built in, and nobody rearranges your tickets overnight.
- You won't wait on a platform team. There are nine engineers; if the deploy pipeline annoys you, you're allowed to fix it.
- No growth-hack work. We don't build dark patterns, and marketing can't file engineering tickets.
How we hire for this role
Intro call — 30 minutes
With our head of engineering. What you've built, what you want next, and an honest picture of the codebase, warts included.
Technical conversation — 60 minutes
Walk us through something real you shipped. No live-coding gotchas, no whiteboard algorithms.
Paid work sample — half a day, $400
A small task from our actual backlog, done on your own schedule, followed by a call about the choices you made.
Offer within a week
We check two references, put numbers in writing, and give you a full week to decide. No exploding offers.