EXPERIENCEPROFESSIONAL

Systems I've helped build and evolve.

Backend engineering experience across real-time systems, legacy applications, APIs, data, and high-throughput processing.

01PROFESSIONAL EXPERIENCE

2025 — PRESENTMINU

Backend Developer

Supporting and evolving business-critical backend systems.

Working across both legacy and modern backend systems, supporting business operations through application maintenance, API development, troubleshooting, and new functionality.

Legacy system investigation

Investigating production issues by tracing application behavior, database relationships, business rules, and user flows before making changes.

API development

Maintaining and extending a .NET 8 API used by external partners to access voucher card information and related operations.

Business application support

Supporting the voucher management portal and investigating issues involving data, functionality, access paths, and application logic.

Backend development across technologies

Working primarily with .NET and also contributing to Node.js services and other backend applications when required by the system.

TECHNICAL CONTEXT

.NET Framework.NET 8Node.jsSQL ServerMySQL

2023 — 2025GS TRACKME

Backend Developer

Building and evolving a real-time tracking platform.

Contributed to the development of a new version of a vehicle tracking platform, working primarily on the backend and taking part in architecture, data modeling, distributed processing, and system evolution.

Backend architecture

Designed and developed .NET services according to the responsibilities and requirements of each part of the platform.

Real-time processing

Developed the backend processing flow responsible for receiving, validating, processing, and reacting to continuous tracking data.

Data and distributed systems

Worked across PostgreSQL, MongoDB, Redis, RabbitMQ, and gRPC to support persistent data, fast state, asynchronous communication, and service-to-service processing.

Performance and scalability

Investigated processing time, database workload, memory usage, expensive operations, and resource consumption as tracking volume increased.

System evolution

Helped establish the new platform from its early development, explaining service responsibilities and architecture as additional developers joined the project.

TECHNICAL CONTEXT

C# / .NETPostgreSQLMongoDBRedisRabbitMQgRPC

02HOW MY EXPERIENCE EVOLVED

From building backend features to understanding the systems around them.

My experience has gradually moved from implementing individual backend functionality toward understanding larger systems, their constraints, and the decisions required to keep them maintainable as they grow.

Backend Development

Building APIs, business logic, database interactions, and services that support real-world applications.

System Understanding

Learning how different components, data relationships, business rules, and users interact before making changes.

Distributed Systems

Working with multiple services, asynchronous communication, real-time processing, caching, and different data stores.

Performance & Scale

Investigating processing time, memory consumption, database workload, concurrency, and resource usage as system demand increases.

03TECHNICAL CONTEXT

Technologies I've worked with across different systems and constraints.

My strongest experience is with C# and .NET, while my work has also required working across different languages, databases, communication patterns, and infrastructure concerns.

BACKEND

C#.NETNode.jsGo

DATA

PostgreSQLSQL ServerMySQLMongoDBRedis

COMMUNICATION

REST APIsgRPCRabbitMQWebSockets