Backend developer, now in Japan
I build backend systems in the part of reality where requirements, legacy code, and delivery pressure all exist.
I am a C#/.NET developer with experience in government platforms, emergency dispatch software, legacy modernization, and modern backend ownership from requirements to deployment.
Why this profile
I am useful when the system is larger than the happy path.
Modern .NET backend ownership
I can take a backend from rough requirements to working service: API shape, PostgreSQL/EF Core persistence, authentication, CI/CD, tests, and explicit error behavior.
Legacy systems that still have to ship
I have worked in large .NET Framework, WPF, WCF, IIS, SQL Server, stored-procedure-heavy systems where progress meant careful modernization, not assuming a rewrite was available.
Public-sector delivery context
My strongest projects were real public-sector systems: emergency dispatch, government services, archive systems, and assessment tools with concrete constraints around delivery and correctness.
Fit
The roles I want should have actual engineering weight.
I am preparing for a future job search in Japan while improving my Japanese. The target is not a decorative title or a generic web profile; it is backend work where I can own decisions, understand the domain, and leave the system easier to operate than I found it. My core is backend engineering, but I do not stop at artificial boundaries when the problem needs a wider view.
- C#/.NET backend roles where ownership matters more than ticket-passing.
- Systems with domain complexity, integrations, legacy constraints, or public-service pressure.
- Work where crossing boundaries into frontend integration, deployment, databases, scripts, or unfamiliar tooling is useful.
- Teams that value direct technical judgement, maintainability, and practical delivery.
Selected work
The proof is in the systems.
Unified Contact Center Platform
A large emergency-service platform where the useful work was making a difficult system buildable, extendable, and shippable under real constraints.
State Probation Service
A from-scratch backend for a public-service assessment system, with versioned tests, JSON scoring rules, explicit errors, auth, and deployment ownership.
Government Services
Backend rescue work across public-sector services: project-template migration, auth stabilization, framework upgrades, and a data-leak fix.