Top 5 reasons engineers quit their jobs in Australia

This title was summarized by AI from the post below.

🔥𝐓𝐎𝐏 5 𝐑𝐞𝐚𝐬𝐨𝐧𝐬 𝐖𝐡𝐲 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬 𝐈𝐧 𝐀𝐮𝐬𝐭𝐫𝐚𝐥𝐢𝐚 𝐇𝐚𝐭𝐞 𝐓𝐡𝐞𝐢𝐫 𝐌𝐚𝐧𝐚𝐠𝐞𝐫𝐬🔥 I’ve worked with hundreds of software engineers, placing them in startup, scale-up, and enterprise teams here in Australia. People don't always quit because of their manager, but when they do, I'm on the frontline, so I get their uncensored thoughts and feedback about their management team. Here's the TOP 5 frustrations I hear on repeat, and how engineering leaders can potentially avoid them: 1. Invisible Engineer Syndrome The team does the work, but they get no credit. ➡️ Don't take the spotlight or forget about them. ✅ Give credit and praise your team every opportunity you get. 2. "Just A Quick...." You’re Devs are in deep flow, solving problems, and you drop in with “just a quick....” ➡️ Don't interrupt focus for 'quick' tasks. ✅ Protect your team's focus as if it were sacred. 3. The Meeting Vortex You book meetings to plan more meetings, and stand-ups last way too long. ➡️ Don't fill calendars and stop your team from being productive. ✅ Audit meetings and cancel or downsize as many as possible! 4. “Just A Button....” You're non-technical (or a bit out-of-touch) and expect tasks “shouldn’t take long.” ➡️ Don't make unrealistic promises to stakeholders that negatively impact your team. ✅ Ask your team before you commit, and trust and respect their judgment. 5. The Dangling Carrot. 🥕 You promise promotions, pay rises and new projects, but never deliver them. ➡️ Don't make false promises or lie about shiny greenfield work coming up. ✅ Be clear about feedback, promotion targets, and if it's BAU, just say it's BAU. Number 5 is the most common one I come across. Does anyone have any others that they would add to this list? #SoftwareEngineering #Leadership #EngineeringManager

Number 4 ..... NUMBER 4!!! Oh my goodness, the number of times I have experienced stakeholders wildly underestimate the work needed to complete something, is quite frankly wild.

Number 5 for sure! It's worrying how many people start new jobs and then quickly realise they were misled during the interview about the technology, project, or pipeline.

See more comments

To view or add a comment, sign in

Explore content categories