Software engineer × Developer relations

I build things. Then I figure out how to explain them.

6+ years building web, mobile, API and interactive experiences. I turn technical concepts into practical experiences, documentation and content developers can actually use.

01 / About

An engineer who keeps ending up between the people who build a product and the people who use it.

My work has moved across web development, mobile, APIs, interactive experiences and rich media. Alongside the building, I have spent a lot of time explaining: writing things down, running community events, answering questions, and turning what users say into something a team can act on.

I like building things I can explain, and explaining things I understand because I have built them. That is most of what I do.

  • EngineeringWeb, mobile, APIs, interactive experiences
  • ProductShaping what gets built and why it matters
  • CommunityEvents, education, feedback, conversation
  • CommunicationWriting, documentation, developer content

02 / How I work

Tap a principle to read it

Build

I learn by building.

Reading about a tool tells me what it claims. Building with it tells me what it costs. Most of what I know about deployment, APIs, animation and mobile came from shipping something small and then finding out where it broke.

  • Web
  • Mobile
  • APIs
  • Interactive experiences
  • Rich media

Explain

If I can't explain it, I probably don't understand it well enough.

Writing is where I find the gaps. A tutorial forces an order on the ideas, and the place where the order falls apart is usually the place I skipped. That is also what makes good documentation: someone who got stuck first, on purpose, so you don't have to.

  • Technical writing
  • Tutorials
  • Talks
  • Developer content

Listen

Developer experience starts with understanding the developer.

Running community events taught me that the question someone asks out loud is rarely the whole problem. You get the real one by staying in the conversation after the session ends. That habit changes how I read issues, support threads and feedback forms.

  • Community events
  • User education
  • Feedback gathering

Improve

Build, observe, learn, iterate.

Feedback is only useful if something changes because of it. The part I care about is the return trip: taking what developers actually struggled with and turning it into a fix, a doc, a better default or a clearer error message.

  • Product thinking
  • Developer experience
  • Iteration

03 / Selected work

A short list of my work, with the thinking attached.

01 Ecommerce · Gamification

Shop With Pages

Problem Shopping online is efficient, but it often lacks engagement and excitement.

Idea Treat the store like a game surface. Discounts and coupons become something you optionally play for rather than something you are tricked into using.

Build A gamified ecommerce experience combining product browsing, interactive mechanics and a coupon and discount system.

Visit project
02 Rich media · Interactive

3D Car Simulator

Context Rich media advertising has a hard constraint set: tiny weight budgets, no framework, and it has to run everywhere on the first try.

Build Interactive ad experiences and 2D / 3D web experiences in vanilla JavaScript and GSAP, animated on transform and opacity for stable frame rates.

Why it matters Working inside a strict budget is the best training for performance. This site is built with the same rules.

  • JavaScript
  • GSAP
  • Canvas
  • 2D / 3D
Visit demo
03 APIs · Developer tools

APIs and integrations

Focus Backend and API work where the consumer is another developer, which changes what counts as done.

Approach Predictable shapes, useful errors, and documentation written while the reasoning is still fresh.

Detail A specific example of an API endpoint, how it was consumed, and any fixes applied.

View documentation
04 Rich media · Banking

Fidelity interactive creative

Concept A portrait campaign experience that turns Fidelity's product story into an animated, interactive display unit.

Build Lightweight JavaScript and GSAP motion designed around a strict 300 × 600 advertising canvas.

Result A focused creative that communicates quickly while still giving the audience something to explore.

  • JavaScript
  • GSAP
  • Rich media
  • 300 × 600
Visit demo
05 Rich media · Automotive

Maserati acceleration creative

Concept Translate the feeling of Maserati acceleration into a compact interactive advertising experience.

Build Motion, pacing and responsive interaction simulate speed inside a lightweight 300 × 600 creative.

Result A performance-led product story that makes the car's speed feel immediate rather than simply describing it.

  • JavaScript
  • GSAP
  • Automotive
  • 300 × 600
Visit demo

More projects

The full list, with live previews of the ones you can open.

View all work

04 / Path

Learning, then engineering, then community, then product.

  1. 2019 – 2021

    Nigerian Navy, Port Harcourt Logistics Depot

    IT Specialist / Documentation Engineer

    Supported IT systems, networks, workstations and office infrastructure, and wrote the documentation that went with them: procedures, inventory systems, configurations, troubleshooting. Most of it had to be readable by people who were not technical. That is where I learned that explaining something is a separate skill from knowing it.

    • IT support
    • Technical documentation
    • Knowledge transfer
  2. 2021 – 2023

    CAD Consulting

    Junior Front-end Engineer

    Production Angular work on enterprise applications. State management with NgRx and Elf, reusable components, and a share of the frontend architecture. The first place my code had to survive other engineers reading it.

    • Angular
    • NgRx
    • Elf
    • Component architecture
  3. Seasonal · 2023 – 2024

    Atlassian Community DevRel

    Community Events Lead

    Planned and organised community events, workshops and meetups. Created awareness and orientation around Jira, Trello and Bitbucket, and helped developers adopt them in their own workflows. Kept the community active by making room for knowledge sharing and practical product education rather than product pitches.

    • Events
    • Developer education
    • Community building
    • Product feedback
    Read the case study
  4. 2023 – 2024

    Vroom

    Front-end Engineer / API Documentation Engineer

    Built the internal API documentation site covering the APIs developers needed, and documented what each one actually does rather than what it returns. Also built the admin dashboard and a ride-flow simulator that exercised the APIs end to end for internal testing. Worked across frontend and backend to understand how developers were really using them.

    • API documentation
    • Frontend
    • Developer tooling
    • Internal DX
  5. 2024 – Present

    Eskimi

    Rich Media Developer

    2D and 3D animated adverts, web games and interactive advertising experiences in JavaScript, GSAP and Three.js. Built and maintained reusable rich media templates and demo projects for internal and partner developers, and worked with product managers on documentation so engineers could adopt the templates without needing me in the room.

    • JavaScript
    • GSAP
    • Three.js
    • Templates and demos
    • Documentation

06 / Community

Community Events Lead: DevRel before I had a word for it.

Community work looks like event logistics from the outside. In practice it is a feedback loop. People show up with a product they half understand, they ask the questions they are slightly embarrassed to ask, and if you listen properly you leave with a list of everything the product failed to make obvious.

Plan and run events
Workshops and meetups that give developers a reason to show up and a reason to come back.
Create awareness
Orientation on Jira, Trello and Bitbucket, and what each one is actually for.
Educate developers
Walking people through the tools until the concepts land, not just the clicks, and into their own workflows.
Gather feedback
Capturing the friction people hit, including the parts they do not report anywhere.

The transferable part is not the events. It is the loop underneath them, and it is the same loop a developer relations team runs at a larger scale.

  1. 01Community
  2. 02Questions
  3. 03Feedback
  4. 04Education
  5. 05Better product understanding

07 / The Lab

The Lab

What happens when an engineer actually uses the product?

Reading a tool's documentation tells me what it claims. Shipping on it tells me what it costs. So I build something real, then write down what the experience was actually like, including the parts where I got stuck. That last part is the whole exercise.

Current subject Signal Face · Postgres on Railway

  1. FrontendNext.jsVercel
  2. APIREST serviceRender
  3. DatabasePostgreSQLRailway

What What I built

Signal Face, a social platform with a digital economy inside it. On the surface it works like Instagram: profiles, posts, following. Underneath, every creator has their own currency that fans can buy and sell, and its price moves with their following and engagement, the way a share price does. It was a client project, and it became the thing I used to learn PostgreSQL properly.

Why Why I built it

Two reasons at once. The client needed it, and I wanted a real excuse to use PostgreSQL and Railway rather than read about them. A creator economy turned out to be a good test: social data and financial data live in the same system, which is exactly where the database stops being a preference and starts being a constraint.

Easy What was easy

The frontend. I have been building interfaces for years, so I implemented the core design and the reusable components myself, set the standard, then had AI generate the rest of the screens against it, the way I would hand work to a junior developer. That works once you have already decided what good looks like. It does not work as a substitute for deciding.

Stuck Where I got stuck

Both times, outside the code. KYC for withdrawals stalled while I waited on my Smile ID, so the entire money-out path sat unfinished on someone else's timeline. Content moderation took longer: there is plenty of advice and very little of it is specific, and it cost me real research before I settled on Cloudinary. Neither was a hard engineering problem. Both are the kind of thing that quietly eats a sprint.

Learned What I learned

PostgreSQL is the right default for a social product that touches money. The social half wants relationships: users, follows, posts, and joins across all of them. The money half wants transactions that either complete or do not, because a currency ledger cannot be approximately correct. Postgres does both in one place, so there were never two stores to reconcile. Running it on Railway kept it out of my way: it has been reliable, and the dashboard loads fast enough that I actually open it.

Improve What I would improve

The free tier. Not every developer building on a platform has a budget yet, and the people most likely to become advocates for it are often the ones who cannot pay for it early. I would rather be allowed to keep building until I am ready to ship, with the expensive resources capped the way Render limits GPUs. Cap the ceiling, not the runway.

Share What I would tell another developer

Use it. If you are building anything where social data and money sit in the same product, PostgreSQL on Railway gets you further before you hit a wall than the alternatives I have tried, and the setup cost is close to nothing. Then budget time for the parts that are not code: identity verification and content moderation will take longer than your schema did. And decide your architecture first, price it second. A free tier is a good reason to start somewhere and a bad reason to build something a particular way.

  1. Build
  2. Use
  3. Observe
  4. Document
  5. Share
  6. Get feedback
  7. Improve

08 / DevRel

What does developer relations mean to me?

Developers Listen Developer
relations
Educate Product

Developer relations sits at the intersection of technology, communication and community.

Build credibility
Use the product. Ship something real with it before saying anything about it.
Explain complexity
Make difficult concepts understandable without making them wrong.
Listen carefully
Understand the problem a developer has, not the one that is easiest to answer.
Feed insights back
Return what you heard to the team so the product itself gets easier.

09 / Approach

What I look for in the tools I work on.

What I notice

The tools I end up recommending all do the same thing: they shorten the distance between an idea and something running. The ones I lose patience with treat friction as a fact of life rather than a product problem. I notice the difference quickly, because I have lost weekends to the second kind.

Where I would dig

The gap between the first success and the second week. Onboarding usually gets attention; environments, data, and the moment a side project picks up real users usually do not. That gap is where developer experience is won or lost, so that is where I would keep building and keep notes.

What I bring

An engineer who builds the thing before writing about it, explains without dumbing down, and is comfortable in a community running the unglamorous half of the job: answering questions, collecting friction and carrying it back to the people who can fix it.

Written about how I work, not about any one company. Specifics belong in a conversation.

10 / Reviews

Reviews from people I've worked with.

Real feedback from collaborators, teammates and project leaders.

Marta Jurkšaitienė

in

Director, Global Client Success and Operations @ Eskimi

★★★★★
Had the pleasure of working with Wisdom in our Creative Studio, where he contributed to developing our rich media banners. He quickly became a reliable team member, proactive, curious, and always eager to learn. Wisdom brought great energy to every project, adapted fast to feedback, and delivered on time. He showed interest in AI and had several innovative projects using the skills. A promising developer with a bright future ahead!

Babajide Awodire

in

Android Developer

★★★★☆
I had the pleasure of working with Wisdom at Vroom NG, where we collaborated on building a ride-hailing solution. Wisdom handled the web development side of things, and his technical skill, creativity, and attention to detail stood out from day one. He consistently delivered high-quality work, communicated effectively, and approached every challenge with a positive and solution-oriented mindset. Working with him made the entire development process smoother and more efficient. Wisdom is not only a talented developer but also a great team player who understands how to bring ideas to life. I strongly recommend him for any opportunity that values innovation, collaboration, and solid technical expertise.

Chibuzo Madumere

Front-end Rich Media Developer @ Eskimi

★★★★★
I worked with Wisdom as a teammate and highly recommend him. He is a strong fullstack web and mobile developer with excellent problem solving skills, fast delivery, and a high level of reliability. He communicates clearly, takes ownership of his tasks, and is a pleasure to work with. A great asset to any team.

Kasper Apsega

in

Creative Project Manager @ Eskimi

★★★★★
What stands out most about Wisdom is his attitude and determination. He works incredibly hard to improve his coding skills and never backs down from a tough problem. He is a resilient professional who brings 100% effort to the table every day. Was an absolute pleasure to have him on the team!

Omotola Monique Orowale

Digital Media & Strategy Leader | Programmatic Advertising | AI-Driven Marketing | Global Growth & Innovation

★★★★★
I had the pleasure of working closely with Wisdom at Eskimi and he consistently delivered at a high level. He is proactive, detail oriented, and very strong at driving tasks to completion, even when timelines are tight. What stood out most was his mindset: he takes feedback well, asks the right questions, and always looks for smarter ways to get results. If you are looking for someone who is reliable, collaborative, and impact driven, Wisdom is a great hire.