Resume building, course delivery and placement are usually three separate products, and the joins between them are where learners fall through. Someone who finishes a course and never reaches an employer has had every system work exactly as designed and still got nothing out of it.
Edzer runs all three on one platform, with a back-office portal the team uses to manage everyone who enrols and the work they do. The learner record, the course progress and the placement activity are one record rather than three that have to be reconciled by hand.
The portal is the product
Learners are on the platform for a few hours a week. The operations team is in the portal all day — enrolling, chasing, matching, reporting. Edtech builds routinely spend their effort on the learner-facing surface and leave the staff on spreadsheets, which is how the operation stops scaling before the product does.
Placement is a workflow, not a page
A job board is a listing. Placement is a pipeline with states — applied, shortlisted, interviewed, offered — that someone has to move people through and report on. Modelling it as a workflow is what lets the platform answer the only question that matters to a learner, which is what happened to their application.
One learner record
The resume, the courses completed and the placement history describe the same person. Held together, the resume can be built from what the learner has actually done on the platform and the placement team can see it without asking.