When a problem crosses layers, I trace the affected flow through callers, services and data before choosing the change. If the system cannot determine the correct state safely, I prefer an explicit error to silently returning a plausible but wrong answer.
CAREER · CURRENT ROLE
Atena
Jr. Software Engineer
At Atena, I work mainly on .NET backend services and also contribute to an Angular administrative frontend in an existing fintech product.
CURRENT FINTECH Jan 2026 – Present
Official website opens in a new tab SELECTED CONTRIBUTIONS
- 01 Work mainly on .NET backend services and also contribute to an Angular administrative frontend in an existing fintech product
- 02 Implement and maintain API, authorization, integration and frontend changes across existing product workflows
- 03 Coordinate contract changes when backend services and frontend or service consumers need to evolve together
- 04 Use tests, compiler feedback and static analysis to identify affected code and validate regression-prone changes
WORKING ON EXISTING SYSTEMS
Backend services, frontend features and integrations
DEBUGGING
Debugging across service and data boundaries
AUTHORIZATION + INTEGRATION
Authorization and service integration
Authorization and contract changes can affect more than one consumer. I check tenant scoping and the callers that depend on the behavior so backend, frontend and service consumers evolve together when a contract changes.
VALIDATION
Regression validation
I use tests, compiler feedback and static analysis to identify affected code and check the behavior I changed. For regression-prone fixes, I sometimes remove the change temporarily to confirm the new test fails for the intended reason. If new evidence points to a different cause, I update the diagnosis instead of keeping the first explanation.
ENGINEERING FOCUS
TECHNOLOGIES
- .NET 8
- Entity Framework Core
- Angular 19
- Signals
- TypeScript
- SQL Server
PRACTICES
- Typed API Contracts
- Unit Testing
- CI/CD