Skip to content

software engineer

I buildsoftware.

Backend, frontend, and every process in between.

$

software engineer

Muiz Oyebowale

The working set.

The tools I've worked with.

A starting point, not the boundary. The problem determines the tool, and these are the ones I've used to solve problems so far.

Languages

  • Python
  • TypeScript
  • HTML
  • JavaScript
  • Bash
  • C
  • Lua
  • Go
  • Rust

Frameworks

  • Django
  • FastAPI
  • Django Ninja
  • Next.js
  • Express
  • Node.js
  • Django REST Framework
  • Flask
  • React

Data

  • PostgreSQL
  • MySQL
  • Redis
  • SQLAlchemy
  • Django ORM
  • SQLite

Infrastructure

  • Linux
  • AWS EC2
  • Docker
  • Celery
  • Nginx
  • Uvicorn / Gunicorn
  • GitHub Actions

Tooling

  • Neovim
  • Git
  • Tmux
  • Zsh
  • fzf
  • ripgrep
  • lazygit

Places I've worked.

Full-Stack Engineer, Team Lead

Apr 2026 — Jun 2026 · internship

Tech lead over an 11-engineer team (4 backend, 7 frontend) building Anvila, an AI-agent manifest generator. Users describe an agent, answer follow-up questions, preview the generated files, and publish them to GitHub. Shipped in under a month.

  1. Wrote the technical requirements document, made the feature calls, and split the backend work by experience: beginners took utilities, authentication, and the Redis cache helper, while the other senior engineer took the LLM adapters, conversation compression, and the message API layer.

  2. Owned database design and migrations for the whole team. Every engineer extended schemas I originally built, which kept the data layer consistent as the team grew.

  3. Built the prompt-to-manifest generation pipeline and its event-publishing layer, the path that turns a user's prompt into a set of customized agent manifest files. 30+ manifests generated in production use.

  4. Built publishing to GitHub: manifests go to a public org repo or the user's private account, with an install link. Matched skills are pulled from ClawHub and cached in the GitHub org so they're reused instead of re-fetched. Took over and finished the ClawHub integration after it hit problems.

  5. Decided where to use SSE versus regular requests, and chose SSE over WebSockets because the client never needs to push live messages. Status events ('thinking', 'matching skills') drive the UI while responses stream with a typing effect. Messages go by POST and are persisted, so a refresh never loses them.

Python · FastAPI · Next.js · PostgreSQL · Redis · Celery · SSE · GitHub API

The person behind it.

more about me

I'm a software engineer driven by curiosity about how things work, from intuitive frontend experiences to the systems and data models behind them. I enjoy understanding problems deeply, making thoughtful engineering decisions, and building software that works well and stands the test of time. Lately, I've been exploring AI and machine learning, particularly how to turn them into useful products.

Portrait of Muiz Oyebowale
@muizzyranking

Let's build something that has to work.

Open to software engineering roles — or a good conversation about systems.