Java Backend Engineer | Spring Boot | Kafka | SQL | System-Oriented Thinker

I’m a backend-focused software engineer with hands-on experience building and maintaining enterprise-grade Java applications.
My strength is not tools — it’s understanding how systems actually work under the hood.

I work primarily with Java + Spring Boot, design clean service layers, handle data correctly, and care about performance, maintainability, and correctness.

No fluff. I prefer clarity over cleverness.

• Java (Core, Collections, Streams, Concurrency basics)
• Spring Boot (Web, JPA, Security, Config, Validation)
• Spring Data JPA & Hibernate
• REST API design (DTOs, Controllers, Service layers)
• Kotlin (Micronaut framework)

• Apache Kafka (Producer/Consumer basics, real usage in projects)
• Event-driven communication patterns

• SQL (MySQL)
• NoSQL (Amazon DynamoDB)
• Schema design, joins, indexing basics
• JPA queries (@Query, projections, pagination)

• AWS (DynamoDB, AWS CLI)
• GitHub CLI
• Rancher Desktop (local Kubernetes)
• WSL (Windows Subsystem for Linux)

• React (Micro Frontend architecture)
• Cypress (end-to-end testing)

• Clean code & layered architecture
• Configuration management (application.yml)
• Logging & debugging
• Migration & upgrade work (JDK upgrades, dependency alignment)

• Data Structures & Algorithms (Java)
• Strong focus on why an algorithm works, not just syntax

A production-grade learning platform built with a modern, cloud-native stack.

• Backend: Kotlin + Micronaut framework
• Frontend: React with Micro Frontend architecture
• Database: Amazon DynamoDB (NoSQL)
• Testing: Cypress for end-to-end testing
• Infrastructure: AWS CLI, GitHub CLI, Rancher Desktop, WSL
• Focused on scalable service design and clean cross-team integration patterns

A modular Spring Boot application where each DSA topic is implemented as a separate service.

• Clear separation of concerns
• Controller → Main Service → Topic Services
• Designed for deep understanding, not shortcuts

Worked on large-scale government-related systems involving:

• Spring Boot microservices
• Database-driven workflows
• Kafka-based communication
• Strict correctness and validation requirements

(Code not public due to confidentiality)

• Kotlin + Micronaut patterns and idiomatic usage
• Advanced Java Streams & functional patterns
• System-level thinking (how components interact)
• Writing fewer abstractions — but better ones
• Becoming exceptionally strong in fundamentals

• Code that someone else can understand in 6 months
• Predictable behavior over “clever” tricks
• Learning things deeply instead of collecting buzzwords

• GitHub: https://github.com/prince07g