Backend Developer • Myanmar

Kyaw
Kyaw Htet

I build backend systems, APIs, dashboards, and occasionally spend hours tracking down a bug that turns out to be a missing comma.

Checking logs for Yangon telemetry...
“Most software problems don't start in code. They start in conversations.”
01

How did I become a developer?

I studied Mechanical Engineering before moving into software. Today I build production applications used by real businesses, mainly focusing on backend systems and integrations.

02

What do I actually build?

Laravel applications, NestJS APIs, travel booking integrations, dashboards, automation tools, and systems people rely on every day.

03

What have I learned from production?

Logs are usually more honest than meetings. The best code is rarely the cleverest code. Simple solutions tend to survive longer.

04

What have I worked on?

Travel booking systems, flight pricing engines, SOAP and REST integrations, reporting dashboards, financial calculations, enterprise systems, and more XML than I would like to admit.

05

What technologies do I use?

Laravel, NestJS, PHP, TypeScript, JavaScript, MySQL, PostgreSQL, Linux, AWS, Docker and Git.

06

What keeps me interested?

Learning. Not necessarily new frameworks, but understanding systems more deeply and becoming better at solving real problems.

07

What is it like working with me?

I ask a lot of questions. I prefer simple solutions over clever ones. Before blaming the code, I check the logs.

08

A few things that describe me.

Self-taught developer.
Mechanical Engineering background.
Laravel enthusiast.
NestJS explorer.
Linux user.
Professional log reader.

“I like understanding how things work. That's what brought me from machines to software.”

Let's Talk.