Edufy
A web platform for Edufy, Neslo Tech's training-and-placement subsidiary that turns junior developers into job-ready hires — the warmer, more energetic sibling to the Neslo brand system.
Head of Design at Neslo, leading UX/UI and web design for Edufy as part of the same team that built the parent Neslo brand and site.
Approach
Discovery sessions with the Neslo Tech team surfaced the real training gaps and hiring pain points on both sides of the marketplace before any screen got designed. The site was then built around two tracks rather than one: a practical, project-based learning path for developers trying to break in, and a direct hiring-pipeline pitch for the companies deciding whether to hire from it. Both were tested with real users, students, mentors and employers, to check the language and flow actually worked outside the room.
The problem
Traditional education leaves a gap between what junior developers learn and what companies actually need: graduates come out the other side long on theory and short on practical experience, while employers struggle to find candidates who can start contributing from day one. Edufy, Neslo Tech's training-and-placement subsidiary, set out to close that gap directly, connecting structured, practical training to the companies that would eventually hire from it.
The goal
A site that could do two jobs on the same brand: give a junior developer a legible path from 'no experience' to 'job-ready', and give a hiring company confidence that Edufy's pipeline was worth building a relationship around.
Key decisions
Two tracks, one pipeline: Internal Training-to-Consulting and the 'Resource' Model
Edufy runs two parallel routes into the industry. Internal Training-to-Consulting takes a learner through a 6-month intensive programme, then into a 2-year contract with Edufy's own consulting team, gaining real client experience before ever interviewing elsewhere. The 'Resource' Model lets a partner company sponsor a candidate directly, with training tailored to that company's stack and culture so the handover from training to team is close to seamless. Naming and explaining both tracks on the same page was the clearest way to show two very different audiences, junior developers and hiring managers, why the same programme works for both of them.
Made the numbered path the navigation, not just a metaphor
The whole pitch is organised as a six-step sequence, 01 Who We Are through 06 Join Us, echoed in the fanned-page hero treatment itself. It turns a fairly dense case (skills gap, training model, company pipeline, growth path) into something that reads as a straightforward journey rather than a wall of sections, and it doubles as the site's own navigation, so a visitor can always see how far through the pitch they are.
Style guide
Shares Neslo's near-black-on-off-white base, but brings the family's coral accent into the product itself rather than keeping it off-site the way Neslo does, carrying the step numbers, active states and calls to action in a warmer register suited to an audience still deciding whether a tech career is open to them.
A custom lowercase 'edufy' lockup with a looped stroke through the u, set in a rounded sans that holds up from hero scale down to the footer.
Where it landed
Live at edufy.neslotech.co.za.
What I learned
Writing for two audiences on one page is a sequencing problem more than a content problem. Once the numbered path gave each audience a reason to keep scrolling to 'their' section, companies past 'Who We Are', learners past 'For Companies', the page stopped trying to win every visitor with every sentence.
Building Edufy right after Neslo made the shared system's flexibility real rather than theoretical: turning the same structural DNA up in temperature for a completely different audience, without it reading as an unrelated site, was the actual test of the brand work.