The #1 reason software engineers leave their jobs is a lack of growth opportunities. Often they feel stagnant due to unclear career paths, outdated tech stacks or limited chances to upskill. If you’re in a management role, you’re likely balancing business objectives, team goals, and your team members’ individual aspirations - it's really hard to get things right without a competency framework in place. First of all, it makes hiring a lot easier when you know exactly what skills and behaviours are non-negotiable. Secondly it really can drive performance in your team: when competency frameworks are well-defined everyone knows where they are, what's expected and how to move forward. And lastly, to get back to the retention issue: engineers don't leave companies - they leave stagnation. With the righ competency frameworks in place you can provide a roadmap for growth, showing team members exactly how they can develop and advance, keeping them engaged and motivated. If your team doesn't have a framework for what defines skills and success, you're esentially flying blind and it will be really hard to hire well, define and offer growth and ultimately make your team better. Over the last couple of years I've supported a number of startups defining compentency frameworks for specific roles within their engineering teams. From out-of-the-box SFIA 8 & 9 aligned frameworks, to bespoke frameworks tailored to the structure of the business. Recognize this challenge? Let's do something about it this year. Reach out via DM or [email protected]
Bastiaan Vermeulen’s Post
More Relevant Posts
-
I feel this should be addressed to CEOs personally 😅 'Dear CEO - it's not 2015 anymore, you actually have to care about how good the engineers you hire are now.' The reason I address this to CEOs rather than CTOs is that board level, and indeed executive discussions, do not include as much technical leadership or HR leadership as they should. I personally think given the importance of technology, how can a board not have technical stakeholders present during discussions? Its actually very scary if you consider it that way. Especially re security. I object to the idea that 'engineers are spoiled', it's too general so adding my 2c which are still generalised but drill down a little more. My thoughts below are based on the assumption that you hire good people (like in any role). Bad people in any role are inherently spoiled so I'm excluding that discussion. Bad engineers getting good engineers salaries obviously makes them spoiled and yes, there are a lot of bad engineers. Entry level engineers yes definitely spoilt - entry level staff salaries are too high / have been too high given the cost of training a junior to the same level (especially in the US, they are actually fine in the UK). Enthusiasm and willingness to learn are what you pay for in a junior and that exists in abundance if you're a good place to work. Mid level maybe - the main requirement between a junior and a mid level engineer is around applying business logic to code, communication and collaborative capabilities (nothing to do with writing code). Tooling and programming syntax are permission to play for both junior and mid level roles. I feel a good mid level engineer is very valuable based on their future potential. Senior, no way are they spoiled - a single good senior engineer can completely change a companies direction and profit margins. Software still has, arguably even more nowadays, the ability to add more value than any other role as an individual outside of leadership. e.g One person can save Netflix millions/tens of millions a year from one/ten lines of code. Given techs importance in this day and age I think that many of the issues described in this article are caused by engineering being *excluded* from key business conversations. The number of boards which still don't include any technical talent is outrageous. How can engineering communicate with other departs in context if no engineering team members are included (CTOs / lead engineers) in business decision making? No CTO / engineering lead wants loads of less capable people being paid more on their team 😅. Feels like a non tech company hiring tech people issue to me. An issue for companies who have no technical stakeholders on their board / in their board meetings.
Engineering leaders are acting like it's still 2015. 🚫 They think that it's Product Management's job to explain what engineers do. 🚫 They think priorities can be set on trust and good faith. 🚫 They mistake DevEx metrics for ‘productivity’ indicators. Engineering in 2024 isn't about hoarding and amassing talent, but pushing the limits on streamlining. Hundreds of thousands of eng jobs have been cut, with more each quarter. The era where engineers never feared unemployment is over. This is a problem because 90% of the REAL work of engineering - resourcing, maintenance, and architecture - is completely invisible outside the engineering team. How do you visualize breaking up a monolith? Your maintenance load? Your critical institutional knowledge? How do you assess capability? In other words: how do you make strategic cuts (or assess the promise of an unknown quantity like AI) when you don't even know what the work is? The truth is that Big Agile is far, far divorced from the actual work of engineering. When misguided non-technical leaders make blind cuts into critical resourcing trying to use 'story points', they're just shooting themselves in the foot. This is my 🔥spiciest🔥 post to date. https://lnkd.in/eBEMiCbh 🧐 Thoughts, feedback, pushback, and new perspectives always welcome ❤️ Help a founder out? Please share/repost/subscribe if you enjoyed this read
To view or add a comment, sign in
-
Software engineers in big tech aren’t inherently more skilled than those outside of it. However, one key takeaway from working in big tech is understanding the business impact and value of the work you do. Unfortunately, some companies try to "protect" their engineers by withholding this information, thinking they’re doing them a favor. In reality, this approach: 1. Erodes accountability within engineering teams, leading to a culture of blame. 2. Limits engineers’ understanding of the bigger picture, resulting in decisions that don’t align with business goals. 3. Hinders innovation, as engineers lack the context to suggest impactful solutions. 4. Creates a gap between technical work and real-world outcomes, diminishing motivation and job satisfaction. When software engineers are empowered with business context, they not only write better code but also become vital contributors to the company’s success. They also gain valuable experience in understanding how businesses operate. Neglecting this connection is a lost opportunity for growth—for both engineers and the organization. #SoftwareEngineering #BusinessContext #CareerGrowth #Innovation #Leadership #TeamCulture #Developers #BigTech #Motivation
To view or add a comment, sign in
-
Two of our best engineers don't have traditional engineering degrees. Last week, midnight: 1. Production issue hits 2. First engineer (Ajith Kumar VM) spots the problem messages the group. 3. I jump on the slack call. not that I can help. Just a moral support. 3. He's already isolated the problem and coded the fix. But needs a 2nd person's approval to push to production 4. Calls his partner-in-crime (SACHIN S) 5. Sachin is at a movie (Venom 3). he steps out, reviews the code and approves (I don't know why he has a laptop at a movie) 6. Issue fixed! Our CTO Aromal Sivadasan is fast asleep and didn't even know until morning. 😂 What's wild is: • Neither has a traditional engineering degree • Both learned coding through diploma courses • Previous startups they worked at failed • Most big tech wouldn't even interview them - because "no proper degree" 🤦♂️ They're absolute rockstars. Yet, last month alone: • Implemented enterprise-grade 2FA • Built complex automation systems from scratch • Fixed critical issues in minutes • Zero escalations to anyone else The kicker? They come as a package deal. Worked in 3 startups together. Where one goes, the other follows. Like a buy-one-get-one deal, except you're getting two engineering powerhouses who consistently make your billion-dollar competitors look silly. To every recruiter who's rejected candidates because they lack a "proper degree": Your loss is my competitive advantage. — To every founder obsessing over credentials: While you're filtering resumes by university names, these "unqualified" engineers are shipping features, fixing production issues, and building the future. To Ajith Kumar VM and SACHIN S: Keep making the "highly qualified" engineers wonder how you do it. 🧡 — In an industry obsessed with pedigree, remember: The next game-changing engineer might be the candidate your ATS just rejected. Think about that.
To view or add a comment, sign in
-
-
Platform engineering is transforming how organisations operate. One of the biggest advantages is efficiency. By creating a standardised platform, teams can streamline development processes. This reduces duplication of effort and speeds up time-to-market. 🚀 Another key benefit is reliability. With a dedicated platform, you can ensure consistent environments for development, testing, and production. This minimises errors and enhances system stability. Lastly, platform engineering fosters innovation. By freeing up developers from repetitive tasks, they can focus on creating new features and improving user experience. What are your thoughts on platform engineering? Comment below or connect with me if you're looking to hire or find a new role. Visit charles-simon.co.uk. ✅ Efficiency ✅ Reliability ✅ Innovation #PlatformEngineering #TechInnovation #ITRecruitment
To view or add a comment, sign in
-
What’s driving software engineers to leave? 🧑💻 https://lnkd.in/dnBG-wH3 One key reason is feeling the hierarchy’s weight. When leaders demand unquestioned acceptance of their decisions, without allowing feedback or discussion, frustration builds. Developers want to feel heard and respected, not silenced by hierarchy. Leaders should support, not demand. Listening to your team’s ideas fosters collaboration and loyalty — ignoring them drives talent away. There are more reasons why tech professionals leave. Discover them in the article 👉 https://lnkd.in/dnBG-wH3 #motivation #retention #recruitment #quit #IT #softwareengineer #techteam
To view or add a comment, sign in
-
-
Tech offers diverse career paths for software engineers, from independent contracting to management roles. Prioritize professional development, support your team, conduct one-on-one meetings, mitigate unconscious bias, and enhance virtual management skills to excel. #180Engineering #TechCareer #EngineeringManager #SoftwareEngineer #CareerGrowth #ManagementSkills #ProfessionalDevelopment #Leadership #RemoteWork #DiversityInTech
To view or add a comment, sign in
-
Almost each Tech & IT skill gets upgraded with new versions within weeks if not days, just-in-time requirement for talent & short tenure for the resource makes it imperative to look at "staff augmentation models" to bridge & fulfill talent needs. Useful pointers if you are building robust & agile Tech Engineering & IT Teams in below article: https://lnkd.in/gm83UPFa
To view or add a comment, sign in
-
If you are an American startup, hire engineers in America (including immigrants). When it comes to software, quality matters. Engineers abroad are cheaper, but that does not matter if your software delivers little to no value to its users. There is a reason why the very best software companies in the U.S. mostly hire engineers in America. The only exception is if you can have them work U.S. hours, treat them as members of your team, and fit your culture. Of course, quality should be top-notch.
To view or add a comment, sign in
-
🎖 💻 The Often Unseen Synergy Between Military Experience and Software Development and Engineering 💻 🎖 We live in an era where technology rapidly evolves and shapes our future. The intersection of diverse experiences and fields has never been more critical. Transitioning from a Marine to a Senior Software Development Mentor and Senior Software Engineer, I've lived at this crossroads, witnessing firsthand the synergy between military skills and software development and engineering, as well as the challenges of transitioning from the military into the tech industry. Discipline and Precision: The military instills a level of discipline and attention to detail unmatched in most professions. In software development, this translates to writing clean, efficient code and meticulously testing and debugging applications. The ability to focus on the task at hand can mean the difference between a successful launch and a buggy release. Adaptability and Problem-Solving: Problem-solving is the number one skillset that any developer or engineer can have. The battlefield teaches you to adapt in high-stress situations with limited information. Similarly, the tech landscape is ever-changing, requiring developers to continuously learn and apply new technologies and methodologies. Leadership and Teamwork: Leadership in the military isn't just about giving orders; it's about inspiring trust, fostering teamwork, and leading by example. These skills are equally vital in tech projects, where cross-functional teams must collaborate effectively to bring complex projects to fruition. Strategic Planning: Military operations require careful planning and strategy, considering various outcomes and their impacts. This instills a great amount of foresight in our military veterans. This mindset aids in architectural decision-making, ensuring scalability, security, and efficiency from the ground up. Resilience and Grit: Perhaps most importantly, the military teaches resilience—the ability to face setbacks and continue marching forward. In the world of tech, where failure is often seen as a step towards innovation, having the grit to persevere through challenges is a priceless trait. To those transitioning from the military to tech: Your skills are not just transferable; they are a competitive advantage. Embrace them. It may be difficult to get your foot in the door, but there are many hiring managers that see your skills as huge assets to their team. Keep driving forward. If you ever need advice, please reach out, I'm always willing to help a brother/sister in arms. To hiring managers in tech: Look beyond traditional profiles. The diverse experiences and skills veterans bring to your teams can drive innovation and success in ways you might not have anticipated. The journey from the military to tech is not without its challenges, but the rewards—the chance to innovate, to solve complex problems, and to continue serving a purpose bigger than oneself—are truly worth it.
To view or add a comment, sign in
-
This post https://lnkd.in/gQFYzbV5 — “This isn’t universally true of all engineering leaders, but these norms pervade engineering culture. Engineering has operated under unique circumstances for so long that most CTOs have never experienced a ‘normal’ business environment. They think priorities can be set on trust and good faith. They mistake developer experience metrics for ‘productivity’ indicators. They think that the product team sharing a roadmap should be enough to explain what engineering is working on. “ … “This wouldn’t be a problem in any other function; you don’t read about JetBlue making cuts to their marketing budget and immediately wonder if you could also cut your ad spend. But engineering has a unique problem because no one really knows what engineers actually do all day.” And we are still producing developer productivity benchmarks using the number of pull requests merged by engineering teams. Because.. that’s what engineering leaders want… The message has clearly not gotten through.. #developerproductivity #engineering #software
To view or add a comment, sign in