How to build an edtech portfolio as a teacher

Instructional design, learning experience, curriculum, content, assessment, design, and research roles commonly benefit from work samples. Implementation, customer success, professional learning, partnerships, sales, and product roles may not ask for a portfolio, but a concise case study or plan can strengthen a transition when direct title experience is limited. Do not force a visual portfolio onto a role that primarily evaluates commercial results or account ownership.

Review 15 target postings and note explicit portfolio requests, presentations, case exercises, writing samples, role-play, and preferred evidence. Build for that evaluation. A curriculum reviewer may want standards-aligned materials; an implementation interviewer may learn more from a risk register and launch plan than an e-learning module.

Each sample should prove a distinct high-value capability. One might show analysis and problem framing, another execution and craft, and another feedback and iteration. Avoid publishing six versions of the same lesson. Depth gives the reviewer better interview material and allows you to show what changed during the work.

Select work whose context you can explain confidently. You do not need paid experience for every sample. An independent project can demonstrate a new medium or workflow if the constraints are plausible and the label is honest. Volunteer work can add real stakeholders, but get permission first and do not ask an organization to absorb an oversized project for the sake of your portfolio.

Open with a two-sentence summary: who faced what problem and what you did. Then cover context, audience, goal, constraints, your role, research or evidence, options considered, decisions, artifact, feedback, revision, outcome, limitations, and next step. Use headings and visuals so a busy reviewer can skim before choosing where to read deeply.

Make your contribution explicit when the work was collaborative. Name what you created, facilitated, analyzed, or decided, and credit partners for their work. If outcomes were not measured, say what you would measure. Admitting a limitation is more credible than vaguely claiming that the project increased engagement.

Do not publish student names, images, records, accommodations, assessment data, colleague communication, private links, district strategy, vendor credentials, or materials you lack permission to redistribute. Blurring names in a screenshot can still leave identifying context. When in doubt, rebuild the structure with fictional data and original assets.

Explain the adaptation in the case study: the project was inspired by a real classroom need but recreated for public sharing. Use openly licensed or original media and record attribution where required. Remove metadata from files when it may reveal protected names or locations. Privacy discipline is itself evidence of professional judgment.

A hiring portfolio should never require a student, family, colleague, or employer to surrender privacy for your career transition.

A basic website, well-organized document, or slide deck can work. Use a stable public link, readable typography, descriptive headings, meaningful link text, alt text for informative images, captions or transcripts for media, and sufficient contrast. Test on a phone and in a private browser window. Do not require a login unless the employer has agreed to it.

Keep navigation shallow: short introduction, two or three case studies, resume or contact link, and optional about section. Place the most relevant sample first. Large video files, elaborate animation, and decorative mockups can slow the page without improving the evidence. The portfolio's design should support the work rather than become the work.

Ask someone familiar with the target role to review one case study for role relevance, problem clarity, evidence quality, decision logic, craft, accessibility, outcome honesty, and ease of navigation. Ask what they believe you owned and what interview questions the work creates. If they misunderstand your role or cannot find the decision, revise the explanation.

Do not rely only on friends who focus on encouragement or visual polish. The feedback you most need may be that a sample targets the wrong audience, covers too much, or fails to prove the responsibility you intended. Revise that sample before adding another project.

• Can the reviewer identify the problem and audience in 30 seconds?
• Does the artifact match the target role's real deliverables?
• Are decisions connected to evidence and constraints?
• Is feedback or iteration visible?
• Are outcomes and limitations stated honestly?
• Can the reviewer tell exactly what you owned?

On days one and two, choose the role, problem, audience, and evidence you need to demonstrate. On days three through five, gather information and write a brief. On days six through nine, create a small prototype or document. On days ten and eleven, test or review it with representative people. On days twelve through fourteen, revise and publish the case study.

The constraint is useful. A narrow, complete case study demonstrates more than an ambitious half-built course or app concept. After the first sample creates feedback, choose the second to fill a different evidence gap.