Enterprise Strategy Consultant

About the role

The Enterprise Strategy Consultant owns a full engagement module — a coherent problem area within a GuideWell strategy engagement — and runs it autonomously from hypothesis to recommendation. The Associate shapes the module’s hypotheses and analytical approach, picks the right methods unprompted, and synthesizes the work into a defensible recommendation that holds up to challenge. Associates also carry the day-to-day relationships with the business-unit stakeholders in their module, and are fluent in a domain — Medicare Advantage, commercial, pharmacy, or similar — to be credible with the subject-matter experts they work alongside. This is the level at which the toolkit becomes judgment: the priority is to be trusted with a whole problem area, and to prepare for Senior Associate, where scope widens to several modules and a small team. GuideWell is building an in-house Enterprise Strategy team — a strategy and internal-consulting group that works on the company’s most important questions — and we are hiring Associates to help form its foundation. As an Associate, you own a full module of an engagement: you frame the hypotheses, decide how the problem gets solved, direct the analysis, and carry it through to a recommendation you can defend to the business. You also own the day-to-day relationship with the stakeholders in your problem area — consulting-caliber ownership and a close-up view of a Fortune 500 health company, without the constant travel. You will thrive here if you would rather shape the approach than receive it, are comfortable being the person who owns a whole problem area, and want to go deep enough in a domain to be credible with the people who live in it every day.

Responsibilities

• Own a full engagement module — a coherent problem area — autonomously, from framing through to recommendation.
• Set and manage the module workplan, sequencing the analysis and making the trade‑offs that keep it on time and on point.
• Direct the Analysts and Senior Analysts contributing to the module, and own the quality of everything that comes out of it.
• Escalate early and precisely when the answer is moving, the data will not support the question, or the scope needs to change.
• Frame the hypotheses for the module and choose the right analytical methods unprompted.
• Design analyses that answer the question rather than merely describe the data, and know when a rough cut is enough.
• Challenge the module’s own conclusions — look for the disconfirming evidence before someone else finds it.
• Build a module‑level narrative end to end, moving from findings