Boitsholo Ramokhua
SQUAD ROTATIONthe engine, a relentless box-to-box daily-driver.
Based on public GitHub activity only. Not a full picture of private work.
TRAITS
SIGNALS
- Rapid Fire
I'm a BSc Computing with Finance graduand from the University of Botswana. I've worked as a full-stack developer at InRent, building and maintaining two platforms — the main InRent platform and Bonno, a student housing management solution. I also completed an attachment at Mascom Wireless, gaining exposure to enterprise ERP and business systems. I currently work as a Service Assurance Engineer, where I apply my technical skills to monitor, maintain, and improve system reliability. I hold Cisco certifications in Network Defense and Cybersecurity, and I'm currently pursuing AWS Solutions Architect certification. I'm passionate about fintech, cloud infrastructure, and building systems that matter. In 2026, I won the Cavista Hackathon (Overall Winner & Theme A Winner) with GeneShield, an AI-powered hereditary cancer risk platform built in 24 hours. When I'm not coding, you'll find me exploring new tech, contributing to open-source projects, or preparing for my next hackathon.
Portfolio / bookingGITHUB METRICS
AI Summary
Boitsholo Ramokhua posts a 73 scout score with solid public GitHub activity and a frontend and product surface role fit.
- Sustained output is the strongest signal at 82, backed by 810 commits this year and 1,233 total public contributions.
- Shipping speed scores 77, with work spread across 72 active days and 4 languages led by JavaScript, HTML, CSS, and PLpgSQL.
- Technical range scores 73; 27 stars earned and 147 followers show modest reach, but all signals come from public GitHub only.
- Public output shows 0 owned repos, 0 pull requests, and 0 reviews, so collaboration and review habits are not visible here.
Based on public GitHub activity only, this profile fits frontend and product surface work where steady day-to-day delivery matters. The read is an industrious, consistent contributor with strong commit volume rather than visible repo ownership or review leadership. Hiring managers should confirm pairing, code review, and ownership expectations in interviews, since those patterns do not appear in public output.