GitHub Portfolio

Make your projects show how you think as an engineer.

Whether you're starting from scratch or already have projects, we'll look at what you want your GitHub to demonstrate.

Together, we can choose a suitable first project, review your existing repositories or identify where better structure, testing and documentation would strengthen your work.

You'll leave with clear priorities for what to build or improve, not simply suggestions for making your profile look better.

Your repository should make the engineering visible.

  1. 01

    Scope

    A strong project starts with a clear purpose. Explain the problem you're solving, what you chose to build and why.

  2. 02

    Structure

    Make it easy to understand how your software works. Clear organisation and design choices help others follow how the different parts of your system fit together.

  3. 03

    Quality

    Show how you've tested your software and considered reliability and future changes. Working code is important, but so is demonstrating how carefully it was built.

  4. 04

    Evidence

    Together, these details help someone reviewing your GitHub understand what you've built, how you approached the work and what you're capable of as an engineer.

That is the distinction between showing that you built something and providing evidence of how you approach engineering.

Look beyond the README.

Depending on the project and what you want it to demonstrate, a review can examine areas such as:

  • 01

    Project Scope

    Decide what to build to demonstrate your skills, or assess whether an existing project has a clear purpose and realistic scope.

  • 02

    Architecture & Structure

    Review how your software is organised and whether its design decisions are appropriate and easy to understand.

  • 03

    Testing & Reliability

    Examine how testing, automation and handling failures demonstrate the reliability of your software.

  • 04

    Code Quality

    Identify improvements to readability and maintainability that make your code easier to understand and develop further.

  • 05

    Documentation & Workflow

    Check whether your documentation, setup instructions and Git workflow make the project easy to explore.

  • 06

    Engineering Evidence

    Understand what your repository demonstrates about your technical abilities and where stronger evidence is needed.

Not every project needs every one of these elements. The point is to identify which choices genuinely strengthen the work and which would only add unnecessary complexity.

Know where to start and what to improve.

  1. 01

    Understand your starting point

    Examine what your GitHub already demonstrates, or identify what you need to build if you're starting from scratch.

  2. 02

    Identify what matters

    Work out which projects, engineering improvements or presentation changes would make your technical abilities clearer.

  3. 03

    Prioritise your next steps

    Decide what to build, refine or document next, with priorities grounded in your goals and current experience.

Choose the depth of support you need.

Engineering Consultation

In a focused 50-minute consultation, we'll work through one GitHub or portfolio challenge, whether you're deciding where to start or reviewing an existing project.

Book a consultation

Focus & Development Programme

If you need support beyond a single consultation, the Focus and Development Programmes offer a structured way to develop your projects and engineering skills over time.

Explore programmes

Whichever service you choose, you'll receive a personalised Action Brief capturing the key points of our discussion and practical next steps you can take forward.

Engineering review, not project implementation.

Your project remains yours to develop. Together, we'll assess the architecture behind it, identify where the work can be stronger and discuss practical improvements you can make yourself.

I won't implement missing features, take over project development or assessed work on your behalf. The focus is on the technical substance of your projects, not simply how your GitHub profile looks.

Engineering review from both professional and academic perspectives.

Software Engineering

As a practising Software Engineer, I work across software quality, test automation and the technical decisions involved in building and maintaining reliable systems.

Academic Perspective

As an Associate Lecturer in Computing, I supervise and assess final-year projects, examining how students design, develop, test and explain their technical work.

Together, these perspectives help me assess both the engineering quality of your projects and how clearly they demonstrate the decisions behind your work.