About the Product Designer Role at Substack

Substack is building a subscription-based economic engine for culture, giving independent creators their own publishing platform instead of leaving the terms of culture to legacy media or ad-driven social platforms. This Product Designer role sits on the Design team (San Francisco HQ, though most of the team, including the Head of Design, is remote) and is explicitly framed as "Product Design with Engineering Characteristics." Substack wants a designer who can craft beautiful, usable, scalable interfaces across a huge surface area (web dashboards, iOS and Android apps, feeds, email layouts, even smart TVs) and who is genuinely eager to exploit LLMs for prototyping, production, pixel-fitting, and bug-fixing.

Just as important is temperament. Design at Substack is described as "somewhat wild," with very little fixed process, close collaboration with executives and other functions, and a high tolerance for ambiguity. They want rigorous, high-output designers who can toggle between independent exploration and service-design collaboration, and who understand that Substack's direct-subscription model changes what "good" product design even means (thousands of true fans, not millions of ad impressions). The role requires at least 3 years designing software, high Figma competence, and strongly prefers front-end skills (TypeScript, React, SwiftUI) and hands-on LLM workflows.

Quick Stats

* Typical process: 4 to 5 rounds (recruiter screen, hiring manager, portfolio presentation, design/technical exercise, culture and craft conversations), roughly 3 to 5 weeks

* Format: Video-first for early rounds; portfolio and exercise rounds over video, with possible onsite or extended remote sessions

* Core focus: Portfolio depth, systems thinking, LLM-augmented workflows, front-end fluency, comfort with ambiguity, breadth across product surfaces

* Difficulty: Hard, because you must show both strong end-to-end craft and real "engineering characteristics" (coding or LLM-driven prototyping) while proving you thrive with almost no fixed process

What Substack Looks For

* A portfolio demonstrating end-to-end design solutions in relevant areas, especially social networks, content networks, or content systems

* At least 3 years designing software and high competence with Figma

* Eagerness and ability to leverage LLMs for prototyping, production, and even bug-fixing (front-end skills in TypeScript, React, or SwiftUI are a strong plus)

* High tolerance for ambiguity plus comfort operating both independently and as a collaborative service designer

Round 1: Recruiter Screen (~30 minutes)

What to Expect

A recruiter or Design team member walks through your background, motivation, and logistics. Expect questions about why Substack's direct-subscription model appeals to you, your years of software design experience, your comfort with startup ambiguity, and whether you are SF Bay Area or NYC based or fully remote (remote is fine here). They will also confirm your portfolio link works and get a quick read on your interest in LLMs and front-end tooling.

Example Questions

* "Why Substack, and what draws you to a direct-subscription model over an ad-driven platform?"

* "Walk me through your design experience, especially any social, content network, or content-system work."

* "How comfortable are you working with very little fixed process and shifting priorities?"

* "How have you used LLMs or front-end tools in your design workflow so far?"

Tips

* Have a crisp 60-second story linking your experience to content or social products and to Substack's model.

* Be honest about your technical range; they explicitly welcome novices to development as long as you are eager to go deeper.

* Rehearse this quick pitch and the ambiguity questions with Nora's Standard Mode so your motivation and background sound natural, not scripted.

Round 2: Hiring Manager Interview (~45 to 60 minutes)

What to Expect

A conversation with the hiring manager (likely the Head of Design or a senior designer) focused on how you think and operate. Expect behavioral and situational questions probing your ability to rapidly build context in unfamiliar domains, identify high-leverage opportunities, weigh trade-offs across user groups, and switch between independent exploration and service-design collaboration. This is where fit for a "somewhat wild," high-output, low-process team is really assessed.

Example Questions

* "Tell me about a time you dropped into an unfamiliar product area and had to build context fast."

* "Describe a project where you identified a high-leverage opportunity and made it practicable through staging or go-to-market planning."

* "Give an example of balancing conflicting user groups or second-order effects in a product system."

* "When have you had to act as a service designer versus striking out independently, and how did you handle each?"

Tips

* Use STAR structure and emphasize outcomes, trade-offs, and how you handled ambiguity.

* Show you can think about Substack as a whole system (profiles, CRM, analytics, moderation, email, feeds), not just isolated screens.

* Drill these behavioral stories with Nora's Behavioral Mode so your examples land tightly and you can flex between the independent and collaborative modes they describe.

Round 3: Portfolio Presentation and Craft Deep-Dive (~60 minutes)

What to Expect

You present one or two projects to a panel of designers and cross-functional partners. They care less about polish than about evidence you can craft real design solutions in relevant product areas. Expect deep questioning on your decisions: how you framed the problem, iterated in Figma, made accessibility and scalability choices, and shipped across multiple surfaces (web, iOS, Android, email, and beyond). Be ready to discuss constraints and what you would do differently.

Example Questions

* "Walk us through a project end to end: the problem, your process, and the outcome."

* "How did you make this interface scalable and usable across different surfaces or platforms?"

* "What trade-offs did you make here, and what would you change with more time or fewer constraints?"

* "Where did LLMs or front-end tooling speed up your prototyping or production on this work?"

Tips

* Pick projects close to content networks, social systems, or complex dashboards and flows.

* Narrate your reasoning and trade-offs, not just the final visuals; they want rigor and systems thinking.

* Practice presenting and defending your work aloud with Nora's Standard Mode to tighten your narrative and handle probing follow-ups smoothly.

Round 4: Design and Technical Exercise (~60 to 90 minutes, plus prep)

What to Expect

Given this role's "engineering characteristics," expect a hands-on exercise: a design prompt in Figma, a rapid prototype, or a discussion of how you would build or code a front-end. Some candidates may be asked to show LLM-driven prototyping or lightweight front-end work (TypeScript, React, or SwiftUI). Substack is not testing mastery of a specific language; they are testing familiarity with software production processes and your drive to leverage LLMs quickly to make work faster and better.

Example Questions

* "Here is a product zone (for example a moderation system or analytics view). Sketch an approach and talk us through it."

* "How would you use LLMs to prototype, pixel-fit, or bug-fix this interface?"

* "Talk us through how you would take this design from Figma toward a shippable front-end."

* "Which front-end tools or frameworks have you used, and where do you want to go deeper?"

Tips

* Think out loud; they value how you reason through production and staging, not a perfect final artifact.

* If you code, show it; if you do not, show concrete ways you use LLMs to prototype or accelerate delivery.

* Run mock technical and prototyping walk-throughs in Nora's Technical Mode so you can explain your LLM and front-end workflow clearly under time pressure.

Round 5: Team Fit, Values, and Offer (~30 to 45 minutes)

What to Expect

A closing conversation, often with the Head of Design and possibly an executive, covering culture fit, how you would shape Design at Substack's processes, and your view on the creator economy and healthy creator-audience relationships. If it goes well, this flows into compensation. The cash salary range is stated as 150K to 215K per year (USD), plus equity for all full-time roles and benefits, with final offers varying by experience and expertise.

Example Questions

* "How would you help diversify the kinds of creators Substack supports?"

* "What does a healthy, long-lasting creator-audience relationship look like to you as a designer?"

* "How would you shape the culture and processes of a low-process, high-output design team?"

* "What are your compensation expectations for this role?"

Tips

* Connect your ideas to Substack's model: reduced scales, trust, and long-term investment in creators rather than ad-driven engagement.

* Research the full package (salary, equity, benefits) before you name a number, and anchor to your experience.

* Practice the money conversation with Nora's Salary Negotiation Mode so you can discuss the 150K to 215K range and equity confidently without underselling yourself.

Frequently Asked Questions (FAQ)

1) How many rounds are there?

Typically 4 to 5: a recruiter screen, a hiring manager interview, a portfolio presentation, a design or technical exercise, and a team fit plus offer conversation. Substack has very little fixed process, so the exact structure can vary; treat this as the realistic shape rather than a guaranteed sequence.

2) What topics are most common?

* Portfolio craft and end-to-end design decisions across web, mobile, email, and other surfaces

* Systems thinking, trade-offs, comfort with ambiguity, and LLM-augmented or front-end (TypeScript, React, SwiftUI) workflows

3) How long does the process take?

Usually about 3 to 5 weeks from recruiter screen to offer, depending on scheduling and how quickly the design and exercise rounds are arranged. As an evolving startup, timelines can shift.

4) How should I prepare?

* Curate a portfolio showing relevant social, content network, or content-system work with clear reasoning and trade-offs.

* Sharpen your "engineering characteristics" story: how you use LLMs to prototype, pixel-fit, and ship, plus any front-end coding.

* Prepare behavioral stories about thriving in ambiguity and switching between independent and service-design modes.

* Use Nora AI to rehearse: Standard Mode for the recruiter screen and portfolio narrative, Behavioral Mode for the hiring manager stories, Technical Mode for the design and LLM exercise, and Salary Negotiation Mode for the 150K to 215K plus equity offer talk.