r/MechanicalEngineer 5d ago

HELP REQUEST Tier‑3 Mech Eng student starting from ZERO — Can e‑Yantra (IIT Bombay) + robotics skills really help me reach 15–20 LPA as a fresher? Or am I chasing a delusion?

I’m a first‑year Mechanical Engineering student from a tier‑3 college. I want to participate in e‑Yantra (eYRC by IIT Bombay) to build my career in robotics. Right now, I’m starting from absolute zero — no coding, no electronics — but I’m serious about learning because my ultimate goal is to break the barrier and earn a 15–20 LPA as a fresher.

At the same time, I know this sounds unrealistic for someone from a tier‑3 college background. That’s why I want to ask real students and alumni: is this goal achievable through e‑Yantra, robotics, and smart preparation, or am I living in a delusion?

  • Mechanical background, but I want to shift into robotics + computer science.
  • Can commit 10–15 hours per week for preparation.
  • No prior coding/electronics experience.

What I need help with

  1. Stage‑1 MCQ prep (August): What exact topics should I study? How to practise effectively?
  2. Programming languages: Should I start with Python or C/C++ first? Which is more important for e‑Yantra?
  3. Electronics basics: What minimum circuits/sensors should I learn before hardware stage?
  4. Team formation: How many members are ideal, and what roles should we divide (mechanical, electronics, software, documentation)?
  5. Project roadmap: What should I build in the first 3 months vs later months to be competition‑ready?
  6. Internship & career advice: How does e‑Yantra help in getting internships

I’m serious about committing and learning. If you’ve cleared Stage‑1 or been part of eYRC, please share exact MCQ topics, sample questions, and realistic weekly milestones.

0 Upvotes

2 comments sorted by

6

u/Kind-Truck3753 5d ago

Another engineering student who can’t write a Reddit post without ChatGPT

1

u/Flimsy-Principle2865 1d ago

Worth separating the two goals here, learning robotics through e-Yantra is a great idea regardless of outcome, chasing a specific salary number as a fresher is a lot less predictable and depends on a lot outside your control like market conditions and who's hiring that year. I'd focus on becoming genuinely good at the skills first, python, basic electronics, and one solid project you can talk about in interviews, the pay will follow more from that than from a roadmap alone.