How to Become a Technical Reference?
Do you want to grow in your career and become the person your team trusts with tough technical challenges? It’s not just about writing more code. Becoming a true technical reference means developing skills that go far beyond your keyboard.
In this post, we’ll break down practical advice from Pedro Carrijo, a Senior Solutions Architect, on how to build the skills you need to become that go-to expert.
It’s More Than Just a Technical Game #
The first step is realizing that your deep technical knowledge is only one part of the puzzle. To truly become a reference, you need to connect with people, and that starts with understanding their problems. This means shifting your focus from just talking to listening.
Being a good listener helps you identify the real “pain point” — the core problem that needs solving. As Pedro explains, the technology can always change, but the underlying problem usually can’t.
Pedro: The technical side is important, but listening to our audience is more important than that because the technical [part] we can change, and the pain point we can’t change.
Think about it: have you ever built a technically perfect feature that nobody used? That often happens when we focus on the “how” before fully understanding the “why.”
Master the Art of Simple Communication #
Once you understand the problem, you need to explain the solution clearly. This is especially important when you’re talking to people who aren’t developers, like project managers or stakeholders. Using too much technical jargon can confuse your audience and hide the value of your work.
The real skill is making complex ideas simple. Pedro suggests using analogies to connect technical concepts to everyday experiences.
Pedro: You could, for example, compare a Kubernetes cluster with a kitchen in a restaurant. So many other people without the technical side could understand the benefits. For me, this is the way that I learn. When I am learning something new, I search for simple analogies to compare with my day-to-day.
This is similar to the famous Feynman Technique: if you can’t explain a concept to a child, you don’t really understand it yourself. Practicing this will not only make you a better communicator but also deepen your own understanding.
Share What You Know (Even if You’re Not an “Expert”) #
Feeling like you’re not expert enough to share your knowledge? You’re not alone. This feeling, often called “impostor syndrome,” stops many talented developers from building their reputation.
The truth is, you don’t need to know everything to help someone. Sharing what you learn as you go is a powerful way to build your authority and confidence.
Pedro: The hardest part for me is to be confident in myself that I’m doing something good… The impostor syndrome… For me, this was the hardest part… to be confident that the people will not judge me.
So, how can you create content without spending hours on it? Pedro has a great tip: turn your learning process into content.
Pedro: When I am learning, I love to do a little demo with the concepts to really understand it. After that, with a demonstration, I already have material and content to do a blog post, a LinkedIn post, or a lecture.
Practical Tools to Sharpen Your Skills #
Okay, so we know we need to listen, communicate clearly, and share knowledge. But how can we practice these skills? Here are two powerful methods Pedro uses.
1. The STAR Method #
The STAR method (Situation, Task, Action, Result) is a fantastic way to structure your thoughts, especially when explaining a project or an experience. It forces you to be clear and focus on the outcome.
- Situation: What was the context?
- Task: What was your responsibility?
- Action: What specific steps did you take?
- Result: What was the outcome of your actions?
This method helps you tell a compelling story about your work, making it easier for others to see the value you created.
2. Use AI as Your Interviewer #
This is a brilliant and modern trick. Instead of asking an AI to write an article for you, ask it to help you write it with your own voice.
Pedro: I say, “I would like to write an article about X subject, and I would like you to ask me many questions about this subject.” I will answer you with my own words and my own experience, and after all that, I need you to organize these words into an article structure. I have a new article from zero with my own words, and I used AI to help me do this faster.
This turns content creation into a conversation, ensuring the final piece is authentic, personal, and much faster to create.
The Leap from Senior Dev to Problem Solver #
As you grow in your career, especially if you move towards roles like an architect, your focus will naturally shift. You’ll spend less time coding and more time understanding business goals. Your job changes from being a coder to being a problem solver.
This doesn’t mean your technical skills are no longer important! In fact, your deep technical background is what allows you to find the best solutions. The key is to connect those solutions to business value.
Pedro: If you want to grow in value, for example, and you already are very technical, you can use this experience to become more expensive by helping the company gain more money. If you sell, you are very important, and the architect or engineering solutions are positions that are side-by-side with salesmen.
Conclusion #
Becoming a technical reference is a journey of growth. It’s about more than just mastering a language or framework. It’s about learning to:
- Listen to understand the real problem.
- Communicate complex ideas simply.
- Share your knowledge consistently, even when you feel like an impostor.
- Connect your technical work to business value.
By developing these skills, you’ll not only become the go-to expert on your team but also open up new and exciting opportunities for your career.