The IC-to-manager move is one of the few career decisions that's almost entirely invisible from the outside. You can shadow a designer, sit in a sales call, watch a developer code. You cannot watch a manager manage. The work happens in 1-on-1s, in Slack DMs, in the half-second of judgement before sending a message - none of it visible, almost none of it written down. So when you're trying to decide whether to make the jump, the public internet helps less than you'd hope.
The shortcut is one good conversation with someone who made the move recently enough to remember the texture, and ideally hasn't forgotten what being an IC felt like. These nine questions are the ones we keep watching produce the most useful answers.
Why most IC-to-EM content is bad
Three reasons, all structural.
First, the people who write about the move publicly are mostly the ones who liked it. The ones who hated it and went back to IC don't write tweets called "Why I went back to IC" - they just go back. The corpus is filtered for people who stuck.
Second, the meaningful texture of management - the bored stretch of a 1-on-1 where you're trying to figure out if someone is unhappy or just tired, the slow accumulation of micro-decisions that adds up to a team's culture - is hard to compress into a thread. So writers reach for the cleaner stuff: frameworks, tier-lists, "I made this transition and now I love it" essays.
Third, the work itself varies enormously across companies. A Big Tech EM and a Series-A engineering lead are doing different jobs with the same title. Generic advice can't tell you which one you're walking into.
1. The day-to-day
Why it matters: Abstractions hide everything. "I do 1-on-1s, planning, hiring" is not the same as "I had four 1-on-1s, two of them about scope, one about salary, and one was a person crying about their manager - me." Force concreteness.
What a good answer sounds like: They walk you through actual blocks of time, name what surprised them, and admit which parts they enjoyed and which they didn't. If they only describe the parts that look good in a tweet, ask again.
2. The thing they didn't see coming
Why it matters: The published "what to expect" lists are about 70% accurate. The remaining 30% is what every new manager learns in the first six months and what nobody writes down. This question goes after that 30%.
What a good answer sounds like: Specific. Probably uncomfortable. "Carrying other people's anxiety home with me" is a real answer. "It's harder than I thought" is not.
3. The first hard call
Why it matters: Hiring decisions, performance conversations, scope cuts - the IC versions of these are smaller and rarer. The manager versions are bigger and constant. You want to know what the first one felt like, because that's the closest you'll get to a preview.
What a good answer sounds like: They name the actual decision and the actual people. They mention what they got wrong, even slightly. The ones who say "they were all fine, you just have to follow the framework" are either lying to you or to themselves.
4. Saying no
Why it matters: A surprising amount of management is the act of saying no - to scope creep, to stretch projects, to a promotion someone isn't ready for. Most ICs underestimate how much of the job is this. If the person you're talking to can't remember the last time, that's information.
What a good answer sounds like: A specific moment. Probably some lingering discomfort. The good managers we know remember exactly when and how, because the conversation cost them something.
5. The skills that didn't transfer
Why it matters: Every great IC has a few habits that don't survive the transition. The instinct to fix the bug yourself. The reflex to give the technical answer in a 1-on-1 instead of a question. Knowing which ones get in your way matters more than knowing which ones transfer.
What a good answer sounds like: They name the habit, the situation that caught them, and what they replaced it with. This question separates the people who thought about the transition from the people who just survived it.
6. The promotion path
Why it matters: The next rung is often a different job again, with a different scoring rubric. If the person you're asking can't describe what gets you to the next level, they probably aren't on track for it - and that tells you something about whether their company is the right reference point for your move.
What a good answer sounds like: Specific behaviours, specific scope, specific people who recently got promoted. If the answer is "you just keep doing the job well," the company doesn't have a clear path.
7. Going back to IC
Why it matters: This is the question that gets the most honest answer of any in this list. People who've done both can tell you which trade-offs they'd actually make again. The "would not miss at all" half is usually where the truth lives.
What a good answer sounds like: A short list of each, in plain language. Not "I'd miss the impact" but "I'd miss the satisfaction of finishing something on a Friday and being done."
8. The compensation honesty
Why it matters: The pay bump for becoming a manager is often smaller than people assume, especially when it's framed as a lateral move. The hour-stretch is almost always larger. Asking the rupee question directly avoids the polite version of the answer.
What a good answer sounds like: A real comparison - either "yes, by maybe 25-30 percent, and it was worth it" or "no, the bump was small and the hours were 1.5x and I'm still figuring out if it was the right call." Both are useful answers.
9. The advice they'd ignore
Why it matters: The internet is saturated with management advice. Most of it is fine. Some of it is wrong in specific ways that people who've actually done the job can name. Asking what to ignore is a faster route to good judgement than asking what to do.
What a good answer sounds like: Confident, specific, slightly contrarian. Bonus points if it makes you mildly uncomfortable.
How to actually find someone to ask
Three options, in roughly increasing order of usefulness for this specific decision.
- Your network. Cheapest, but biased - they know you and probably want to be encouraging. Use them for one of the nine questions, not all nine.
- A second-degree intro. A friend's manager, a former colleague's lead. They have less stake in your decision and can be more honest. Worth asking, but expect a 30% reply rate.
- A paid 1-on-1 with someone who's done the move. Faster, more direct, and the conversation is built around your situation rather than catching up. For a decision this big, the per-minute cost is trivial relative to the decision cost.
Talk to a manager who made the jump in the last year - not five years ago.
Amigzo Guides include EMs across product, infra, ML, and design who became managers recently enough to still remember what IC felt like. Per-minute, no commitment. Join the waitlist to get early access.
The 90-second version
- The IC-to-manager move is invisible from the outside. The internet under-prepares you for it.
- Most public content is filtered by survivorship bias - you're hearing from the people who liked it.
- One real conversation with a recent manager beats a year of articles. Pick four of the nine questions above.
- Watch for specific, slightly uncomfortable answers. They're the ones with information in them.
- Ask question 7 last. It's the one that gets the most honesty.
Nidhi R.
Editorial, Amigzo
Nidhi writes about career moves and management. She's interviewed forty-something managers in the last six months, and these nine questions are the ones that produced the answers she still thinks about.