<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: RainbowRoadPrep</title>
    <description>The latest articles on DEV Community by RainbowRoadPrep (@rainbowroadprep).</description>
    <link>https://dev.to/rainbowroadprep</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4254895%2Fcb66fca9-bb50-41f1-99d8-bfb14516b614.png</url>
      <title>DEV Community: RainbowRoadPrep</title>
      <link>https://dev.to/rainbowroadprep</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rainbowroadprep"/>
    <language>en</language>
    <item>
      <title>Your First 90 Days as a New Engineering Manager</title>
      <dc:creator>RainbowRoadPrep</dc:creator>
      <pubDate>Fri, 20 Nov 2026 05:56:53 +0000</pubDate>
      <link>https://dev.to/rainbowroadprep/your-first-90-days-as-a-new-engineering-manager-69l</link>
      <guid>https://dev.to/rainbowroadprep/your-first-90-days-as-a-new-engineering-manager-69l</guid>
      <description>&lt;p&gt;You got the job. Now what? The first 90 days as a new engineering manager set the tone for everything after — and the most common mistake is trying to prove yourself too fast.&lt;/p&gt;

&lt;p&gt;New managers often arrive with a list of changes. They reorganise the team in week two, rewrite the roadmap, or fix a process nobody asked them to fix. The team reads that as: this person did not bother to understand us first.&lt;/p&gt;

&lt;h2&gt;
  
  
  Days 1–30: Listen
&lt;/h2&gt;

&lt;p&gt;Your first month is a listening tour. Meet every person on your team one-to-one, and ask the same few questions: what is working, what is frustrating, what would you change, what do you need from me? Meet your peers, your manager, and the people your team depends on. Map the team: who does what, who is stretched, who is quiet, where the knowledge lives.&lt;/p&gt;

&lt;p&gt;Write it down. A simple team map — people, strengths, risks, open questions — is worth more than a dozen opinions. Run your first team meeting as an introduction, not a strategy session. Tell the team what you are doing in the first 30 days (listening), and when you will come back with a plan. Then keep that promise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Days 31–60: Align
&lt;/h2&gt;

&lt;p&gt;Now pick one to three levers — the changes that would help most — and run one small experiment. Not a reorganisation. One experiment: a better on-call rotation, a clearer definition of done, a weekly planning meeting that actually ends on time. Set working agreements with the team: how decisions get made, how feedback works, what "done" means.&lt;/p&gt;

&lt;p&gt;This is also when difficult conversations start. Feedback given early, specifically, and kindly is far easier than feedback saved for a review. If someone is struggling, say so in week five, with a clear plan and support — not in month six, when it has become a performance case.&lt;/p&gt;

&lt;h2&gt;
  
  
  Days 61–90: Lead
&lt;/h2&gt;

&lt;p&gt;By now you should be able to review the experiment honestly: did it help, what would you change, what is next? Set direction for the next quarter, write growth plans with each person, and clarify decision boundaries — what you decide, what the team decides, what goes up to your manager. Manage up, too: tell your manager what you learned, what you changed, and what you need from them.&lt;/p&gt;

&lt;p&gt;Check in with yourself at day 30, 60 and 90. Are you listening enough? Are you delegating, or doing the work yourself because it is faster? Are the quiet people getting heard? A fifteen-minute weekly review — what went well, what did not, what to try next — keeps you honest.&lt;/p&gt;

&lt;h2&gt;
  
  
  The mistakes to avoid
&lt;/h2&gt;

&lt;p&gt;Do not change everything at once. Do not keep the old manager's habits just to be liked. Do not avoid the hard conversation. Do not try to be the technical expert on everything — your job is now the team, not the code. And do not skip one-to-ones when things get busy; that is exactly when they matter most.&lt;/p&gt;

&lt;p&gt;The first 90 days are not a test you pass or fail. They are the foundation for the next year. Listen first, align on a few things, then lead — in that order.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Want the templates? The First 90 Days as a New Engineering Manager Playbook ($15) has a listening-tour script, team map, 30-60-90 plan, 1:1 and team-health templates, and day 30/60/90 checklists: &lt;a href="https://rainbowroadprep.gumroad.com/l/guqmxi" rel="noopener noreferrer"&gt;https://rainbowroadprep.gumroad.com/l/guqmxi&lt;/a&gt; — and the free interview sample is here: &lt;a href="https://rainbowroadprep.gumroad.com/l/qiptza" rel="noopener noreferrer"&gt;https://rainbowroadprep.gumroad.com/l/qiptza&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>engineeringmanager</category>
      <category>career</category>
      <category>leadership</category>
      <category>management</category>
    </item>
    <item>
      <title>Salary Negotiation for Engineering Managers: Don't Rush the Money Talk</title>
      <dc:creator>RainbowRoadPrep</dc:creator>
      <pubDate>Fri, 20 Nov 2026 05:48:17 +0000</pubDate>
      <link>https://dev.to/rainbowroadprep/salary-negotiation-for-engineering-managers-dont-rush-the-money-talk-2oah</link>
      <guid>https://dev.to/rainbowroadprep/salary-negotiation-for-engineering-managers-dont-rush-the-money-talk-2oah</guid>
      <description>&lt;p&gt;You passed the interviews. The recruiter calls with good news, then asks the question most candidates dread: what are your salary expectations?&lt;/p&gt;

&lt;p&gt;Most engineering manager candidates rush this part. They name a number too early, accept the first offer out of relief, or avoid the conversation entirely and hope the company is fair.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with research, not a number
&lt;/h2&gt;

&lt;p&gt;Before you talk money, find your range. Look at public salary data for the role, level, company size and location, and talk to peers if you can. Write down three numbers before any call: your walk-away (the lowest you would accept), your target (what you would be happy with), and your anchor (the first number you state, slightly above your target). If you do not know your walk-away, you cannot negotiate — you can only hope.&lt;/p&gt;

&lt;p&gt;Remember that compensation is not just base salary. Bonus, equity or RSUs, sign-on, refreshers, vesting schedules, remote flexibility and time off all have value. A lower base with strong equity and a sign-on can beat a higher base over three years. Compare offers over three years, not just year one, and write the comparison down.&lt;/p&gt;

&lt;h2&gt;
  
  
  Say less, ask more
&lt;/h2&gt;

&lt;p&gt;On the recruiter call, your job is to listen first. Ask how the range was set, what the level covers, and what flexibility exists. When you do state a number, give a reason tied to the role: scope, team size, on-call, the market range you found.&lt;/p&gt;

&lt;p&gt;If the recruiter pushes back, do not panic. Pushbacks are normal, and most have calm replies. "That's above our band" can be answered by asking what the band is and what else can move — equity, sign-on, a review in six months. "We need an answer today" can be answered by asking for 24 hours to review the full written offer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ask for things besides salary
&lt;/h2&gt;

&lt;p&gt;If base will not move, other things often will. More equity, a sign-on bonus, extra time off, remote days, a learning budget, a title that matches the scope, or a compensation review after six months are all real asks. Make a list of twelve such asks before the call, ranked by what matters to you, so you are not inventing them under pressure.&lt;/p&gt;

&lt;h2&gt;
  
  
  The five-day plan
&lt;/h2&gt;

&lt;p&gt;You do not need weeks. Day one: research the range and write your three numbers. Day two: build your three-year offer comparison. Day three: pick your scripts for the recruiter call, the counter email, and the pushbacks you expect. Day four: practise them out loud, ideally with a friend playing the recruiter. Day five: make the call, then put the final offer in writing before you accept.&lt;/p&gt;

&lt;p&gt;The most common mistake is treating negotiation as confrontation. It is not. It is a conversation about fit: the company wants you, and you want the role to work for three years, not three months. A calm, prepared counter respects both sides.&lt;/p&gt;

&lt;p&gt;No one can guarantee an outcome, and no script works in every situation. But a candidate who knows their numbers, has scripts ready, and compares offers over three years will almost always do better than one who improvises.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Want the scripts and worksheets? The EM Salary Negotiation &amp;amp; Comp Playbook ($19) has 15 copy-and-edit scripts, a three-numbers worksheet, a 3-year offer comparison, 10 recruiter pushbacks and 12 non-salary asks: &lt;a href="https://rainbowroadprep.gumroad.com/l/ovgaxt" rel="noopener noreferrer"&gt;https://rainbowroadprep.gumroad.com/l/ovgaxt&lt;/a&gt; — and the free interview sample is here: &lt;a href="https://rainbowroadprep.gumroad.com/l/qiptza" rel="noopener noreferrer"&gt;https://rainbowroadprep.gumroad.com/l/qiptza&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>engineeringmanager</category>
      <category>salary</category>
      <category>negotiation</category>
      <category>career</category>
    </item>
    <item>
      <title>How I prepare EM candidates to answer 30 leadership questions with 12 stories</title>
      <dc:creator>RainbowRoadPrep</dc:creator>
      <pubDate>Fri, 20 Nov 2026 05:22:00 +0000</pubDate>
      <link>https://dev.to/rainbowroadprep/how-i-prepare-em-candidates-to-answer-30-leadership-questions-with-12-stories-1oic</link>
      <guid>https://dev.to/rainbowroadprep/how-i-prepare-em-candidates-to-answer-30-leadership-questions-with-12-stories-1oic</guid>
      <description>&lt;p&gt;Most engineering manager candidates I talk to prepare the same way: they write out full answers to 30 interview questions, memorise them, and then freeze when the interviewer asks the question slightly differently.&lt;/p&gt;

&lt;p&gt;It is not a knowledge problem. It is a preparation problem. You cannot memorise 30 scripts and deliver them naturally under pressure. You can, however, prepare 12 stories and use them to answer almost any leadership question.&lt;/p&gt;

&lt;p&gt;That is the whole method. The rest of this post is how to do it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why scripts fail
&lt;/h2&gt;

&lt;p&gt;A script is brittle. If the interviewer asks "tell me about managing an underperformer" and your script is about an underperformer, you are fine. If they ask "tell me about a time you had to give difficult feedback to someone who was struggling," and your script was filed under a different question, you hesitate — and hesitation reads as uncertainty.&lt;/p&gt;

&lt;p&gt;A story is flexible. One real experience — an engineer who was missing commitments, the plan you put in place, the weekly check-ins, the outcome — can answer the underperformer question, the feedback question, the follow-through question, and the "how do you support struggling people" question. Same facts, different emphasis.&lt;/p&gt;

&lt;p&gt;Interviewers are not scoring your memory. They are scoring evidence: did you act early, did you do something specific, did you follow through, and did anything change after?&lt;/p&gt;

&lt;h2&gt;
  
  
  The 12 stories
&lt;/h2&gt;

&lt;p&gt;Start by listing 12 experiences from your own work. Not 12 perfect successes — 12 real situations with a decision in them. A useful starter set:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;An underperformer who turned it around — or didn't&lt;/li&gt;
&lt;li&gt;Giving hard feedback&lt;/li&gt;
&lt;li&gt;Letting someone go, handled well&lt;/li&gt;
&lt;li&gt;A conflict with a peer&lt;/li&gt;
&lt;li&gt;Retaining someone who was about to leave&lt;/li&gt;
&lt;li&gt;A project rescue&lt;/li&gt;
&lt;li&gt;A bad hire, and what it taught you&lt;/li&gt;
&lt;li&gt;Disagreeing with your manager — and committing&lt;/li&gt;
&lt;li&gt;Leading an incident&lt;/li&gt;
&lt;li&gt;Growing a senior engineer toward staff&lt;/li&gt;
&lt;li&gt;Delivering across teams&lt;/li&gt;
&lt;li&gt;A difficult stakeholder&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You do not need a dramatic story for each one. You need a specific situation, what you actually did, and an outcome you can defend. Approximate numbers you can explain beat precise numbers you invented — "about a third of reviews were late" is fine; a metric you cannot explain under follow-up is not.&lt;/p&gt;

&lt;p&gt;Write each story in STAR form, but keep it short: situation in two lines, what you did, the outcome, and what changed after. If it takes more than 90 seconds to say out loud, it is too long.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mapping stories to questions
&lt;/h2&gt;

&lt;p&gt;Now take 30 leadership questions — the usual spread across people and performance, delivery, technical leadership, team and culture, stakeholders and strategy, and your management story — and map each question to one or two of your stories.&lt;/p&gt;

&lt;p&gt;This is where the method pays off. "How do you retain your best people?" is not a philosophy question. It is story 5: who was at risk, how you knew, what you changed, how long they stayed or grew. "How do you handle conflict between two reports?" is story 4, or a version of it: hear each side separately, a joint conversation, an agreement, a check-in afterwards.&lt;/p&gt;

&lt;p&gt;When you map it out, you will find gaps. Maybe you have no story for hiring, or no story for letting someone go. That is useful information — it tells you what to prepare, rather than discovering the gap in the interview.&lt;/p&gt;

&lt;p&gt;Practise the mapping out loud, timed. Ninety seconds per answer is the target. Two minutes is the ceiling. If your answer is over two minutes, you have lost the interviewer, however good the content is.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a strong answer actually sounds like
&lt;/h2&gt;

&lt;p&gt;Take the underperformer question. A weak answer sounds like this:&lt;/p&gt;

&lt;p&gt;"I waited and hoped, then put them on a PIP and it worked out."&lt;/p&gt;

&lt;p&gt;It has no timeline, no action, and no evidence. Compare it with a strong version of the same story:&lt;/p&gt;

&lt;p&gt;"Missed 2 commitments. 6-week plan, pairing twice a week, Friday check-ins. By week 6, 5 of 6 PRs passed clean."&lt;/p&gt;

&lt;p&gt;Same story. One has evidence. The difference is not talent — it is preparation. The strong version names the gap, the plan, the cadence, and the outcome. An interviewer can score that. They cannot score "I waited and hoped."&lt;/p&gt;

&lt;p&gt;The same pattern holds for feedback. A weak answer is vague, only happens in reviews, and assumes the person "just knew." A strong answer names the specific behaviour, its impact, what you asked for, how they responded, and the follow-up date.&lt;/p&gt;

&lt;h2&gt;
  
  
  System design, through a manager's lens
&lt;/h2&gt;

&lt;p&gt;EM system design is not IC system design, and preparing for it the same way wastes time. Interviewers are not mainly testing whether you can draw a diagram. They want judgement: trade-offs, who owns what, what breaks first, and how you would staff it.&lt;/p&gt;

&lt;p&gt;Practise with prompts like these: who gets notified, when, and what happens if they miss it? Push or pull, retry or drop, noisy failure or silent failure — and why? Who is on call for it, and what breaks first?&lt;/p&gt;

&lt;p&gt;A worked walkthrough helps here — for example, walking through a notification system end to end, naming the trade-offs at each step, rather than memorising a system-design textbook. Six focused prompts, practised out loud, will do more than a week of reading.&lt;/p&gt;

&lt;h2&gt;
  
  
  A 14-day plan that fits in real life
&lt;/h2&gt;

&lt;p&gt;If you have two weeks, here is a shape that works:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Days 1–3: Write your 12 stories. No polishing, just get them down.&lt;/li&gt;
&lt;li&gt;Days 4–8: Map them to the 30 questions. Practise out loud, timed, 90 seconds each. Start with three: the underperformer, difficult feedback, and conflict between two reports.&lt;/li&gt;
&lt;li&gt;Days 9–12: System design prompts, plus mock interviews. Score yourself on evidence, structure, timing, and follow-through — not on whether it "sounded nice."&lt;/li&gt;
&lt;li&gt;Days 13–14: Scorecard, weak spots, rest. Do not cram new material the day before.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Track your progress simply: mark each question not started, in progress, or ready, so you practise the ones you dread instead of the ones you already know.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this method is not
&lt;/h2&gt;

&lt;p&gt;It is not a shortcut, and it will not guarantee an offer — no preparation method can. It is not a video course, and it does not cover LeetCode or salary negotiation. It is a way to turn experience you already have into answers you can actually deliver, in 90 seconds, under pressure.&lt;/p&gt;

&lt;p&gt;If you try it, start with three stories and three questions. Practise them out loud today. If you can answer those three cleanly in 90 seconds each, the method works for you — and the other 27 questions are just mapping.&lt;/p&gt;




&lt;p&gt;If you want the full version — 30 questions, 12 stories mapped to all of them, 8 worked STAR answers with weak vs strong versions, 6 manager-lens system-design prompts, and a tracker — I put it together as a $15 starter kit. A free 8-page sample (Q1–Q5, one worked answer, tracker preview) is here: &lt;a href="https://rainbowroadprep.gumroad.com/l/qiptza" rel="noopener noreferrer"&gt;https://rainbowroadprep.gumroad.com/l/qiptza&lt;/a&gt; — full kit: &lt;a href="https://rainbowroadprep.gumroad.com/l/zwsrde" rel="noopener noreferrer"&gt;https://rainbowroadprep.gumroad.com/l/zwsrde&lt;/a&gt;&lt;/p&gt;

</description>
      <category>engineeringmanager</category>
      <category>interview</category>
      <category>leadership</category>
      <category>career</category>
    </item>
  </channel>
</rss>
