Designer who thinks
like a builder.
I grew up in Yogyakarta, surrounded by batik patterns and pixel-art games in equal measure. Both taught me the same thing: good systems have rhythm, and every detail either earns its place or leaves.
The path so far.
Born in Yogyakarta, raised on patterns.
Yogyakarta, Central Java
Yogyakarta is a city that takes craft seriously. Growing up surrounded by batik workshops and wayang puppet theater taught me early that design is never decoration — it's a language. My parents ran a small textile business; I spent afternoons watching dye patterns repeat across fabric, learning how systems create beauty without anyone trying to be beautiful.
Computer Science at UGM. Fell into design by accident.
@ Universitas Gadjah Mada
I enrolled in CS for the problem-solving, but a second-year HCI elective changed everything. I spent six hours building a wireframe that should have taken thirty minutes — and I didn't notice the time passing. That was the moment. I started volunteering to do UI work on every group project, then picked up freelance identity work for student organisations on the side.
Junior designer. Shipped more in 6 months than expected.
@ Startup (Jakarta)
Moved to Jakarta straight after graduation during a pandemic — not ideal timing, but it meant hiring was digital and geography didn't matter. Landed a junior role at a logistics startup where I was the only designer. Brutal, but I learned to work with ambiguity, ship fast, and defend design decisions to engineers who had every right to be skeptical of a new grad.
Astra International. Scale, systems, and learning to lead.
@ Astra International — Jakarta
Joining Astra meant designing for 200+ internal users across a complex operational domain. I built my first real design system from scratch, ran usability tests with people who had never seen a prototype before, and learned that good UX at enterprise scale is 40% design and 60% stakeholder management.
Senior designer. Open to what's next.
Jakarta, Indonesia
Currently working on a mix of product design, design ops, and the occasional brand project. I'm interested in roles where design sits close to the product and engineering team — where I can see the thing I designed actually ship.
How I work.
I don't drop deliverables over the wall. The best work I've done has been in tight loops with engineers and product — where the spec evolved in Figma and in code at the same time.
My default move when something feels complicated is to remove a layer, not add one. Complexity is usually a sign that the problem isn't understood yet.
Perfect is the enemy of learning. I'd rather put a 90% solution in front of real users than spend another sprint polishing something nobody's tested.
and product design roles.
Jakarta-based, open to remote. I work best on 0→1 product problems and systems that need to scale. If you're building something that deserves thoughtful design, let's talk.