Technology, Computing and Digital Product· Intermediate level

Building means writing software: web, mobile, backend, embedded. Evidence is working projects you can explain.

Running means keeping systems working: IT support, networks, systems administration, cloud operations. Evidence is hands-on configuration, troubleshooting and often vendor certifications.

Securing means protecting systems: security analysis, incident response, governance. It usually comes after experience in building or running, so treat it as a destination rather than a starting point.

Analysing means data: analysis, reporting, dashboards, and later machine learning. Evidence is a project that answers a real question with real data, plus comfort with statistics.

Pick a main and a backup. Then write down what evidence that lane expects, because it differs: a portfolio for building, certifications and hands-on work for running, a documented analysis for data.

All three are real. They cost different amounts of time and money and open different doors.

In Ghana, computer science and related degrees run at institutions including KNUST, the University of Ghana, Ashesi University and Ghana Communication Technology University, and technical universities offer HND programmes in computing and networking. Confirm accreditation with the Ghana Tertiary Education Commission for any private provider before paying.

In Canada, university degrees in computer science, software engineering and information systems often include co-op work terms, which are the main route into a first job. College diplomas in programming, networking and IT support are shorter and lead directly to employment.

Certifications from established vendors and industry bodies, in areas such as networking, systems, cloud and security fundamentals, are recognised by employers, especially for the running lane. They cost money per examination and they expire, so plan the sequence rather than collecting them randomly.

Be careful with any provider promising a job. Ask what proportion of students finish, what the refund terms are, and who accredits it. If they will not answer, walk away.

The jump from tutorial projects to real work is having someone else use the thing.

Find a real user with a real problem: a family business that needs a price list people can find, a school club that needs a sign-up sheet, a market trader who counts stock on paper. Build the smallest thing that solves it.

Use version control from the first commit. Write a readme that explains what it does, how to run it, and what it does not do. Write down the decisions you made and why.

Then watch your user use it without helping them. Note every place they hesitate. Fix the top three.

Before you share anything: remove keys and passwords, remove real personal data, and check what you are allowed to publish if the project involves someone else's business.

Two or three well-documented projects beat thirty abandoned ones. Employers and admissions tutors open the first one and read the readme.

For each project, include what problem it solves, how to run it, what you would do next, and what you would do differently. Add a licence so people know what they may do with it.

Be honest about collaboration and about AI assistance. Say what you generated and what you wrote, and make sure you can explain every part when asked, because you will be asked.

Protect yourself. Do not publish your school, home address, phone number or timetable. Do not publish other people's data. Review your commit history for anything you pasted in and forgot, because it stays there even after you delete the file.

Ask a mentor for a code or project review, not a compliment. Ask them what they would refuse to merge and why. Ask what a junior in their team is expected to do unsupervised after three months.

Ask about the local market too: which lanes are actually hiring where you plan to work, and whether remote work is realistic from where you are.

Then plan the term: the project to finish, the certification or subject to work on, the programmes to compare, and the review date.