Privacy-respecting analytics

Joh uses Google Analytics to understand which stories and portfolio pages are useful. Advertising storage stays off. Read the privacy notice.

Joh Azores

Software engineer and product builder

I’m Joh Azores. I build useful software and keep it maintainable.

I am a full-stack software engineer from Quezon City with more than ten years of experience across SaaS products, WordPress, membership platforms, e-commerce, booking, payments, APIs, server operations, and AI-assisted workflows.

My work usually sits where product requirements, legacy systems, external integrations, and real operational constraints meet. I focus on clear architecture, small reusable components, dependable releases, and software that another engineer can understand after I leave the room.

Quezon City, Philippinesjohanssen.azores@gmail.comGitHub
Joh Azores, software engineer and product builder

How I work

Direct, practical, and accountable

Remote collaborationProduction ownershipLong-term maintenanceClear documentation
Capabilities

Broad enough to own the product, focused enough to keep the system simple.

Product engineering

End-to-end product work across discovery, architecture, implementation, release, maintenance, and iterative improvement.

Next.jsReactTypeScriptNode.jsPHPWordPress

Platforms and integrations

Multi-tenant portals, membership systems, REST APIs, payment flows, external-service adapters, background jobs, and operational tooling.

PrismaMongoDBPostgreSQLREST APIsStripeOAuth

Production operations

Practical deployment, server administration, logging, monitoring, failure handling, performance work, and production support.

LinuxNginxCI/CDVercelSecurityObservability

AI-assisted workflows

Human-governed content, support, research, and automation systems that preserve review, sources, provenance, and rollback.

OpenAI APIPrompt systemsRAGHuman reviewAudit trails
Selected work

Systems shaped by real product and operational needs.

These examples describe publicly shareable architecture and responsibilities. They avoid confidential customer data, private credentials, and unsupported metrics.

Explore the project archive

Software engineering for WordPress support products

Heroic Inbox and HeroThemes

Plugin and interface development, email workflows, performance improvements, release work, and AI-assisted reply composition with human control.

Lead engineering for a membership and property-insights platform

Hotspotting

A Next.js membership portal with subscriptions, third-party integrations, enterprise white-label controls, and one maintainable multi-tenant codebase.

Multi-venue API and integration engineering

DailyPress membership platforms

Membership, wallet, notification, venue, and gaming-system integrations with monitoring, adapter boundaries, and operational troubleshooting.

Independent publication and governed AI CMS

Joh Editorial

The site itself is a working case study in source-aware drafting, immutable versions, human approval, original-asset provenance, SEO, and controlled distribution.

Engineering principles

The standards I use to make technical decisions.

Keep architecture understandable and proportional to the problem.

Prefer maintainable systems over impressive but unnecessary complexity.

Treat production reliability, security, and accessibility as product features.

Use AI to assist people—not to remove accountability, evidence, or review.

Communicate constraints and unfinished work honestly.

Beyond the code

I am also a musician, traveler, and independent editor. Those interests influence how I think about interfaces, rhythm, communication, context, and the people who eventually depend on a product.

Joh Editorial is where I document useful technical ideas, product decisions, responsible AI practices, and selected experiences without separating engineering from the wider culture in which technology operates.