Lead, Product Designer

Lead Product Designer, CBS Sports App

Discipline:
Design. Team Model:
Embedded on a cross‑functional CBS Sports App squad.

You’ll be a lead designer on a cross‑functional squad shipping features across the CBS Sports App for iOS and Android. You’ll work directly with a PM and a handful of engineers on problems that show up in the product within weeks, not quarters.

Your day‑to‑day is wide. Some weeks you’ll be deep in audience behavior data, pulling analytics directly to understand how fans actually move through the product and where they get stuck. You’ll build user profiles, map out flows, and test concepts directly with fans—sometimes running your own surveys alongside our research team to make sure our strategy is crystal clear.

Other days you’ll prototype in an LLM or deep in code, building something interactive to see if an idea actually works ers you’ll prototype in Figma tightening states, specs, and details with your engineer. You move across all of it, not splitting research, prototyping, and production across different people.

• Fast & Fluid
  :
  We workshop ideas, rough up prototypes, and figure out the smartest way to ship. We’re leaning into a hybrid, builder‑led process focused on getting interactive, holdable features into the hands of fans as quickly as possible.
• No Handoffs
  :
  You don’t “deliver” designs; you shape the product alongside your team. We value builders with different strengths over specialists who stay in their lane.
• Craft is a Team Sport
  :
  We critique regularly, post work‑in‑progress, and expect opinions. Polish is something the whole squad holds.
• Your toolkit: AI + Figma.

• AI Native
  :
  We use LLMs to think through problems, stress‑test hierarchies, explore edge cases, and draft specs. AI‑assisted building is a natural, everyday part of how you design.
• Rapid Prototyping to Production
  :
  You’ll use tools like Cursor or Claude to concept, pull from code repos to iterate directly, and build “holdable” prototypes with real data feeds. When it makes sense, you’ll push changes directly into the product with an engineer reviewing.
• The Canvas for Art Direction
  :
  We view the design canvas (Figma, for now) as a two‑way street with code. Since our components are increasingly being built and managed directly in code, we don’t use the canvas as just a static library. Instead, it’s our free‑flowing space for exploration. It’s where we sweat the visual details, explore high‑polish ideas before bringing them back into the build, and set the specific visual rules that guide our AI tools.
• Systems Thinking at Scale
  :
  You bridge the gap between AI and the canvas perfectly. Rather than designing bespoke, one‑off screens, you use both toolsets to plan, structure, and generate scalable solutions that hold up across the entire product ecosystem.
• Internal Tools
  :
  You’ll use AI to spin up internal SaaS‑style tools that help the squad move faster. If a workflow can be automated or prototyped with a prompt, we expect you to do it.

• You own the result: accountable for outcomes, not just artifacts. You know exactly which metric your work is supposed to move before you start and still watch it after launch.
• Shipped mobile work: portfolio of consumer‑facing mobile apps where we can see interaction decisions, visual craft, and your willingness to push past the happy path.
• Self‑serve research: treat research as a velocity tool, not a gate. Read product analytics, understand the audience, and use what you learn to adjust direction when the data says something different.
• Slope over intercept: we care less about exactly where you trained and more about your rate of improvement. You have high agency, high urgency, and a builder…