Onoja Possible
Software Engineer · 7+ years professional experience
Story
I build software I actually want to stand behind: stuff that runs in production, handles edge cases honestly, and helps real people get something done.
I've been writing code since I was a kid. It started with messing with games and small apps. That kind of tinkering taught me to stay with a problem until it behaves, and to prefer shipping a fix over talking about the bug.
If my name is on a release, I want it to look like someone cared. UI matters. Architecture matters. Performance matters. So does not leaving a mess for whoever opens that file six months later.
I've started companies. Some worked out, some didn't. Either way you learn that feedback from real users beats polishing in a vacuum.
I'm fine with tight deadlines and half-baked specs. I work fine with designers, PMs, and other engineers. What I want at the end is something people open, use, and don't immediately bounce from.
Education
B.Eng. Computer Engineering
University of Ilorin · Nigeria
Graduated 2026
Skills
Mobile
Flutter · Dart · Android native basics · Kotlin · Offline-first & sync
Backend
Node.js · TypeScript · NestJS · Express · Supabase · Firebase
Frontend
React · Next.js · Tailwind CSS · TypeScript
AI
OpenAI · Anthropic · Claude · Google Gemini · DeepSeek
Architecture & data
REST API design · Postgres · Redis · Queue workers · WebSockets
DevOps
Docker · Linux · Nginx · CI/CD (GitHub Actions)
What I deliver
- •I ship real features on real timelines. I don't like shipping broken stuff just to say we shipped.
- •I can take a vague idea and get to a v1 you can actually click through and argue about.
- •I try to keep codebases organized so future me (or whoever inherits it) doesn't hate past me.
- •I'll tell you if I'm blocked. I over-communicate on status because silence is expensive.
Contact
More projects: /projects