What I Would Tell Someone Starting Out In Data and Cloud Strategy

By Eric Kalin, Alpharetta, GA

Start with the business problem, not the platform

Early in a career like this, it is tempting to learn the technology first and figure out the business later. I would flip that order. Multicloud, Agentic AI, security tooling, none of it means anything to a customer until you can connect it to something they are trying to fix or grow. I still start every conversation with what a customer needs, not with what a product does.

If you are new to this field, spend your first year learning to ask better questions before you spend it learning every feature of a platform. The features change every year. The discipline of listening for the real problem does not.

Learn to sit across the table from more than one function

One thing I did not appreciate early on is how much time gets wasted when sales, engineering, and operations talk past each other. Every organization I have worked in, from consulting to the large cloud providers, has some version of this problem. People defend their tower instead of solving the customer's problem.

If you are starting out, get yourself into rooms with people outside your own function as often as you can. Sit in on a solution engineering call if you are in sales. Sit in on a client meeting if you are in delivery. You will pick up more about how work actually gets done in those hours than in any formal training.

Why this matters more now

Data platforms and AI solutions cut across every part of a business now. A decision about where data lives touches security, compliance, sales, and engineering all at once. Someone who can only speak one of those languages will get stuck translating instead of leading.

Pick your certifications, but pick your mentors first

I have gone through formal training in negotiation and consultative selling, things like Holden International, TAS, SPIN Selling, Solution Selling. Those frameworks are useful. They give you a structure when you are new and unsure what to say next.

But frameworks only get you so far. The people who shaped how I think about leadership were not in a training manual. Reading about how someone like Winston Churchill held a room together under pressure, or how Golda Meir made decisions with incomplete information, taught me more about steadiness than any certification did. You do not need to study historical leaders to get this. Find people, living or not, whose judgment you trust, and study how they made hard calls.

Say yes to the unglamorous rotation

Some of the most useful years in my own path were not the flashy ones. Time spent on the operations side of a business, learning how outsourcing and delivery actually run, taught me things I still use when I talk with customers about scale and cost. If you get offered a rotation that looks less exciting than a client-facing sales role, take it anyway. You will understand the business better for having done it.

Get comfortable being wrong in front of people

Nobody starting out in technology has all the answers, and pretending otherwise is the fastest way to lose a room's trust. I would rather have someone on my team say "I don't know, let me find out" than guess and get it wrong. Customers can tell the difference. So can the people you manage later.

This is also where empathy earns its keep. Selling and leading technology decisions means understanding what a customer is afraid of, not just what they want to buy. That takes patience, and it takes being willing to sit with someone else's uncertainty instead of rushing past it to close the deal.

Build habits outside of work on purpose

It is easy to let a demanding job crowd out everything else, especially in the first few years when you are trying to prove yourself. I still make time for things that have nothing to do with data platforms, working on classic cars, fishing, getting outside. Those hours are not wasted time. They are what keeps judgment sharp when the job gets hard.

The short version

Learn the business problem before the product. Cross into other functions early. Choose frameworks and mentors deliberately. Take the rotation that teaches you something even if it is not glamorous. Admit what you do not know. Protect time for a life outside the job.

None of this is complicated. Most of it is just easy to skip when you are in a hurry to get ahead.