Skip to main content
← Back to Jobs

Staff Product Designer

Instrumentlβ€’Canada, United Statesβ€’πŸŒ Remote
Full-time3-7
$200k - $230k
per year
πŸ‘οΈ 0 viewsβ€’πŸ“ 0 applicationsβ€’Posted 9/4/2026β€’Expires 11/3/2026
Tailor Resume for This JobCheck ATS Score

Get alerts for roles like this

More Staff Product Designer roles in Canada, United States β€” straight to your inbox. No account needed.

Applying to this role? Tailor your rΓ©sumΓ© to this job description in one click, then download it clean β€” no watermark, no subscription.

Job Description

Hello, we’re Instrumentl . πŸ‘‹ Nonprofits do some of the most important work in the world, and most of them are still managing grants in spreadsheets. We're fixing that. Instrumentl is a profitable, hypergrowth, YC-backed SaaS platform building the operating system for grant-funded organizations.

More than 5,500 nonprofits use Instrumentl to discover, track, and win grant funding, from local community organizations to the San Diego Zoo and the University of Alaska. Collectively they’ve moved over $1 billion through our platform. We're growing quickly, customers love us (check out our G2 reviews!)

, and we're hiring people who want to build something that matters. About the role: We are hiring a Staff Product Designer reporting to the Head of Design.

You'll own GrantOS, the foundational layer every other product area at Instrumentl sits on top of: Platform (the data layer, MCP, BI), Core (Tracker, Tasks, Reports, Integrations), and the enterprise surfaces that connect them.

This is the seat where you define how grant professionals experience Instrumentl as a system rather than a set of features, which means the data models, permissions, and interaction patterns you set get inherited by every designer and every pod after you.

Much of this area is still being invented, so you will be defining problems rather than receiving specs.

What you'll do: Platform & Systems Own end-to-end design for GrantOS across Platform, Core, and enterprise, from discovery through ship and iteration Define the data relationships, permission models, and integration surfaces that hold up across every workflow in the product Set the interaction patterns and design system foundations that every other product area inherits Design how work connects across pods, so a change in one area makes the next one smarter instead of harder Zero to One Drive definition in genuinely greenfield spaces where the right answer is not obvious yet Write your own brief, frame the problem, and set roadmap direction in p

Required Skills

end-to-end designdata relationshipspermission modelsintegration surfacesinteraction patternsdesign system foundationsgreenfield spacesroadmap direction

The best-paying roles in your field. Every week. Free.

Join 10,000+ professionals getting job alerts and salary insights in their inbox

We respect your privacy. Unsubscribe anytime with one click.