Sharing Your Work as a Software Engineer

Sharing your work is an important skill for software engineers.

And it doesn’t have to feel like self-promotion.

A lot of engineers believe that doing great work should be enough. If the work is good, people will notice.

Sometimes they will. Often, they won’t.

Sharing your work can simply mean sharing what you learned while solving a problem, explaining a technical decision you made, documenting the impact of a project, or asking someone more experienced for feedback on your approach.

It could also mean writing a blog post, giving an internal tech talk, or taking a speaking opportunity outside your company.

But it doesn’t always need to be a big effort.

Sometimes it’s just sharing something useful with your team, doing a small show-and-tell after finishing a piece of work, walking through a design decision, or explaining something you learned that could help someone else.

You don’t have to talk about how great you are. You can talk about the problem, the trade-offs, what worked, what didn’t, and what you learned.

For example, a mid-level engineer could ask a Staff Engineer for feedback on a system design they worked on. That conversation creates visibility, but more importantly, it creates learning.

I understand why this can feel uncomfortable, especially for engineers who are naturally more introverted.

But sharing your work has real benefits:

• It builds your reputation. Over time, people start to associate you with certain problems or areas of expertise.
• It compounds your knowledge. Writing or speaking about what you worked on forces you to clarify your thinking and crystallize what you learned.
• It helps other engineers learn from your experience.
• It creates opportunities for feedback, collaboration, and eventually, greater responsibility.

You don’t need to constantly announce what you’ve achieved.

Just make your work, your thinking, and your learning a little more visible.

Something I have come to learn

The real value of your knowledge and your work isn’t just in what you know or what is done, but in the leverage you create with it. And that leverage comes by socializing your work and ideas.