Skip to content
Godwill Barasa

Portfolio Vol. 01 2026

Nairobi / Remote

GodwillBarasa

Senior Web Engineer building, scaling and optimising high-traffic web applications — high-performance, accessible, measurable digital products.

  • Web Engineering
  • Frontend Architecture
  • Performance
  • Product

Since 2018 — 8+ years

02Thesis

Ship beautifully crafted interfaces.Engineer to a performance budget.Measure what actually changed.

Position

Eight-plus years building, scaling and optimising high-traffic web applications, specialising in React, Next.js and experimentation-driven product development.

Focused on turning ambiguous ideas into production-ready, user-centric experiences — from shaping frontend architecture and performance budgets to measuring impact through Core Web Vitals, funnel analytics and continuous experimentation.

Comfortable operating in monorepo-style environments and cross-functional, remote teams, with a track record of standardising frontend tooling, strengthening CI/CD pipelines, and improving delivery reliability and quality.

Collaborating directly with designers, PMs and customers, and iterating quickly so teams can ship, learn, and make better decisions, faster.

03Selected work

Four engagements, examined

Two client platforms. Two open-source instruments. Evidence where evidence exists.

Work 012025 — PresentFairfax, VARemote

Piedmont Global

Senior Web Engineer (Marketing) · Public-facing marketing properties

Mandate
Lead React and Next.js development across the company's public-facing marketing properties.
Intervention
Introduce standardised performance budgets, shared component libraries and build optimisations — code splitting, memoization, lazy loading — rather than tuning pages one at a time.
Engineering
Refined GitHub Actions CI/CD with engineering and DevOps: automated builds, Jest suites, and a preview deployment per branch. Owned Google Tag Manager, GA4 and Meta Pixel — key funnels and events instrumented, tracking scripts loaded in a performance-conscious way. Wrote the internal guidelines for SEO, accessibility, performance and shared tooling.
Outcome
Improved Core Web Vitals, lower time-to-merge, regressions caught earlier — and roughly 40% gains in page speed and accessibility scores on key routes.

~40%

Page speed & accessibility gains

Measured on key routes after performance budgets, shared components and build optimisation were standardised.

Fig. 01 — Reported outcome, Piedmont Global
Work 022024 — 2025Nairobi, KenyaRemote

Ogilvy Africa

Staff Frontend Engineer · Multi-project frontend platform

Fig. 02 — On-time delivery, before and after standardisation

On-time delivery rose from 70% to 95%A slope between two observations on a 0 to 100 percent scale: before standardisation, on-time delivery was 70 percent; after, 95 percent.05010070%95%BEFOREAFTER
Two observations, not a trend line. Reported before/after values only.
Mandate
Lead a distributed engineering team building and operating multiple client-facing React/Next.js and WordPress properties in a multi-project, monorepo-style setup.
Intervention
Define and enforce standardised frontend tooling — shared ESLint and Prettier configs, component patterns, TailwindCSS conventions — plus performance budgets applied across every project rather than per-campaign.
Engineering
Ran A/B tests on landing pages and funnels with product and marketing, using feature flags and analytics to read search performance, user behaviour and conversion impact. Acted as the frontend platform contact — unblocking engineers on build issues, deployment workflows and shared tooling across time zones.
Outcome
15+ features and campaigns shipped per quarter · on-time delivery 70% → 95% · production defects −30% · average page load −35% · handoff delays −40%.
Work 03Open sourceMIT · TypeScript

PixelPress

Repository →

Image compression & conversion utility · Next.js, Sharp, TypeScript

A compressor that searches for the smallest file a given image can survive being — instead of guessing at a quality number.

Sharp exposes quality as a dial from 1 to 100. Turning it by hand is a blind trade between bytes and visible damage. PixelPress makes that a search problem: binary search across the quality range with tolerance-based convergence, parallel quality probes, and progressive dimension scaling when quality alone cannot reach the target.

  • Output formatsWebP · AVIF
  • DeliveryInstallable PWA, offline
  • LicenceMIT

Fig. 03 — Quality search, interval narrowing

Binary search narrowing the quality intervalFour stacked number lines from quality 1 to 100. Each iteration halves the candidate interval around a probe until the encoded size converges within tolerance of the target.Q1Q100i.1i.2i.3i.nprobewithin tolerance
Schematic of the documented algorithm, not a captured run.
Work 04Open sourceGPLv2+ · PHP

Site Performance Tracker

Repository →

WordPress performance monitoring · PHP 8, PageSpeed Insights API

Fig. 04 — Two measurement paths, one store

Lab and field measurement pathsSynthetic audits are queued and processed by a built-in PHP worker that calls the Google PageSpeed Insights API. Separately, visitor browsers send real-user Core Web Vitals. Both write to custom database tables that feed the admin dashboard and a REST API.AUDIT QUEUEurl · schedulePHP WORKERasync · no nodePageSpeedInsights APIVISITORpage viewRUM BEACONlcp cls fid fcp ttfbCUSTOM TABLESindexed · retentionDASHBOARDadmin uiREST APIcsv · html report
Architecture as documented in the repository README.

Lab data tells you what a page can do. Field data tells you what it did. The plugin collects both and keeps them in the same place.

Synthetic audits run against the Google PageSpeed Insights API for desktop and mobile; real-user monitoring collects LCP, CLS, FID, FCP and TTFB from actual visitors. The worker is plain PHP — no Node.js dependency — so it installs on ordinary WordPress hosting, processes queued audits asynchronously, and recovers stuck jobs.

  • RequiresWordPress 6.0+ · PHP 8.0+
  • Version1.0.0 (2024)
  • AccessAdmin UI · REST · WP-CLI
  • ExportCSV · HTML report

04Chronology

Eight years, five rooms

Headline first. Detail on request.

Web EngineerMobile EngineerFullstack EngineerStaff Frontend EngineerSenior Web Engineer

2025 — NowPiedmont GlobalSenior Web Engineer (Marketing) · Fairfax, VA · Remote
  • Led React and Next.js development for public-facing marketing properties, introducing standardised performance budgets, shared component libraries, and build optimisations — code splitting, memoization, lazy loading — that improved Core Web Vitals and yielded ~40% gains in page speed and accessibility scores on key routes.
  • Collaborated with engineering and DevOps to refine GitHub Actions–based CI/CD workflows: automated builds, Jest test suites, and preview deployments per branch — reducing time-to-merge and catching regressions earlier.
  • Owned Google Tag Manager configuration and GA4 / Meta Pixel integrations, instrumenting key funnels and events while keeping tracking scripts loaded in a performance-conscious way.
  • Created internal documentation and guidelines for SEO, accessibility, performance and shared tooling, mentoring engineers and content stakeholders.
2024 — 2025Ogilvy Africa KenyaStaff Frontend Engineer · Nairobi, Kenya · Remote
  • Led a distributed engineering team building and operating multiple client-facing React/Next.js and WordPress properties in a multi-project monorepo-style setup — shipping 15+ website features and campaigns per quarter while improving on-time delivery from 70% to 95% and reducing production defects by 30%.
  • Defined and enforced standardised frontend tooling (shared ESLint/Prettier configs, component patterns, TailwindCSS conventions) and performance budgets across projects, cutting average page load times by ~35%.
  • Partnered with product and marketing to run A/B tests on landing pages and funnels, using feature flags and analytics to analyse search performance, user behaviour and conversion impact.
  • Acted as a go-to for frontend platform questions — unblocking engineers on build issues, deployment workflows and shared tooling, mentoring cross-functional developers across time zones and reducing handoff delays by 40%.
2021 — 2024Belva Digital AgencyFullstack Engineer · Nairobi, Kenya · Remote
  • Developed and maintained React and Next.js applications (with TailwindCSS) backed by Laravel, contributing to shared component libraries, configuration patterns and deployment playbooks.
  • Implemented code splitting, memoization and lazy loading as part of a standardised performance toolkit, significantly improving Core Web Vitals and page speed for SEO-critical and high-traffic landing pages.
  • Designed and integrated RESTful and GraphQL APIs for complex, data-heavy interfaces, working with backend teams to define contracts and improve error handling.
  • Wrote and maintained Jest unit tests for React/JavaScript components and integrated them into CI pipelines.
2019 — 2021Legibra AgencyMobile Engineer · Nairobi, Kenya
  • Built and maintained cross-platform applications using React Native, Bootstrap and Python, delivering production systems while enforcing clean code standards and performance optimisation.
  • Integrated RESTful APIs and middleware services in agile environments, collaborating with distributed teams to ship iterative features.
  • Wrote and maintained unit tests using Jest to ensure code reliability, catch regressions early and uphold high test coverage across React Native and JavaScript projects.
2018Procter & GambleWeb Engineer, Intern · Nairobi, Kenya
  • Modernised regional brand microsites to align with P&G's global design systems and accessibility standards.
  • Implemented marketing automation workflows, integrating CMS-driven content with analytics and engagement platforms.

05Impact index

Numbers, with their context attached

Each figure is attributed to the engagement it came from. Nothing here is aggregated across roles.

~40%

Page speed & accessibility gains

On key routes, after performance budgets, shared component libraries and build optimisations were standardised.

Piedmont Global · 2025 — Now

95%

On-time delivery, up from 70%

Standardised tooling and performance budgets applied across every project rather than per campaign.

Ogilvy Africa Kenya · 2024 — 2025

−35%

Average page load time

Shared ESLint and Prettier configs, component patterns and TailwindCSS conventions, enforced across projects.

Ogilvy Africa Kenya · 2024 — 2025

−30%

Production defects

Recorded over the same standardisation programme that lifted delivery reliability.

Ogilvy Africa Kenya · 2024 — 2025

15+

Features & campaigns, per quarter

Sustained cadence across multiple client-facing React/Next.js and WordPress properties.

Ogilvy Africa Kenya · 2024 — 2025

−40%

Handoff delays

Outcome of owning frontend platform questions — build issues, deployment workflows, shared tooling — across time zones.

Ogilvy Africa Kenya · 2024 — 2025

Note — figures as recorded by Godwill for the engagements named. Where a measurement is approximate it is written as such.

06The stack

Organised by what it is for

Tools are listed under the job they do. The tool is never the story.

01Interface

  • ReactComponent architecture
  • Next.jsSSR · SSG · routing
  • TypeScriptType safety
  • JavaScript ES6+Language
  • TailwindCSSStyling conventions
  • HTML5 · CSS3Semantics · layout
  • React NativeCross-platform
  • StorybookDesign systems

02Platform

  • WordPressCMS architecture
  • Laravel · PHPApplication backend
  • REST · GraphQLAPI contracts
  • PythonServices · tooling
  • Nx · TurborepoMonorepo workflows
  • Docker · KubernetesRuntime
  • AWS · ServerlessInfrastructure

03Quality

  • Core Web VitalsThe scoreboard
  • Performance budgetsThe constraint
  • ProfilingWhere time goes
  • Code splittingShip less
  • Memoization · lazy loadDo less
  • AccessibilityNon-optional
  • JestUnit & regression
  • LighthouseStatic asset analysis

04Delivery

  • GitHub ActionsCI/CD
  • Preview environmentsPer branch
  • Vite · WebpackBuild
  • ESLint · PrettierShared configs
  • GTM · GA4 · PixelInstrumentation
  • Feature flags · A/BExperimentation
  • Logging · alertingObservability
  • Incident resolutionWhen it breaks

07Laboratory

Open source & instruments

Work made outside a client brief. Both are measurement tools; both are published under an open licence.

PixelPress

Spec. 01

A compression and conversion utility that treats "smallest acceptable file" as a search problem rather than a setting. Binary search across quality 1–100 with tolerance-based convergence; parallel probes; dimension scaling as a fallback when quality alone will not reach the target.

  • Engineering problemConvergence without visible damage
  • StackNext.js · React · Sharp · TypeScript
  • DeliveryInstallable PWA · offline
  • LicenceMIT
  • StatusIn development
Repository

Site Performance Tracker

Spec. 02

A WordPress plugin that runs synthetic audits against the PageSpeed Insights API and collects real-user Core Web Vitals from live traffic, storing both in indexed custom tables with a retention policy. The background worker is plain PHP, so it runs on ordinary hosting.

  • Engineering problemAsync work without a Node runtime
  • StackPHP 8 · WordPress 6 · PSI API
  • AccessAdmin UI · REST · WP-CLI
  • LicenceGPLv2 or later
  • Statusv1.0.0 · maintained
Repository

Instrument — this page, measured on your device

Measuring…

LCP
Largest contentful paint
CLS
Cumulative layout shift
INP
Interaction to next paint
TTFB
Time to first byte
Transferred
Total over the wire
Requests
Including this document

Read live from the Performance API in your browser, on your connection. Not a claim, a reading — and it will differ from anyone else's.

08Field notes

Writing

Production notes from real systems — M-Pesa and the Daraja API, Core Web Vitals, and the failure modes that never make the getting-started guides.

09About

The person behind the record

Nairobi, Kenya. Working remote since 2021.

Godwill Barasa
Godwill Barasa, Nairobi

Godwill Barasa

Senior Web Engineer

Eight-plus years building, scaling and optimising high-traffic web applications, specialising in React, Next.js and experimentation-driven product development. The work runs from shaping frontend architecture and performance budgets through to measuring impact with Core Web Vitals, funnel analytics and continuous experimentation.

Comfortable in monorepo-style environments and cross-functional, remote teams — standardising frontend tooling, strengthening CI/CD pipelines, and improving delivery reliability and quality. Most of it is done alongside designers, PMs and customers.

  • Based
    Nairobi, Kenya
  • Working
    Remote, across time zones
  • Currently
    Piedmont Global — Fairfax, VA
  • Also
    Mentoring · writing · open source
  • 10Contact

    Ship, learn, and make better decisions, faster.

    If there is a product that needs to be fast, accessible and measurable — and someone to own the architecture, the budget and the evidence — this is the address.

    godwill.codes@gmail.com