Start with the workflow
Map who uses the system, where work gets stuck, and what needs a person's approval. Set the scope before asking an agent to build.
I'm Fery. I design applications and the workflows around them, using AI to help plan, implement and review. I set the constraints and check the result.
AI helps with planning and implementation. I keep the design decisions explicit and check the result against the original need.
Map who uses the system, where work gets stuck, and what needs a person's approval. Set the scope before asking an agent to build.
Define system boundaries and data flow. Record failure paths and release checks, so the plan explains how the system will run.
Use AI to turn a reviewed plan into small changes. Give each task a clear scope and acceptance criteria, with isolated workspaces where needed.
Review the changes and test the user's workflow. An agent's completion message is a claim to check; passing unit tests alone can still miss a broken first run.
Human approval in marketing automation. Task isolation in coding-agent tools. Application architecture and release automation for edbot.ai.
I designed the path from staff updates to draft posts, with human approval required before publication. Built on AWS Bedrock.
live tools on Solve Education's automation platform in one quarter.
I designed a coding-agent orchestrator with isolated git worktrees and task closure based on passing project checks. Architecture decisions live in ADRs.
Local-first memory built from agent transcripts. Events and read progress commit in one SQLite transaction, so interrupted capture can resume.
I owned the frontend architecture of edbot.ai, which delivered 32M+ lessons across 10+ countries. I also introduced the team's first CI/CD pipeline and end-to-end tests.

A benchmark can reward a forecaster for reporting something other than what it believes. We examine why, test the mechanism in simulation and practice tasks, and propose normalization fixed before the outcome.
Per-Outcome Baseline Normalization Makes Proper Forecast Scores ImproperFery Yundara Putera and Bramantya Farid Prakoso.Accepted for poster presentation at Agenthon 2026: Verifiable AI for Quantitative Finance, a workshop at NeurIPS 2026.
Workshop details ↗Personal products I designed and shipped solo, each with a different workflow and platform constraint.

Mac cleaner with a Safe or Moderate label on every item. 9 scan categories, $12 once.

A 30-day guided reset for prayer consistency. Donation-based, nothing paywalled.

Daily basketball plans for 6 player types, with audio drills and an Elite tier.

Alarms that fire even in Doze mode or after a reboot. No account, no network.
Senior Software Engineer. I lead the AI automation platform and built the team's AI coding-agent setup. Before that I owned edbot.ai's frontend and built the team's first CI/CD.
Backend Developer. Maintained three live client projects for teams in Singapore and Indonesia. Certified in Sitefinity CRM.
Software Developer. C# microservices and two AngularJS web apps, Spain and Indonesia.
.NET Developer. Dealer management system used in every main branch office.
I'm open to a full-time remote role, and to project-based or freelance work. Both follow the same process: define, design, build with AI, verify.
Application and AI systems design, with responsibility for delivery. My working day overlaps with Asia, Australia and the European morning.
A project with a clear finish line: a new product, an AI workflow or a rebuild. You get a written plan before any code, working software at each step, and a handover your team can run.
Workflows that do the routine work and wait where a person must decide. Proof: a marketing workflow on AWS Bedrock that can't publish without approval.
Web and mobile products shipped end to end. Proof: four apps I designed and released solo on macOS, iOS and Android.
Shared rules, required checks and delivery commands, so agent work passes review. Proof: the setup my team uses today.
Tell me what you want to build, as a project or a full-time role. I reply within 24 hours with questions and a first take on scope.
Or email feryyp.work@gmail.com