Responsibilities

• Define the MVP scope: must-have vs. nice-to-have vs. not-now.
• Produce a prioritized feature list with rationale and tradeoffs.
• Provide a lightweight competitive/alternative analysis (what schools already use; where switching costs are high).
• Create a simple plan to validate the MVP quickly:
• Pilot design ideas (what success looks like in a classroom/district)
• Metrics to track (activation, weekly active usage by role, teacher retention, outcome proxies)

Qualifications

• 7+ years in US K–12 EdTech product (product management, product strategy, or equivalent)
• Demonstrated ability to define MVP scope and make tradeoffs (not just ideation)
• Strong understanding of how US K-12 actually works: Stakeholders: teachers, principals, curriculum, district IT, procurement
• Adoption realities and classroom workflows
• Ability to communicate clearly with founders/engineering and turn insight into actionable decisions
• Background across different segments (elementary vs secondary, core instruction vs supplemental)
• Experience with district deployments, pilots, or procurement/RFP processes is a plus

How we’ll work together

• Weekly working sessions (3-5 hours) + async review of feedback
• Fast iteration: propose → critique → decide
• You’ll have direct access to the founder/product owner and engineering lead