From Executive Assistant to Chief of Staff: Is It a Realistic Career Change?

62% skills matchTypical timeline: 12–18 months

This transition is realistic for Executive Assistants with 5+ years of experience who have already operated at the boundary of operational and strategic work — but it requires a deliberate shift from execution-on-behalf-of to independent decision-making and stakeholder influence, and typically takes 12–18 months of intentional positioning.

Skills: what you have, what transfers, what to build

Skills you already have

Skills that transfer with reframing

Skills to build

Salary comparison

Executive Assistant

40,000–70,000 EUR per year (mid-career EA supporting C-suite, EU market)

Chief of Staff

70,000–120,000 EUR per year (Chief of Staff at a scale-up or mid-market company, EU market)

The salary trajectory is genuinely upward, but a short-term dip is possible if you transition into a Chief of Staff role at a smaller company or earlier-stage startup that offers equity in lieu of base pay. EAs joining larger enterprises as Chief of Staff typically move up without a base salary dip, but may need to accept a junior or 'Associate Chief of Staff' title initially — which carries a lower band. Expect the full target range to be accessible 18–24 months after the transition, not immediately.

A realistic transition timeline

  1. Foundation (months 0–3)

    • Audit your current role: list every task that touches strategy, decision support, or cross-functional coordination — these are your Chief of Staff proof points.
    • Read 3 books foundational to the role: 'High Output Management' (Grove), 'Measure What Matters' (Doerr), and 'The Effective Executive' (Drucker).
    • Begin a business analysis course (Coursera Business Analytics or a university executive education short course) and complete at least one module.
    • Have a direct conversation with your current executive about your ambition — many EAs get their first Chief of Staff opportunity internally.
  2. Repositioning (months 3–9)

    • Volunteer to own one strategic project end-to-end: write the brief, structure the workplan, track progress, and present findings to leadership.
    • Rewrite your LinkedIn profile framing your EA experience in Chiefs of Staff language: 'managed executive decision pipeline', 'coordinated cross-functional initiative', not 'managed calendar'.
    • Attend at least two Chief of Staff community events or online meetups (Chiefs of Staff Network, CoS-focused LinkedIn groups) to understand how the role is scoped in different companies.
    • Request to shadow or co-own one OKR or quarterly business review process.
  3. Active Transition (months 9–18)

    • Apply to Associate Chief of Staff or Chief of Staff roles at companies one size smaller than your current employer — your experience reads as senior there.
    • Prepare a transition portfolio: 2–3 one-page case studies of strategic projects you led, written in the voice of a Chief of Staff, not an EA.
    • Target internal promotion first: present a formal proposal to your current executive for a title and scope change, backed by a summary of strategic work already delivered.
    • Complete at least 10 informational interviews with sitting Chiefs of Staff to understand what their hiring managers actually look for and adjust your narrative accordingly.

Who makes this transition successfully

A senior EA with 8 years of experience supporting a CEO at a 300-person scale-up, who had gradually absorbed project management of two company-wide initiatives and was informally running the leadership team's weekly operating rhythm.

The boundary between their EA role and a Chief of Staff role had already blurred in practice. They formalised what they were already doing by requesting a title change, and used a new CEO hire as the moment to negotiate the repositioning. The strategic work was already on their CV — they just needed to name it correctly.

A big-four consulting firm EA with 5 years of experience who completed an MBA part-time and used the degree as the credibility bridge into a Chief of Staff role at a mid-market professional services firm.

The MBA gave them structured frameworks for the strategic analysis gap and signalled strategic ambition to hiring managers who otherwise read EAs as pure operators. They were explicit in interviews about the transition intent, which differentiated them from passive applicants.

An EA at a fast-growing startup who stepped in to lead an internal reorganisation project when the company had no Chief of Staff and the CEO was overwhelmed — and converted that 3-month project into a permanent Chief of Staff mandate.

Startup environments are more willing to reward demonstrated capability over title pedigree. Their proximity to the CEO and willingness to take on ambiguous strategic work with no additional compensation initially gave them the proof of concept they needed.

Common mistakes to avoid

Positioning yourself as 'an EA who wants to do more' rather than as 'a candidate who has already been doing Chief of Staff work'.

Audit your last 24 months and extract every instance of strategic coordination, decision support, or cross-functional leadership. Lead with that evidence in your CV and interviews, not with your aspirations.

Applying to Chief of Staff roles at companies larger than your current one, assuming years of experience create seniority in the new function.

Hiring managers at large enterprises will read you as entry-level in strategic functions regardless of your tenure as an EA. Target companies one tier smaller first, build a Chief of Staff track record for 12–18 months, then move up.

Keeping the EA framing in your CV — listing duties like 'managed travel bookings' and 'coordinated diaries' — when applying for Chief of Staff roles.

Reframe every bullet point around outcomes and strategic contribution. 'Owned the CEO's decision pipeline for a 15-person leadership team, reducing decision latency by restructuring the weekly operating rhythm' is the same job described for the right audience.

Underestimating the authority gap — assuming that because you had access to senior leaders as an EA, you can influence them as a peer in a Chief of Staff role.

Chiefs of Staff must drive accountability upward and laterally without formal authority. This is a genuinely different skill. Practice it explicitly by owning the follow-up on cross-functional commitments before you make the title change, so you have evidence it works.

This analyzed the generic Executive AssistantChief of Staff move.

Your CV, your constraints, and your goals change the answer. Get three personalized career paths, your real skills match, and filtered job links — free.

Analyze my career — free

Frequently asked questions

Can an Executive Assistant become a Chief of Staff without an MBA?

Yes — the majority of Chiefs of Staff in scale-ups and mid-market companies do not hold MBAs. What matters more is demonstrated ability to structure problems, drive cross-functional initiatives, and influence senior stakeholders. An MBA helps close the credibility gap with skeptical hiring managers at larger enterprises, but it is not a prerequisite and should not be the first investment you make.

What is the actual difference between an Executive Assistant and a Chief of Staff?

The clearest distinction is the direction of accountability: an EA's primary job is to extend the executive's capacity — reactive, execution-focused, on behalf of. A Chief of Staff's primary job is to drive strategic initiatives and organisational alignment — proactive, decision-shaping, and often independently accountable for outcomes. In practice the boundary is blurry at senior EA levels, which is exactly where the transition opportunity sits.

Is the Chief of Staff role at risk from AI automation?

The administrative and coordination components of the role — scheduling, notetaking, document formatting — are being automated, which actually raises the bar for what a Chief of Staff must deliver. The role is moving toward higher-stakes work: strategic problem-framing, leadership alignment, and organisational change management. These require human judgment and relationship capital that AI does not replicate. Chiefs of Staff who lean into that territory are well-positioned; those who stay in coordination-only work are more exposed.

How do I explain in an interview why I am making this transition from EA to Chief of Staff?

Frame it as a natural evolution of scope, not a dissatisfaction with the EA role. A strong answer sounds like: 'Over the past four years I have increasingly taken on strategic coordination work — owning our leadership operating rhythm, tracking cross-functional initiatives, and preparing board materials. Chief of Staff is the title that matches what I have been building toward.' Avoid framing it as escape from administrative work, which signals to interviewers that you may resent the operational components that Chiefs of Staff still own.