About

Khairul AlamSenior Web Developer

Senior Web Developer with 10+ years of experience designing, architecting, and shipping web platforms, from custom WordPress, Drupal, and Craft CMS builds to modern headless stacks powered by Next.js (App Router & React Server Components), React, and TypeScript.

Get in touch LinkedIn

Years shipping web platforms

10+

Custom CMS, headless, modern app router

WCAG 2.1 / 2.2 accessibility

Audited with axe-core in CI

Core Web Vitals targets

p75

LCP < 2.5s · INP < 200ms · CLS < 0.1

Technical role on most projects

Lead

Architecture, reviews, mentorship

What I focus on

Four things I won't compromise on

The longer I do this work, the shorter the list gets. These are the ones that stayed.

Architecture first

Decide where complexity lives before writing it. RSC vs. client, edge vs. node, CMS vs. code. Match the shape of the problem.

Accessible by default

Keyboard paths, semantic HTML, focus rings, reduced motion, contrast that holds up in both themes. WCAG 2.2 AA as the floor, not the ceiling.

Performance as UX

Core Web Vitals are a user feeling, not a score. Ship less JS, stream what you can, defer what you can't.

Mentorship and review

Set front-end standards, run reviews that teach, write specs juniors can build from. The team's level matters more than any single PR.

How I work

Pragmatic, measured, hands-on

Start by mapping the real constraint — budget, deadline, team shape, traffic profile — before picking the stack. Most architectural decisions only make sense in context.
Translate Figma into accessible, semantic markup first; styles and motion come after structure works. This catches a11y and SEO gaps before they're load-bearing.
Cut PRs small enough to actually review. Pair on the tricky ones. Document the decision in the commit, not a wiki nobody reads.
Measure what shipped — Web Vitals, error rates, conversion deltas. Cut what isn't working. Boring observability beats clever heroics.

I'm also an early and heavy adopter of AI-assisted development, using agentic workflows daily and working with Codex, DeepSeek, Gemini, and Gemma to ship faster without compromising quality.

Right now

Building

This portfolio site (Next.js 16 App Router, Tailwind v4, monochrome theme).

Exploring

Agentic workflows with AI tools a daily driver: scoping, refactoring, code review, and shipping.

Reading

Sebastian Markbåge on RSC, Lea Verou on CSS color spaces, and the WCAG 2.2 Understanding docs.

Open to

Senior Web Developer, Team Lead / Tech Lead, and Front-End Developer roles.

SeniorTech LeadFront-End Lead

Activity

Live from GitHub

Public contributions over the last 12 months. Updates hourly via the GitHub GraphQL API.

Public commits

1,095in the last year

@devkhairul

MayJunJulAugSepOctNovDecJanFebMarAprMay

MonWedFri

LessMore

Currently open to Senior Web Developer, Team Lead / Tech Lead, and Front-End Developer roles.

The fastest way to reach me is the contact form. I read every message.

Start a conversation See the stack

Pragmatic, measured, hands-on

Start by mapping the real constraint — budget, deadline, team shape, traffic profile — before picking the stack. Most architectural decisions only make sense in context.

Translate Figma into accessible, semantic markup first; styles and motion come after structure works. This catches a11y and SEO gaps before they're load-bearing.

Cut PRs small enough to actually review. Pair on the tricky ones. Document the decision in the commit, not a wiki nobody reads.

Measure what shipped — Web Vitals, error rates, conversion deltas. Cut what isn't working. Boring observability beats clever heroics.

I'm also an early and heavy adopter of AI-assisted development, using agentic workflows daily and working with Codex, DeepSeek, Gemini, and Gemma to ship faster without compromising quality.