How do I prepare for this role?

Tayyari answers with a short, structured plan instead of an essay: the gaps between your graph and the role, the one move that closes most of them, a plan sized to the hours you have, and buttons for what to do next.

Start with your skill graph

Where you stand

The first block shows the role's gaps as bars, from where you are today to what the role expects. The numbers come straight from your skill graph and are drawn before any model has answered. The biggest gap is marked.

Each gap has a one-line reason behind a tap, with a chip that says where it comes from, for example "From your resume". What you are already strong at is a single quiet line. The header says how close the role is as "closest of your roles", never as a percentage.

The one move

Tayyari proposes the move that closes most of the gap. It lists what you already have that the move builds on, each item cited, and names the gaps the move works on. There can be up to three moves, best first, shown one at a time. A move names its gaps and nothing more: it does not predict how much it will help.

Your plan

The plan has phases. Each phase has a title, the hours it needs, two or three tasks and one deliverable. You choose how many hours a week you have, 3, 6 or 10, and code works out how many weeks that takes.

One phase is open at a time. Tasks are checkboxes that are saved with the plan, and you can add a link to what you shipped for a phase.

Next actions

The last block is buttons, not prompts:

  • Put the plan on your calendar, as a file made in your browser.
  • Pick the repository to start from, ranked in code from what Tayyari already read of your GitHub, with nothing fetched.
  • Rewrite your headline for this role. It is kept only if every name and number in it is in the evidence it cites.
  • Practise the interview for this role.

If you prefer to read, the same blocks are available as plain text.

How the plan stays honest

Code supplies every number: the levels, the gaps, the ranking and the hours. The model writes the reasons and the moves, and each one cites evidence from your graph before it may say anything. If a sentence contains a number that is not in the cited evidence or the gap figures, the sentence is dropped. Hours per phase are held between 1 and 40, and a plan has at most five phases of four tasks each.

If you already have a posting in mind, job match checks it requirement by requirement, and job search finds roles from employers' own boards that suit your graph.

Questions

Do I need a job posting?

No. The plan starts from a role in your skill graph. If you have a specific posting, use job match to check it requirement by requirement.

How are the weeks worked out?

By code, from the hours in each phase and the hours a week you choose: 3, 6 or 10. A model does not estimate them.

Is my progress saved?

Yes. The tasks you tick, the hours you chose and any link you add are saved with the plan.

Does the plan promise I will get the role?

No. It describes work to do. It does not predict whether you will get a role, and it never shows a predicted number for how much a move will help.

Can I still ask follow-up questions?

Yes. The plan is four blocks, and the chat stays available under it for anything you want to ask about the role or a gap.