# Product Thinking: Yash Ganar

HTML: https://yashganar.com/product
Markdown: https://yashganar.com/product.md

Product strategy and case studies from work planned, shipped, and still owned.

## Case studies

### SlopTeacher

Prove you wrote it, not the model.

Status: shipped MVP · v1.1.0 (live)

Paste a public GitHub repo. Get quizzed on ownership. Walk away with a pass, pending, or slop report.

- Website: https://slopteacher.com
- App: https://app.slopteacher.com
- Case study: https://yashganar.com/product/slop-teacher
- Case study Markdown: https://yashganar.com/product/slop-teacher.md

Case study map (HTML pages are public and crawlable):
- Overview: https://yashganar.com/product/slop-teacher
- Markdown mirror: https://yashganar.com/product/slop-teacher.md
- Executive summary (on overview): Developers often struggle to explain the reasoning behind code in repositories they've worked with, making interview preparation difficult. SlopTeacher explores a way to turn a developer's own GitHub repository into an interactive interview experience. This case study documents the problem discovery, solution design, product decisions, and initial implementation of that experience.

#### Product Discovery
- Problem Discovery: https://yashganar.com/product/slop-teacher/problem-discovery
  - Problem Statement: Producing a working codebase does not necessarily mean understanding how it works. SlopTeacher assesses understanding of a public GitHub repository and returns a repository-grounded diagnostic.
  - Why This Problem Matters: Code production and ownership differ, technical confidence needs evidence, interview prep lacks personal context, and knowledge gaps are hard to spot alone.
  - Assumptions: Hypotheses to validate about overestimated understanding, interview prep gaps, need for objective evidence, deeper comprehension, and actionable feedback. No formal validation yet.
- Research: https://yashganar.com/product/slop-teacher/research
  - Research Plan: Planned discovery research: objectives, questions, participants, analysis framework, assumptions A1-A8, success criteria, and limitations. Not yet completed.
  - Competitive Analysis: Landscape across four adjacent categories, seven competitor profiles, a directional feature matrix, competitive findings, and positioning hypotheses.
  - Market Research: Secondary signals from Stack Overflow, Octoverse, and HackerRank; segments and beachhead, JTBD hypotheses, sizing caveats, limitations, and claims to avoid.
  - User Personas: Early-career and interview-prep developers first, then independents, unfamiliar-repo contributors, mentors, and interviewers.
  - Jobs to be Done: Candidate JTBD statements for core assessment, interview prep, self-assessment, and sharing, plus critical questions to validate in interviews.
  - Key Insights: Ownership gap over code production; compete on structured assessment; interview-prep beachhead; badge unproven; primary research still needed.

#### Product Development
- Product Strategy: https://yashganar.com/product/slop-teacher/product-strategy
  - Product Vision: Enable developers to evaluate and demonstrate their understanding of a codebase through repository-specific assessments, emphasizing understanding over producing code.
  - Product Principles: Assess understanding not authorship; ground quizzes in the repo; make results actionable; be transparent about uncertainty; keep sharing optional; protect trust with clear boundaries.
  - Success Metrics: Measurement areas: activation, assessment quality, and continued value. Quantitative targets and internal performance data are not disclosed.
  - Product Requirements: Public GitHub ingest with compact snapshot, quiz length and difficulty options, text interview with pass / pending / slop, diagnostic report, optional badge, and auth.
  - Constraints: Public repos only, auth required, daily usage limits for sessions and model calls, and badges record a session result rather than authorship or competence.
  - Prioritization: MVP prioritized the core assessment journey; features outside that path were deferred to keep the product focused and operable.
  - MVP Definition: Shipped MVP v1.1.0: marketing site, authenticated assessments on public GitHub repositories, diagnostic report, and optional shareable badge and result page. The product is live.
- Solution: https://yashganar.com/product/slop-teacher/solution
  - Information Architecture: Site map across marketing pages, the signed-in app (home, active session, sidebar), and the public badge share surface.
  - User Flows: Landing through interview, then results with or without a badge depending on whether the full test was finished.
  - Design Decisions: Locked product choices: landing refresh, GitHub paste CTA, bento results, optional README badges, and shipping UI on the testing branch first.
  - Prototype: Instead of a Figma prototype, we used an Agentic AI approach and deployed into testing branches before production for faster development.
  - Final Product: The live SlopTeacher product is available at slopteacher.com.
- Reflections: https://yashganar.com/product/slop-teacher/reflections
  - SlopTeacher is live, but shipping it feels more like the beginning than the finish line.

#### Go-to-Market
- Status note: SlopTeacher is currently being deployed in live markets. Once event data is gathered, Go-to-Market results will be published here.
- Overview: https://yashganar.com/product/slop-teacher (Go-to-Market tab)

## Certifications

- Google UX Design · Coursera: user-centered process from research through wireframes, prototypes, and usability testing.