About Malay Mehta, Software Architect and Mentor
My Journey
My journey into software engineering started with a simple curiosity and a line of code many developers remember fondly:
#include <studio.h>
At the time, I barely understood what that line meant. I didn't even know I had misspelled the header file. What started as a beginner's mistake turned into years of building, breaking, and figuring things out.
As a self-learner during college, I started with Java, JSP, Servlets, and MySQL, building projects and exploring concepts beyond the classroom.
Over time, that curiosity led me through Spring, cloud-native development, distributed systems, platform engineering, DevOps, Kubernetes, event-driven architectures, and enterprise-scale retail platforms.
Over the years, I got more interested in the stuff around the code than the code itself. I started paying attention to how business requirements become software, how engineering decisions affect cost and scalability, how teams communicate effectively, and how systems operate in production long after they are deployed.
Today, I enjoy working across the entire software lifecycle: architecture, design, implementation, deployment, observability, optimization, and operational excellence.
I also keep a foot in production outside of client work. Finworthly, a net worth tracker for Indian families, is mine end to end: architecture, implementation, deployment, and everything that comes after.
Solving the right problem matters more than applying the fastest fix.
Whether diagnosing a production issue, designing a new platform, or mentoring engineers, I focus on understanding root causes and fixing things in a way that actually stays fixed.
Lessons Learned
Technology Is Only Part Of The Solution
The most successful projects come from aligning technical decisions with business realities.
Technical Debt Compounds Quietly
Technical debt rarely creates immediate pain, which is why it often gets ignored. Over time, however, it slows innovation, increases operational complexity, and makes simple changes expensive.
Root Cause Beats Quick Fixes
Sustainable engineering comes from understanding why something failed rather than simply making the symptom disappear.
Continuous Learning Matters
The industry evolves constantly. The willingness to learn is often more valuable than existing expertise.
Things I've Built
Side work I run myself, which is where the operational lessons above come from.
A net worth tracker for Indian families. Values are entered by hand instead of pulled from bank accounts, which keeps the whole balance sheet in scope: property, gold, EPF and PPF, not only what an account aggregator can reach. React and Spring Boot, running on a single small cloud VM.
Technology Domains
Rather than focusing on individual technologies, I prefer to think in terms of capabilities and business outcomes.
Designing scalable, maintainable, and high-performance backend systems that evolve with changing business requirements.
Java • Spring Boot • Microservices • REST APIs • Event-Driven Architecture • Kafka • RabbitMQ • Redis • PostgreSQL • MySQL
Building and operating cloud-native platforms with a focus on automation, reliability, security, observability, and operational excellence.
AWS • Kubernetes • Docker • Helm • Kong • Keycloak • Grafana • Prometheus • CI/CD
Designing real-time data pipelines, reporting systems, and analytical platforms that transform operational data into actionable insights.
Debezium • ClickHouse • MySQL CDC • Redis • Event Streaming
Applying Agentic AI workflows and engineering accelerators to improve developer productivity while maintaining engineering quality and human oversight.
ChatGPT • Claude • Cursor • GitHub Copilot • MCP • Skills • AI-Assisted Testing • Code Generation Workflows
Beyond Engineering
Related reading
- How I think about system design
Trade-offs, when to scale, and when not to.