Senior Software Engineer

About The Role

We're looking for someone to join us as a Senior Software Engineer, working across our marketplace businesses — italist, HEWI and DOZR. This is not a role where a product manager hands you a ticket and holds your hand to the finish line — there is no product manager. You'll talk directly to the people who need something built, figure out what actually needs to exist, then build it, test it, deploy it, and validate that it's working in production and moving the number it was supposed to move. You own the outcome, not the pull request.

This is a full-time, remote-first role — you can be located anywhere in the world.

Things You'll Work On

• End-to-End Feature Ownership: you'll take features from a conversation to production — scoping directly with stakeholders (GMs, marketers, operators), building, testing, shipping, and then checking your own work: is it live, is it working, did it have the intended effect?
• "Merged" isn't done. Done is validated and in customers' hands.
• Full-Stack Development: you'll build in JavaScript across the stack — React on the frontend, Node on the backend. The surfaces vary: customer-facing storefront features, internal admin tools, third-party integrations, data pipelines and automations that keep marketplaces running.
• Working Across Businesses: one week you might be shipping a personalization feature for a luxury fashion marketplace, the next building supplier tooling for heavy equipment rentals.
• AI-Native Engineering: you'll work with Claude Code or another AI copilot as your daily driver — not autocomplete, but genuine agentic workflows: parallelizing work, generating and reviewing code, writing tests, automating the repetitive parts.

Attitudes

• You're competitive and love to win.
• You're competitive and are always looking for an edge.
• You have a high bar (some would say "unrealistic") for yourself and those you work with.
• You do whatever it takes.
• You're willing to do what others won't to achieve what others can't.

Who this role is right for

• Product-minded engineers who want to own outcomes, not close tickets — you'd rather be judged on whether the feature worked than on story points
• Someone who's already made AI central to how they build — Claude Code, Cursor or similar is your daily driver, and it's made you faster and more ambitious, not sloppier
• Someone comfortable sitting with a non-technical stakeholder, turning a fuzzy ask into a scoped build, and pushing back when the ask isn't the real problem
• Generalists who are energized (not exhausted) by switching between businesses, codebases and domains

Who this role is not right for

• People who want a stable, predictable or repetitive role/set of tasks
• People looking for active mentorship (i.e. you'd rather have someone tell you exactly what to do vs. figure it out on your own)
• People who are excited about building and managing a team vs handing the details themselves
• People who find comfort in following a playbook
• People who don't want to be in the weeds, spending hours querying a database and slicing the data to find new insights and hypotheses to test
• People who prefer stability over speed or "strategy over execution"