I ended up building systems because I kept living inside broken ones.
I'm Christine Anastacio, an AI Solutions Engineer based in the Philippines. My path into engineering ran straight through the operational messes most software is supposed to prevent.
Early on, my work was the unglamorous operational layer: reconciling files that never quite matched, chasing confirmations across inboxes, and rebuilding the same report by hand every week. The pattern was always the same. The problem wasn't a lack of effort or talent. It was a lack of dependable systems.
So I started building them. I taught myself Python, JavaScript, APIs, and data pipelines, and began turning the processes I understood from the inside into automation that ran on its own, with validation, evidence, and a clear status a human could trust.
That operations-first perspective is still how I work. I don't start with a framework; I start with how the work actually happens: where information enters, where people lose time, which exceptions matter, and what a reviewer needs to sign off. The code comes after that's clear.
Today I focus on AI-assisted and agentic systems, with the same discipline. AI is added only where it genuinely improves a workflow, never where it hides how a decision was made.
- Based in
- Philippines, remote-friendly
- Focus
- Automation, data engineering, AI-assisted systems
- Core stack
- Python, APIs, SQL, data pipelines, JavaScript
- Status
- Open to engineering roles
From the front line to the build side
My route into engineering wasn't a straight line, and I think that's exactly why I build the way I do.
Customer care
I started on the front line in customer care, where you feel every broken process the moment it reaches a real person. It taught me to listen for the problem underneath the complaint.
Team lead
Leading a team, I kept seeing the same manual workarounds pile up day after day. Instead of just managing around them, I started digging into why the workflows kept breaking.
AI Solutions Engineer
When AI started booming, I switched paths for good, and I genuinely love it. Now I build the systems that make those front-line problems disappear, with the empathy of someone who lived them.
The kind of engineering I want to do
Understand before automating
The best systems come from understanding the real process, not from bolting tools onto a problem nobody mapped.
Make the reasoning visible
Outputs should carry their evidence. Anyone reviewing a result should be able to see why it turned out that way.
Build things people can maintain
Clear code, sensible structure, and documentation so the system outlives any single person, including me.
Keep humans in the loop
Automation should give people leverage and confidence, not remove their judgment from decisions that matter.
Think we'd work well together?
Tell me about the role and the problems your team is solving, or just book a quick call.