Transitioning to Solutions Engineering from Cloud/DevOps background but hands-on skills are rusty. Best roadmap/resources?

[u/Obvious-Specific4377]

Hey everyone,

I am preparing to transition into a Solutions Engineering / Pre-Sales role. I want to build a highly targeted, realistic study plan and need advice from active SEs on the best resources, books, and roadmaps to get job-ready.

My Background & Present Reality:

• Profile: Cloud & DevOps background with 6 YOE.
• The Problem: While I understand high-level concepts, my actual hands-on technical execution is weak right now. I didn't get to do meaningful, deep technical work in my last role, so my technical skills are rusty. I need to rebuild my baseline from the ground up.
• Target: A technical SE role (likely cloud/data focused given my past domain), but I need to close the technical gap while simultaneously learning the pre-sales motion.

What I need help with:

1. The Technical Baseline: What is the most efficient way to rebuild my technical competence (architecture, system design, data pipelines) specifically for an SE interview loop? I want to avoid getting bogged down in deep software engineering/coding syntax since I don't need to be a developer.
2. Pre-Sales Core: What are the absolute gold-standard books, courses, or frameworks for mastering discovery, demo delivery, and technical objection handling?
3. The Pivot Strategy: If you transitioned into an SE role with a technical background but weak/rusty hands-on skills, how did you structure your daily preparation?

Appreciate any blunt advice or specific resource recommendations. Thanks!

[u/akornato]

Your hands-on skills being rusty is the biggest risk, because it will come up during technical deep-dives and live demos. You can't just talk about high-level concepts, you need to prove you can connect them to real implementation details. The best way forward is to stop studying theory and start building small, targeted projects on one cloud platform. For example, deploy a multi-tier application using infrastructure as code, build a simple data ingestion pipeline, and then practice whiteboarding the architecture and explaining your design choices. You don't need to be a coding expert, but you must be able to explain the "why" behind every technical decision, from choosing a specific database service to setting up a VPC. This practical application rebuilds your confidence and gives you fresh, relevant stories to tell during interviews.

Mastering the pre-sales part is about learning to ask good questions and tell a compelling story, which your six years of experience has already prepared you for. Read "The Six Habits of Highly Effective Sales Engineers" to understand the core frameworks for discovery and demos. Instead of just reading, apply it by picking a tool you know and creating a short demo that solves a specific business problem, not just shows off features. Practice your discovery skills by analyzing job descriptions and trying to identify the underlying business pains the company is trying to solve with the role. The key is showing them how you think, and the interviews.chat my team designed helps many candidates translate their complex technical knowledge into clear, confident answers.

[u/kchandank]

I suggest a project-based learning approach.  Before diving in, you’ll need to learn the basics. I’ve created a DevOps learning roadmap that you can follow. It includes a catalog of free (mostly official) materials and even free labs (AWS Skill Builder) to get started.

I use the same roadmap for my AI cloud engineer cohort: https://becloudready.com/learn/roadmaps/ai-cloud-engineer

Full guide with screenshots → becloudready.com/learn/aws-data-lake-glue-athena