Welcome

Learning engineers apply the learning sciences and engineering methods to iteratively improve learning outcomes at scale.

This site is a practice-centered guide for people doing the work, people curious about the role, and people adjacent to it. It's organized around what you might actually need — not around a graph of citations.


What learning engineers do

They work at the intersection of learning science, instructional design, data analysis, and systems thinking. They diagnose why a course or training program isn't producing the outcomes it should, redesign the intervention with evidence in mind, instrument it to collect signal, and iterate. The work spans K–12 classrooms, higher-ed platforms, workplace training, and high-consequence domains like medicine and defense.

What learning engineering adds to instructional design is an emphasis on evidence of impact — and the willingness to treat learning interventions as systems that can be measured, debugged, and improved.

Who this site is for

  • Practitioners who already do this work and want a shared vocabulary, practice references, and a way to point colleagues to the field.
  • Students and new entrants deciding whether learning engineering is the right path — and where to study or start.
  • Adjacent professionals (instructional designers, ML engineers, learning scientists, HR/L&D leaders) who need to understand how this role overlaps with theirs.

About this site

Most entries come from a hand-curated workbook of IEEE ICICLE–adjacent resources, plus original practitioner posts in Field Notes. Items are tagged by format and by curatorial cluster (e.g. "ICICLE resources," "Bror Saxberg," "I/ITSEC"). Sources with incomplete provenance carry a visible source unknown badge — we'd rather show you a promising lead we haven't verified than quietly drop it. More on scope & method →