A software engineer recently shared his career journey on the Developers India subreddit, explaining how his annual salary rose from ₹6 lakh to ₹21 lakh through persistence, self-learning, and strategic preparation. His experience reflects how initiative and consistent effort can reshape a stagnant start into a rewarding trajectory.
Early Career and Unexpected Setback
He completed his graduation in 2022 from a mid-tier engineering institution with a degree in mechanical engineering. Despite not having a computer science background, he secured a campus placement at a multinational corporation, where he was hired as a GenC developer. During his internship, he received training in .NET full-stack development and officially joined the company in August 2022 as a full-time employee.
However, what initially seemed like a promising beginning soon turned discouraging. For nearly two and a half years, extending until March 2025, he was not assigned any meaningful work. Around the end of his first year, he recognized the lack of growth and decided to take matters into his own hands instead of waiting indefinitely.
Self-Learning and Skill Building
Determined to build a solid technical foundation, he began independently studying Java and Spring Boot. Alongside this, he started practicing coding problems regularly on LeetCode, sharpening his problem-solving abilities. His preparation was consistent and focused, even without immediate opportunities to apply those skills at work.
By March 2025, he was officially placed on the bench, which meant he had no active project. Rather than seeing this as a setback, he used it as an opportunity to pursue better roles. Within a week, he managed to clear three rounds of interviews focused on Java and Angular. A hiring manager, willing to look beyond his lack of real-world experience, decided to give him a chance based on his knowledge and potential.
Career Breakthrough
After joining the new role, he quickly proved his capability and became an essential contributor to the team. Within a short span, he transitioned from being overlooked to becoming a key resource, demonstrating how preparation and confidence can outweigh initial disadvantages.
Insights into Interview Patterns
Reflecting on his experience, he shared useful insights into how companies assess candidates for mid-level Java roles. Large multinational firms typically conduct two rounds of interviews, sometimes followed by client discussions. These interviews often focus on theoretical concepts such as Java architecture, multithreading, Spring Boot annotations, security, and features introduced in newer Java versions. Database-related topics like SQL joins and indexing, along with optimization techniques, are also commonly discussed. Candidates are often asked to solve problems using stream APIs and handle scenarios involving collections and data grouping.
In product-based or global capability centers, the process can be more extensive. Companies like EPAM emphasize core Java concepts and Spring Boot internals, along with coding exercises involving data structures, algorithms, and API-based problems. Meanwhile, organizations like UPS may include system design discussions, focusing on scalability, database optimization, logging, deployment, and code reviews, often involving international interview panels.
Final Takeaways and Community Response
He emphasized that perfection is not necessary to succeed in interviews. Confidence, clarity of thought, and the ability to explain one’s approach effectively can leave a strong impression. Even though he made mistakes in system design and coding rounds, his reasoning and preparation helped him move forward. His extensive practice on coding platforms and an active GitHub profile also played a significant role in impressing hiring managers.
He recommended several resources for preparation, including specialized Java ebooks, coding channels, interview experience blogs, and online tools for reference and practice.
The post sparked engagement from other users. One individual shared that they had a similar start but were assigned to a project early and were now looking for ways to switch roles. Another simply appreciated his journey, acknowledging his efforts and success.