Shubham Chepe Java Full Stack Developer · Spring Boot · Microservices · React.js · AWS
Nagpur, Maharashtra · Open to Remote
I've built Java systems for 3+ years. Now I support them at enterprise scale. 150+ REST APIs shipped with zero post-release defects — and a daily, front-row view of what makes software fail in real customers' hands. You get a developer who writes code the way a support engineer wishes everyone did.
Shubham Chepe is a Java full stack developer (Java 17, Spring Boot 3, microservices, React.js, AWS) based in Nagpur, India, currently working as a Technical Support Engineer at Salesforce. Previously he built fintech microservices at Trust Fintech and enterprise REST APIs at Riverstream Consultancy Services.
"Most developers only see their code until it ships. I've seen both sides of the table — writing it, and being the engineer the customer calls when it breaks. That's why my code doesn't come back."
Why a Java developer who has sat on the other side of the table writes better software
Salesforce doesn't fill its Technical Support Engineer seats with script-readers. The role is written for developers: Java proficiency and hands-on experience debugging Java applications are baseline requirements, and the job is to take a customer's broken integration, reproduce it, find the root cause, and work with product engineering to fix it. I was hired into that seat because of my full-stack Java background — and it has changed how I think about every line of code I write.
- Green builds and passing tests
- The happy path in the ticket
- My service, my logs, my database
- "Works on my machine"
- What the customer actually sent
- The edge case nobody wrote a test for
- Three systems, two teams, one angry deadline
- "Works everywhere except production"
Error messages are a product feature
A bare 500 Internal Server Error costs a customer a day and a support engineer hours. My APIs return errors that name the field, the reason, and the fix.
Logs are written for a stranger at 2am
Correlation IDs, structured logging, no swallowed exceptions. If someone who has never seen my code can't trace a failed request in five minutes, the logging isn't finished.
An API contract is a promise to people you'll never meet
Backward compatibility, versioning, idempotent retries and timeouts aren't nice-to-haves. Every breaking change I've seen lands on someone's desk as an escalation.
Reproduce first, then fix
No guess-patches. A minimal reproduction, a confirmed root cause, a regression test — the same discipline I used to resolve 30+ P1 bugs in under 4 hours, now applied daily.
What that means for your team: fewer escalations, faster incident resolution, code the next engineer can support without calling me — and a developer who can talk to customers, support and product in their own language.
Work Experience
- Hired into Salesforce's Technical Support Engineering team on the strength of a full-stack Java development background — a role that requires reading and debugging code, not following scripts.
- Troubleshoot complex customer issues across APIs, integrations, data and application behaviour — reproducing problems, isolating root cause and driving them to resolution.
- Partner with product engineering on defects, turning customer-reported symptoms into clear, reproducible bug reports.
- Write technical knowledge articles so the next engineer — or customer — solves the same problem in minutes, not hours.
- Built 20+ microservices for KYC, onboarding & loan processing — enabling 500+ monthly transactions with zero compliance rollbacks.
- Automated loan workflow orchestration, cutting approval time from 48 hrs → 12 hrs — a 75% reduction that eliminated the need for a manual review headcount.
- Raised code quality from SonarQube C → B in 2 months, reducing new-developer onboarding time by 30%.
- Owned 3 backend modules end-to-end — zero missed sprint deadlines, zero post-release defects across all deployments.
- Built 100+ REST APIs across 4 enterprise apps — sub-200ms response times serving 5,000+ active users.
- Fixed 20+ SQL performance bottlenecks — API speed increased 40% and client support tickets dropped by 50%, saving an estimated 8 hrs/week of manual triage.
- Refactored 3 monolithic modules into clean service layers — SonarQube D → B, onboarding time cut from 2 weeks to 5 days.
- Resolved 30+ P1 bugs under 4-hour SLA — sustained 99.5% uptime over 2.5 years with zero critical incidents.
Projects
Writing: Java, Spring Boot, Kafka, Kubernetes & AWS
Spring Boot 3.5 is out of support: a practical Spring Boot 4 migration guide
Java 27 is out: what actually changes for your Spring Boot services
Kafka can finally act like a queue: share groups for Java developers
Technical Skills
Certifications
A developer who builds it — and knows how it breaks
Education
Recruiters: verify me in 10 minutes
- Read real code. The full-stack Billing & POS system — Spring Boot, Spring Security + JWT, React.js, MySQL.
- See how I explain hard things. My Project Valhalla deep dive — the same clarity I bring to design docs and incident write-ups.
- Check the numbers. 150+ APIs, 0 post-release defects, P1s fixed in under 4 hours, 99.5% uptime — every claim is backed in my resume.
- Talk to me directly. java@shubhamchepe.com or WhatsApp +91 96658 11415. Happy to do a live coding or debugging session instead of a quiz.
Frequently asked questions
Who is Shubham Chepe?
Shubham Chepe is a Java full stack developer from Nagpur, India with 3+ years of experience in Java 17, Spring Boot, microservices, React.js and AWS. He currently works as a Technical Support Engineer at Salesforce, after building fintech microservices at Trust Fintech and 100+ enterprise REST APIs at Riverstream Consultancy Services.
Is Shubham Chepe open to new Java developer roles?
Yes. He is open to Java full stack, Spring Boot backend and microservices roles — remote, hybrid, or on-site in India. Recruiters can reach him at java@shubhamchepe.com or on WhatsApp at +91 96658 11415, and he usually replies within two hours.
What does a Technical Support Engineer at Salesforce do?
A Salesforce Technical Support Engineer resolves complex technical issues for enterprise customers — reproducing problems in APIs, integrations and application code, finding the root cause, and working with product engineering on defects. Salesforce's postings for the role ask for Java proficiency and hands-on experience debugging Java applications, which is why it is often filled by developers.
Why does support engineering experience make someone a better Java developer?
Support engineers see how software fails in production, not just how it passes tests. That experience produces developers who write clearer error messages, better logs, backward-compatible APIs and code that other engineers can debug — which means fewer escalations and faster incident resolution for the team that hires them.
What is Shubham Chepe's tech stack?
Java 8/11/17, Spring Boot 3, Spring Security, Spring Data JPA, Hibernate, REST APIs, microservices, Apache Kafka, React.js, MySQL, PostgreSQL, Redis, AWS (EC2, RDS), Docker, Kubernetes, JUnit 5, Mockito and SonarQube.
What has Shubham Chepe delivered?
150+ REST APIs across two companies with zero post-release defects; 20+ fintech microservices that cut loan approval time from 48 hours to 12; a 40% API speed-up from fixing slow SQL and N+1 queries; and 99.5% uptime with P1 bugs resolved in under 4 hours on average.