Product Design Lead (Canada)

Proof · Canada · 130k – 160k · posted today ago

Listing supplied by Himalayas. 101 Careers did not originate this post and applications are handled by the employer.

About this role

This is a fully remote role based in Canada. Candidates may work from anywhere within Canada.

About Proof

We’re Proof, a high-growth company in the legal tech industry, founded in 2017. We’ve built a best-in-class platform trusted by thousands of law firms across the United States for Service of Process, the formal delivery of legal documents, and E-Filing. We connect law firms with process servers and enable electronic court filing, delivering over a million documents per year through a network of thousands of process servers. We’re working to make the legal system more efficient, transparent, and accessible than it’s traditionally been.

Design at Proof

We design for the whole service, not just the interface. We aren't a downstream team turning tickets into screens; we help the company understand complex problems, make ambiguity concrete, and decide what should become simpler before more gets built.

Design isn't an approval gate that every decision has to pass through. Depending on the work, we may lead the problem framing, partner with Product, Engineering, and Operations to explore a solution, or help a team improve work already underway. The goal is to bring the right level of design involvement while important decisions are still open.

The role

We’re looking for a Senior Product Designer to take on challenging product and service workflows, with a primary focus on the onboarding workflows that power legal document delivery.

Delivering documents in the real world comes with inevitable edge cases and complications. An action in the field ripples through our internal systems and what a law firm sees. For example, if a process server finds a recipient has moved, the law firm needs clarity, internal teams need to resolve the exception, and the delivery workflow changes. Designing here means understanding those connections and deciding whether the right intervention is software, a process shift, automation, or all three.

You’ll report directly to the Director of Design on a small, high-leverage team, partnering with Product, Engineering, and Operations leadership to frame ambiguous problems, explore tradeoffs, and shape direction before solutions are locked in.

You’ll have meaningful autonomy to frame problems, choose the right approach, and drive work forward, with close cross-functional partnership, not a prescribed playbook.

What you’ll do

Own complex workflows end-to-end: Aid in framing problems, navigate ripple effects across operations, servers, and customers, and drive through to delivery.
Prototype to learn: Build prototypes at the right fidelity to test assumptions, make ideas tangible, and help teams make clear decisions early.
Work with the hood open: Share unfinished work early, invite critique, and partner with Product, Engineering, and operations while problems are still malleable.
Design whole systems, not just screens: Create coherent workflows, interfaces, information architecture, and states across digital tools and operational processes.
Contribute to the practice: Create and improve interaction patterns and language within your work that help Operations specialists, process servers, and law firms move through the product without having to re-learn it. Share what you learn and work alongside other designers to strengthen craft and service thinking.

How we work

Part of the work here is strengthening how we build context, shifting toward an everyday habit, not a scheduled research phase. Rather than wait for complete briefs, we dig into the mechanics of the service by shadowing Operations specialists, listening to law-firm calls, talking with process servers, and asking questions until we have a solid understanding. From there, we move fluidly between sketching, prototyping, and writing clear recommendations to help teams make confident decisions while the problem is still open.

What you bring

Experience: Product design experience, or equivalent demonstrated expertise, including independently owning end-to-end design for complex product or service workflows.
End-to-end ownership: Proven track record leading ambiguous product or service work through shipped delivery, with clear reasoning and tradeoffs.
Rapid context-building: High domain curiosity and the ability to ramp up quickly on complex systems. You treat learning as a continuous habit, shadowing, listening to users, and digging into real workflows to develop a grounded point of view while the problem is still open.
Service & operational craft: Experience designing for internal operations, complex systems, or expert users where workflow efficiency and trust are paramount. You balance speed with clarity and accuracy, especially when mistakes have consequences beyond the interface.
Change in established environments: Experience introducing thoughtful change inside organizations with established workflows and deep tribal knowledge.
Prototyping: Comfort building prototypes at varying fidelities to explore ideas, communicate intent, and get early feedback from users and teammates.
Influence & partnership: A history of shaping product and technical direction across disciplines without relying on formal authority.
Craft & collaboration: Experience creating reusable design patterns, contributing thoughtful critique, and helping other designers improve their work.

Bonus points

You may also bring experience with:

Legal technology, logistics, marketplaces, or field-service products
Workflow automation or AI-assisted products, with sound judgment about where automation creates leverage and where human judgment, transparency, and restraint matter more

This may not be the right role if

You prefer to receive complete requirements or follow a prescribed process before beginning design.
You see design primarily as producing polished interfaces after the problem and direction have already been defined.
You prefer to stay within one part of the design practice and rely on handoffs rather than move across the work as the situation requires.