SupportHybrid
Support Engineer
Answer the hard tickets, reproduce the weird bugs, and be the reason a yard manager's Tuesday gets better.
Apply by email
Opens a pre-filled email. Applications go straight to a human at hiring@slipway.example.
What you'd actually do
- Own the support inbox with two teammates — around forty conversations a day over email and phone, mostly from friendly non-technical yard staff.
- Reproduce bugs properly and file reports engineers thank you for. You get a real staging environment and read access to the codebase.
- Write and update the help docs whenever the same question shows up twice.
- Spend Thursday afternoons with the product team, turning support patterns into roadmap arguments.
- Work from the Portland office two or three days a week — spring launch season is all hands on deck, winters are genuinely quiet.
What you won't be doing
- No ticket quotas and no CSAT leaderboard. We measure whether problems actually got solved.
- You won't be a human shield for engineering. Engineers take support rotations too and read tickets every week.
How we hire for this role
Intro call — 30 minutes
With our support lead. Your story, our setup, and what a normal Tuesday actually looks like in the inbox.
Paid ticket exercise — 2 hours, $150
Three real anonymized tickets. You write the replies on your own schedule; we talk through them together after.
Meet the team — 45 minutes
Casual call with the two people you'd share the inbox with. Ask them anything — including what's annoying.
Offer within a week
One reference, numbers in writing, a week to decide, and a proposed office-days schedule you can push back on.