Finally Friyay!!!!!!
This week I hosted a resume hacking sesh with Johnny Wu as part of his CCing my EA AI office hours. Imma be real…I was scared sh!tless beforehand. I had this fear in the back of my mind like…What if I get on this call and add ZERO value? What if I’m awkward and forget how to speak English? What if everyone’s like “cool cool cool…why am I here?”.
Tell me why it was so much fun?!?
The room was SHARP, the questions were legit, and we got into the kind of real resume strategy that actually moves the needle in this market.
So we’re running it back!
The next session with CCing my EA will be on March 11th @ 11a EST. Make sure you’re subscribed to CCing my EA ↓↓↓ to get the calendar invite when it comes out. This time, I’m planning to live-strategize with people on how to get around the job board entirely. In this market, simply applying online with your resume isn’t going to cut it.
Anyway!
Quick personal update for those of you who have been here since my dating horror story era last summer…
I’m pleased to report (and I really hate talking about my dating life, so please appreciate the personal growth) that I am, in fact, seeing someone now who I quite like!
He’s a data scientist doing quantitative R&D (I only have the vaguest understanding of what that actually means), he’s been at his company for 6 years, and he’s starting to think about what’s next.
The other day I picked up Cracking the Coding Interview off his desk, sat down to flip through it…and immediately realized there are some VERY real takeaways that EAs can use to structure stronger, sharper interview answers. Soooooo…… let’s talk about it!
(Me after reading one hour of coding content.)
Did someone forward this newsletter to you?
🔥 This Week's Best Openings
•Executive Business Assistant (Um, what do we think about this title? Haven’t seen this exact iteration of EA before) – ATX, $100K+ [Apply here]
•Executive Assistant – Wild Alaskan, Remote [Apply here]
•Manager, Executive Assistant – MongoDB, Remote [Apply here]
Good luck if you applied!!!!
What EAs Can Steal from Cracking the Coding Interview
When most people hear Cracking the Coding Interview, they assume it’s only for software engineers.
I mean it technically is.
But at its core, the book teaches something far more valuable: how to demonstrate structured thinking under pressure. And that is precisely what hiring executives are testing when they interview you.
After years of helping founders and execs hire EAs, I can tell you this confidently: the people who get offers fastest are not always the most experienced, but the ones who think thoroughly, visibly, clearly, and calmly in the interview.
Here are the three biggest takeaways EAs can borrow from the tech world to instantly elevate their interview performance.
Takeaway #1: Think Out Loud. Don’t Just Give the Answer.
One of the biggest principles in technical interviews is that interviewers want to hear how you think, not just the final answer.
Most EAs make the mistake of giving polished but shallow responses.
Weak answer
“Yes, I’ve managed very complex calendars.”
This tells the interviewer almost nothing about your judgment.
Strong answer (think-out-loud style)
“When I manage a complex executive calendar, I start by mapping meetings to business priorities: revenue, board visibility, and external stakeholders come first. Then I look for patterns where reactive meetings are fragmenting focus time. From there, I build protected blocks and a triage system for last-minute requests.”
Now the interviewer can see your brain working.
Realistic example
Interview question:
“How do you manage competing priorities for your executive?”
High-impact response:
“I treat competing priorities as a prioritization exercise, not just a scheduling exercise. First, I confirm the executive’s current top three business priorities for the quarter. Then I evaluate each request against that lens. For example, in my last role, both Sales and Product leadership requested time during the same window. Because the Sales meeting directly impacted a live enterprise deal, I preserved that slot and worked with Product to move their review earlier in the week. I always try to make the decision logic explicit so stakeholders understand the why.”
Notice what this screams:
structured thinking
business awareness
calm decision-making
executive alignment
This is exactly what top tech candidates do and top EAs should too.
Takeaway #2: Clarify Before You Solve
In coding interviews, strong candidates rarely jump straight into the solution. They ask smart clarifying questions first.
Why? Because senior operators know that bad assumptions create bad outcomes.
EAs who do this in interviews instantly stand out.
Weak behavior
Interviewer:
“How would you handle a last-minute travel change?”
Candidate:
immediately launch into rebooking flights
This feels junior.
Strong move
Pause. Scope. Then solve.
Example response:
“Before I act, I take a quick beat to assess the variables. For example, whether the executive is already in transit and how time-sensitive the destination is. The context determines whether we reroute immediately or stabalize the existing plan forst.”
This shows:
composure
precision
real-world experience
operational maturity
Interviewers LOVE this because they get a window into how you actually work.
Realistic example
Interview question:
“How do you support multiple executives with competing needs?”
Elevated response:
“I’d love to clarify the operating model first…are the executives typically aligned on priorities, or is part of the EA’s role helping mediate conflicts between them?”
Then continue:
“In my last role supporting two VPs, alignment varied week to week. I established a weekly priority sync with both leaders so I had air cover when tradeoffs were needed. When conflicts did arise, I referenced the agreed priorities and proposed options rather than forcing a yes/no decision.”
This answer demonstrates senior-level systems thinking, not just task execution.
Takeaway #3: Walk Through Your Tradeoffs (Not Just the Outcome)
In technical interviews, candidates get major points for explaining tradeoffs and why they chose a particular path.
This is massively underutilized by EAs.
Anyone can say what they did but the people who get offers explain why that was the smartest move.
Weak answer
“I rescheduled the board prep meeting.”
Strong answer
“I considered rescheduling the board prep, but because it involved external directors across three time zones, the coordination cost was high. Instead, I protected the meeting and moved an internal review that had more flexibility. My goal is always to minimize executive and stakeholder disruption, not just solve the immediate calendar conflict.”
Now you sound like:
a business partner
an operator
someone who understands downstream impact
Realistic example
Interview question:
“Tell me about a time something went wrong with executive travel.”
High-signal response:
“During a multi-city investor trip, our executive’s connecting flight was canceled due to weather. I quickly evaluated two paths: rebooking the same night through a different hub or holding the executive overnight and preserving the morning investor meeting. Because the first meeting was with a top-five institutional investor, I prioritized arrival certainty over speed. I rerouted through an alternate airline, arranged car service on landing, and proactively briefed the investor relations team. The executive arrived 45 minutes before the meeting and the trip proceeded without escalation.”
What makes this strong:
shows options considered
shows risk awareness
shows business context
shows calm execution
This is exactly the mindset Cracking the Coding Interview rewards.
The Bottom Line
Interviewers aren’t really testing whether you can:
book travel
manage calendars
schedule meetings
They are testing whether you can think like a calm operator in the middle of a shit storm.
The EAs who consistently win offers are the ones who:
think out loud
clarify before acting
explain their tradeoffs
show structured judgment
stay composed under pressure
Borrow this playbook from the tech world, and watch how differently the room responds to you!!!
Ask a Recruiter
Stuck in your job search? Not sure how to handle a tricky interview question or navigate the hiring process? Submit your question anonymously, and I’ll answer it in an upcoming newsletter.
📅 See you next time!
Was any of this helpful?! Hit reply and let me know :)
Sydney Morris
Founder, N+1 Search
Author, The Offer Letter