Product Engineer
Own the product surfaces partners and brands actually live in — fast, clear, and AI-native.
Take the challenge
We hire this role by what you build, not by where you've worked. Skip the resume. Open the challenge, use any tools you want, and show us how you'd run the work.
About the role
Replenysh is the operating layer for circular supply chains — routing, recovering, verifying, and reconciling material flows across a 5,000+ partner network. All of that complexity has to become something a person can actually use. We are a small team of generalists who work across the full stack, care deeply about craft, and ship customer-facing software that makes a messy physical network feel legible and fast. We need a product engineer who can take an idea from a conversation with founders and design straight through to a shipped, polished feature — and who builds AI into the core of the product, not as a bolt-on.
Why this role matters
Partners and brands experience Replenysh entirely through the product. If the interface is slow, noisy, or unclear, the whole network feels untrustworthy no matter how good the systems underneath are. Great product engineering is where the complexity of thousands of live orders turns into a screen that tells you exactly what needs you and why. The surface is the product, and the product is the trust.
What you will own
- —Customer-facing features end to end — from a rough idea with founders and design to a shipped, polished release.
- —The surfaces partners use every day to see order state, custody, exceptions, and what needs attention now.
- —AI-powered functionality built into the core product — summaries, triage, assistive workflows that are reliable and fast.
- —A UI component system that stays beautiful and consistent as the product grows.
- —Application performance — the product should feel instant even with thousands of live orders.
- —Shaping problems, not just implementing tickets — you help decide what to build, then build it.
Who we are looking for
- —Strong product engineer with experience shipping customer-facing software at a company with a high engineering bar.
- —Real product sensibility — you care about UX, speed, and polish, and you push back when something does not feel right.
- —High ownership: self-directed, full-lifecycle builder who takes a feature from idea to shipped.
- —Comfortable working without heavy PM overhead. You clarify the real problem instead of waiting for a spec.
- —AI-native — you use Claude Code, or your tool of choice, to move faster, and you understand exactly what you ship.
- —Track record of driving complex, end-to-end features with visible impact, not just incremental refactors.
- —You sweat the details others skip: empty states, loading, error paths, the thing that happens at 2am.
How we will evaluate the challenge
- —Product judgment — did you build the surface that helps the partner most, and put the right things first?
- —Craft — UX, hierarchy, polish, empty and error states, and how fast it feels.
- —End-to-end ownership — did you shape the problem and carry it to something shippable?
- —The AI feature — is it genuinely useful, reliable, and well-integrated, not a gimmick?
- —How fluently you used AI tools to move fast while understanding what you shipped.
- —How clearly you communicate your decisions and tradeoffs.
The challenge
It is your first week. The order book lives across a spreadsheet, email, and a Slack channel, and partners cannot answer ‘what needs me right now?’ without ten minutes of digging. You have the raw order data and the full event log. Build the surface that fixes this.