G

GERYENKOHAWSEN

Solution Architect,Frontend-Minded Builder

I build solutions that do not just work (動いているだけではなく), but are usable from the end user's perspective (使える) through UI/UX judgment and frontend experience.

I turn messy business operations into internal software people actually use.

AboutSkills

ABOUT ME

I'm Geryenko Hawsen, a Tokyo-based Solution Architect who mainly uses Retool.

My background is frontend engineering, so I care about whether the tools I design are actually usable, maintainable, and clear. I work best at the overlap of business workflows, internal tools, frontend systems, demos, and stakeholder communication.

I do not see internal tools as just screens connected to data. I see them as decision surfaces: places where business rules, user behavior, technical constraints, and delivery speed have to meet cleanly.

  • Tokyo, Japan
  • Solution Architect who mainly uses Retool
  • Former Frontend Engineer

SKILLS

The rare overlap

Most portfolios separate technical skill, architecture, and communication. My work sits where they overlap.

Frontend

  • TypeScript
  • JavaScript
  • Next.js
  • Nuxt
  • Vue.js
  • Tailwind CSS
  • shadcn/ui

Architecture

  • Retool
  • Internal Tools
  • Workflow Apps
  • APIs
  • GraphQL
  • Drupal
  • Headless CMS

Communication

  • English
  • Japanese
  • Bahasa Indonesia
  • Discovery
  • Demo
  • Technical Storytelling
  • Stakeholder Alignment

  • Frontend Engineering

    I care about state, performance, accessibility, design systems, and maintainable UI.

  • Solution Architecture

    I map real business workflows into scalable internal tools, Retool apps, workflows, and operating surfaces.

  • Trilingual Communication

    I work across English, Japanese, and Indonesian contexts, with experience in teaching, translation, interpretation, and client-facing delivery.

Work / Case Studies

SELECTED_WORK

A curated collection of internal tools, frontend systems, and solution architecture work built with clarity, usability, and business context in mind.

  • CASE STUDY 01

    Retool Internal Operations App

    Internal workflow application for managing business operations, approvals, and operational visibility.

    • Retool
    • Workflow
    • Internal Tools

  • CASE STUDY 02

    Enterprise Dashboard & Admin Surface

    Dashboard and admin experience designed around real user behavior, decision-making, and maintainable frontend patterns.

    • Frontend
    • Dashboard
    • UX

  • CASE STUDY 03

    Sales Demo & Solution Prototype

    Interactive prototype used to make abstract business pain concrete and support stakeholder alignment.

    • Demo
    • Prototype
    • Solution Architecture

What I build

WHAT I BUILD

Internal software for teams that have outgrown spreadsheets, manual approvals, and fragmented tools.

  • Retool internal apps

    Internal apps that connect data, workflows, and business logic into one usable operating surface.

    Outcome: Less context switching, clearer ownership, faster operations.

  • Workflow applications

    Workflow apps that make state, ownership, actions, and review steps visible.

    Outcome: Fewer manual steps, fewer hidden dependencies, better operational control.

  • Dashboards and admin surfaces

    Dashboards, admin panels, and decision tools that match real user behavior.

    Outcome: Better visibility, faster decisions, and fewer fragile workarounds.

  • Frontend systems

    Frontend systems with reusable components, consistent patterns, and maintainable architecture.

    Outcome: More consistent delivery, cleaner implementation, and better user experience.

  • Sales demos and prototypes

    Demos and prototypes that turn abstract business pain into something concrete and testable.

    Outcome: Clearer conversations, faster alignment, stronger solution confidence.

TRILINGUAL

English, Bahasa Indonesia, and Japanese — for work that crosses teams, cultures, and expectations.

I work across English, Bahasa Indonesia, and Japanese. That matters because solution architecture is not only about systems. It is about helping people understand the problem, trust the plan, and adopt the software.

ENGLISH

For global teams, technical explanation, and clear written communication.

BAHASA INDONESIA

For cultural fluency, personal grounding, and communication across Southeast Asian contexts.

日本語

For Japanese business settings, client conversations, and day-to-day collaboration in Tokyo.

Alignment

  • Client clarity

    I can explain technical decisions in language that business stakeholders can actually use.

  • Cross-cultural alignment

    I can move between global expectations and Japanese enterprise communication styles.

  • Technical storytelling

    I can turn unclear workflow problems into demos, diagrams, and explanations that make the solution easier to believe.

How I work

HOW I WORK

Fast enough to prototype. Structured enough for enterprise.

A practical six-step approach for turning messy workflow problems into software people can actually use.

  1. 01

    Diagnose

    Clarify the real business pain, not just the requested screen.

  2. 02

    Map

    Turn workflows, users, permissions, data, and edge cases into a solution model.

  3. 03

    Prototype

    Build the fastest useful version to make the discussion concrete.

  4. 04

    Design the experience

    Make the tool understandable, usable, and consistent with real user behavior.

  5. 05

    Harden

    Handle auth, data flows, validation, errors, review states, reliability, and maintainability.

  6. 06

    Enable

    Demo, document, train, gather feedback, and iterate after launch.

LET'S TALK

Have a workflow that deserves better software?

I can help map it, prototype it, build it, and explain it to the people who need to believe in it.