iTranslated by AI

The content below is an AI-generated translation. This is an experimental feature, and may contain errors. View original article
🛣️

Defining My Own Staff Engineer Role as a Developer in an SIer

に公開

The Problem of Not Seeing Beyond Senior

I am currently a Tech Lead at a small-to-medium-sized SIer (System Integrator). My areas of responsibility are backend and cloud, where I serve as the technical lead for assigned projects and work on improving our internal technical infrastructure.

Then, it struck me: "What happens after this?"
In terms of company hierarchy, I have a title that sounds appropriate, but I am not becoming a manager, nor am I a "Senior Engineer" in the traditional sense.

When I asked my boss what I should be doing in this position, the response was, "Thinking about that is exactly what your level is for."
While I thought, "Fair enough," I found myself unable to take specific action from there.

It was during a brainstorming session with an AI while struggling with these vague feelings. When I consulted it about how "my career path ahead is clouded," the AI suggested, "I recommend the book 'Staff Engineer' by Will Larson."


I didn't know AI could recommend books too...

https://www.amazon.co.jp/dp/B0C231J7FC

According to the Amazon description:

My recommended way to read this is to first read the interviews of 2-3 people in Chapter 5, then proceed to read Part 1.
Especially for engineers who have gained a certain level of experience, I believe you will greatly resonate with the concrete episodes of Staff Engineers appearing in Chapter 5.

I started reading from Chapter 5 as suggested, and I was floored by the constant stream of "I've been there" moments. I thought, "This is it." However, as I continued reading, a sense of discomfort also started to emerge.

Product Companies and SIers Have Different Structures

This book is written with product companies in mind—a world where you meticulously nurture your own product. But SIers are different.

Product Companies SIers
Technical Assets The company's own codebase Generally handed off after delivery to the client
Time Horizon Nurturing the same system for years Completed on a per-project basis
Technical Debt Something you continue to carry Belongs to the client (depends on maintenance contract)
Technical Impact The entire product Project level + internal cross-project rollout

Personally, the biggest gap I feel is in the handling of "technical debt." In product companies, there is value in paying down debt, but in an SIer, it becomes the client's decision after delivery, so there are many situations where you have no choice but to provide the optimal solution on the spot.

I realized that I needed to replace the book's content with perspectives unique to an SIer.

Concepts Learned from the Book

Although there are differences in structure, what I gained from this book was significant.

Making Yourself Understood is Your Responsibility

The other party has no obligation to understand you; it is your responsibility to speak in a way that ensures you are understood.

Once you reach the senior level or higher, you find yourself explaining technical matters to non-engineers more often. You might think, "Why don't they understand?" but that is not their fault; it is a problem with how you are communicating.

Disagree, But Commit

The concept of "Disagree and commit." If you cannot agree, express your dissent properly.
However, once a decision is made, carry it out with full responsibility, even if it differs from your own opinion.

Make Yourself Successful

If you think the company will lead you to success, discard that expectation.

When I read this, I was reminded of my interaction with my boss at the beginning. "Thinking about that is exactly what your level is for"—in short, this is what he meant. No one is going to prepare a career path for you. You have to create it yourself.

Articulate and Document Your Thoughts

Don't just provide conclusions; document the path of "why you thought that way" in writing.

Even if the information is incomplete, start writing with what you have. It's fine to write bad prose.
By doing so, others can correct and expand upon it.

Actually, this is also what triggered me to start writing on Zenn.
I decided it was time to turn my focus, which had been closed off in private (internal company) settings, outward.

Defining the Staff Engineer Role for an SIer

Having finished reading the book, I reached the main topic. I will define the role of a staff engineer from the perspective unique to an SIer.

What Does an SIer Staff Engineer Focus On?

Staff engineers in product companies lead the technical direction of their own products. There is a clear pillar—the product itself—and technical decisions are made within the context of "how to evolve this product."

SIers have a different structure; nothing starts unless you win a project. "We can handle this technology" and "We are good at this domain" are weapons for sales, and technical prowess is a business model directly linked to winning projects.

So, what does an SIer staff engineer look at? Based on this context, I believe it is about properly selecting the company's "weapons" and deploying them across projects. While product companies hone their technical skills "for the product," SIers hone theirs "to win and execute projects." It feels like the demand is for selecting versatile weapons that are not tied to any specific product.

The Premise of "High Personnel Turnover"

SIers have a constraint that product companies do not: personnel fluidity.

Employees move from project to project, and even for maintenance projects, the same people are not attached indefinitely. Partners often join on a project basis, making turnover even more intense.

In other words, technical choices must be made so that "anyone can run the project." The assumption that "the same team will nurture the project for years," common in product companies, does not apply here.

The Difficulty of Choosing "Weapons"

The targets for selecting the company's weapons include not just programming languages, but also frameworks, SaaS, and AI tools. This is incredibly difficult. If you choose the wrong weapons, it impacts your ability to win projects.

If you jump on the latest trends, you might find something better shortly after, or discover hidden flaws. Or perhaps, "Wait, it's not becoming as mainstream as I thought?" or "The recent updates aren't really heading in the direction we need." Changing weapons affects future projects and team members significantly, so you cannot switch unless you have a high degree of confidence.

On the other hand, leaving them untouched leads to obsolescence. Clinging to old technology puts you at a disadvantage in recruiting and makes it harder to secure partners. Furthermore, considering the "high turnover" premise, technology with too high a learning cost is impossible for newcomers to catch up, technology that is too niche makes it hard to find partners, and technology prone to silos leads to failure when key people leave.

I believe the core of an SIer staff engineer's job is balancing these factors while choosing weapons.

The Mission

With that in mind, here is the mission I have defined for myself:

Identify the technical stack (languages / FW / tools / services) that serves as the company's "weapon" and organize it in a form that can be deployed across projects.
Raise the technical level of the organization by creating systems that allow projects to run even when personnel change, while balancing the risks of jumping on trends versus obsolescence.

Writing it out, it might seem obvious, but by holding it as a clear definition, I hope my decisions will remain consistent.

I then organized what the specific work entails:

Category Content
Projects Technical lead, architectural design, technology selection
Cross-project Maintaining internal technical foundations, supporting implementation in other projects, judging technology updates
Mentoring Developing senior candidates, providing cross-organizational technical guidance
External Recruiting and building trust through technical outreach (speaking at conferences, writing articles)

There is work "tied to projects" and work that is "cross-project." Being a technical lead for a project can be done by a senior engineer. I think the unique value of a staff engineer lies in work that influences the organization beyond individual projects.

The Staff Dilemma

However, it is easier said than done.

Joining a project generates revenue and adds to your track record, but you lose the ability to do cross-project work. Conversely, focusing solely on cross-project work helps the infrastructure grow, but you tend to be seen as "what is that person doing?" and it is hard to evaluate since it does not directly link to revenue.

Honestly, cross-project work is often invisible. That is why I am consciously trying to "self-service" my work. I organize documentation, sample code, and templates to create a state where things run even without me. If I do that, I hope it leaves a record in the form of "using that foundation."

Summary

This time, I defined my role as an SIer-version staff engineer.

Choose the company's weapons and deploy them across projects. Create a system that works even when people change, while balancing the latest trends and obsolescence. With this single pillar in place, I have established a criterion for judging, "Is this work that I should be doing as a staff engineer?"

I wrote at the beginning that my career path felt hazy, but I think that haze has cleared. Now, I just need to do it.

Also, I never expected a book recommended by an AI to hit home this hard. I'm getting slowly molded by AI...

Discussion