AI Native Product Builder (K-12 Prototype Engineer) (United States)

About IMPACTER Pathway

IMPACTER Pathway is a Human Skills Analytics company building the measurement infrastructure schools have always needed and never had — the ability to see student growth in the human competencies that actually predict long-term success: purpose, grit, curiosity, perspective-taking, compassion. Our platform turns authentic student voice into rubric-aligned, decision-grade insight for districts, county offices, and state systems. We're one of the fastest-growing EdTech companies in the country, serving 200K+ monthly active students across 236+ school sites, with state, county, and district contracts coast to coast.

The role

You're design-minded and you know code. You live in Figma and you're just as comfortable in a terminal — you know your way around Git, the command line, and how software actually fits together, and you can take an idea from sketch to a working, clickable thing in an afternoon using Claude Code, Codex, and the modern AI building stack.

You'll build solutions that communicate and demonstrate our data, like these:

And statewide accountability systems that bring transparency to taxpayer-funded initiatives, like these:

You're not a career software engineer, and that's fine — you're the person who turns what if we could into something people can actually click. (We have a 20-person engineering team that owns and ships our production code. This isn't a seat on that team, and it isn't a heads-down back-end or infrastructure role.)

What you'll do

• Take real customer problems from districts, county offices, and school site teams, and turn them into working product in days, not months
• Design and ship beautifully crafted UX/UI surfaces using Claude Code, Codex, Figma, and the modern AI building stack
• Prototype new features, internal tools, customer-facing dashboards, and district reports — the stuff that lives between what if we could and here, try this
• Partner with our ML and engineering team on anything that touches production systems or our scoring pipeline — they own production, you build the thing that proves it's worth building
• Move fast, document well, ship constantly

Who you are

• You have a real technical foundation. CS coursework, a CS degree, or equivalent hands-on experience. You're comfortable with Git, the command line, and the basic mechanics of how software gets built and shipped.
• You can code, even if you're not a developer. You don't identify as a software engineer, and that's fine. But you can read, write, and debug real code, not just prompt your way around it. When an AI tool hands you something broken, you can figure out why.
• You're AI-native. You've shipped real things with Claude Code, Codex, Cursor, Lovable, Replit, or the equivalent, and you can show us a live link.
• You have strong design sensibility. You know Figma, you know what good product looks like, and you can build to that bar.
• You're a tinkerer. Curious, willing, restless. The kind of person who breaks things to learn them.
• You write well. We run on async writing.
• K-12, education, or classroom background is a plus — domain empathy helps — but it is not a requirement for this role.

Not for you if:

• You want a heads-down back-end or infrastructure engineering job (we have that team, this isn't that seat)
• You've only ever prompted — you've never actually touched Git, a terminal, or real code
• You want a VA / executive assistant / general operations role
• You can't show us a working thing you've shipped with AI building tools

Logistics

• Compensation: $30–$40/hr (commensurate with experience), with a contract-to-full-time conversion path
• Location: Remote (Pacific Time overlap). SoCal preferred for periodic in-person sprint days
• Must be authorized to work in the United States and physically based in the US. Due to FERPA, COPPA, and state-level student data privacy requirements, all work, devices, and data handling must occur within the United States. This role is not eligible for offshore contracting or remote work outside the US.

How to apply (required, in this order)

1. Your LinkedIn or resume
2. A live link to something you've built or shipped using Claude Code, Codex, Cursor, Lovable, or Replit. This is required, not optional. If you don't have one, this isn't the role for you yet.
3. A 90-second voice note: the three words people would use to describe you, and why you'd thrive in this role. (We'll send you a link for this separately.)

We screen on what you've built, not what you've claimed. That's the most important part of your application.