Full-stack software engineer with a strong emphasis on backend architecture and distributed systems. Currently working at SolarView, building and maintaining production systems that involve complex business rules, financial integrations, and ci/cd workflows.

My engineering focus goes beyond making things work, I'm concerned with how they're built: clean separation of concerns, appropriate design patterns, and database choices that match the problem, not just the familiarity.

• Layered and hexagonal architectures to enforce clear boundaries between domain, application, and infrastructure
• Event-driven design with message brokers (RabbitMQ) for decoupled, resilient services
• RESTful API design with consistency in contract, error handling, and versioning

• Application of patterns like Repository, Factory, Strategy, Observer, and CQRS where they reduce complexity — not as a checklist
• Dependency injection and interface-driven development for testability and flexibility
• Awareness of when a pattern adds structure vs. when it adds noise

• Cache-aside and write-through patterns depending on read/write ratios
• Identifying cache boundaries: what to cache, for how long, and what invalidation strategy makes sense
• Avoiding premature caching and understanding its tradeoffs in distributed environments

• Relational (MySQL, PostgreSQL) for transactional integrity, complex queries, and normalized data models
• Document stores (MongoDB) for schema flexibility and hierarchical data
• Understanding the CAP theorem in practice: choosing consistency vs. availability depending on the domain
• Query optimization, indexing strategies, and avoiding N+1 patterns