BANGKOK, THAILAND / THEERAWEE RANGRAM

An architect
at heart.
An engineer
by craft.

Before I built systems,
I imagined spaces for people.

Boom · AI Engineer & AI Solutions Architect

I design and build AI experiences that make complex work feel clear, approachable, and inviting to use.

9+ years in software deliveryConnect on LinkedIn
A luminous purple woven membrane folds above a flowing network landscape.
Living architecture · 00
ONE PERSON. ONE DRAWN LINE. A PLACE BUILT FOR PEOPLE.01 / THE STORY BELOW ↓

01 / THE FIRST BLUEPRINT

Before AI · the urge to design

A blank page.
A world waiting
to happen.

As a child, I wanted to be an architect—to design spaces people could step into and inhabit.

  1. 01Imagine a place
  2. 02Draw the first lines
  3. 03Turn the drawing into an interface

That early pull toward design stayed with me when I chose to study software engineering. Frontend became my creative space—a place where code took visible form, where people could touch, test, and make it their own.

I care about the character of what I build. The proportion of an interface, the rhythm of its interactions, and the clarity of its next step all shape how it feels to use. Software simply gave that same architectural impulse a different medium.

Architecture at heartFrontend by craft
Designing for a screen was only the start; real software has to hold its weight in daily use.What happens when people begin to rely on what you build?
A symbolic maker sketches an architectural blueprint above a woven landscape before the lines shift into a software interface.
Living architecture · 01

02 / FOUNDATIONS

Before AI · frontend foundations

A beautiful idea
has to hold up.

Frontend that has to work as part of a system people depend on.

  1. 01Build one component
  2. 02Fit it into a larger system
  3. 03Make it dependable

Enterprise frontend work at Allianz Technology gave my interest in design a practical discipline. A single screen is never an island; it lives inside a larger application with strict requirements, shared standards, and real users relying on it.

Collaborating across teams in Munich and Bangkok taught me to look beyond surface polish. The quiet details a user never consciously notices are often the ones an engineer has to get right.

Allianz TechnologyAngular and enterprise frontend development, working with stakeholders and engineering teams in Munich and Bangkok.

AngularEnterprise frontendMunich ↔ Bangkok
Reliable components are only half the craft; they still have to fit into a wider architecture.How do you build when your screen is just one piece of a much larger effort?
A symbolic maker shapes a single component, connects it to a wider structure, and inspects its details above a woven landscape.
Living architecture · 02

03 / CONNECTIONS

Before AI · working across a larger system

The world grows
beyond your screen.

What I built on screen had to connect with other people’s work.

  1. 01Listen to the requirement
  2. 02Connect across boundaries
  3. 03Bring the pieces together

Corporate banking work at Accenture sat right where business intent meets hands-on engineering. My role lived inside a shared delivery effort—listening closely to what stakeholders actually needed, translating those requirements into frontend architecture, and building alongside engineers across locations.

When squads work across different places, shared clarity matters just as much as clean code. It trained me to see the whole structure first, so the piece I owned would fit naturally into everyone else’s.

AccentureCorporate-banking frontend delivery, translating stakeholder requirements and collaborating with distributed engineering squads.

Corporate bankingRequirementsDistributed teams
In 2024, while I was still working at ttb, I began developing my AI capabilities.What if intelligence could become part of the workflow?
A symbolic maker studies a brief, links nodes across a network, and assembles separate parts into a shared structure above a woven landscape.
Living architecture · 03

04 / THE POSSIBILITY BECOMES PERSONAL

Beginning AI development while still working at ttb

I could see it.
I wanted to build
something to try.

I began developing my AI capabilities while I was still at ttb. What I believed still needed to take shape as something people could test in real work.

  1. 01See something worth building
  2. 02Put the belief to the test
  3. 03Build something people can try

Some people around me were not yet convinced, including people working in the same field. I wanted to give them something they could actually try. My belief alone could only take the idea so far.

I started with the work in front of me: bringing GPT into Jira, Confluence and Bitbucket workflows, with people reviewing the outputs. The possibility I had imagined began to present real problems I had to work through.

A model’s answer was a starting point. I still needed to understand where it came from, what was missing, and where a person should stop and inspect it. Working through those details showed me the distance between an answer and a tool someone could trust enough to use.

ttb sparkSenior software engineering in banking, including frontend delivery. Began developing AI capabilities in 2024 while at ttb, with GPT-assisted Jira, Confluence and Bitbucket workflows and human review.

I wanted to give them something to try before asking them to believe.
Jira · Confluence · BitbucketHuman review
Beneath the visible progress lay real friction—edge cases, false starts, and moments when the path forward was unclear.What did I do when I could not yet see the next step?
A symbolic maker brings an AI element into the workflow, pauses to inspect the output, and decides what moves forward above a woven landscape.
Living architecture · 04

05 / ANOTHER SIDE OF THE BEGINNING

A closer look at the AI work that began at ttb

Not everyone
saw it yet.
I kept building.

As I began learning and developing AI, some people around me did not yet see the same possibility.

  1. 01Hold on to the possibility
  2. 02Meet the resistance
  3. 03Stay with the problem
  4. 04Return to the work
  5. 05Keep the light alive

Even peers in the same discipline were unconvinced—and fairly so, while the idea existed mostly in theory. To make it tangible, I started building on my own, working through each obstacle one piece at a time.

Every skill and workflow I create traces back to those hands-on encounters. I test an approach against a real problem, examine where it breaks, look for sharper methods, and return to refine the next version. Week after week, that steady cadence became HolyMind.

Every difficult part asked something of me. Every return to the work left something I could build on.
Independent explorationContinuous refinement
The problems I encountered gradually became lessons I could carry into the next piece of work.How does a lesson become a skill with a character of its own?
A symbolic maker protects a small light while the surrounding network closes in and fragments. In the quiet that follows, the pieces gather into a repaired path and the maker rises.
Living architecture · 05

06 / EXPERIENCE, DISTILLED

Lessons gathered through developing AI

The problem
becomes part
of the craft.

I let my experience developing AI settle, then ask what is worth keeping.

  1. 01Keep the lesson
  2. 02Look beyond my own methods
  3. 03Distil a capability
  4. 04Build a distinctive advantage

Once a lesson holds up in practice, I look outward. I study research, engineering patterns, and tools from around the world, selecting and combining the strongest methods I can find for the problem in front of me.

Through repeated testing and trimming, each skill earns its own purpose, method, and character. Connected into workflows, those capabilities give new work a stronger foundation from the start.

That is the moat I am building: not a secret shortcut, but lived experience, deliberate curation, and revision after revision until a capability proves its worth in real use.

  1. Encounter
  2. Reflect
  3. Research
  4. Synthesize
  5. Refine

A visual metaphor for learning and synthesis. The scenes are symbolic, not documentary recreations.

Follow these capabilities into the work
PurposeMethodCharacter
All that depth still needs a way for someone to reach it.How do you make all that complexity feel human?
A symbolic maker examines a distilled lesson, draws methods from surrounding sources, and assembles them into a structured skill above a woven landscape.
Living architecture · 06

07 / WHERE IT COMES TOGETHER

Today · design, software and AI together

The soul of
AI experiences.

I want people to feel the possibility, without carrying all the complexity.

  1. 01Face the hidden complexity
  2. 02Shape a clear way in
  3. 03Give the person agency
  4. 04Make the experience inviting

Working with AI brings my frontend instincts and software engineering background together in a wider creative space. I can shape both the underlying machinery of a tool and the way someone enters, understands, and works with it.

The interface should absorb the heavy complexity behind the scenes while keeping the next step clear, the interaction inviting, and the person in control. Reasoning, sources, and moments for human review remain within reach whenever they are needed.

Thoughtful design opens the door, but care in every detail of use is what makes people want to return. To me, that is the heart of AI experiences.

Independent AI Solutions ArchitectAI-assisted product architecture and development using React, FastAPI and PostgreSQL access controls. Translate requirements into product specifications, source-backed outputs and explicit review paths.

Explore beneath the surface
01 / Experience

A clear starting point, meaningful feedback, and a next step you can understand.

02 / Orchestration

Applications, models, and tools connected around the task.

03 / Review & access

Explicit permissions, inspectable sources, and human review paths.

An illustration of my design approach, not a live system diagram.

ClarityAgencyTrustEngagement
The work comes full circle: making a place someone wants to enter.What happens when you step inside?
A cutaway reveals layered architecture beneath the surface before a symbolic maker opens a clear threshold for another person to enter.
Living architecture · 07

08 / OPEN TO EXPLORATION

Current public work

Now, step inside.

HolyMind interactive portfolio

  1. 01Open the door
  2. 02Make the work inspectable
  3. 03Offer the next possibility

Step into a browser-based demonstration of how human intent, workflow boundaries, and interface design work together. Explore three illustrative scenarios, trace fictional source-to-output examples, and carry your selections into a planning brief.

This is a portfolio demonstration, not a live agent service or a claimed client result. Its browser behavior is open to inspect here; client source code, private records, and confidential documents are never published.

FOLLOW A CAPABILITY INTO THE WORK

Make work reviewableFrom a repeated task to a decision someone can inspect.
  1. Problem

    A repetitive request still needs an accountable owner and a clear review boundary.

  2. Design choice

    Make the draft, missing information and next decision visible together.

  3. Workflow

    Explore the repetitive-work scenario, inspect the example input, then review the proposed output.

  4. Explore the work

Keep the source in sightFrom scattered information to an answer you can trace.
  1. Problem

    A confident answer is difficult to assess when its supporting information is hidden.

  2. Design choice

    Keep claims connected to approved excerpts and leave unsupported facts unanswered.

  3. Workflow

    Open the scattered-knowledge scenario and follow a draft claim back to its fictional source.

  4. Explore the work

Carry intent into the next stepFrom an interesting capability to a brief with a purpose.
  1. Problem

    Exploring a collection should lead somewhere useful when a capability catches your attention.

  2. Design choice

    Keep the visitor’s scenario and chosen skill connected to the next conversation.

  3. Workflow

    Choose a scenario, explore a HolyMind skill, then carry that skill into the starting brief.

  4. Explore the work

InputWorkflowOutput
Every interface choice here is grounded in years of building software for real teams.See the work and responsibilities behind the story.
A symbolic maker opens an interface threshold, highlights points for human review, and offers the work outward for inspection.
Living architecture · 08

09 / THE PROFESSIONAL VIEW

Experience,
at a glance.

The maker stands and reflects on the experience behind the work.
Living architecture · 09

Selected experience, most recent first. Detailed CV and project context are available in a recruiter conversation.

HolyMind

34 skills shaped through practice.

Read all 34 skills

Reason

  • Angle agentsSee a challenge from several perspectives.
  • Spec before buildDefine the specification clearly before building.
  • Decision cardMake the trade-offs easy to inspect.
  • Choose a skillFind a useful place to start.
  • Calibrated inferenceKeep assumptions visible.
  • Resolve a deadlockFind a way forward when options clash.
  • Dual-agent debateGive a proposal a thoughtful challenge.
  • Plan modeLook ahead before taking action.
  • Scope bridgeConnect related contexts clearly.
  • Seed expansionGrow a useful lead into a wider view.
  • Triad techniquesExamine a problem through three lenses.
  • The crystallizerTurn scattered thinking into a clear takeaway.
  • Workflow blueprintGive the work a practical structure.

Build

  • Goal-driven executionKeep the business outcome in sight.
  • MCP orchestrationCoordinate tools around a shared goal.
  • Subagent fanoutExplore independent tasks in parallel.
  • Environment setupPrepare the context for focused work.
  • Task offloadHand over a well-defined piece of work.
  • Context thriftKeep the useful context close.
  • Skill sequencingPut the next steps in a useful order.
  • Enhancement engineImprove what matters most.
  • Pause and resumeKeep coordinated work under control.
  • Structured Thai outputMake the answer clear in Thai.
  • Context handoffCarry the important context forward.
  • Workflow executionMove from a plan to the next action.

Verify

  • Chain of verificationCheck a claim against its evidence.
  • Grounded synthesisBring sources together without losing them.
  • Hindsight reviewJudge a result against the original question.
  • Constraint discoveryLearn what the system must respect.
  • Evaluate and improveTurn feedback into a better next version.
  • Evidence manifestKeep the proof easy to trace.
  • Pre-registered triggersSet decision criteria before the result.
  • Skill inspectionLook closely at how a capability is defined.
  • WatcherKeep attention on important changes.
Explore the HolyMind collection
01

Independent AI Solutions Architect

AI-assisted product architecture and development using React, FastAPI and PostgreSQL access controls. Translate requirements into product specifications, source-backed outputs and explicit review paths.

02

ttb spark

Senior software engineering in banking, including frontend delivery. Began developing AI capabilities in 2024 while at ttb, with GPT-assisted Jira, Confluence and Bitbucket workflows and human review.

03

Accenture

Corporate-banking frontend delivery, translating stakeholder requirements and collaborating with distributed engineering squads.

04

Allianz Technology

Angular and enterprise frontend development, working with stakeholders and engineering teams in Munich and Bangkok.

Where I can contribute

AI Solutions Architect

Translate business requirements into system boundaries, integrations, access controls and a delivery plan.

AI Engineer and GenAI Engineer

Build AI-assisted workflows that connect models, tools and existing applications, with evaluation and human review.

Forward Deployed Engineer

Bring customer-facing requirements, hands-on software delivery and international stakeholder coordination into one implementation conversation.

AI Transformation Consultant

Identify a useful first use case, define the workflow and governance, and agree how its results will be evaluated.

These are relevant roles to discuss, not a list of job titles I have held. Scope, availability and commercial terms are agreed in conversation.

For recruiters & teams

Where is Boom based?

Bangkok, Thailand. My enterprise background includes collaboration with teams in Bangkok and Munich.

Is the experience all AI research?

No. My background is enterprise software delivery; I began developing AI capabilities in 2024 while at ttb. My current focus is applied GenAI, AI solutions architecture and agentic automation—not a claim of nine years of foundation-model research.

How can I discuss a role or request a CV?

Use LinkedIn with the role, team, location and problem you need solved. We can discuss fit and the appropriate supporting project context.

10 / THE NEXT CHAPTER

I still build places for people. The medium has changed.

What could we
make possible?

Bring the problem your team is trying to solve. Let’s explore an AI experience people can understand, trust, and want to use.

Return to the first line
The symbolic maker opens a curved woven space for people, recalling the first architectural drawing.
Living architecture · 10