Hiring in EdTech

• Product & engineering

  EdTech PMs · Full-stack engineers · Mobile engineers · Learning-platform architects

• Learning & content

  Instructional designers · Learning scientists · Curriculum leads · Content producers

• B2B sales

  District sales reps · Higher-ed BD · Customer success managers · Renewal specialists

• Buyer vs learner

  Teachers, admins, procurement and learners all matter. Rubrics capture which stakeholder the candidate actually served.

• Content pedagogy

  Instructional design, learning science and content ops are distinct disciplines — scored explicitly.

• Compliance and safeguarding

  COPPA, FERPA, SEND and GDPR-child-data belong in engineering rubrics — surfaced from the CV.

• B2B sales cycles

  District and university procurement is long. Sales rubrics capture named accounts, RFP wins and pilot-to-district evidence.

Every candidate is scored against the role's rubric, and every score points back to a specific line in the CV. For edtech, these are the signals that carry weight:

• Audience-specific rubric
• Pedagogy portfolio surfaced
• District/university procurement evidence

1. A ranked set of candidates, each with a score and the evidence behind it.
2. Eligibility checks resolved before the candidate reaches you — right to work, credentials, location model.
3. Salary expectation against your band, stated plainly, before you invest interview time.
4. One decision per candidate: advance, hold or decline, reversible for a short window.

Candidates stay invisible to you until we've reviewed them for your specific role, and contact details are released as a separate step.