Product Manager (7342)

Product Manager

Location: Remote, Canton/Cleveland, OH, working in the Central or Eastern time zone is highly preferred.

Salary: $105,000–125,000

Reports to: Director of Product

FLSA status: Exempt / Salary

Summary

DeliverThat is redefining what delivery looks like, and we're building the team to do it. Our platform handles delivery for everything from catering to groceries to alcohol with consistency, control, and scale. We combine people-first service, real-time technology, and hands-on partnership to make delivery a channel our clients and independent drivers can actually count on. If you're someone who takes ownership, moves fast, and wants to work somewhere your contributions visibly matter, we want to talk to you.

We're looking for a Product Manager to own the merchant side of our platform. Product and Engineering at DeliverThat are organized into lanes, each with one Product Manager, a tech lead, and a dedicated group of engineers. You'll own the Merchant lane: you'll be the product voice for restaurants, brands, and grocers, and you'll be accountable for what they experience.

What You'll Do

The Merchant lane's mission: every merchant can get an order delivered, routed to the right fulfillment, visible in their Dashboard, and can change how they work with us without an engineer.

Specifically:

• Own the merchant experience. The merchant Dashboard, order intake from every source, delivery management (which fulfillment route a delivery takes, overflow, lead times), self-delivery as a merchant feature, and merchant and customer messaging, including the tracking link.
• Carry the lane's numbers. Leadership sets the targets; you own the results on the merchant side: on-time and fulfillment rates, overflow and refunds by fulfillment method, and how much merchants can do without an engineer. You watch them, explain them, and move them.
• Set the roadmap. Propose a quarterly roadmap for the lane, grounded in merchant conversations, data, and company goals. Present and defend it with leadership, including the CEO. Then deliver it, and say early when it needs to change.
• Run the backlog. Intake, shaping, and priority order for the lane are yours. Write backlog items with clear Expected Outcomes and Acceptance Criteria that describe behavior, not implementation. Keep next-up work ready before the team needs it, partner with your tech lead to keep work moving, and confirm in production that what shipped did what it was supposed to.
• Understand the business. Talk to merchants and the DeliverThat teams that serve them. Use data (Metabase, PostHog, SQL) to measure outcomes after shipping, and test our own products regularly.
• Coordinate across teams. You'll work with Ops, Partnerships, Account Management, Accounting, and the other lanes so what we build works in the real world – comms, rollout sequencing, and operational readiness included.
• Improve what exists. Not every problem needs a new feature. Sometimes the right move is fixing a workflow, cleaning up an edge case, or making a tool less painful. You'll spend meaningful time on this kind of work, and it matters.

What We're Looking For

• 4–7 years of product experience in B2B, marketplace, or logistics software, including at least one stretch owning a product area end to end – the roadmap, the numbers, and the backlog. Restaurant technology, delivery, or gig-economy experience is a real plus; the customer here is restaurants, brands, and grocers.
• You've owned a roadmap and been held to outcomes. You've proposed what to build, defended it to leadership, shipped it, and measured whether it worked. We care less about which framework you used and more about whether things got out the door and moved a number. Agile, Kanban, whatever – continuous progress matters more than process orthodoxy.
• Comfortable getting hands-on. Small team, no analysts, no QA team. You'll write SQL queries, test features yourself, draft internal comms, and occasionally dig into error logs. If that sounds energizing, you'll fit in here.
• AI is part of how you work. We use AI tools every day for analysis, drafting, prototyping, and reading data, and Engineering is building an AI-first development process. You don't need to be an expert today, but you'll be expected to make these tools part of how you work from the start and to keep getting better at it.
• Strong communicator. You can bridge technical and non-technical audiences – engineers on edge cases, Ops on workflow changes – and you're comfortable representing merchants with the CEO and department heads: evidence first, and say no when the evidence says no.
• Solid product instincts. You understand user experience principles, can sketch wireframes or mockups when needed to communicate ideas, and know when "good enough" is the right call.
• Analytical and skeptical. You check your assumptions, look at the data before forming opinions, and aren't afraid to say "I don't know yet."
• Autonomous by default. You take ownership of your lane without needing to be managed closely, and you loop people in early and often because coordination is part of the job.