Industries we serve
IT & Technology
Product engineering, enterprise IT and the digital layer now sitting on top of every industrial plant — the sector that hires the widest and screens the hardest.
What this sector screens for
Shipping something someone else has to maintain: version control used as a team would, testing, code review, and explaining a design decision out loud.
Roles we prepare for
- Software engineer
- Data engineer
- QA engineer
- DevOps engineer
- Technical analyst
Disciplines that place here
- Computer Science
- Electrical
- Allied Technical
At a glance
- 5
Entry roles
Titles this sector's track is written against.
- 3
Feeder disciplines
Degrees that place into this sector.
- 4
Track modules
Domain modules built for this sector alone.
- 5
Pipeline stages
Screen, Gap Identify, Develop, Certify, Place.
The hiring bar
What you are expected
to do unsupervised.
Not the job description. The four things a team quietly assumes a new graduate can already handle, and notices immediately when they cannot.
01
Open a change someone wants to review
Small, described, tested, on its own branch. A reviewer's willingness to pick up your work is a measurable thing, and it is measured.
02
Read a codebase you did not write
Find where a behaviour lives without a tour. Almost all professional work is comprehension before it is authorship, and no assignment ever asks for it.
03
Say why, out loud
Defend a design decision and name the trade-off you accepted. “It works” is not an answer to a question about why it is built that way.
04
Own something after it ships
Logs, an alert, and a way back. Graduates are rarely asked to build the rollback plan, and are always asked in the interview whether they would have one.
Syllabus versus shortlist
Two different
reading lists.
The degree is not wrong. It is answering a different question from the one you will be asked across the table.
- What the degree gives you: Code written once, for a mark.
- What the shortlist asks for: Code somebody else maintains for the next four years.
- What the degree gives you: An assignment with a known answer.
- What the shortlist asks for: A ticket with an ambiguous requirement and a stakeholder you have to go and ask.
- What the degree gives you: It works on your machine.
- What the shortlist asks for: It works in CI, in review, and in an environment you have never logged into.
- What the degree gives you: A language listed on a CV.
- What the shortlist asks for: A language you can be interrogated in for forty minutes without flinching.
The domain track
Written against
this sector only.
Four modules, specified by practising engineers in this sector and re-reviewed on a fixed cycle. Your gap report decides the order you meet them in.
01
Fundamentals where they pay off
Data structures and complexity applied to problems that resemble work — not competitive puzzles, and not a second theory course.
02
How a team actually ships
Branching, pull requests, review etiquette and continuous integration, practised against a shared repository rather than described.
03
Testing and quality
Unit and integration testing, what is worth testing, and reading a failure honestly instead of re-running it until it passes.
04
Systems and delivery
API contracts, schema design, deployment and observability — the shape of a system a maintainer inherits from you.
The language of the room
Words you are assumed
to already have.
An interviewer will not define these before using them. The track puts you inside the vocabulary rather than handing you a glossary to memorise.
Version control and delivery
- Branching strategy
- Pull request
- Code review
- CI/CD
- Rollback
- Semantic versioning
Quality
- Unit test
- Integration test
- Regression
- Linting
- Code coverage
- Bug triage
Systems
- API contract
- Schema design
- Indexing
- Caching
- Logging and alerting
- Containerisation
Where these roles sit
Same sector,
four different rooms.
The bar is the sector's, but what each kind of employer leans on hardest is not the same. Knowing which one you are sitting in front of is half the preparation.
Product engineering companies
Building and owning one product for years. Screens hardest on code quality, reasoning out loud and the ability to maintain what you wrote.
IT services and global capability centres
The widest entry-level intake in the country. Structured hiring, structured onboarding, and a technical bar that has risen sharply.
Industrial digital and OT-IT teams
The software layer over plants and assets, where an engineering degree plus real code is an unusually strong combination.
Startups and scale-ups
Small teams, wide ownership, no ramp. Hires for demonstrated shipping rather than for pedigree, and asks you to prove it in the room.
Sector questions
Asked before
anyone applies.
What the sector expects
Do I need a computer science degree?
No. Electrical, instrumentation and allied technical graduates place into software, data and QA roles regularly, and an engineering background is a genuine advantage in industrial software. The bar is demonstrated code, not the degree name.
How much does competitive programming matter?
It gets you through some screening rounds and none of the later ones. Beyond the first filter, the questions are about design, trade-offs and code somebody else has to live with.
Is a portfolio of projects enough?
Only if you can be questioned on it. A project you cannot critique reads as a tutorial you followed, which is why the mock interview spends its time on your own repository.
How the track runs
Do I write code that gets reviewed by a person?
Yes. Work is submitted as a change request against a shared repository and reviewed by a practising engineer, and the review comments are the assessment. Receiving that well is itself part of what is being taught.
Which language does the track use?
The one your target roles hire in, chosen at the Screen stage. The engineering practice — review, testing, delivery — transfers across all of them, and it is the half that graduates are actually missing.
I want data engineering rather than backend.
Flag it early. The data route keeps the version control, testing and delivery core and sequences into pipelines, schema design and warehouse modelling rather than into service architecture.
IT & Technology
Get the gap report
for this sector.
The Screen stage measures you against what this sector actually specifies, not against a generic benchmark.