Hims PM Portfolio Projects That Stand Out in Interviews 2026
TL;DR
The only portfolios that survive Hims’ final interview are those that combine a measurable impact story, a deep‑level product thinking framework, and a clear ownership narrative; flashy side‑projects or generic case studies are filtered out early. Build a two‑page deck that quantifies results (e.g., “+37 % MAU in 62 days”), frames the problem with the “Jobs‑to‑Be‑Done × Value‑Effort” matrix, and ends with a personal “I‑owned‑this‑end‑to‑end” clause. Anything less will be dismissed in the first 15‑minute debrief.
Who This Is For
You are a product manager with 2–4 years of experience at a mid‑size consumer tech firm, currently earning $138–$162 k base plus 0.07 % equity, and you have a portfolio of three to five projects. You’ve been invited to Hims’ “Design + Execution” interview loop (four rounds, each 45 minutes) and need concrete guidance on which projects to surface, how to frame them, and what the hiring team will actually be judging.
Which projects should I put in my Hims PM portfolio?
The verdict: Only projects that demonstrate a closed‑loop impact on a core Hims metric (user acquisition, retention, or lifetime value) belong. In a Q2 debrief, the senior PM on the team rejected a candidate who presented a “personal health tracker” because it never tied back to a business KPI; the hiring manager asked, “If we can’t measure the lift, why does it matter to Hims?”
Counter‑intuitive Insight #1 – The problem isn’t the idea but the ownership signal.* Candidates often think that a novel concept will win the interview. In reality, the interview panel is looking for proof that the candidate can own the entire product lifecycle—from hypothesis to post‑launch analysis. A project that ends at “launch” without a 30‑day KPI review is a non‑starter.
Framework in practice:
- Identify the Hims metric you moved (e.g., “New subscriber conversion”).
- State the baseline and the delta (e.g., “Base: 4.2 % → Post‑launch: 5.9 % in 45 days”).
- Show the experiment design (A/B test, cohort analysis, or funnel redesign).
- Explain the iteration loop (what you learned, what you changed, and the final outcome).
Script you can copy:
> “At my current role, I owned the redesign of the checkout flow for a subscription service. We started with a 4.2 % conversion baseline. By introducing a single‑page checkout and a progressive‑profiling form, we ran a two‑week A/B test that delivered a 1.7 % absolute lift (5.9 % conversion) and a $2.3 M incremental ARR within 45 days. I led the hypothesis, the design hand‑off, the data analysis, and the post‑launch monitoring.”
How detailed should the impact metrics be?
Answer: Every claim must be backed by a concrete number, a time horizon, and a source of data. In a recent hiring council, a candidate cited “significant user growth” without a figure; the panel asked for “the exact percentage and the measurement window.” The candidate stalled and the hire was rescinded.
Counter‑intuitive Insight #2 – Not more data, but the right data matters. You might think that dumping every KPI (CTR, bounce, NPS) strengthens the case, but the interviewers will flag “noise” and focus on the metric that aligns with Hims’ business model. Choose the single most relevant KPI and treat all others as supporting footnotes.
The “One‑Metric‑Rule” in action:
| Project | Hims‑aligned KPI | Baseline | Post‑launch | Timeframe | Source |
|---|---|---|---|---|---|
| Tele‑dermatology onboarding flow | Avg. time to first consult | 7.4 days | 4.9 days | 62 days | Mixpanel cohort |
| Subscription upsell email series | Revenue per user (RPU) | $12.30 | $14.78 | 30 days | Amplitude A/B |
| Mobile‑first landing page | New visitor conversion | 3.1 % | 4.6 % | 45 days | GA4 experiment |
When you present the table, narrate the why behind the chosen KPI: “Hims values speed to consult because it correlates with higher adherence, so I focused on reducing time‑to‑first‑consult.”
What storytelling structure convinces Hims interviewers?
Conclusion: Use the “Problem → Hypothesis → Execution → Learnings → Ownership” cadence, and embed a “Jobs‑to‑Be‑Done × Value‑Effort” matrix in the middle. In a March debrief, the hiring manager stopped the candidate mid‑story because the candidate skipped the “hypothesis” step; the manager said, “We need to know your mental model before we trust your execution.”
Counter‑intuitive Insight #3 – Not a linear narrative, but a loop narrative wins. The panel expects you to articulate how you would revisit the problem after launch, not just celebrate the win. The loop demonstrates that you treat products as evolving systems—exactly how Hims runs its “continuous‑care” model.
Script excerpt for the matrix:
> “I mapped the opportunity using the JTBD × Value‑Effort matrix. The core job—‘Get a prescription without waiting’—ranked high on value (9/10) but medium on effort (5/10) because of regulatory constraints. This guided us to prioritize a “pre‑screen questionnaire” that could be built in two sprints, delivering a 22 % reduction in friction without legal risk.”
Add the matrix as a one‑page visual in the deck; the interviewers will reference it in the next round’s design critique.
How many projects should I showcase and how should I order them?
Bottom line: Show exactly three projects, ordered by relevance to Hims’ current product pillars (Telehealth, Consumer Goods, Brand Loyalty). In a Q4 debrief, a candidate presented six projects; the panel spent 12 minutes debating relevance and never got to the candidate’s depth. The hiring manager summed it up: “More is less when you can’t keep the focus.”
Ordering rule:
- Flagship metric‑driven project (closest to Hims’ top‑line, e.g., “30 % increase in new subscriber sign‑ups”).
- Cross‑functional ownership project (shows you can align engineering, design, and compliance).
- Strategic thinking project (demonstrates you can define a new JTBD for a nascent market segment).
If you have a “side‑project” that is technically impressive but not metric‑aligned, tuck it into the appendix with a brief “personal experiment” note—never let it dominate the main deck.
What visual style and length does Hims expect for the portfolio deck?
Verdict: Two‑page PDF, 11‑point Helvetica, 70 % white space, one data chart per project, and a final “I owned X, Y, Z” bullet list. In a live interview, the senior PM asked a candidate to “zoom in on the chart” because the slide was cluttered with three tables; the candidate lost points for visual noise.
Counter‑intuitive Insight #4 – Not a “pretty” deck, but a “readable in 30 seconds” deck. Hims interviewers skim 30‑second thumbnails before the interview; if they can’t extract the core impact at a glance, the candidate’s story never gets a chance.
Visual checklist:
- Header: Project title, role, dates (MM/YY – MM/YY).
- Left column (30 % width): Problem statement (one sentence).
- Right column (70 % width): Impact chart (single bar or line) with baseline and post‑launch values labeled.
- Bottom bar: Ownership bullet (“Hypothesis → Execution → Analysis → Iteration”).
Keep the total file size under 1.2 MB; the ATS rejects larger PDFs during the upload stage.
Preparation Checklist
- - Draft three impact‑focused project narratives using the “Problem → Hypothesis → Execution → Learnings → Ownership” cadence.
- - Quantify each story with a single KPI, baseline, delta, and 30‑day window; verify numbers in the analytics dashboard.
- - Build a two‑page PDF deck following the visual style rule; limit to one chart per project.
- - Practice the 90‑second elevator pitch for each project; rehearse with a peer until the script feels like a natural story.
- - Work through a structured preparation system (the PM Interview Playbook covers the “JTBD × Value‑Effort” matrix with real debrief examples, so you can mirror the language the Hims panel uses).
- - Prepare a one‑page “ownership map” that lists every stakeholder you coordinated with (Design, Legal, Data Science) and the decision‑making authority you held.
- - Simulate a 45‑minute interview with a senior PM friend, focusing on answering follow‑up “why did you choose that metric?” questions without deviating from the core narrative.
Mistakes to Avoid
| BAD (What candidates do) | GOOD (What Hims wants) |
|---|---|
| Lists every KPI – “We improved CTR, reduced bounce, increased NPS, and grew revenue.” | Singles out the KPI that maps to Hims’ business goal – “Revenue per user rose from $12.30 to $14.78, a 20 % lift, directly supporting higher LTV.” |
| Shows a polished slide deck with dense text – “10‑slide deck, 3‑minute read per slide.” | Delivers a two‑page, high‑contrast PDF – “One chart, one sentence of context, and a clear ownership bullet per project.” |
| Ends story at launch – “We shipped the feature on week 4.” | Closes loop with post‑launch data – “After 30 days, the feature drove a 15 % retention bump; I led the A/B analysis and iteration plan.” |
FAQ
Q: Do I need to include side‑projects like open‑source contributions?
A: Not unless they can be tied to a Hims‑relevant KPI. The panel discards unrelated work in the first 10 minutes; focus your deck on three metric‑driven projects.
Q: How should I talk about failure or a project that didn’t meet its goal?
A: Not “I failed,” but “I identified a gap, iterated, and delivered a 12 % improvement after the second cycle.” Hims values learning loops; demonstrate the hypothesis‑adjust‑re‑test cadence.
Q: What compensation can I expect if I get the role?*
A: For a PM II at Hims in 2026, the typical package is $165–$182 k base, 0.08–0.12 % RSU refresh, and a sign‑on of $20–$35 k. Salary is calibrated to your measured impact, so a portfolio that shows a $2.3 M incremental ARR can push you toward the top of the range.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.