👋 I'm Faldy. Teams hand me the vague, expensive problems — the ones where nobody agrees what's actually broken yet — and I turn them into systems that hold.
I solve problems. Backend is where I keep my tools.
Systems thinking
Deep debugging
Pragmatic architecture
Measured decisions
Problems
I've solved
Each one started as something nobody could name yet. Here's what was actually wrong, and what it took.
Problem solving
Problem solving
Problem solving
Problem solving
How I actually work
Most engineering problems are not code problems. They are unclear problems wearing a code costume. I start by finding out what is genuinely broken — the query, the contract, the assumption, or the way the team framed it — and only then decide what to build. More often than you'd think, the answer is less code.
Diagnosis
Architecture
Performance
Delivery
Mentoring
Data pipelines
API platforms
LLM integration
Cost control
Developer velocity
8+
Years turning vague problems
into systems that hold
50%
Faster response time on the
endpoints that mattered most
40%
Cut from the cloud bill
without cutting capacity
40%
More order volume after the
Open API platform shipped
Performance & scale
Data pipelines
API & platform design
LLM integration
Cost & infrastructure
Developer velocity
Experience
Tech Lead
at EngageRocket
Lead the Dashboard Squad, overseeing the end-to-end development of the company's core analytical reporting tools and data visualization features.
Jul 2025 — Present
Senior Software Engineer
at EngageRocket
Engineered the backend integration leveraging Dashboard analytics, enabling users to translate data insights into trackable business actions.
Feb 2025 — Jun 2025
Senior Software Engineer
at A Job Thing
Optimized and improved the job search engine system utilizing Elasticsearch.
Aug 2024 — Feb 2025
Principal Engineer
at Lifepack.id
Designed and developed a custom API gateway, resulting in faster development cycles for the new microservice architecture.
Apr 2023 — Jun 2024
The toolbox
Tools serve the problem. This is what I reach for most.
Languages
Infrastructure & Tools
Writing
Notes from the debugging: what broke, what I assumed, and what the fix turned out to be.
Got a problem that won't sit still?
If something in your system is slow, expensive, or nobody can agree why it's broken — that's the conversation I enjoy most. Email is the fastest way to reach me.