Skip to content

Hey, I'm

Ryan.

I turn complex product problems into clear, lively web experiences.

Frontend engineer working with React, Next.js, and TypeScript.

Where the details come together

01

Systems

Make complexity clear.
02

Interaction

Make it feel right.
03

Motion

Give it a pulse.
Built with care for the detailsScroll to explore
02 / Selected workSystems / Motion / Storytelling

From idea to interface

Things I’ve made.

Different problems, same instinct: make the complicated feel clear and the everyday feel a little more alive.

More ideas are out thereBrowse all 15 projects

behind the browser

Good work starts with being curious.

I'm Ryan, a frontend engineer who likes the messy middle: making complex product flows feel clear, finding the small interaction that makes a screen click, and building it so the next engineer can keep going.

01

Find the shape.

I untangle the flow until the next step is obvious, especially when the product itself is complex.

02

Give it a pulse.

I explore UI direction visually, build the responsive version, then tune motion and feedback in the browser.

03

Make it last.

I review the implementation, test tricky states, and keep the React and TypeScript code clear for the next engineer.

Selected experience / field notes

Where the work got interesting.

Different products, different constraints. Here are a few of the problems I've spent real time inside.

2026 / now

Alpha Red Group

Frontend Engineer

I build AI Hiring and permission-aware Portal workflows, plus Hotel Price Intel interfaces for room-type comparison and date-scoped rates.

2023 / 2025

HyperBeam

Frontend Engineer

I led a legacy comics platform’s move to Next.js and worked on live auctions, search, price charts, and subscription flows alongside a backend engineer.

2019 / 2022

by.U · Telkomsel

Lead Frontend Engineer at Aleph

I led the web app’s move from React inside Drupal to standalone Next.js, and built payment and shipping flows with real service and regional rules.

2018 / 2019

Honda CMS

Frontend Engineer at Aleph

I built recursive React tables so CMS modules could define headers and mappings once, instead of rebuilding similar CRUD screens each time.

Have something
worth making?

Tell me what you're working on. I'd like to hear what makes it interesting.

ryanyohenry@gmail.com
Ryan Henry · Frontend engineerBack to top