What you can do
Your competence, described precisely
A profile that records skills, tools, standards and disciplines — not a job title and a list of buzzwords.
The EveryEng Graph
A live model of what every engineer can do, what every engineering job requires, and what closes the gap between the two.
What is in the graph
These numbers come straight from the graph and refresh daily.
Distinct engineering competencies
Roles with defined skill requirements
Mapped to the skills they teach
From piping to power systems
Tracked against member progress
Links between everything above
How it works
People, roles and content are all described with the same engineering vocabulary — disciplines, skills, software tools and standards. That shared language is what makes them comparable, and it is the whole idea behind the graph.
What you can do
A profile that records skills, tools, standards and disciplines — not a job title and a list of buzzwords.
What the job needs
Jobs and certifications carry the same skill vocabulary as people, which is what makes the two comparable at all.
What closes the gap
Because people, roles and courses share one vocabulary, the gap between where you are and where you want to be is a query — not a guess.
A slice of the graph
Each circle is a skill, sized by how many engineers hold it. A line means the same people tend to hold both. Only skills held by enough engineers to stay anonymous are shown.
Where it comes from
Nobody fills in the graph by hand. It updates as members build profiles, creators publish, employers post roles and learners finish courses.
Signals in
Answers out
The platform
Being specific about AI
The graph itself is not a language model — it is structured data about engineering. AI is used in specific, bounded places, and a person confirms the result wherever it touches someone's profile or a published course.
Courses, jobs and profiles are embedded as vectors, so a search for “pipe stress” finds CAESAR II work even when the words differ.
Paste a CV and a model extracts the skills and experience it evidences, which you confirm before anything is saved.
Course authors get tag suggestions drawn from a fixed engineering vocabulary, plus written feedback on their draft copy. Every suggestion is accepted or dismissed by the author.
Creators can generate a cover image for a course, mentoring offering or seminar from a text description.
Our course catalogue is published as MCP tools, so assistants like Claude and ChatGPT can query it directly rather than scraping it.
Engineering judgement stays with engineers. AI does not decide who is hired, does not grade assessments, and does not award certificates.
The network behind it
Members building a profile
Published and open for enrolment
Practising engineers teaching
Where our members work
Build a profile, and the graph will tell you what you are close to — and what is missing.