Episode 2: Leading Without Becoming a Manager: Mentoring Without Micromanaging

Jona Obrador • July 22, 2026

Experienced engineers notice a pattern. The same developers keep coming back with the same kinds of questions. Not because they lack ability, but because the senior engineer has become part of their problem-solving process.


When a senior engineer becomes a required step in someone else's problem-solving process, that is a dependency, not a mentoring relationship.


Mentoring without micromanaging is one of the most practical and difficult skills in technical leadership. It requires a deliberate shift in how engineers measure their own value.

The Mindset Shift Mentors Have to Make

The Mindset Shift Mentors Have to Make

As covered in Episode 1, technical influence is built through trust. Having authority and influence are different, but mentorship is where that plays out most directly.


Engineers often measure their value by how much they know and how quickly they can solve a problem. As a mentor, that metric works against the people being mentored.


The goal is not to be constantly needed. The goal is to build engineers who no longer need to ask the same question twice.

Authority comes from a title. Influence comes from trust. In most NetSuite development environments, you will need influence long before you are ever handed a management role.


Technical skill may earn you a seat at the table. Trust determines whether people follow your recommendations once you’re there. These are two different things, and confusing them is one of the most common reasons senior engineers struggle to move teams.

Stop Being the Search Engine

When someone asks a question, the instinct is to answer it. The answer is known, it saves time, and everyone moves forward.


But every immediate answer removes a chance to think. Over time, that pattern teaches developers to ask before they try, rather than try before they ask.

When someone asks a question, the instinct is to answer it. The answer is known, it saves time, and everyone moves forward.


But every immediate answer removes a chance to think. Over time, that pattern teaches developers to ask before they try, rather than try before they ask.

A more effective approach is to respond with questions first:

  • What have you tried so far?
  • What do you think is causing the issue?
  • What information are you missing?
  • If you had to make a decision now, what would you choose?
Stop Being the Search Engine

Asked consistently, those questions build a habit. Developers start running through that same checklist before they reach out. That is how independent engineering judgment forms.

A more effective approach is to respond with questions first:

  • What have you tried so far?
  • What do you think is causing the issue?
  • What information are you missing?
  • If you had to make a decision now, what would you choose?


Asked consistently, those questions build a habit. Developers start running through that same checklist before they reach out. That is how independent engineering judgment forms.

Productive Struggle Is Part of Learning

Watching someone work through a hard problem is uncomfortable. The fix is obvious, the solution is close at hand, and the senior engineer could resolve it in minutes.


But some of the most durable lessons in engineering come from problems that required genuine effort to solve. Removing the struggle often removes the learning.


The distinction worth drawing:

Most engineers invest years building technical skills. Fewer invest time in the skills that extend their impact across a team or organization.


Those skills include influencing decisions without formal authority, giving feedback that improves other people's work, handling disagreements professionally and constructively, scaling ownership beyond your own tasks, and making the engineers around you more effective.


These are learnable skills. They do not require a management track to develop, and they make a measurable difference in how projects get delivered.

Remove This Keep This
Blockers that prevent progress entirely Problems with a path forward, even if unclear
Risks to production, security, or data Low-stakes trial and error
Missing context the developer cannot access Discomfort that builds problem-solving instinct

Mentors do not leave people stranded. They give enough guidance to keep momentum while preserving ownership of the solution.

Teach the Thinking, Not Just the Answer

Teach the Thinking, Not Just the Answer

The most transferable thing a mentor can share is not a quick fix. It is a way of reasoning through problems.


When walking through an approach, experienced engineers should go beyond what they would do: don’t stop at what you do, explain the why. They should explain the trade-offs they considered, the assumptions built into their decision, the risks they were trying to avoid, and what would change their recommendation.

The most transferable thing a mentor can share is not a quick fix. It is a way of reasoning through problems.


When walking through an approach, experienced engineers should go beyond what they would do: don’t stop at what you do, explain the why. They should explain the trade-offs they considered, the assumptions built into their decision, the risks they were trying to avoid, and what would change their recommendation.

When developers hear that reasoning consistently, they start to internalize it. That is when independent judgment begins to form.

When developers hear that reasoning consistently, they start to internalize it. That is when independent judgment begins to form.

Mistakes Are Part of the Process

Every experienced engineer has made mistakes that shaped how they work today. Preventing every mistake in a junior developer's path also prevents some of those formative lessons.


There are clear situations where stepping in is necessary: production stability, security exposure, or significant customer impact. Outside of those, small and recoverable mistakes often teach more than a well-timed correction.

Every experienced engineer has made mistakes that shaped how they work today. Preventing every mistake in a junior developer's path also prevents some of those formative lessons.

There are clear situations where stepping in is necessary: production stability, security exposure, or significant customer impact. Outside of those, small and recoverable mistakes often teach more than a well-timed correction.

Leadership Starts Before Any Title Does
Leadership Starts Before Any Title Does

In NetSuite environments, where customizations and integrations can carry long-term consequences, this judgment call matters. The mentor's job is to hold that line clearly, not to intervene at every sign of uncertainty.

Mentorship Is Measured by Independence

Mentorship Is Measured by Independence

Micromanagement is not just constantly checking on someone’s work; it’s also answering every question, making every decision, and solving every problem for them. The clearest sign that mentoring is working is when a developer says: "I figured it out.” Not because the mentor was unavailable, but because the guidance built enough confidence to reason through it independently. 

Real mentorship looks different. It asks questions. It builds confidence. It creates ownership. Because the best mentors aren’t remembered for having all the answers, they’re remembered for helping others discover their own.


At ATSOURCE, we build NetSuite teams where that kind of technical growth is part of how the work gets done. Let's talk about what that looks like for your organization.

Real mentorship looks different. It asks questions. It builds confidence. It creates ownership. Because the best mentors aren’t remembered for having all the answers, they’re remembered for helping others discover their own.


At ATSOURCE, we build NetSuite teams where that kind of technical growth is part of how the work gets done. Let's talk about what that looks like for your organization.

Jona Obrador Senior Netsuite Developer

Meet the Author

Jona has over a decade of experience in SuiteCloud Development on the NetSuite platform. She specializes in implementing advanced solutions and has led teams in creating high-quality software. Jona holds multiple certifications and has been recognized with awards like the Summit Award and Quality Champion Award.

Tags

Accelerate ERP Success with Expert Solutions

Ready to put what you've learned into practice? ATSOURCE delivers both the specialized talent and comprehensive NetSuite support you need to turn strategy into results.‍Connect with our experts today and move from planning to performance.

Episode 1 title slide: “Technical Leadership Starts With Trust, Not a Title” on a purple background with icons and a podium.

Episode 1: Technical Leadership Starts With Trust, Not a Title

By Jona Obrador • July 14, 2026
Authority comes from a title. Influence comes from trust. Learn how senior NetSuite engineers build technical leadership before any management role arrives.
Why Leadership Doesn’t Require a Title

Episode 0: Leading Without Becoming a Manager: Why Leadership Doesn’t Require a Title

By Jona Obrador • June 23, 2026
Not all leadership means becoming a manager. Learn how NetSuite developers grow their impact through technical leadership, mentoring, and influence.
Purple banner reading “Engineering Beyond Code: The Skills That Actually Define Great Engineers” with a code notebook icon

Episode 8: Engineering Beyond Code: The Skills That Actually Define Great Engineers

By Jona Obrador • June 18, 2026
Technical skills get engineers in the room. Communication, judgment, and ownership determine impact. See what great NetSuite engineering really looks like.