Beyond Code: The Skills That Accelerate Engineering Careers
Technical mastery is essential for every embedded engineer, but in the corporate engineering landscape it is only one piece of the progression puzzle. Many talented engineers stagnate not because they lack technical skill, but because they fail to develop the complementary abilities that enable influence, visibility, trust, and leadership.
In this microtalk, I will distill key non-technical skills that accelerate career growth for embedded professionals:
- Communicating technical ideas to non-technical stakeholders.
- Building cross-functional relationships.
- Developing business awareness and understanding product impact.
- Proactively shaping engineering decisions.
- Mentoring others to scale your own knowledge.
I will share real examples from my journey leading global firmware teams, illustrating how engineers who cultivate these capabilities expand their impact, gain organizational recognition, and open doors to leadership roles. This talk aims to provide a concrete perspective on how to evolve from an excellent engineer into a high-value engineering leader in a corporate environment.
What this presentation is about and why it matters
What actually helps an engineer grow when strong technical work alone is not moving the career forward? Manuel Herrera, who leads embedded engineering teams globally, uses a short, opinionated career lens to explore that tension. Rather than a code-centric tutorial, this microtalk connects engineering growth to how work is understood, communicated, and noticed inside an organization. He grounds the idea in familiar embedded-career realities, then widens the frame to product, roadmap, and cross-team impact. If you are trying to understand why good work sometimes stalls, or how to make your contributions easier for others to act on, this talk gives you a focused way to think about it.
Who will benefit the most from this presentation
- Embedded engineers who are delivering solid technical work, but want their broader contribution to be recognized.
- Technical leads or managers who need to help engineers connect implementation details to product impact.
- Individual contributors in cross-functional teams where communication shapes what gets prioritized.
- Engineers early in leadership growth who want a clearer model for career development beyond code quality.
What you need to know
No special technical background is needed. It helps to be familiar with everyday engineering work and the realities of collaborating across a team or organization.
Glossary (terms used in this talk)
- Meta skills: Skills that increase the reach and effectiveness of technical ability, especially in how work is communicated, understood, and applied by others.
- Capability: The actual ability to do the work, solve problems, and deliver results. In career discussions, it is one side of the gap between what someone can do and what others perceive.
- Perception: What others believe about a person's ability, impact, or readiness, based on what they can see and hear. It often influences decisions when direct visibility into the work is limited.
- Formula One: A motorsport example often used to contrast raw performance with strategy, coordination, and execution under pressure.
- Visibility: The practice of making your work, impact, and decisions understandable and discoverable by others so they can recognize and act on them.
- Capability-perception model: A simple career-growth model that frames outcomes as the interaction between capability (what you can do) and perception (what others believe you can do).
Final thoughts
Practical and reflective, this microtalk offers a compact career lens rather than a checklist. The value is in the mental model: a way to reason about why some engineering work travels farther than other work, and what helps technical contributions become legible to the people who make decisions. It will be useful for engineers, tech leads, and managers who care about growth that is grounded in real impact. Clear work matters, and being seen clearly matters too.
This overview is AI-generated from the session transcript. Spot an issue? Let us know.
Thanks Manuel for the advice, you are correct.
And I agree with Max, the middle management plays an important role in nurturing and rewarding talented and dedicated staff. Most engineers I know are introverts and will happily remain under the radar as long as the work is interesting.
I can't help but think of the Peter Principle when talking about careers :-)
Insightful talk. I agree that the "visibility" and "communicability" of the engineers play a fundamental role in career and reward in many companies. And since we are engineers, we solve problems; investing more in communication is our way to cope with this.
Changing perspective and watching this from the company's point of view, the risk is to demotivate or lose competent and skilled engineers, just because they don't love to show off and the company is not able to understand what they do. Maybe a middle layer of technical management capable of bridging the engineers' achievements with the upper management and/or the career opportunities would be a good investment.