SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 90,000 - 110,000 / annual
CodeHS is a comprehensive K-12 computer science education platform used by millions of students and thousands of schools and districts. The company provides curriculum, professional development, and a full software platform with the mission to empower all students to meaningfully impact the future through coding literacy.
You will join a growing product team within engineering, reporting to Zach Galant (CTO & co-founder). The engineering organization consists of about fifteen engineers organized in small project teams that reform each cycle and ship constantly. The primary constraint on impact is not engineering capacity but conviction about what to build, why, and how to communicate it—this is where you come in.
In this role, you will own projects within a product area from problem understanding through launch and adoption. You'll make calls on scope, specs, and tradeoffs for your projects and work closely with engineers building them. Initially, larger strategic decisions (which problems to tackle, what not to build) will be made collaboratively with leadership, but more of these decisions will become yours as you demonstrate judgment.
Your day-to-day work involves: building working prototypes using AI coding agents (which engineers then take to production); writing detailed specs, product briefs, and decision documentation; talking directly with teachers, districts, and customers to understand real needs; and connecting engineering priorities with input from sales, customer success, support, and curriculum teams.
The role is in-person in CodeHS's River North Chicago office, five days per week. This is intentional—the company believes that onboarding, learning the product and customers, understanding how the engineering team works, and receiving mentorship all happen faster in person. CodeHS is hybrid overall with people in other offices and remote, but this specific role requires in-office presence.
You'll sit in on priority-setting conversations across teams to see how decisions get made and develop your own product judgment.
Requirements:
- At least one year of full-time work experience in any role (product management internship also counts)
- Comfortable around code and able to read pull requests and ask engineers good technical questions, though you don't need to be an engineer yourself
- Fluent with AI tools and adaptive to rapid change; you should be prototyping with coding agents, running research through them, and building yourself tools. You should also be able to describe a time an AI model was confidently wrong and you caught it
- High agency: you'll receive problems, not tasks, and should come back with a plan and perspective on whether the problem is the right one to solve
- Clear communicator who leads with the bottom line and makes it easy for others to respond
- Early in your career with real work behind you; you don't need prior PM experience
