A tech-scholarship selection committee is reading dozens — sometimes hundreds — of applications per cohort. The committee is staffed by people who actually teach in the programme, run the academy, or both. They are reading for specific signals, and the signals are not always what applicants think.
Here is what is actually being looked for and the patterns that close applications fast.
What committees are scoring
Most rubrics, formal or informal, weigh four things:
- Aptitude. Will this applicant be able to keep up with the cohort's pace?
- Commitment. Will this applicant actually finish, given the demands?
- Fit. Does this person have a real reason to be in this specific track?
- Need. Would the scholarship change the realistic prospects for this person?
The order varies. The weights differ across cohorts. But applications that fail typically fail on one or more of these dimensions, and applications that succeed usually score well on at least three.
The aptitude question
Most programmes test this with a timed multiple-choice test before the rest of the application proceeds. The test is not asking you to know how to code. It is asking whether your pattern-recognition and reasoning speed is in the band the cohort assumes.
How to do better:
- Treat it like a test. Sleep the night before. Sit in a quiet room. Have water nearby.
- Practise the format — logical reasoning, number patterns, verbal reasoning. Free practice tests for civil-service or aptitude-based job applications use the same patterns.
- If a question is taking more than 90 seconds, mark it and move on. Come back if there is time.
- Be honest. Cheating on these is usually transparent at the interview stage and resets your application status to zero.
The commitment question
Committees have seen many applicants who say they will commit and then don't. The signal they look for is not assertions; it is evidence of past commitment to comparable things. Things that read as commitment:
- You have finished hard things before — a degree under difficult circumstances, a long-term project, a sustained learning effort visible on GitHub or LinkedIn
- You can articulate the time you intend to allocate per week, and you have thought about how it fits the rest of your life
- You are not applying to five cohorts at once with the same generic application
The fit question
The most common application failure is "I want to learn tech." The committee already knows that. What they cannot tell from a generic statement is whether you have a reason to want the specific track you applied for.
Strong fit signals:
- "I work at a credit union and I want to build internal tools — backend track."
- "I have been doing data analysis in Excel for two years and want to move beyond it — data science track."
- "I have been building UI in Figma for clients and want to learn to ship them as real apps — design or web development track."
- "I lead a small youth tech group at my church and want to be able to teach AI properly — AI engineering track."
Weak fit signals:
- "I have heard tech pays well."
- "I love technology."
- "I want to learn the latest skills."
- "AI is the future."
These are not wrong, exactly. They are just not specific enough to distinguish you from the dozens of other applications saying the same thing.
The need question
Selection committees feel the weight of this one. Many applicants would benefit from the scholarship and the programme; the question is whether the scholarship moves the needle for you specifically.
How to handle this part well:
- Be specific and factual. "My family supports four other students; I work part-time; the standard fee is genuinely not feasible" lands better than abstract statements.
- Do not exaggerate. Committees can tell.
- Do not minimise. If your situation is genuinely tight, say so — the lower tiers exist for exactly this.
- Treat the interview as the place to discuss this in detail, not the written form.
The motivation submission
In the SmartHub flow this is a short video or essay submitted between the aptitude test and the interview. The committee reads each one carefully. What works:
- Lead with the specific. A first sentence that establishes who you are and what you actually want, not a wind-up about your love of innovation.
- Include one concrete story. "Last year I tried to automate a process at my workplace using Excel macros; I could only get so far before I realised I needed real programming" tells the committee more than five paragraphs of generalisations.
- Show evidence of effort. Link to a GitHub, a small portfolio, a Codecademy completion. Anything that demonstrates the desire is not abstract.
- Be specific about the use case. What will you build, for whom, after you finish?
A 300-word submission with one specific story beats a 1,000-word one full of general statements. Length is not a virtue.
What closes applications fast
- Obvious AI-generated copy. Committees see hundreds of these now and they are recognisable.
- Templated language reused from other scholarship sites.
- Application to a track you cannot explain why you picked.
- Aptitude test scores that contradict the rest of the application.
- Evidence of misrepresentation — exaggerated work history, claimed projects that do not exist, etc.
What helps if your application is borderline
- Referrals. SmartHub specifically rewards applicants who bring other serious candidates into the funnel.
- A clean, professional video submission rather than written.
- A small portfolio that already demonstrates the kind of work the track teaches.
- A specific, recent learning effort — completed Codecademy modules, a GitHub with a few real projects, an FCC certificate.
Related: how the SmartHub Tech Scholarship works step by step
