Software Engineer | Backend & Full-Stack | Distributed Systems, IAM, Cloud

Software engineer focused on building production-ready backend and full-stack systems, with strong experience in identity platforms (IAM), distributed architectures, and enterprise integrations.

Backend: NestJS · ASP.NET Core · Spring Boot · Django
Languages: Java · C# · TypeScript · Python · JavaScript · C++
Architecture: Microservices · Event-Driven · DDD · TDD · Clean Architecture
APIs & Messaging: Kafka · gRPC · REST · GraphQL
Databases: PostgreSQL · MongoDB · Oracle · SQL Server
Cloud & DevOps: AWS · Azure · Docker · Jenkins · GitHub Actions · CI/CD
Security: OAuth2 · OIDC · JWT · SAML · ADFS · Microsoft Entra ID
Frontend: Vue.js · React · Next.js
AI Integration: LLM API integration · Chatbot backend development

Production-oriented microservices architecture showcasing enterprise integration patterns and full-stack system design.

Key focus areas

• Service-to-service communication using Kafka and gRPC
• Clear separation of domain, application, and infrastructure layers
• Designed around scalability, resilience, and maintainability trade-offs

Java 17 · Spring Boot 3 · Apache Kafka · gRPC · Redis · PostgreSQL · Vue 3 · React 18 · Docker

Enterprise IAM backend designed to model real-world identity and access control challenges, with strong emphasis on tenant isolation and security boundaries.

Key focus areas

• Multi-tenant architecture with strict data isolation
• Role-Based Access Control (RBAC) and JWT-based authentication
• Designed to reflect enterprise IAM patterns and security constraints

NestJS · TypeScript · PostgreSQL · Prisma · Docker

Full-stack application focused on API robustness, validation, and consistent error handling.

Key focus areas

• JWT-based authentication and authorization
• Centralized error handling and input validation
• Practical backend–frontend integration

Express · TypeScript · MongoDB · Next.js · Zod

C++ project emphasizing object-oriented design, correctness, and modern C++ standards.

Key focus areas

• Rule of Three and object lifecycle management
• Emphasis on correctness through unit testing
• Clean, maintainable C++17 codebase

C++17 · CMake · Unit Tests

• Prioritize correctness, maintainability, and clarity over feature quantity
• Make explicit design decisions with well-defined boundaries
• Apply the same architectural and testing principles across multiple languages and stacks