Software Engineer
Backend-oriented Software Engineer working remotely from Peru, currently building and maintaining fintech software with .NET, C#, Angular, and TypeScript.
I connect technical decisions with business rules, product needs, validation, and maintainability. I document the reasoning behind the work so problems, trade-offs, and lessons become reusable technical knowledge.
Backend engineering · Product-aware development · Open source · Developer tooling
Kioku is a local-first .NET MCP server for preserving and retrieving structured knowledge from Obsidian vaults across AI-agent sessions.
AI agents ↔ MCP ↔ Kioku ↔ Markdown and YAML ↔ Obsidian vault
I design and maintain the project across MCP contracts, retrieval, automated testing, CI, security, documentation, and release automation. Stable releases and active development are documented separately so features and evidence remain branch-aware.
Evidence
Yukidoke is a private household personal-finance application built with a modular .NET API and an Angular client, with financial rules and permissions owned by the backend.
Keycloak identity · PostgreSQL system of record
.NET domain authority · Angular presentation
I design and maintain the product across backend, frontend, architecture, testing, documentation, and cross-repository contracts. The V1 API is feature-complete by backend criteria, while the Angular client remains in active beta and is migrating toward server-authoritative financial behavior.
Evidence boundary
- The source repositories and current deployment are private.
- No public production use, adoption, revenue, or external-user results are claimed.
- The project demonstrates architecture, household privacy, financial consistency, testing, and coordinated Angular/.NET development.
Problem → Research → Alternatives → Decision → Implementation → Validation → Learning
- Break complex problems into manageable parts and investigate constraints before deciding.
- Connect implementation choices with product needs, business rules, and explicit sources of truth.
- Build for maintainability, testing, reproducibility, and operational clarity.
- Turn project work, errors, and decisions into reusable technical knowledge.
- Keep claims bounded by the evidence that can be reviewed.
- Backend:
C#·.NET·APIs·Model Context Protocol - Frontend:
Angular·TypeScript - Engineering:
automated testing·CI/CD·containers·documentation·developer tooling - Data:
relational databases·document databases - Domain experience:
fintech·financial workflows
These technologies describe my current working context. Public repositories, releases, tests, pull requests, and documentation are the primary evidence.
I am deepening my backend engineering practice, increasing responsibility through verifiable work, contributing to open-source tooling, and preparing for international opportunities.
Longer term, I aim to grow toward technical leadership and building technology products, supported by progressively stronger evidence and responsibility.