A secondary school student in Nigeria can start learning technology by choosing one area, creating a realistic weekly routine and completing small projects with the resources available. You do not need to understand the whole industry before beginning. You need a clear first direction, consistent practice and honest evidence of what you can do.
This guide explains how to move from general interest to a practical next step. It reflects the structure TalentMakers Foundation uses across TechSpark and the Scholars Programme: exposure first, focused practice next, then a completed piece of work and a pathway forward.
Start with a problem, not a job title
“Tech” is too broad to be a useful learning plan. It includes many kinds of work, and an impressive job title tells you very little about the daily tasks behind it. Begin by noticing the kinds of problems you enjoy.
If you like building things and seeing people use them, Software Engineering may be worth exploring. If you enjoy organising information, spotting patterns and explaining what numbers mean, Data & Analytics may fit. If you are curious about how systems fail and how people and organisations keep information safe, Cybersecurity may be a better starting point.
These are not permanent labels. Choosing one gives you enough focus to practise. You can change direction later with more information than you had at the beginning.
Ask yourself:
- What problem would I willingly spend time understanding?
- Do I prefer making, investigating, organising or explaining?
- Which school subjects or activities hold my attention?
- What can I practise using the device and connection available to me?
- Who can give me feedback on what I finish?
Write down the answers. A written choice is easier to test than a vague intention to learn technology someday.
Understand the three learning tracks
The TMF Scholars Programme offers three tracks because each one creates a different kind of foundation.
Software Engineering
Software Engineering is about building and maintaining digital tools. Early practice should help you understand how the web works, how instructions become behaviour and how to break a larger problem into manageable parts. The goal at the beginning is not a complex application. It is a small working result that you can explain.
Data & Analytics
Data & Analytics is about turning information into a useful account of what is happening. It involves careful organisation, questions, patterns and communication. A learner can begin with tables and spreadsheets before moving into more advanced tools. Accuracy and clear reasoning matter as much as the software used.
Cybersecurity
Cybersecurity is about protecting systems, accounts and information. It requires curiosity, discipline and an understanding that people and processes are part of security. Early learning can focus on digital safety, threat awareness and explaining sensible security practices clearly.
The Scholars Programme page describes how each track connects foundations to applied practice, workplace readiness and a next step.
Build a weekly routine you can keep
Consistency matters more than designing a perfect timetable. Choose hours you can repeat around school, family responsibilities, power availability and internet access. The Scholars Programme requires access to a device and internet for at least six hours a week. That is a useful reference point because it makes the practical commitment visible.
If six hours are available, divide them into smaller blocks. Use one block to learn a concept, one to practise without copying and one to improve or explain what you made. Keep brief notes after each session:
- What did I try?
- What worked?
- What failed or confused me?
- What will I do next?
These notes become evidence of progress when a project feels slow. They also make it easier to ask a teacher or mentor a specific question.
Do not measure commitment by how many tutorials you open. Measure it by how often you return, practise and finish.
Use the resources you actually have
Limited access is a real constraint, but it should be described precisely. A student using a shared device has a different planning problem from a student with a personal laptop. A learner with intermittent data needs to prepare offline tasks. Naming the constraint helps you design around it where possible and ask for the right support where it is not.
When device time is limited, plan before you log on. Plan the project offline first, then reserve connected time for tasks that genuinely require a device or the internet.
A school computer room, a shared family device or a supervised public facility may provide a starting point. Protect personal information and keep safe copies of your work.
If the limitation prevents meaningful participation, say so clearly when applying to a programme or speaking with a school. Good programme design should make access requirements visible rather than pretending they do not exist.
Finish one small project
A finished project changes the learning conversation. Instead of saying “I am interested in data”, you can show how you cleaned and organised a small dataset. Instead of saying “I want to build websites”, you can open a working page and explain the choices you made. Instead of saying “I like cybersecurity”, you can present a clear walkthrough of account protection for classmates.
Keep the first project small enough to complete. A useful project has:
- A specific audience or problem
- A clear beginning and end
- A result another person can inspect
- A short explanation of the decisions made
- A list of what you would improve next
Completion does not mean perfection. It means the current version works well enough to review. Once feedback arrives, you can improve it.
In the Scholars Programme, each participant completes capstone work. The capstone is a larger demonstration of the same habit: combine learning, make decisions and produce something that can be discussed as evidence.
Build workplace habits while you build technical skills
Technology work involves other people. Communication, collaboration, problem-solving and professional conduct are part of readiness, not extras to add after technical training.
You can practise these habits now. Arrive when you agreed to arrive. Tell a teammate early if a task is blocked. Keep file names and notes organised. Explain a decision without hiding behind jargon. Credit the people and materials that helped you. Protect information that is not yours to share.
These habits make your technical work easier to trust. They also prepare you to discuss a project in an application, interview or placement conversation.
Find structured exposure
Self-directed practice is useful, but it is easier to choose well when you can see the field through people doing the work. TechSpark creates several entry points.
The TechSpark Conference brings students, teachers and technology practitioners together for career exposure, practical sessions and direct conversation. TechSpark School Visits bring the pathway into classrooms. TechSpark for Teachers supports educators who can continue guiding students after an event or visit.
TMF's records currently show more than 3,750 students reached through conferences and school visits, 16 schools and institutions engaged and activity across five local government areas. These are reach figures, not promises about what happens to every participant. Their importance for a student is practical: there are established ways to encounter the programme and understand the next step.
Prepare for the Scholars Programme assessment
The Scholars Programme is for Nigerian students aged 15–24 who can attend regular cohort sessions and have access to a device and internet for at least six hours a week. No prior coding or technical experience is required.
Selection uses a structured assessment covering digital literacy, aptitude and workforce readiness. You do not need to pretend you know more than you do. Prepare by being able to explain:
- Why one track interests you
- What problem you would like to work on
- How you have handled a difficult learning task
- What weekly commitment you can realistically make
- What support or access constraints you need to state
The application is not a competition for the most technical vocabulary. It is the beginning of a process for understanding fit and commitment.
You can review current eligibility and submit your details on the application page.
Turn learning into a visible next step
As projects accumulate, organise them. Keep a short description of each problem, your role, the tools used, the difficult decision and what you learned. This becomes the beginning of a portfolio and makes interview preparation more concrete.
The Scholars Programme includes portfolio support, interview preparation and introductions to placement opportunities. An introduction is not a guarantee. The scholar still needs to demonstrate skill, communicate clearly and meet the opportunity's requirements.
Cohort 1 provides a grounded example. Ten scholars completed the programme, including capstone work, and four progressed into internship placements. Those figures describe verified outcomes for that cohort, not a promise that every future journey will look the same. Read more on the Scholar Stories page.
A simple 30-day starting plan
For the next month, keep the goal narrow.
Week 1: explore and choose
Learn what Software Engineering, Data & Analytics and Cybersecurity involve. Choose one track and write down why it interests you.
Week 2: learn one foundation
Choose one introductory concept in that track. Practise it in short sessions and keep notes on questions and mistakes.
Week 3: make something small
Use the concept to create a result another person can inspect. Keep the scope small enough to finish within the week.
Week 4: explain and improve
Show the work to a teacher, mentor or trusted peer. Ask specific questions, make one round of improvements and write a short explanation of what you learned.
At the end of 30 days, you will not have mastered a profession. You will have something more useful than a vague intention: a tested area of interest, a repeatable learning habit and one finished piece of work.
Frequently asked questions
Can I start learning technology without owning a laptop?
You can begin learning concepts, planning projects and using available shared or school devices, but meaningful technical practice requires dependable device access at some stage. State access limitations clearly when seeking programme support.
Which technology track should I choose first?
Choose the track whose everyday problems interest you most: building digital tools for Software Engineering, organising evidence for Data & Analytics, or protecting systems and information for Cybersecurity. Treat the first choice as a focused experiment, not a permanent identity.
Do I need prior coding experience to apply to TMF?
No. The Scholars Programme does not require prior coding experience. Selection uses a structured assessment covering digital literacy, aptitude and workforce readiness.
Does completing a technology programme guarantee an internship?
No credible programme should guarantee that outcome. TMF provides structured training, mentorship, capstone work and next-step support. Four Cohort 1 graduates progressed into internships, but each future opportunity has its own requirements.