Academyby Code2Deploy

Not sure where to start?

Ask first. The advice is free.

Fifteen tracks is a lot to choose between, and picking wrong costs you months. If you cannot decide — or you are not sure this is realistic for you at all — email us before you spend anything. We will read it properly and tell you where to start, including when the honest answer is a free resource or a different provider.

  • No cost, and no obligation to enrol afterwards.
  • A reply from an engineer, not a sales sequence.
  • We will say plainly if we think you are not ready yet, or if we are the wrong fit.
Email us for advice — no cost

Coming from outside IT entirely

Most people we teach did not start in technology. Drivers, accountants, teachers, retail and care workers, graduates whose degree went nowhere. It is a real route, and it is also longer than the adverts elsewhere suggest — so here is the honest shape of it rather than a promise about ninety days.

  1. Months 1–3
    Cloud & System AdministrationThe entry track. No prerequisites at all — you learn Linux, networking and servers from nothing.
  2. Months 4–6
    DevOps EngineeringPipelines, containers, Kubernetes and cloud. This is the track that maps onto the job titles being hired for.
  3. Months 7–8
    One certificationRHCSA or AWS Solutions Architect. The credential that makes you legible to an employer who does not know your university.
  4. Alongside, then after
    Interviews and the working cultureMock interviews, the real-world workflow guide, and job support once you are in the role. This is the part people underestimate and it decides more outcomes than the technical work does.

That is roughly eight months of consistent evening study, not a weekend course, and it works for people who keep going after the first hard month. If someone promises you the same outcome in six weeks, ask them what happens in week seven.

Support that continues once you're hired

Job support

Once you are in the role, you can bring the actual problem you are stuck on. Sessions are scheduled around your working day and cover your employer's stack, not a teaching example.

  • Help with live tasks you have been assigned
  • Available after the course ends, on a monthly basis
  • Confidential — we never ask for anything you cannot share

Mock interviews

Full technical and behavioural rounds run the way employers actually run them, with written feedback afterwards on what would have failed you and why.

  • Live troubleshooting and system design rounds
  • Behavioural and situational questions with structured feedback
  • CV and profile review against the roles you are targeting

Real-world workflow guide

The unwritten part of the job. How work moves through a real team — and how that differs between a startup, an enterprise and an offshore delivery team, because the same behaviour reads as initiative in one and as recklessness in another.

  • Tickets, sprints, estimation and standups as they actually run
  • Pull request etiquette, code review, and disagreeing well in writing
  • On-call, incident calls, escalation and blameless postmortems
  • Change management, approvals and documentation expectations
  • Working across time zones with a client team

For teams

Bring any track in-house, for your team only

Same curriculum, same working-engineer instructors, scheduled around your team's calendar. Ask for a private-batch quote.

Ask about a private batch