90–120 min
Build, break and explain a tiny API
Backend Engineering · Feel data modeling, validation, failure and debugging—not only the happy path.
Open experimentTry before you choose
Try the work before you fall for the title.
These are not courses or assessments. They are focused 60–120 minute experiences for noticing which problems you want to revisit.
Build Software
Build, test and improve products and the systems behind them.
75–100 min
Build an accessible orientation card
Frontend Engineering · Experience the gap between a screen that looks right and one that works well.
Open experiment90–120 min
Make a reading list survive a restart
Mobile App Development · Feel state, persistence and interruptions—not just drawing a screen.
Open experiment75–120 min
Find a risk, report it, protect the fix
Software QA & Testing · Experience the reasoning behind QA: choose risks, gather reproducible evidence and automate a useful regression check.
Open experimentWork With Data
Make data reliable, useful and available.
90–120 min
Repair a messy data pipeline
Data Engineering · Experience cleaning, contracts, repeatability and data-quality investigation.
Open experiment75–120 min
Challenge one metric before drawing the dashboard
Data Analytics & BI · Experience analysis as question, validation, metric definition and communication—not chart decoration.
Open experimentBuild Intelligence
Design and evaluate learning systems.
90–120 min
Train a tiny classifier—and challenge it
Machine Learning Engineering · Experience baselines, evaluation and error analysis instead of model theatre.
Open experiment90–120 min
Build an evaluated answer finder—not an AI demo
AI Engineering · Experience retrieval, evaluation and refusal boundaries before adding a generative model.
Open experimentProtect Systems
Understand threats and reduce real risk.
60–90 min
Investigate one authorized web-security flaw
Cybersecurity · Experience careful evidence, authorization and remediation—not random attacking.
Open experiment90–120 min
Triage one fictional login alert without crying wolf
Security Operations (SOC & Incident Response) · Experience SOC work as evidence, competing explanations and careful escalation—not staring at a dramatic dashboard.
Open experiment75–120 min
Threat-model and protect one tiny feature
Application Security · Experience application security as design, evidence, a fix and regression protection—not scanner output.
Open experiment90–150 min
Run one tiny authorized web-security assessment
Offensive Security & Penetration Testing · Experience penetration testing as scope, hypotheses, minimal proof, reporting and remediation—not a race to run the most tools.
Open experimentRun Systems
Make delivery and operations dependable.
90–120 min
Deploy, break and diagnose a small service
DevOps / SRE · Experience deployment, observability and calm diagnosis.
Open experiment60–90 min
Trace one request through your own lab
Network Engineering · Experience packet evidence and controlled failure diagnosis rather than command collecting.
Open experimentWork Close to Hardware
Design electronic systems and connect software to the physical world.
90–150 min
Read a sensor without blocking time
Embedded Systems · Experience physical feedback, timing constraints and datasheet-driven debugging.
Open experiment60–90 min
Design and verify a tiny logic circuit
Hardware Engineering · Feel hardware design as a specification, circuit and independent verification—not just wiring a demo.
Open experimentUnderstand Computing Deeply
Study the ideas and systems beneath tools.
2–3 days
Reproduce and question a small result
Systems, Algorithms & Research · Experience disciplined curiosity, baselines and honest reporting.
Open experimentTechnology + People
Connect technical work, decisions and teams.
90–120 min
Turn a confusing form into a usable flow
UX/UI Engineering · Experience the bridge between observing a problem, testing an idea and implementing an accessible interaction.
Open experiment75–100 min
Turn a vague request into a decision
Technical Product & Leadership · Experience listening, problem framing and transparent trade-offs.
Open experimentReflection rule
Finishing is not the success. Noticing something honest is.
Where did time move quickly? What drained you? Would you spend five more hours here? Nothing is saved; write the answer for yourself.