Amman, Jordan · 2025–2026
Cybersecurity & Digital Forensics Program
Open Role · LevelUp Economy

Teaching
Assistant

TAs are a critical execution layer in this program — not passive support. You maintain learner momentum, reinforce readiness standards, support live labs, and surface risk early so small issues do not become silent failure.
📍 Amman, Jordan 16-week program Primary coverage: Wks 3–12 Min. 3 · Preferred 4–5 Contract
3–5
TAs needed
Minimum 3 required. 4–5 preferred for full coverage across three hybrid cohorts.
10
Primary active weeks
Weeks 3–12. The core phase where track-specific skills are built and assessed daily.
100
Learners
75 in cybersecurity across two cohorts, 25 in digital forensics — all in hybrid format.
48h
Grading SLA
Drills and labs within 48 hours. Items requiring escalation or second-level review should be routed to the Support Instructor within 72 hours.
Responsibilities

What you'll do

Your work spans daily learner monitoring, grading, live lab support, debugging coaching, and curriculum review — across hybrid cohorts and across whichever track you are assigned to support.
Every day

Monitor & support

  • Check the student dashboard to identify learners of concern — never rely on what a student says they completed; always verify first
  • Group learners by issue type and run targeted support sessions proactively — do not wait to be asked
  • Brief sync after each session; log notes and escalate blockers to the Support Instructor the same day
Lab & assignment support

Keep everyone moving

  • Attend lab sessions, observe where learners struggle, and run targeted support after the Support Instructor completes the demo
  • Ensure every learner submits an attempt before end of each lab day — even an incomplete one; attempts must be on record
  • Prioritize learners who still need to complete assignments, always working with the highest-need students first
Grading

First-pass review

  • Conduct first-pass grading of labs, integration tasks, peer reviews, and reflection artifacts
  • Manually evaluate screenshot authenticity, commit message quality, PR description completeness, README documentation, and rubric alignment
  • Complete drills and labs within about 48 hours; route items needing second-level review or escalation to the Support Instructor within 72 hours
Tone standard: Direct. Precise. Professional. Not praise-heavy. Not vague. Example: "README is missing environment setup instructions. Please document venv creation and dependency installation steps."
Debugging & coaching

Build independence

  • Ask learners to show the failing line, output, or error — guide interpretation before suggesting the next step
  • Suggest the next diagnostic move rather than providing the answer outright
  • Do not write their solution or paste corrected code. The goal is building independence, not dependency
  • Process reflection exports and act on flagged learners within 24 hours — flags are predictive, so act early
  • Escalate integrity concerns to the Support Instructor before any learner outreach
Curriculum review

One week ahead, every week

Beginning each Sunday, review module materials scheduled for two weeks out. Feedback is due one full week before delivery begins.
Sunday

Open & begin

Open module materials scheduled for 2 weeks ahead. Begin testing instruction clarity, assignment flow including GitHub Classroom repos, and difficulty levels.

60–90 min/day GitHub Classroom
Mon–Thu

Continue reviewing

Continue testing and leaving feedback daily outside of onsite hours. If you find a blocking issue at any point, flag it to the Lead Instructor immediately — do not wait for the deadline.

Deadline

Due: one week out

Feedback is due no later than Sunday of the week prior to teaching — one full week before delivery begins. Do not leave it until the deadline.

Instruction clarity Assignment flow Difficulty levels
Scope limits

What you are NOT responsible for

The TA role has a clear boundary. These items sit with the Support Instructor or Lead Instructor — not with you.
Re-running automated checks manually unless explicitly assigned
Modifying curriculum content or assignment requirements
Making unilateral academic integrity judgments
Overriding rubric standards set by the Support Instructor or Lead Instructor
Weekly rhythm

What your week looks like

Core hours are Monday–Thursday in a hybrid format. Curriculum review runs Sunday through Thursday outside of onsite hours.
Day
Core focus
Key actions
Every day
Monitor & support
Check dashboard → group by issue → run targeted support → log notes in ClickUp
Sunday
Curriculum review begins
Open module materials (2 weeks ahead); begin testing and leaving feedback on clarity, flow, and difficulty
Monday
Applied Lab day
Attend session → publish Lab in TalentLMS → targeted support → ensure all attempts submitted before end of day
Tuesday
Lab completion + Stretch
Continue Lab support (highest-need first) → publish Stretch Assignment when eligible learners are ready
Wednesday
Integration Task day
Attend session → publish Integration Task → targeted support → ensure all attempts submitted before end of day
Thursday
Integration + Stretch + Sync prep
Continue Integration support → publish Stretch when eligible → prep Module Feedback for Lead Instructor sync
Key priorities: Seek out learners rather than waiting for them to ask. Always prioritize struggling learners over advanced ones. Never let a learner remain stuck for more than one day.
Qualifications

What you bring

TAs do not need deep expertise across both tracks. Depth in one relevant area is acceptable. What matters most is proactivity, documentation discipline, sound technical judgment, and the ability to support learners in a fast-moving hybrid environment.
Required

Core qualifications

  • Hands-on technical experience in cybersecurity, digital forensics, or a closely related field
  • Familiarity with tools relevant to at least one program track — for example: Nmap, Metasploit, ELK/Wazuh, Sysmon, or Burp-style workflows for Cybersecurity; or Volatility, Autopsy, Plaso, Timesketch, ALEAPP, or ILEAPP for Digital Forensics
  • Ability to enforce professional habits: clean repo structure, meaningful commit messages, proper branching, clear README files, and reproducibility standards
  • Strong communication skills and comfort working in hybrid environments
  • Organized and proactive — you seek out struggling learners rather than waiting to be flagged
What excellence looks like: Struggling learners are identified and supported same-day. Curriculum issues are caught before delivery. Feedback is submitted on time. The cohort moves forward together.
Preferred

Nice to have

  • Familiarity with the Security+ / CySA+ cert pathway
  • MITRE ATT&CK framework knowledge
  • Experience with TalentLMS or similar LMS platforms
  • Arabic language skills for optional learner support sessions
Security+ CySA+ MITRE ATT&CK TalentLMS