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.

15+Years in production
1K+Interviews run
25+Engineers mentored
$0No fee, no pitch

Who this is for

Three tracks, three stages of the same journey. Find yours, then come with something specific.

Track A

Architecture & technical depth

Senior developers, aspiring software architects

The path into architecture, and the decisions it actually turns on. Bring a design doc, a diagram, or a napkin sketch — you get an honest outside read on where it bends under load and the failure mode you haven't thought about yet.

Track B

Leadership transition

New & first-time tech leads, engineering managers

The jump from best engineer to running the team has no manual. Org shape, hiring and leveling, and the operating cadence that holds quality as you grow from 5 to 50. Patterns learned the expensive way, not theory.

Track C

Career guidance & work review

Early-career engineers, students welcome

Career-path building, the IC-vs-management fork, and a candid review of your work or portfolio with real feedback. This is career counseling, not a placement — open to anyone earlier in the journey, including students and interns.

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.

01

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 yet. I've been the one paged at 3am for the design — I review like it.

02

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. I've been on both sides of 1,000+ interviews — I'll tell you what the level really means, not what the ladder doc says.

03

First-time engineering leaders

The jump from best engineer to running the team has no manual. Org shape, hiring and leveling, and the operating cadence that holds quality as you grow from 5 to 50. Patterns I learned the expensive way, not theory.

04

Pragmatic AI adoption

Where AI gives real leverage in day-to-day engineering and where it quietly adds debt. Spec-first workflows, agent guardrails, and what's actually worth measuring. Production reality — I run this daily, not from a keynote.

05

A recurring 1:1

For someone earlier in the journey: a steady monthly sounding board for the decisions and doubts that don't fit into a single conversation. Not a course — a person who's been there and will say it straight.

06

Work & portfolio review

Bring a project, a side build, or your portfolio. I'll give specific, honest feedback on what's strong, what reads as junior, and the two things that would move you furthest. Useful whether you're a student or a senior engineer.

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.

Who it's for
  • 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.
What it isn't
  • An internship or a job. There's no company, no placement, no stipend — students and interns are welcome for career guidance and work review, same as anyone else.
  • A consulting funnel in disguise — there's 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 or no 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.

01

Apply with a real question

One short message: what you're working on, where you're stuck, and what you'd want out of a call. "Here's my design and what I'm unsure about" gets a faster, better reply than "can we chat sometime."

02

I check fit and capacity

Within a day or two I read it and tell you straight: whether the topic aligns with what I actually know, and whether I have the time to do it justice. If it's outside my lane, I'll say so — and sometimes point you to someone better.

03

We schedule a 1:1

If it's a fit, I'll send a 30-minute slot — your timezone, not mine. Come with the specifics; I keep it informal. Some things resolve in one call, some become a recurring monthly sounding board.

04

No invoice

That's the whole thing. If it helped, pass it forward to someone a few steps behind you. That's the only fee I'll ever ask.

Ruchit Suthar

Senior Software Architect & Technical Leader

linkedin.com/in/ruchit07

Connect on LinkedIn

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 a short message on LinkedIn or by email describing 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 the 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.