Skip to main content
Novel Technologies
Training

IT Training

Most training programmes are written once and taught until the market moves past them. Ours is taught by engineers who spend most of their week on client delivery, so the work corrects the curriculum. You learn a role-aligned stack, build in the toolchain a professional team uses, and have every assignment reviewed as a pull request.

Format
Live online, evenings & weekends
Duration
16–22 weeks by track
Cohort size
Capped at 18
Tracks
Six, each mapped to a role
What's included

What the programme covers

  • Role-aligned tracks

    Six tracks — Java full stack, .NET, QA automation, DevOps, data engineering and business analysis — each mapped to a specific job title rather than a general subject area.

  • Live instruction, not recordings

    Every session is taught live by a practising engineer. Recordings exist for revision, but the teaching itself is synchronous so questions get answered while they matter.

  • Code review from working engineers

    Assignments are reviewed the way a pull request is reviewed at work — with comments on structure, naming, tests and edge cases, not just a pass mark.

  • The real toolchain, not a sandbox

    Git with branches and pull requests, a CI pipeline that will fail your build, a ticket board, a review queue. Nothing is handed in as a zip file.

  • Instructors who are still shipping

    Every instructor spends roughly 40% of their time on live client delivery. It costs us teaching capacity and makes hiring harder, and it is why the curriculum changes when the work does.

  • Alumni office hours, permanently

    Weekly office hours and the alumni channel stay open after your cohort ends, at no further cost. Most questions asked there come from people already in work.

Process

How the programme runs

Written down so you can hold us to it.

  1. Assessment and track selection

    A 45-minute conversation and a short technical baseline. We recommend a track based on your background and target role — and tell you plainly if we think the timing is wrong for you.

  2. Foundations

    Four to six weeks establishing language fundamentals, version control, testing discipline and how professional teams actually work day to day.

  3. Core track

    Eight to twelve weeks of role-specific engineering, delivered as a sequence of building projects that accumulate into a portfolio.

  4. Capstone under review

    A three-week build against a written specification, reviewed at checkpoints by an engineer who does not teach your cohort — a deliberately unfamiliar reader.

  5. Capability review

    A written assessment against your track’s competency list once the capstone is marked: what you can do unsupervised, what you can do with review, and what you cannot do yet. We do not soften the last one.

Outcomes

What you leave with

  • A portfolio of four to six reviewed projects with source history you can walk an interviewer through
  • Working familiarity with the tools of a professional team — Git, CI, ticketing, code review, stand-ups
  • A written capability review against your track’s competency list, including where it says you are not ready
  • A development environment you configured yourself and can rebuild from scratch
  • The habit of working in small reviewed increments, which is what survives a change of stack
  • Alumni access to office hours and the community channel, permanently
Detail

Tracks and curriculum

Java Full Stack

  • Java 21
  • Spring Boot
  • JPA & Hibernate
  • React
  • REST & OpenAPI
  • JUnit
  • PostgreSQL

.NET Full Stack

  • C#
  • .NET 8
  • ASP.NET Core
  • Entity Framework
  • Blazor or React
  • xUnit
  • SQL Server

QA Automation

  • Selenium
  • Playwright
  • TestNG
  • API testing
  • CI pipelines
  • Performance basics

DevOps

  • Linux
  • Docker
  • Kubernetes
  • Terraform
  • GitHub Actions
  • AWS or Azure
  • Observability

Data Engineering

  • SQL
  • Python
  • Airflow
  • dbt
  • Spark
  • Snowflake or Databricks
  • Dimensional modelling

Business Analysis

  • Requirements elicitation
  • User stories
  • Process modelling
  • SQL for analysts
  • Agile ceremonies
  • Stakeholder reporting
Questions

What people ask about this service

Including the ones with answers you might not want.

Do I need a computer science degree?
No. Roughly half of each cohort comes from outside computing — accounting, healthcare, logistics, teaching and the military are all well represented. What the assessment looks for is comfort with structured problem-solving and the time to commit, not prior credentials.
How much time does it take each week?
Plan for 12 to 15 hours: two or three live sessions of two hours each, plus assignment work. Most participants keep a full-time job throughout, which is why sessions run evenings and weekends.
What does the programme deliberately not cover?
Three things, and better to hear them now. It does not include job placement, interview coaching or résumé work — we train, and do not run a placement service. It does not make you a senior engineer: sixteen to twenty-two weeks produces someone who can be trusted with supervised work on a real team, which is a smaller claim than the industry usually makes. And it does not reach specialisms outside your track, because covering those shallowly would cost the track its depth.
What does it cost?
Tuition varies by track. We publish the full figure before you enrol, offer interest-free instalments over the programme duration, and do not use income-share agreements. Tuition is the only money the programme takes: no deferred fee, no share of what you earn later, nothing contingent on where you work.
Can you sponsor a work visa?
Not for training participants. Enrolling confers no immigration status and we cannot sponsor anyone attending a programme. If your status restricts what you may do while studying, check before you enrol.

Still unresolved? Ask us directly.

Related
  • For individuals

    AI & GenAI Training

    Applied training in machine learning and generative AI engineering — building and evaluating real systems, not prompt tips.

    Service detail
  • For enterprises

    Workforce Solutions

    Vetted engineers, delivered as individual placements or complete teams — screened by engineers, not by keyword match.

    Service detail
Next step

Talk to an admissions advisor

A 30-minute call to review your background, recommend a track, and say plainly whether this is the right year for it.