Transitioning from Engineering to Product

Transitioning from a technical role to a “less” technical role can be scary. Let’s look at how you might evaluate a change, and some tips to succeed in the transition.  

SHOW: 609

CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw

CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"

SHOW SPONSORS:

• strongDM - Secure infrastructure access for the modern stack. 
• Manage access to any server, database, or Kubernetes instance in minutes. Fully auditable, replayable, secure, and drag-and-drop easy. Try it free for 14 days - www.strongdm.com/signup
• Datadog Kubernetes Solution: Maximum Visibility into Container Environments
• Start monitoring the health and performance of your container environment with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.
• CloudZero - Cloud Cost Intelligence for Engineering Teams

 

SHOW NOTES:

I DON’T WANT TO LOSE MY TECHNICAL SKILLS OR REPUTATION

It’s completely normal to be concerned about losing your technical skills, the thing that has established your current value to your employer, if you transition to a more product or business-focused role. 

HOW TO SUCCEED (OR AVOID FAILING) IN A TRANSITION

• Your technical knowledge will still be extremely valuable.
• Not all technical decisions are based on technology. Understanding economics, and business context, and flexibility options, and personalities involved are equally as important. 
• Understand what you’ll be building vs. managing. Is it stand-alone or part of something larger? What are the things you can influence and change? 
• Your people skills will be challenged, and rewarded. 
• Understand that you’re part of a large ecosystem of people that will determine your perceived success. 
• The choices of jobs expands when you’re closer to the people that use your technology.

FEEDBACK?

• Email: show at the cloudcast dot net
• Twitter: @thecloudcastnet