I'm a Software Engineer from Peru, working remotely on fintech software since January 2026.
Most of my day-to-day work is backend-oriented with .NET and C#, but I also work across Angular and TypeScript when a problem crosses the product. What I enjoy most is the investigation behind a good fix: tracing assumptions, narrowing a bug to the right layer, making contracts explicit, and validating that the behavior really changed.
Portfolio · LinkedIn · Link hub · Email
Since January 2026, I've been building and maintaining fintech software with .NET/C# and Angular/TypeScript.
My work has included debugging behavior across layers, tightening authorization boundaries, coordinating contract changes between services, and validating fixes with tests, compiler feedback, and static analysis. The company code is private, so I keep the details sanitized and focus here on the engineering patterns I can discuss responsibly.
A local-first .NET MCP server for preserving, retrieving, and updating structured knowledge in Obsidian vaults across AI-agent sessions.
I maintain the project across MCP contracts, retrieval, testing, security boundaries, CI/release automation, and technical documentation.
Repository · Documentation · Releases
A Bash automation tool that retries Oracle Cloud ARM Always Free capacity, rotates Availability Domains, adds jitter between attempts, and supports unattended execution with notifications.
It is a smaller project than Kioku, but it shows another side of my work: turning an annoying operational problem into a reproducible tool.
Yukidoke is a private household personal-finance product with a modular .NET API and an Angular client. It is currently in active V1 hardening, so I use it as private product/architecture practice rather than presenting it as a finished public product.
- I try to understand the assumption behind a bug before I touch the fix.
- I use compiler/type feedback, tests, and static analysis to find hidden consumers and make changes easier to reason about.
- When new evidence contradicts my first conclusion, I change the conclusion instead of forcing the evidence to fit it.
- I write down useful decisions and lessons so the next investigation starts with more context.
Backend & APIs
Frontend
Data
Tooling
The tools change over time. The part I want to keep improving is the reasoning: understanding constraints, making trade-offs explicit, and building software that is easier to change safely.
I'm currently finishing my thesis, building open-source tools, improving my English, and preparing for international opportunities.
Away from engineering, you'll usually find me around books, Japanese culture, music, or games.
If you're reviewing my GitHub after seeing my profile or application, the best place to get the full picture is my portfolio. You can also reach me on LinkedIn or at hello@sandovaldavid.com.