Skip to content
rootwork.

Rootwork Engineering Fellowship

Build from first principles.

Rootwork is an engineering fellowship where you learn how software actually works, build real projects, receive thoughtful review, and develop the habits required to grow into an independent engineer.

Explore the Fellowship View how Rootwork works →
  • 24 weeks
  • Remote
  • Project-led
  • Code-reviewed
app.rootworkhq.com/home

Current phase · Week 3 of 24

Finding Your Roots

Skills

JavaScript ArraysDemonstrated
DebuggingPractising

Assignment

Loops + Arrays

19/ 20

Reviewed

GitHub

3 commits

PR reviewed

Correction

Handle empty input in the loop

Resolved

Illustrative example · progress measured through evidence

The Rootwork thesis

Learning to code is not the same as learning to engineer.

Tutorials can show you syntax. AI can generate code. Documentation can tell you what an API does.

Engineering begins when you can understand a problem, make decisions, build a solution, debug what breaks, explain your reasoning, and improve the work after review.

Rootwork is designed around that process.

  • 01

    Understand

    Learn concepts deeply enough to reason about them.

  • 02

    Build

    Turn concepts into working software.

  • 03

    Review

    Receive feedback on implementation and reasoning.

  • 04

    Improve

    Correct weaknesses and produce stronger evidence.

The method

  1. 01Understand
  2. 02Build
  3. 03Review
  4. 04Correct
  5. 05Demonstrate
  6. 06Grow

What makes Rootwork different

More than completing lessons.

Traditional learning

  1. Watch tutorial
  2. Complete quiz
  3. Receive certificate
  4. Move on

rootwork.

  1. Step 1: Learn the concept
  2. Step 2: Build something
  3. Step 3: Commit your work
  4. Step 4: Open a pull request
  5. Step 5: Explain your decisions
  6. Step 6: Receive review
  7. Step 7: Fix weaknesses
  8. Step 8: Demonstrate understanding

Progress is not measured by how much content you consumed. It is measured by what you can demonstrate.

The fellowship

24 weeks of becoming more independent.

Six phases, each ending in something you built and can explain. Every phase has its own output and its own evidence.

  1. Phase 01Weeks 1–4

    Finding Your Roots

    Programming fundamentals, JavaScript, Git, reasoning, debugging and problem decomposition.

    OutputConsole application

  2. Phase 02Weeks 5–8

    Building Your First Applications

    HTML, CSS, browser JavaScript, DOM, HTTP, APIs and deployment.

    OutputInteractive web application

  3. Phase 03Weeks 9–12

    Understanding Software Systems

    Node.js, APIs, SQL, persistence, authentication and application architecture.

    OutputPersistent backend application

  4. Phase 04Weeks 13–16

    Exploring Engineering

    Frontend, backend, mobile, automation, data and AI.

    OutputEngineering experiments

  5. Phase 05Weeks 17–20

    Working as Engineers

    Collaboration, reviews, testing, documentation, quality and delivery.

    OutputCollaborative software project

  6. Phase 06Weeks 21–24

    Rootwork Capstone

    Independent planning, implementation, testing, deployment and technical defence.

    OutputCapstone project + engineering retrospective

A week inside Rootwork

A rhythm designed around practice.

Rootwork is designed to fit alongside school, work and life while still requiring consistent engineering practice.

  1. Sunday

    Learn + Launch

    Live engineering session. Main weekly assignment released.

    Live session
  2. Monday

    Reinforce

    Small focused exercise.

    Exercise
  3. Tuesday

    Practise

    Apply another part of the week’s concept.

    Exercise
  4. Wednesday

    Explain

    Reasoning, debugging or implementation exercise.

    Exercise
  5. Thursday

    Ship

    Main assignment due. Pull request submitted.

    Due
  6. Friday

    Reset

    No required task.

    Flexible
  7. Saturday

    Prepare

    Review, catch up and prepare for the next cycle.

    Flexible
Live engineering session
Every Sunday
Main assignment
Released Sunday, due Thursday
Expected commitment
~10 hours a week

Engineering growth

Your growth should leave evidence.

Rootwork does not reduce a developer to one test score. Your profile develops from multiple forms of evidence across the fellowship.

Skill states

  1. Not started
  2. Introduced
  3. Practising
  4. Demonstrated
  5. Strong

States, not percentages. A skill moves forward only when there is evidence for it.

Nuri

Rootworker · Cohort 001

  • Programming LogicDemonstrated
  • Git WorkflowStrong
  • ArraysDemonstrated
  • DebuggingPractising
  • Technical ExplanationDemonstrated

Evidence

Assignments
12
Pull requests
9
Commits
34
Reviews resolved
6
Projects shipped
2

GitHub-native learning

Learn engineering where engineering happens.

Git is not a separate chapter in Rootwork. Branches, commits, pull requests and reviews become part of normal learning from the beginning.

Explore Rootwork on GitHub (opens in a new tab)

  1. assignment/decision-engine

    Branch created

  2. 5 commits

    Work in small, explained steps

  3. Pull Request #2

    Opened for review

  4. Mentor review

    2 corrections requested

  5. New commits

    Corrections addressed

  6. Corrections resolved

    Review approved

  7. Demonstrated

    Skill state updated

AI philosophy

Use AI. Keep the understanding.

Rootwork does not pretend AI does not exist.

Fellows can use AI for explanation, exploration and debugging. But anything submitted must remain understandable and defensible by the person submitting it.

AI can assist the engineer. It cannot become the engineer.

  1. 01Ask
  2. 02Understand
  3. 03Test
  4. 04Change
  5. 05Explain
Prompt → Copy → SubmitNot how Rootworkers work.

Showcase

Built by Rootworkers.

Projects appear here when Rootworkers choose to publish them, with the code, the reviews and the engineering notes behind them.

Coming as Cohort 001 progresses

  • Phase 01 · Console application

    • JavaScript
    • Node.js

  • Phase 02 · Web application

    • HTML
    • CSS
    • JavaScript

  • Phase 03 · Backend application

    • Node.js
    • PostgreSQL

Who Rootwork is for

Rootwork may be for you if…

  • You know some syntax but still struggle to build independently.
  • You have used AI to build projects but want to understand the code properly.
  • You are starting from scratch and want strong foundations.
  • You want feedback rather than just another tutorial.
  • You are willing to submit work consistently.
  • You are comfortable being corrected.
  • You want to become capable of explaining what you build.

Rootwork probably is not for you if…

  • You only want a certificate.
  • You want someone else to build your assignments.
  • You cannot commit consistently.
  • You want to skip fundamentals immediately.
  • You are unwilling to respond to code review.

Next cohort

Start with the roots.

Applications for future Rootwork cohorts will open periodically. Join the next cohort and build an engineering foundation you can actually use.

Join the next cohort list Explore the curriculum
  • Remote
  • 24 weeks
  • ~10 hrs/week
  • Built around real engineering work