Skip to content
Open to full-time remote WordPress engineering roles and focused production collaborations. Start a Project

Available for remote WordPress engineering roles

Saddam Hossen · Senior WordPress Engineer

I build reliable WordPress systems for production teams.

Custom plugins, WooCommerce, Gutenberg, REST APIs, performance and production debugging.

Explore Engineering Read Case Studies
Since 2017
Production web development
Top Rated
Upwork and international clients
Remote experience
Delivery, support and async communication

What I own

WordPress engineering beyond page assembly.

I work across the layers that make a WordPress product dependable: domain logic, editorial workflows, integrations, browser behavior and production operations.

01

Plugin and platform engineering

Custom plugins, data models, settings, background work, admin workflows and clear ownership boundaries.

PHP · OOP · MySQL · Hooks · WP-CLI
02

WooCommerce and integrations

Checkout, catalog, operational workflows, remote APIs, webhooks and recoverable external-service failures.

Commerce · REST · Webhooks · Payments
03

Gutenberg and editor experience

Native blocks, patterns, structured fields and safe editing workflows for developers and non-technical teams.

React · block.json · Patterns · Accessibility
04

Performance, security and support

Root-cause debugging, query and cache analysis, deployment safety, incident communication and defensible controls.

Profiling · Site Health · Privacy · CI

Selected systems

Real constraints, technical decisions and accountable outcomes.

The case studies explain what the system needed, what I owned, why a technical direction was chosen and how risk was controlled.

All Case Studies Browse selected projects

Built for maintainers and editors

Custom architecture should not make everyday editing difficult.

A non-technical client should be able to update text, images and repeatable content without touching templates. I use native WordPress editing tools and reserve custom code for the parts that genuinely need it.

Read the editing architecture guide
01

Blocks for everyday content

Editors update copy, images, lists and simple layouts in the native editor.

02

Patterns for reusable sections

Approved hero, CTA, feature and content layouts stay consistent without rebuilding them.

03

Structured fields for repeatable records

Projects, services and case studies use clear fields instead of fragile free-form pages.

04

Custom blocks only where needed

Complex interactive features keep a stable data contract and an editor-friendly interface.

Professional background

Delivery, support and frontend experience in one engineering practice.

That combination helps me investigate beyond a single code layer and communicate clearly with product teams, clients and support stakeholders.

Current

Independent WordPress Engineer

Custom development, WooCommerce, debugging, performance and ongoing support for international clients.

Previous remote role

WordPress Technical Support Engineer

Reproduced incidents, isolated conflicts, interpreted logs and translated findings into safe next steps.

Foundation

Frontend Developer

Built responsive interfaces and developed strong browser, JavaScript, CSS and accessibility fundamentals.

View Full Experience

Technical writing

Practical WordPress notes built around decisions and examples.

The writing is designed to be useful during real implementation work: architecture, security, APIs, debugging, editor experience and search foundations.

Browse All Technical Writing