LEECOI
Register interest Sign in

Career support

The part after the building

Four areas of support, described by what happens in them rather than by what they promise. Everything on this page is something we actually do; the section on what we do not promise is near the top rather than in the footnotes.

What we do not promise

This is at the top of the page on purpose. It is the part you are most likely to be misled about elsewhere, and burying it below four sections of what we do offer would be its own kind of dishonesty.

  • No placement percentage

    We do not publish one. Any number we quoted would be unverifiable by you, and a figure you cannot check is not evidence, it is decoration.

  • No salary figure

    Same reason. Average packages depend on the market, the city, the role and the person, and quoting one implies a control over those things that nobody has.

  • No job guarantee

    Nobody can promise you a job, and an organisation that does is telling you something about itself. What we control is the portfolio and the preparation, and that is what is described below.

What actually happens

Four areas of support

None of this starts at the end. Portfolio review runs alongside the building, because a project reviewed six weeks after it was written is a project nobody remembers the decisions in.

01

Portfolio review

Every project is read the way a hiring engineer would read it, then sent back for another pass. Not marked. Reviewed, and returned with what to change.

  • Repository structure, README, and reproducible run steps
  • Baseline against final model, with the reasoning written down
  • Error analysis and honest limitations
  • Trade-off notes on accuracy, latency, cost and complexity

The last one is the one people skip, and it is the one an interviewer asks about.

02

Interview preparation

Structured practice on the questions these roles actually ask, with feedback on how the answer landed rather than only on whether it was correct.

  • Fundamentals, and reasoning under follow-up questions
  • Case-style problem framing from a vague business request
  • Code review and debugging exercises
  • Explaining technical decisions to non-technical interviewers

Practice is on your own code, not on trivia. Defending something you built is the interview.

03

Profile and LinkedIn support

Your profile is usually read before your code is. It gets the same review treatment as a repository.

  • Headline and About section rewritten around evidence, not adjectives
  • Project entries a recruiter can scan in seconds
  • Skills and keyword alignment with the roles being targeted
  • A posting approach that builds visibility without performing

04

Job search guidance

The search is a process with its own skills. It is treated as part of the programme rather than as something that starts once the programme ends.

  • Targeting roles that match the track and the evidence you have
  • Resume bullets built from real project outcomes
  • Application tracking and follow-up practice
  • Reading job descriptions for what is actually required

What it works on

None of this works without something to review

Portfolio review needs a portfolio. Interview practice needs code you wrote and decisions you made. The two published tracks set 20 project briefs between them, each with named deliverables, and those are what all four areas above operate on.

See every project brief

Ask about any of this on the call

Register interest and we will send the syllabus for the track you are considering, then arrange a short call. Career support is a reasonable thing to spend that call on.