Your skills as a graph, each one cited

What a skill graph is

Tayyari reads your resume and any other sources you connect, then groups what it finds into four to seven domains: the main areas of work in your own career. Inside each domain are the skills. The domains come from what you have done, not from a fixed list, so a marketer's graph and an engineer's graph have different axes.

The graph is drawn as a radar. Select a domain to see its skills, and select a skill to see exactly what supports it.

What each skill carries

• A name and the domain it belongs to.
• A score from 0 to 100, Tayyari's reading of how strongly your sources show it.
• One or more evidence lines, each tagged with where it came from: your resume, your GitHub, an app you built, your portfolio or another link you connected.
• The roles the skill would strengthen, so you can see why it matters.

That last link between a skill and a role is what the next-roles view uses. It lays the role's requirements over your graph, so you see what you already show and what you do not.

Reading the chart

The axes stay in a fixed order and are never sorted by value, so the shape of your skills becomes familiar the more you look at it. When you flip to a role, you appear as the darker fill and the role as a lighter one, so it is easy to see where the role asks for more.

Every chart comes with a plain data table for screen readers, and the points on it can be reached and opened with the keyboard.

How the graph is kept honest

Before you see the graph, each claim is compared with the text it cites: names, numbers and identifiers have to appear there. A claim that the text does not support is dropped. The scores are a reading by Tayyari, and they are labelled that way. In interview practice, a skill Tayyari rates low is never asked about as if your resume had claimed it.

Tayyari does not score personality, culture fit or coachability. Those cannot be read from documents, so they are not part of the graph.

What you can do with it

• See the roles you are closest to, with what you have and what you lack for each.
• Check a job posting against the same evidence.
• Ask "How do I prepare for this role?" and get a plan built from the gaps.
• Turn it into a portfolio page you can share.
• Select any node and ask the chat to help you prepare for that topic, or to improve your GitHub.

The graph is most useful to people whose employer name does not do the talking for them: students, people changing field, anyone outside a famous company. It shows what you did, no more and no less, and you can point to the line that proves it.

Questions