I’ve been looking at corporate strategy job descriptions and I’m having trouble telling which ones are actually about strategy versus which ones are secretly about process optimization or project management with a “strategy” label.
Because I’m pretty sure some companies just call their ops team “strategy” because it sounds better, and I don’t want to take a role thinking I’m building strategic thinking and then realize I’m just managing initiatives and optimizing workflows.
So here’s what I’m asking: what are the actual signals in a job description, interview process, or when you talk to current people on the team, that tell you whether this is real strategy work or dressed-up operations?
Like, are there certain phrases that are red flags? Certain types of projects that are red flags? Things you should ask in interviews that would reveal whether you’re actually going to be thinking strategically or just executing other people’s strategies?
I’m also curious if anyone’s been burnt by this—like, took what sounded like a strategic role and then realized after a month that you were basically a project coordinator with a fancy title. What tipped you off?
I want to be able to filter these before I waste time interviewing at companies where I’d just be frustrated.
Distinguishing strategic versus operational roles requires examining four indicators. First, stakeholder scope: does the role span cross-functional decision-making or execute within defined parameters? Strategic roles operate across silos; operational roles execute within them. Second, problem definition: does the role define strategic questions or solve predetermined ones? Third, success metrics: are outcomes measured by business impact or execution efficiency? Fourth, reporting structure: does the role report to C-suite directly or through functions? Most legitimate strategy roles score high on at least three of four. Job descriptions emphasizing implementation, timeline management, and cross-functional coordination often indicate operational roles relabeled strategically.
if the job description uses words like “drive alignment,” “improve efficiency,” or “optimize processes” more than “develop strategy” or “identify opportunities,” it’s probably ops dressed up. also if they’re vague about what you actually own strategically, that’s a bad sign. real strategy roles are usually pretty clear about scope.
this is so helpful. i’ll definitely look for those language patterns and ask specific questions about what strategic decisions they’re actually making
During interviews, ask directly: “What strategic initiative did your team originate in the past eighteen months that wasn’t reactive to market or operational necessity?” If they struggle to answer or cite execution of executive-driven strategy, it’s likely operational. Ask also: “Who disagrees with your team’s current strategy, and how do you navigate that?” Strategic roles navigate disagreement; operational roles execute consensus. Most importantly, talk to current team members informally and ask what percentage of their time is spent defining new strategic directions versus executing known ones.
I interviewed at a place where the “strategy” team had been tasked with implementing a cost-cutting initiative. sounded strategic on paper but it was really just tracking where money was going. i asked them what they’d proposed recently that the exec team rejected and they went silent. that’s when i knew it wasn’t real strategy. dodged a bullet there.
so asking about recent rejected proposals is a really smart sanity check. that says a lot about how much real autonomy the team has
You’ll find the right fit! Your thoughtfulness about distinguishing real strategy from ops will serve you well in finding a role that truly stretches you.