LAWAL

All three. I'm open to senior frontend roles, embedded contract engagements with product teams, and well-scoped freelance builds. I'm based in Lagos and also work out of Freetown, which gives me comfortable overlap with EMEA, UK, and US-East working hours.

It usually starts with a short discovery call so we can align on goals, constraints, and what success actually looks like. After that I send over a proposed scope, milestones, and a working cadence. In practice that means weekly demos with continuous Slack or Linear updates in between. Most builds land somewhere between 4 and 10 weeks; embedded contracts naturally run longer.

Next.js, React, and TypeScript at the core. Tailwind and shadcn/ui for styling, with whatever CSS approach the project needs. GSAP and Framer Motion for animation. Mapbox GL and Turf.js when geospatial work shows up, with Socket.io for real-time interfaces. React Native and Flutter on mobile. I'm comfortable across REST, GraphQL, and tRPC, and when a project requires it I'll extend into NestJS, Prisma, MariaDB, and self-hosted infrastructure (NGINX, PM2, Docker, GitHub Actions CI/CD).

Frontend is my core strength, but I extend into backend, real-time, and self-hosted infrastructure when the build genuinely needs it. The clearest example is Trakkam, a multi-tenant GPS fleet SaaS I shipped end-to-end: Next.js 16, TypeScript, Mapbox geofencing, and live WebSocket vehicle tracking on the frontend, with a NestJS and Prisma API, self-hosted Traccar, NGINX, PM2, and GitHub Actions CI/CD on the back. Running it on a $5/month VPS kept operational costs roughly 8x lower than the equivalent managed setup, without compromising reliability. If your project needs that kind of vertical ownership, I can ship it. If a dedicated backend or DevOps team is already in place, I'll happily slot in on the frontend.

I treat both as baseline requirements, not nice-to-haves. I profile early with Lighthouse, WebPageTest, and the React Profiler, and I set LCP, INP, and CLS budgets before any feature work begins. WCAG 2.2 AA is the standard I work to by default. When I re-platformed the SafulPay corporate site to Next.js, the Lighthouse scores went from 68 to a perfect 100 across Performance, Accessibility, Best Practices, and SEO, all while we shipped additional sections and content in the same pass.

Yes, that's actually a sweet spot for me. I lean on GSAP timelines and ScrollTrigger, stick to transform and opacity-only animations so the work stays on the compositor thread, and always wire up prefers-reduced-motion fallbacks. Motion should reinforce hierarchy, not punish someone's device or vestibular system.

Both, depending on what the team needs. At Tech N' Goodwill I direct cross-functional squads across 6+ web applications, working with UI/UX, marketing, and backend engineers. Standardizing our Git/GitHub workflows and structured pull requests cut code-review turnaround by about 30% and noticeably accelerated feature delivery. In smaller contract engagements I'm equally happy embedded as a senior IC.

I happily pair with designers and translate Figma into production-grade UI down to the pixel. When there's no designer attached, I can lead the UI direction myself: wireframes, component system, motion language, and visual polish.

Every milestone ships behind a preview URL with a short Loom walkthrough. Feedback lives in a single thread (Linear, Notion, or GitHub, whichever you prefer), and I batch revisions per milestone so scope creep doesn't sneak in. Two structured revision rounds per milestone is the cadence most teams settle into.

Yes. Most clients keep me on a lightweight retainer for bug fixes, performance audits, and incremental features. I also take on focused one-off engagements: accessibility audits, performance audits, or a targeted refactor on a problem surface.

Drop me a note through the contact section with the rough shape of the project: goals, timeline, team, and any constraints I should know about up front. I'll get back to you within 1 to 2 business days with whether I'm a fit, a proposed scope, and the next steps.