# The Engineering Manager Week: Operating Cadence Source: https://www.techinterview.org/post/3233475121/engineering-manager-week-operating-cadence/ Updated: 2026-07-12 · techinterview.org One of the under-discussed skills of engineering management is calendar discipline. Without it, your week becomes a slurry of meetings, no deep work happens, and you cannot do your job. The interview question "walk me through a typical week" probes whether you have actually thought about this. ## The week's structure A reasonable EM week (40–50 hours): - 1:1s with reports take 4–8 hours, depending on team size. - Manager and skip-level meetings take 1–2 hours. - Cross-functional standups and planning take 2–4 hours. - Strategic and writing time takes 6–10 hours. - Code or design reviews take 4–8 hours. - Hiring (interviews, debriefs) takes 2–6 hours. - Reactive work, Slack, and email take 4–6 hours. - Buffer and catch-up take 4–6 hours. Above ~50 hours/week consistently signals over-commitment, not heroism. ## The meeting calendar Common pattern: - Monday has light meetings, a team sync, and reading time. - Tuesday is 1:1s and cross-functional meetings. - Wednesday is planning and design reviews. - Thursday has 1:1s and deep work blocks. - Friday is async writing, a no-meeting day if possible. Many EMs designate one no-meeting day for strategic work. Protect it. ## The 1:1 cadence Direct reports: weekly 30 minutes. Skip-levels: quarterly 30 minutes. Cross-functional partners: biweekly or monthly 30 minutes. Don't cancel 1:1s. Do reschedule when needed. ## Focus time blocks Schedule 2-hour blocks of focus time on the calendar. Without them: - Meetings expand to fill the calendar - Strategic writing never happens - You become reactive Block them weeks ahead. Decline meetings that conflict. ## The "shadow week" Once a quarter, do a shadow week: track every hour you spend, what category, what value it produced. Patterns will surface: - Recurring meetings that no longer add value - Slack distraction patterns - Time spent in low-leverage IC work Adjust based on what you learn. ## Slack discipline Without rules, Slack consumes the day: - Block Slack-checking to 3–4 times a day - Use status messages to signal availability - Mute non-essential channels - Don't expect immediate responses; don't deliver them ## Email For most EMs, email is a low-volume but consequential channel (executives, recruiters, external). Process once a day. Inbox zero is achievable for most EMs at most companies. ## Reading and writing time Strong EMs spend significant time reading (design docs, internal blog posts, industry articles) and writing. Calendar block this. Without it, your strategic effectiveness drops. ## Off-hours Set explicit boundaries: - No Slack after 7pm - No email on weekends except for active incidents - Real vacations — actually unplugged, with delegation Modeling boundaries helps your team feel safe doing the same. ## The "I am too busy to lead" trap Symptoms: - Back-to-back meetings every day - No time to read team's design docs - Cancelled 1:1s - Strategic decisions made in 5 minutes between meetings Diagnose and fix: - Audit recurring meetings; cut 30% - Delegate more - Set the example of "no" to non-essential meetings ## The interview question "Walk me through a typical week." Strong answers describe specific blocks of time, the rationale, and what gets protected. Vague "I do a lot of 1:1s and meetings" answers signal lack of discipline. ## Frequently Asked Questions ### How many 1:1s should I do per week? One 30-min slot per direct report. For 8 reports: 4 hours. For 12 reports: 6 hours. Beyond 12, the math forces tradeoffs (smaller meetings or more delegation). ### Should I have an open-door policy? Open-door for emergencies; structured time for everything else. Pure open-door makes deep work impossible. ### What if my team needs me late at night for incidents? Real on-call expectations are different from "always available." If you are the only escalation point, your operational structure is broken.