If you have to pick: is it more important for a software engineer candidate to have a certain number of years of experience, or is it more important that they have relevant training/education?

Years of experience50%

Type of training50%

8 PARTICIPANTS

66 views1 Upvote1 Comment

Sort by:

CTO in Mediaa year ago

In most cases, I find experience to have more potential value than a one-off education.
However, time in a role does not mean "years of experience" directly.

Progressive growth is needed, and years of experience can allow that growth.

In any role of impact, I want to know if the candidates have theory understood and have been able to test and prove themselves before.

Content you might like

What are your most important criteria when weighing a new software leadership opportunity? Which aspects of the job do you prioritize over others?

What would make cybersecurity training more enjoyable?

If it were presented in simpler language.19%

If it was more fun (i.e. gamification)60%

If it were broken into shorter courses17%

Nothing, it's boring no matter what!2%

View Results

What benefits drove you to adopt agile practices? Select all that apply.

Enhanced ability to manage changing priorities32%

Accelerated software delivery52%

Increased software maintainability37%

Increased team productivity40%

Improved business & IT alignment35%

Improved project visibility25%

Improved team morale15%

Improved engineering discipline17%

Better management of distributed teams15%

Reduced project cost15%

Reduced project risk10%

Improved response to volatile market conditions8%

Other (please specify)1%

View Results

Software Engineers often get pegged as the team that says “no” or “that’s impossible”. How do you maintain a strong and trusting relationship with the product team while continuing to reset their expectations?

Digital transformation isn’t just about new tools, it’s about changing how teams work. Key lessons I’ve observed: 1. Start with process bottlenecks, not technology 2. Empower cross-functional teams 3. Measure outcomes, not outputs What has been the most surprising lesson your teams have learned during a transformation?