📅 Fluency Class 6 – Daily Work Life
Interview-style deep dive into your typical workday, productivity habits, and work-life balance
Share honestly about a particularly chaotic day you've had recently—back-to-back meetings, unexpected production issues, or context switching overload. Ask: "Does this sound familiar? What does your worst workday look like?"
Talk about a recent change you've made to your work routine—blocking focus time, trying time-blocking, adjusting your wake-up time. Ask: "Have you tried optimizing your schedule? What works for you?"
Share the reality vs expectation of a developer's workday—how much time actually goes to coding vs meetings, communication, debugging. Ask: "How would you explain your typical day to someone outside tech?"
💡 Teacher Tip: Let the student talk first about their own work reality. This class works best when it feels like comparing notes, not interrogating their schedule.
Complete Example Interview – Describing a Typical Workday:
Key Phrases to Practice:
I usually start my day with...
I spend most of my time...
I try to avoid...
By the end of the day, I...
I've gotten into the habit of...
There tends to be...
It depends on...
I make a point of...
One thing I've learned is...
I have a hard stop at...
I've found that...
You end up...
Teacher: Now conduct a 10-15 minute interview with the student about their actual workday, productivity habits, and work-life balance. Choose the pathway that matches their professional experience:
🟢 Path A: Junior Developer (Establishing Routines)
Focus on helping them establish healthy work habits early in their career.
Sample Interview Questions:- "Walk me through your typical day—from when you wake up to when you stop working."
- "When do you feel most productive? Morning, afternoon, evening?"
- "How do you currently manage your tasks? Any tools or systems?"
- "How much of your day is spent coding vs meetings vs learning?"
- "What's the biggest challenge you face with time management?"
- "Have you set any boundaries around work hours? How's that going?"
Deep Dive Focus: Story extraction about what a typical day actually looks like vs what they expected. Probe about challenges establishing routines in remote/hybrid work.
🟡 Path B: Mid/Senior Developer (Optimizing Workflows)
Focus on productivity systems, managing interruptions, and balancing multiple responsibilities.
Sample Interview Questions:- "How has your typical workday evolved as you've gained more experience?"
- "What systems have you put in place to protect focus time?"
- "How do you handle context switching between coding, reviews, and meetings?"
- "Walk me through your productivity stack—what tools are non-negotiable for you?"
- "What's your strategy for declining meetings that don't need you?"
- "How do you recharge after particularly draining days?"
Deep Dive Focus: Trade-offs they've made (availability vs deep work, helping others vs own tasks). Probe about experimentation with different productivity systems and what they've learned.
🔴 Path C: Tech Lead / Manager (Team & System Design)
Focus on designing sustainable work cultures, managing team energy, and systemic productivity.
Sample Interview Questions:- "How do you balance your own focus time with being available for your team?"
- "What systems have you implemented to protect the team's focus time?"
- "How do you recognize burnout signals in yourself and your team?"
- "Walk me through how you structure your week to balance coding, leadership, and strategic work."
- "What policies or norms have you established around meetings, async communication, and availability?"
- "How do you model healthy work-life balance for your team?"
Deep Dive Focus: Systemic thinking about team productivity cultures. Challenge their assumptions about availability expectations. Explore how they make trade-offs between being a hands-on technical contributor vs enabler/unbocker.
💡 After the interview: Briefly reverse roles—let the student interview YOU about your workday. This builds confidence and lets them practice asking follow-up questions (5-7 minutes).
📖 Story Extraction
Use: "Walk me through exactly what happened yesterday from 9am to noon."
Why it works: Forces concrete details instead of generalizations. Reveals actual habits vs idealized versions.
⚖️ Trade-off Probing
Use: "You mentioned protecting focus time—what did you give up to make that happen?" or "What's the cost of being always available on Slack?"
Why it works: Surfaces the real constraints and choices they face, moving beyond surface-level best practices.
🤔 Silence Tolerance
Use: After asking "How do you actually decide what to work on each day?" → wait 5-10 seconds in silence.
Why it works: Allows student to move past rehearsed answers and access real reflections. Resist the urge to fill silence.
🔍 Profundization
Use: "Tell me more about that specific moment when you realized you were burning out." or "What does 'too many meetings' actually mean for you—3 per day? 6?"
Why it works: Pushes past vague statements to concrete, memorable details that reveal true experience.
🔄 Alternative Exploration
Use: "Have you tried working at different times of day? What happened?" or "What would change if you had zero meetings for a week?"
Why it works: Encourages experimentation mindset and reveals what they've already tried vs what they're assuming.
"Describe the last time you felt completely in flow while coding—what conditions made that possible?"
"What's one work habit you've seen in a colleague that you want to steal?"
"If you could redesign your workday with no constraints, what would change first?"
"What does 'productivity' actually mean to you? Lines of code? Features shipped? Something else?"
Teacher: Choose ONE scenario below (or use a real situation from the student's work). Discuss what they would actually do—not the "right answer" but their honest approach. Practice using vocabulary from today.
📅 Scenario 1: Meeting Overload
Situation: You have 6 hours of meetings scheduled tomorrow. You also have a critical bug that needs 3-4 hours of uninterrupted focus. Your manager just asked to add "a quick 30-minute sync" to your calendar.
Questions to explore:
- Which meetings could you realistically skip or send a delegate to?
- How do you communicate needing focus time without seeming uncooperative?
- What's your actual strategy—stay late? Come in early? Push the bug to tomorrow?
🔥 Scenario 2: Burnout Warning Signs
Situation: You've worked 10-hour days for 3 straight weeks shipping a major feature. It launched successfully, but you're exhausted. You're snapping at teammates, your sleep is terrible, and you dread opening your laptop. Your manager just asked you to start the next feature.
Questions to explore:
- How do you have the "I need a break" conversation with your manager?
- What does "recovery" actually look like for you—PTO? Lighter work? Something else?
- How could you have prevented this? What would you do differently next time?
💬 Scenario 3: Deep Work vs Team Availability
Situation: Your team culture is "always on Slack"—people expect responses within 30 minutes. But you need 3-4 hour blocks of uninterrupted time to make progress on complex features. A teammate recently complained that you're "hard to reach."
Questions to explore:
- How do you negotiate focus time without seeming like a "not a team player"?
- What tools or norms could help (office hours, focus indicators, async-first communication)?
- What's a realistic compromise that protects both your focus and team responsiveness?
📊 Option 1: Time Audit Recording
Record a voice memo (3-5 min) explaining where your time actually went yesterday. Break down: coding time, meetings, context switching, admin work, breaks. Use at least 3 phrases from today: "I spent most of my time...", "There tends to be...", "By the end of the day..."
🎯 Real use: Practice for team retrospectives or 1-on-1s where you need to explain capacity issues.
🗣️ Option 2: Workday Explanation (for non-tech people)
Write a short explanation (150-200 words) of what you actually do all day, as if explaining to a family member or friend outside tech. Avoid jargon. Use phrases like: "I usually start my day with...", "One thing people don't realize is...", "It depends on..."
🎯 Real use: Useful for networking, explaining your job at social events, or onboarding non-technical stakeholders.
⚙️ Option 3: Productivity Experiment Proposal
Identify ONE thing you want to change about your work routine. Write a brief plan (100-150 words): What will you try? For how long? How will you measure if it's working? Use: "I'm going to try...", "The main challenge will be...", "I've found that..."
🎯 Real use: Practice for proposing schedule changes to your manager or experimenting with your own productivity systems.
🎤 Option 4: Mock Interview Prep
Prepare answers to these interview questions (practice speaking, don't write): "Walk me through your typical day." and "How do you manage your time when you have competing priorities?" Record yourself or practice with a friend. Use today's phrases naturally.
🎯 Real use: These are common behavioral interview questions—being able to articulate your work habits professionally is valuable.
💡 Teacher: Emphasize that students should pick the option most relevant to their immediate professional context. In the next class, ask them to share what they learned from the exercise (2-3 minutes max).