A job is not a list of tools or courses. On this site, it is described by its purpose, the responsibilities you will hold, the missions you will carry out and the skills they require, with their level. This lesson explains how to read a job page, and why the site starts from the position rather than from a curriculum.
What does a job page contain?
Each page, reached from the jobs list, reads from top to bottom, from the why to the how:
- the purpose: what the position guarantees, in one sentence;
- the responsibilities: what you answer for, each with its importance (core or useful) and its expected level;
- the missions: the concrete situations where these responsibilities are exercised, and what they produce;
- the skills: the gestures the missions require, grouped into readable blocks;
- the alignments: the match with public job frameworks, when it exists.
Here is the “What a platform engineer does” part of the job page: each responsibility unfolds into the missions that make it up, with their deliverable and their proof.
Why start from the job and not from a course?
A course gathers everything the site teaches on a subject; a position often needs only part of it, and crosses several. A site reliability engineer needs Linux, Kubernetes and observability, without following each of those courses in full. The site therefore computes the path from the skills the job requires, not from the courses that contain them.
What does the expected level mean?
Each responsibility carries a level, from guided implementation to steering. The level says what the position expects of you, not how hard a lesson is: the same skill can be expected at a different level from one job to another. A mission's level does not spread to every skill it uses; some remain foundations.
Tools are variants
A job does not depend on a tool. Where several tools serve the same gesture, the site offers a choice: GitHub Actions or GitLab CI, Argo CD or Flux CD, Scaleway or Outscale. Your choice changes the lessons offered and sometimes the prerequisites, never the expected skill.
Key takeaways
- A job is read through its purpose, its responsibilities and its missions, then its skills.
- The expected level applies to a responsibility, not to a lesson.
- Tools are options, not the definition of the position.
- A course serves a job, it does not define it.