Reliability engineer practice: plant reliability and SRE, without mixing them up

People find this site with “reliability engineer”, “maintenance reliability engineer”, and “site reliability engineer”. Those are not three names for one job. Novus Learn already publishes two occupation profiles, in two career families, and they disagree about almost everything except the word reliability.

Industrial reliability engineers analyse failure history, lead root-cause work, set maintenance strategy, and track whether an intervention actually reduced downtime. The occupation page lists mechanical, electrical, or industrial engineering as a common degree route, plus progression from maintenance technician or planner roles, and recognised maintenance-and-reliability certification taken alongside experience. Site reliability engineers keep production systems running: service level objectives, automation of repetitive operational work, incident response, post-incident reviews, and capacity planning. On-call rotations are normal. Aliases on that page include SRE, reliability engineer, and production engineer — which is exactly why a web search collides.

This post does not invent a third profile. It walks the routes that already ship: the two occupation pages, the suites they already cite, the skill lessons behind those constructs, and the August lesson work that put real checkpoints inside every skill page.

Open /careers/reliability-engineer and you get day-to-day duties, entry routes, work context, interest tags, and official source links — not a slogan. The aptitude constructs on that record are data interpretation, mechanical comprehension, inductive reasoning, critical thinking, and planning and scheduling. Related suites are reliability and maintenance engineering, and troubleshooting and fault finding.

Those suite slugs are real catalog entries, each with sixty original questions in four tiers and a study outline you can download as a genuine PDF, HTML, CSV, or plain text. The August export pass replaced the old “page of links” outline with the full lesson content for every skill the suite draws on: worked examples, pitfalls, practice tips, glossary, and sources. Formal suite answer keys stay on the server. Nothing in a downloadable key file is a scored aptitude key.

• Occupation family: engineering and technical design, not information technology.
• Suites already linked from the occupation: reliability-and-maintenance-engineering, troubleshooting-and-fault-finding.
• Skill lessons already behind the constructs: mechanical comprehension, data interpretation, inductive reasoning, critical thinking, planning and scheduling.

Open /careers/site-reliability-engineer and the family is information technology, data, and cybersecurity. Constructs: problem solving, technical reasoning, multitasking and monitoring, situational judgement, and critical thinking. Related suites: DevOps and platform operations, cloud operations, and technical troubleshooting.

If your search was about production software, this is the page to keep. The industrial reliability page will not become more relevant because Google lumped the titles. The Career Matcher ranks twenty families from a device-local questionnaire and will not emit a job title. Use it to see whether engineering or information technology is the stronger family, then read the occupation you actually meant.

The public changelog for 2026-08-08 records two related shipments. Twenty-seven of the thirty-five aptitude skill lessons were rewritten so each one teaches its own skill with six worked examples that belong to that skill alone — the division that recovers a price before a fifteen percent rise, the two-apart rule that folds a cube net, the turns ratio that steps 230 V down to 23 V — instead of sharing one generic passage with the skill name dropped in. Objectives, practice tips, and glossaries grew to match, and every related-topics link now points at a real page on this site.

The same day closed the last gap on in-lesson checkpoints. All thirty-five skill lessons now carry a checkpoint after the objectives and another after the worked examples. The thirteen workplace and job-role skills that previously had no open practice bank — including mechanical, electrical and technical reasoning, situational judgement, planning and scheduling, and monitoring — each gained a twenty-question bank in four themed sections. Answers are checked on your device. They are not added to your formal practice history: two questions inside a lesson are a check, not an attempt.

Typing, monitoring, and reaction time still say so at the top of their banks: a page of questions cannot measure a clock. Those banks practise what reading can improve, and they refuse to pretend otherwise. That is the same honesty rule as the rest of the catalog.

Pick the occupation that matches the work. Open one related suite and one skill lesson. Formal suite attempts are timed and scored on the server; keys never reach the browser. Open skill practice and the in-lesson checkpoints stay in this browser, with explanations shown when you check. Study guides download as a real PDF built from the same lesson text you see on the page.

None of this is a CMRP, a cloud certificate, or a professional reliability licence. None of it is validated psychometrics. The occupation pages cite O*NET, BLS, and Job Bank where those sources exist; where Novus Learn cannot cite a wage figure it does not invent one. Use the map, then verify anything that matters with people doing the work and with listings in your region.