How I led the engineering that took an organisation from an initial marketing website to a platform for students, applications, and community across Africa.
ASN started as a landing page for an organisation supporting African students, most of whom reach it on expensive, unreliable mobile data. I led the engineering that turned it into a platform they can rely on.
The initial setup worked when operations were small: a static website, spreadsheets, and manual coordination over chat groups. But as hundreds and eventually thousands of students applied for cohorts and learning tracks, manual operations broke down.
Today, the platform has a reach of 12,000+ and has taken routine admin work off the team.
Primary engineer across the platform, working alongside the strategy and community teams to turn requirements into production features and operational workflows.
I led the technical decisions, data architecture, and full-stack implementation, building systems designed to hold up under distributed usage and low-bandwidth mobile connections.
Many students access the platform over expensive, metered mobile data connections. Instead of querying deep, nested document hierarchies that consume bandwidth and slow down page loads, I flattened the database schema and consolidated status tracking into compact documents.
Admissions, resource gating, and student progress tracking were previously handled manually via spreadsheets. I built automated application pipelines with role-based access controls, allowing reviewers to evaluate candidates in real time and automatically onboard accepted students.
The organisation now runs its programmes, distributes opportunities, and engages its community on the platform instead of spreadsheets and chat groups.
Live at asnafrica.org.
Hiring an engineer, building a product, or dealing with a problem you haven't figured out yet — start with the problem.
Tell me what you're trying to make happen.