Community first — free, no pitch
Free mentorship for engineers, tech leads & aspiring architects
1:1 guidance from a software architect with fifteen years scaling systems from startup to enterprise. Bring a design you're unsure about, a career fork, the first-time-lead jump, or your work for a candid review. We'll talk it through. No invoice at the end.
Open for new mentees this month — a few 1:1 slots, first come first served.
What we can cover
Six things I get asked about most. Come with a specific question in one of these and it'll be a useful conversation — not a generic pep talk.
Architecture & system-design reviews
Bring a design doc, a diagram, or a napkin sketch. You get an honest outside read: where it bends under load, where you're gold-plating, and the failure mode you haven't thought about. I've been paged at 3am for the design — I review like it.
Career decisions for engineers
IC vs. management, a plateau that won't break, what "senior" or "staff" actually demands, an offer you're unsure about. From both sides of 1,000+ interviews, I'll tell you what the level really means — not what the ladder doc says.
First-time engineering leaders
Best engineer to running the team has no manual. Org shape, hiring and leveling, and the cadence that holds quality as you grow from 5 to 50 — patterns learned the expensive way, not theory.
Pragmatic AI adoption
Where AI gives real leverage in day-to-day engineering and where it quietly adds debt. Spec-first workflows, agent guardrails, what's worth measuring. Production reality — I run this daily, not from a keynote.
A recurring 1:1
For someone earlier in the journey: a steady monthly sounding board for the decisions and doubts that don't fit one conversation. Not a course — a person who's been there and says it straight.
Work & portfolio review
Bring a project, a side build, or your portfolio. Specific, honest feedback on what's strong, what reads as junior, and the two things that would move you furthest — student or senior.
Who it's for — and what it isn't
Honesty saves us both time. Here's exactly who tends to get the most out of this, and where I'll set expectations up front.
- Senior engineers and aspiring architects who want a candid second opinion on a design, a decision, or the path into architecture.
- New or first-time engineering leaders finding their footing with people, process, and scale.
- Early-career engineers and students who want career guidance or an honest review of their work — not a job placement.
- An internship or a job. No company, no placement, no stipend — students are welcome for career guidance and work review, same as anyone else.
- A consulting funnel in disguise — no discovery call, no upsell, no "let's take this to a proposal."
- Unlimited — I have a day job I love. I help where I can, when I can; a slow reply isn't personal.
- A replacement for your manager — I'm an outside read, not your skip-level or your therapist.
How to apply
No forms, no calendar gymnastics. Four steps — and because my time is limited, the second one is a real fit-and-capacity check, not a formality. Open for new mentees this month — a few 1:1 slots, first come first served.
Tell me what you're working on
Three sentences: what you're working on, where you're stuck, what you'd want out of a call. That gets a faster, better reply than "can we chat sometime."
I check fit and capacity
Within a day or two I tell you straight whether the topic is in my lane and whether I have time to do it justice. If it's not, I'll say so — and sometimes point you to someone better.
We schedule a 1:1
If it's a fit, I send a 30-minute slot in your timezone. Come with specifics; I keep it informal. Some things resolve in one call, some become a recurring monthly 1:1.
No invoice
That's the whole thing. If it helped, pass it forward to someone a few steps behind you — the only fee I'll ever ask.
Ruchit Suthar
Senior Software Architect & Technical Leader
linkedin.com/in/ruchit07
Common questions
Is the mentorship really free?
Yes. There's no fee, no pitch, and no paid tier. Fifteen years scaling systems from startup to enterprise, I had a lot of help — this is me giving some of it back. The only ask is that if it helps, you pass it forward to someone a few steps behind you.
Who is this mentorship for?
Senior developers and aspiring software architects, new or first-time tech leads and engineering managers, and early-career engineers (students welcome) who want career guidance or an honest review of their work. If you're stuck on a real, specific problem in one of those areas, it'll be a useful conversation.
Can a mentor review my system design or my work?
Yes — that's one of the most common reasons people reach out. Bring a design doc, a diagram, a project, or your portfolio and you get a specific, honest outside read: where it bends under load, where you're over-engineering, and the two things that would move you furthest.
Can students or interns apply?
Yes, but for career guidance and work review — not an internship. This isn't a job, a placement, or a paid program; there's no company behind it. If you're a student or early in your career, I can help with your career path and review your work, the same as I would for anyone else.
What's the difference between coaching and mentoring here?
Both are on the table. A one-off call to pressure-test a specific decision is closer to coaching; a recurring monthly 1:1 for the decisions that don't fit into a single conversation is closer to mentoring. You tell me what you need and we shape it around that.
How do I apply, and how fast will you reply?
Send three sentences on LinkedIn or by email: what you're working on and where you're stuck. I read everything and usually reply within a day or two on whether I'm the right person and have capacity. If it's a fit, I'll send a 30-minute slot in your timezone.
Bring me a real problem
Send a short message describing what you're working on and where you're stuck. I read everything, and I'll tell you honestly whether I'm the right person to help.
Want to go deeper on your own first? Start the architect pathway, or read the writing to get a feel for how I think.