Frontend Engineering
I care about state, performance, accessibility, design systems, and maintainable UI.
Tokyo, JapanRetool — Internal ToolsEN / JA / ID
ScrollABOUT ME
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
SKILLSThe 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
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.
Selected work
SELECTED WORKWork / Case Studies
A curated collection of internal tools, frontend systems, and solution architecture work built with clarity, usability, and business context in mind.
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.
TRILINGUAL
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.
01 Diagnose
Clarify the real business pain, not just the requested screen.
02 Map
Turn workflows, users, permissions, data, and edge cases into a solution model.
03 Prototype
Build the fastest useful version to make the discussion concrete.
04 Design the experience
Make the tool understandable, usable, and consistent with real user behavior.
05 Harden
Handle auth, data flows, validation, errors, review states, reliability, and maintainability.
06 Enable
Demo, document, train, gather feedback, and iterate after launch.
FAQ
FAQQuick answers
- Who is Geryenko Hawsen?
- Geryenko Hawsen (Gery, ゲリー) is a Tokyo-based Solution Architect who mainly uses Retool. He has frontend engineering roots and builds internal tools, workflow applications, and dashboards that bridge engineering, business, and customers.
- What does Geryenko Hawsen do?
- He designs and builds internal software for teams that have outgrown spreadsheets and manual processes — Retool internal apps, workflow applications, dashboards and admin surfaces, frontend systems, and sales demos.
- What languages does Gery speak?
- Gery is trilingual: English, Japanese, and Bahasa Indonesia. He works across global teams, Japanese business settings, and Southeast Asian contexts.
- What technologies does Gery work with?
- His core platform is Retool. His frontend stack includes TypeScript, JavaScript, Next.js, Nuxt, Vue.js, Tailwind CSS, and shadcn/ui, plus GraphQL, Drupal, and headless CMS architectures.
- Where is Gery based?
- Gery is based in Tokyo, Japan, and works with both Japanese and international teams.
- How can I get in touch with Gery?
- The best way to reach Gery is LinkedIn (linkedin.com/in/geryenkohawsen). His code is on GitHub (github.com/geryenkohawsen) and his articles are on Qiita (qiita.com/geryenkohawsen).
LET'S TALK
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.