Page fetched: June 30, 2026. HTTP 200, 106,642 bytes. All findings reflect the live page at time of fetch.
Current state: The page opens with "Five brands. One platform. No compromise." under a fitness-domain eyebrow. A brief grid surfaces key metrics (600K+ members, 0→MVP in 90 days, 4.8-star rating). A dense UI montage follows, heavy with fitness interface screens. The single most transferable insight to Suno — that retention data drove a navigation architecture rebuilt around instructors as the primary object — lives in the final CTA section. Below the fold, below the montage, below where a scanning hiring manager will ever reach.
The architectural thinking, the speed signal, the platform-scale challenge — all present on the page. But the page sequences all of it behind fitness-consumer framing that registers as domain mismatch before any of those signals land. Three fixes change that outcome. Everything else is refinement.
The Suno posting screens for systems thinking, speed under ambiguity, data-informed decisions, and someone who can reason about content-creator ecosystems. The Suno buyer sees "Consumer Fitness" in the eyebrow, processes "not my world," and bounces.
1. Browser Title — Highest Leverage, Lowest Effort
Currently: Equinox+ · Teaser · Juno Chen
No meta description. No Open Graph tags. If this URL gets dropped into Slack or a recruiter's tracking sheet, the only text representing the work is a brand name and the word "Teaser." None of the signals Suno screens for exist in the current title.
Replace with: 5 Brands → 1 Platform in 90 Days · Juno Chen
Add a meta description:
Led product design unifying five fitness brands into one platform for 600K+ premium members, 0→MVP in 90 days. Retention data revealed instructor loyalty drove engagement — navigation architecture was rebuilt around that signal.
That runs about 210 characters. Standard search display truncates around 155, which means the second sentence (the architectural insight) gets cut in Google but survives in full when pasted into Slack or an ATS note. If you add OG tags, use only the first sentence as og:description: Led product design unifying five fitness brands into one platform for 600K+ premium members, 0→MVP in 90 days. That fits in one pass everywhere.
Do this first. Five minutes. The return on those five minutes outweighs anything else on this list.
2. First-Screen Impression — The Eyebrow Is Killing You
Currently: The eyebrow reads "Equinox · Consumer Fitness · iOS & Android · 2020." The H1 reads "Five brands. One platform. No compromise."
The H1 works. Five brands, one platform. Any platform-design leader recognizes that as a structural challenge worth reading about. The problem is the eyebrow, which stamps "Consumer Fitness" into the buyer's frame before the H1 can land as an architecture problem. At scan speed, the eyebrow wins.
Replace the eyebrow with: Equinox Holdings · Multi-Brand Platform · iOS & Android · 2020
Factually accurate. Reframes the signal from vertical (fitness) to structural (platform architecture). The buyer's next thought becomes "how did they solve that?" instead of "not my domain."
The hero intro paragraph also needs rewriting. It currently frames the design goal as matching "the exclusivity of the physical membership." That is brand language aimed at an Equinox stakeholder. Rewrite it to lead with the constraint:
"Equinox Holdings operates five distinct fitness brands — Equinox, SoulCycle, Pure Yoga, Precision Run, and HeadStrong — each with its own audience, visual identity, and content format. The brief: unify them into a single digital platform for 600K+ premium members without flattening what made each brand work. I led product design from zero to MVP in three months."
Same facts. The constraint is now the first thing the buyer reads. The speed signal closes the paragraph instead of getting absorbed into longer narrative.
3. Platform Architecture Signal — Right Content, Wrong Position
The multi-brand challenge is named in the H1 and the brief grid, then vanishes into a UI montage that reads as fitness screens, not architecture. A designer sees craft in those screens. A hiring manager sees a domain they aren't hiring for.
The three solution blocks at the bottom of the page are exactly the platform-architecture signals the Suno buyer needs:
- Navigation architecture: how five brands coexist in one nav model.
- Brand identity system: how a token architecture preserves brand DNA while sharing components.
- Modality design language: how live, VOD, and audio experiences share interaction patterns without collapsing into sameness.
Every one of those problems has a direct analog at Suno. Multiple creator surfaces. A design system scaling with rapid iteration. Content formats (song creation, studio tools, casual creation) requiring different interaction models within one product. The parallels are obvious, but only if the buyer reaches these blocks. Right now, they won't.
Move the three solution blocks above the montage. Give them a section header: "Three architecture decisions that shaped the platform"
The montage still works as craft evidence below. But the architecture narrative has to land first. The page currently asks the Suno buyer to scroll through dozens of fitness screens on faith that a structural insight is coming. At scan speed, that faith does not exist.
4. Speed and Constraint Framing — Don't Let the Grid Flatten It
"0 to 1 in 90 days" appears in the brief grid as one of six items, alongside company name, product, role, team size, and scale. The grid treats all six with equal visual weight. They do not carry equal weight for this buyer.
The Suno posting explicitly values "balancing speed, experimentation, and polish in a fast-moving environment." Ninety days from zero to MVP across five brands is proof of exactly the operating tempo they are hiring for. It should not sit at the same visual level as "iOS & Android."
The hero intro rewrite above handles the narrative fix. For the grid itself, pull the Outcome row out entirely and set it as a standalone line below the grid:
Outcome: 0 → MVP in 90 days. Five brands unified. 4.8★ App Store rating.
Keep the remaining five rows (Company, Product, Role, Team, Scale) in the grid. The outcome line, separated and given its own visual weight, reads as a result rather than a metadata field. A Suno hiring manager scanning the brief grid will register the five-row grid as context and the standalone outcome line as evidence.
5. Craft Signal — Show the Reasoning, Not Just the Screens
The UI montage demonstrates craft. The screens are polished, the density is high, the range of surface types shows versatility. A Suno buyer expects this level of craft from anyone they'd consider. The screens alone won't separate Juno from the stack.
The differentiator here is visible evidence of design judgment. Why this architecture. What the data actually showed. How the instructor-navigation model changed user behavior.
The instructor-retention insight currently buried in the final CTA section is the strongest craft signal on the page. Suno's posting asks for someone who uses "qualitative and quantitative insight to drive user-centered decisions." That insight is the answer.
It belongs between the hero intro and the solution blocks (which are moving up per Section 3). Add it as a standalone callout:
"Retention data showed that members who followed an instructor came back. Members who didn't churned. That finding drove the core architecture decision: instructor as the primary navigation object."
This gives the page a clear sequence the Suno buyer can follow in one scroll: constraint (hero intro) → data insight (callout) → architecture decisions (solution blocks) → craft evidence (montage). Each layer earns the next.
6. CTA — One Detail Error to Fix Now
"Request the full case study" is clear and functional. One problem: the final CTA section labels this as "Case Study 03" while the URL, hero, and side rail all identify it as CS-04.
Fix the numbering. A detail error in a portfolio piece about design quality is the kind of thing a hiring manager notices and files away. Anyone screening for "exceptional taste" will catch it faster than most.
Priority Stack
The holiday weekend starts Friday. If you have thirty minutes tonight, do these in order:
- Browser title + meta description + OG tags. Five minutes. Highest leverage per keystroke on the entire page.
- Eyebrow rewrite. "Multi-Brand Platform" instead of "Consumer Fitness." Two minutes.
- Hero intro rewrite + retention-data callout below it. Lead with the constraint, close with the speed signal, then land the data insight before anything else. Seven minutes.
- Move the three solution blocks above the montage. Gets the instructor-retention architecture, the brand token system, and the modality design language into the first half of the page. Ten minutes depending on your CSS.
- Pull the Outcome row out of the brief grid as a standalone line. Three minutes.
- Fix the CS-03/CS-04 numbering mismatch. One minute.
The page has the right content in the wrong order for this buyer. The architectural insight that instructor loyalty drove navigation is the single most transferable signal to a company building a creator-centric platform. Right now it is the last thing on the page. Make it one of the first.
- Suno's full role scope: The Head of Product Design posting spans Product Design, Design Engineering, and UX Research, which means outreach should frame leadership across all three disciplines rather than design alone — read the live posting for the exact team-building and research responsibilities.
- Trust essay as Suno opener: The panel discussion flagged that Suno outreach should lead with "Trust Is the New Interface" and Agentic Labs rather than Equinox+, reserving the multi-brand platform story for interview depth once the conversation turns to creator ecosystems.
- Private essay boundary risk: The private essay page still returns full HTML including TinyFish/pricing content before any client-side overlay runs, and the homepage still links to it — a vulnerability worth resolving before any outreach to a buyer who will inspect the site.
- Ramp's agentic signal parallel: Ramp's live Agentic CX posting defines a human-operator and AI-agent hybrid model that maps to the same instructor-as-navigation reasoning pattern — content-creator loyalty driving architecture decisions has a direct analog in human/agent division-of-work design.