Somkene Ojukwu

My path into software engineering didn't start with a computer. It started with a sketchbook and a pair of headphones. I spent years drawing and making music, learning how to take something that exists only in your head and shape it into something real that others can experience. That process of creation, of translating an idea into a finished thing, is exactly what pulled me into code.

When I wrote my first lines of JavaScript I immediately recognised the same feeling. The feedback loop of building something, breaking it, fixing it, and watching it finally work was deeply satisfying in the same way making a beat or finishing a drawing was. I became obsessed quickly. I started building small projects, then bigger ones, pushing myself to understand not just how things work but why they're built the way they are.

Over time I gravitated toward the full stack. I wanted to understand every layer of what I was building, from the interface a user touches to the database storing their data. That breadth lets me move fast, make better architectural decisions, and own features end to end without waiting on anyone. It's made me a much more complete engineer.

Today I specialise in building performant, accessible, and visually sharp web products. I care deeply about the details: transitions that feel right, interfaces that are intuitive without needing instructions, APIs that are predictable and fast. I believe the best engineering is invisible; users shouldn't think about the technology, they should just enjoy the experience.

I've worked with early-stage startups and growing products across Nigeria, the UK, and the US. Each environment taught me something different: shipping fast under pressure, writing code that scales, collaborating across time zones, and communicating technical decisions to non-technical stakeholders. I thrive in environments where the bar is high and the work actually matters.

Outside of work I'm into video creation, editing, and anime all things that have quietly shaped how I think about pacing, composition, and visual hierarchy in interfaces. That creative eye carries directly into the products I build and the decisions I make as an engineer.