Building backend systems
that hold under pressure.
I'm Yatharth Maharwade —> a Backend Engineer specializing in Java, Spring Boot, and PostgreSQL. I focus on clean API design, solid data layers, and services that perform when it matters.
I care about how software actually works.
B.Tech CSE graduate from Nagpur who spent a year in intensive Java training at QSpiders, contributed to R&D at Bliinc, and now builds backend services at Vintyaa Technologies in Pune. I'm drawn to backend problems, API design, data modeling, query performance, and system reliability.
My approach: understand the problem first, design before coding, and ship something that works, not just something that demos well.
Experience
Software Engineer
Vintyaa Technologies Pvt Ltd · Pune
Architecting and building backend services using Java and Spring Boot. Designing RESTful APIs, optimizing PostgreSQL queries, and maintaining service reliability in production.
Student Intern
QSpiders Training & Development · Pune
Intensive full-stack Java development training. Covered advanced Java concepts, Spring Framework, Hibernate/JPA, and SQL. Built multiple projects from scratch under mentorship.
R&D Intern
Bliinc · Nagpur
Contributed to R&D initiatives exploring new technology solutions. Implemented proof-of-concept features, conducted feasibility studies, and collaborated on product innovation.
Selected Projects
Engineering solutions with real problems behind them.
Stack & Tools
What I reach for when building production software.
How I approach engineering
Specific principles I actually follow — not generic platitudes.
Design before code
I map the data model and API contract before writing the first line. Rushing to code means more time debugging the wrong solution.
Query performance is not optional
I check execution plans, avoid N+1 problems, and add indexes deliberately — not as an afterthought when production slows down.
APIs are contracts, not implementation details
Consumers shouldn't need to know how data is stored or processed. The API surface matters more than what's behind it.
Readable code ages better
Clever code is a liability. I name things clearly, keep methods small, and leave the codebase in a state I'd want to find it six months later.
Let's talk engineering.
Open to backend engineering roles, internship opportunities, and interesting technical collaborations. I reply to every message.