1:1 Question Bank
Curated, high-signal questions for managers. Filter by category, find instant inspiration, or build a custom meeting agenda.
How is your mental battery and energy level this week on a scale of 1 to 5?
Context: Quick quantitative pulse check that normalizes talking about energy.
What was the highlight of your past week, inside or outside of work?
Context: Encourages positive reflection and shares personal context.
What is one thing about your day-to-day work environment that you would change if you had a magic wand?
Context: Uncovers low-hanging ergonomic or environmental friction.
Did you get to do any deep, uninterrupted work this week, or did it feel fragmented?
Context: Evaluates calendar fragmentation and maker time.
Which task this sprint gave you creative momentum, and which felt like a soul-draining chore?
Context: Uncovers unbalanced distribution of chores, on-call spikes, or repetitive manual tasks.
What is one small thing I could do differently or start doing to support you better?
Context: Lowers the bar for constructive criticism with "one small thing".
Where do you feel I am providing too much guidance, and where would you like more context or direction?
Context: Calibrates the micro-management vs under-management spectrum.
Is there any decision made recently where you felt out of the loop or disagreed with the direction?
Context: Unearths silent disagreement before it turns into disengagement.
How clear are our team’s top three priorities for this quarter in your mind?
Context: Tests strategic clarity without putting the employee on the defensive.
Am I giving you feedback early enough, or does it ever feel like a surprise?
Context: Ensures feedback latency is near zero.
Where am I unintentionally creating a bottleneck or delay for you?
Context: Identifies delayed code reviews, slow approvals, or unnecessary micromanagement.
Did I handle any meeting or situation poorly recently where I could have shown up better?
Context: Surfaces blind spots in communication, tone, or team defense.
What is something you wish I understood better about your day-to-day reality?
Context: Bridges empathy gaps between high-level management planning and ground-level technical implementation.
Who on the team or in adjacent squads has been especially helpful to you recently?
Context: Surfaces invisible glue work and positive peer recognition.
How comfortable does it feel to voice an unpopular opinion or admit a mistake in our team discussions?
Context: Direct measure of psychological safety within the squad.
Is there any simmering tension, friction, or misalignment in the team that we need to address?
Context: Catches interpersonal friction before it escalates.
Do code reviews and technical debates in our team feel constructive and collaborative, or stressful?
Context: Validates health of the day-to-day engineering culture.
How is collaboration feeling across the team right now? Does anyone feel isolated or out of the loop?
Context: Diagnoses remote disconnect, timezone silos, or simmering quiet disagreements.
Do you feel your ideas and RFCs are taken seriously by the rest of the team?
Context: Uncovers feelings of exclusion, seniority bias, or dominant voices dismissing input.
What is taking up too much of your time right now that feels unnecessarily painful or bureaucratic?
Context: Identifies systemic overhead and process waste.
Which recurring meeting on your calendar feels least valuable or could be handled asynchronously?
Context: Protects focus time and prunes stale meetings.
Is there any dependency on another team that is stalling your progress or causing uncertainty?
Context: Signals where the manager needs to step in to negotiate cross-team boundaries.
If we could improve one part of our local development, CI, or deployment workflow, what would make the biggest impact?
Context: Pins down developer experience bottlenecks.
What is harder in your day-to-day work than it should be?
Context: The classic high-signal friction prompt: slow pipelines, flaky tests, lack of staging data, or painful approvals.
Is there any part of our codebase or architecture that you or the team are terrified to touch, and why?
Context: Identifies legacy landmines without test coverage and single-point-of-failure services.
What is the clunkiest internal tool or process we still tolerate just because "that’s how we’ve always done it"?
Context: Uncovers outdated deployment checklists, manual permission grants, or inertia-driven habits.
If you had two full days to fix any technical debt in our service, what would you tackle first?
Context: Surfaces high-ROI refactoring ideas that engineers usually keep to themselves due to sprint pressure.
Did you run into any permission, cloud IAM, or credential roadblocks this cycle?
Context: Identifies security bureaucracy, slow IT approvals, or missing staging environments.
Do you feel clear on why our current sprint goals matter to our customers and the business?
Context: Prevents engineers from feeling like disconnected factory workers typing tickets without purpose.
Were there any recent announcements or leadership pivots that felt confusing or contradicted our goals?
Context: Uncovers rumors, strategic whiplash, and gaps in executive context.
If a candidate asked you in an interview what our company’s top priority is this quarter, what would you say?
Context: Tests strategic alignment and whether company goals actually filter down to the team.
Do you feel we are building the right thing, or are we solving the wrong customer problem?
Context: Unearths frontline technical doubts about product viability before time is wasted.
What would happen if we didn’t ship this current milestone for another month? Does it actually matter?
Context: Separates genuine business urgency from artificial, management-induced panic.
Looking at our upcoming roadmap, which problem space or project are you most excited to tackle?
Context: Aligns project staffing with genuine personal motivation.
What is a skill or technology you don’t currently use in your day-to-day work that you would love to master?
Context: Informs stretch opportunities and learning budgets.
When you imagine your role 1–2 years from now, are you leaning more toward technical leadership, domain depth, or people management?
Context: Helps navigate the dual career ladder (Staff+ IC vs EM track).
What is one recent piece of work where you felt you performed at your absolute best?
Context: Identifies high-water marks and energizing work.
What is the single biggest skill gap holding you back from reaching the next level?
Context: Focuses career conversations on actionable growth areas (system design, ambiguity, leadership).
Do you feel you are learning faster than the market, or does your professional progress feel stagnant?
Context: The #1 leading indicator of engineer attrition and disengagement.
How sustainable does your current pace of work feel over the next 2–3 months?
Context: Assesses marathon pace vs unsustainable sprint burnout.
Are you able to completely shut down your laptop and work notifications in the evenings and weekends?
Context: Guards boundaries and unplugs culture.
If you had to drop one task or project this week to breathe easier, which one would it be?
Context: Instantly surfaces lowest-value/highest-stress work.
Do you feel pressure to respond to messages outside working hours, even if it’s unspoken?
Context: Surfaces accidental peer or leadership pressure.
I noticed you’ve been working late nights or weekends recently. How are you holding up physically?
Context: Checks for sleep deprivation, physical exhaustion, and health symptoms before acute burnout occurs.
When was the last time you took a full day off and completely disconnected from Slack and email?
Context: Surfaces vacation guilt, hero syndrome, or fear that things will collapse in their absence.
How can I give you air cover so you can catch your breath and reset this coming week?
Context: Invites concrete protective commitments from the manager (declining meetings, pushing deadlines).