Google Staff Engineering Manager Interview Preparation Guide

Engineering Manager

Google

Staff

6 rounds

Updated 6/18/2026

Google's Staff Engineering Manager interview process evaluates technical leadership, people management, system design expertise, and cultural alignment. The process typically includes initial recruiter screening, technical phone interviews, system design and technical depth assessments, behavioral and leadership evaluations focused on Googleyness, and onsite interviews with hiring committees. For Staff level, expect increased emphasis on cross-functional influence, technical strategy, and mentorship of senior engineers.

Interview Rounds

Recruiter Screening

30 min4 focus topicsculture fit

Technical Phone Screen

45 min5 focus topicstechnical

What to Expect

Technical conversation assessing deep systems knowledge, architecture understanding, and ability to explain complex technical concepts. May involve discussing a technical project you've managed, system design fundamentals, or technical problems. Evaluator probes your technical depth and ability to communicate technical decisions to both technical and non-technical stakeholders. For Staff level, expect questions about scaling challenges, architectural trade-offs, and technical mentorship.

Tips & Advice

Prepare a detailed walkthrough of a technically complex project you've managed or architected. Focus on the problem space, constraints, architectural decisions, trade-offs, and how you mentored your team through the complexity. Use clear frameworks to explain technical concepts. Demonstrate systems thinking and ability to evaluate architectural choices. For Staff level, emphasize how you influenced technical strategy and guided senior engineers. Be prepared to discuss why certain technical decisions were made and what you'd do differently. Show comfort with ambiguity and ability to make decisions under constraints.

Focus Topics

Technical Mentorship and Knowledge Sharing

Approach to developing senior engineers' technical skills, guiding their growth, and building technical expertise across the team.

Practice Interview

Study Questions

Scalability Challenges and Solutions

Experience identifying and resolving scalability bottlenecks in systems or organizations. Include architectural changes, technology choices, and outcomes.

Practice Interview

Study Questions

Technical Decision-Making and Trade-offs

Framework for evaluating technical options, considering constraints, and making decisions. Ability to articulate trade-offs between performance, maintainability, timeline, and cost.

Practice Interview

Study Questions

Technical Project Leadership

Examples of managing complex, multi-team technical initiatives from conception through successful delivery. Include scope, team composition, challenges, and outcomes.

Practice Interview

Study Questions

System Architecture and Technical Depth

Deep understanding of distributed systems, scalability patterns, trade-offs, and architectural principles relevant to large-scale systems.

Practice Interview

Study Questions

System Design Interview

60 min5 focus topicssystem design

What to Expect

In-depth system design discussion where you architect a complex system or solve a large-scale technical problem. You'll outline high-level design, identify key components, discuss interactions, explain trade-offs, and drill down into details. Evaluator assesses your systems thinking, architectural knowledge, ability to handle ambiguity, and communication of complex concepts. For Staff level, expect designs involving distributed systems, massive scale, complex trade-offs, and organizational constraints.

Tips & Advice

Use a structured approach: ask clarifying questions to understand requirements and constraints (first 10 minutes), propose high-level architecture (next 10-15 minutes), then dive into details. For Staff level, go deeper on trade-offs, failure modes, and how you'd evolve the system. Discuss scaling to billions of users or petabytes of data. Consider operational aspects like monitoring, deployment, and disaster recovery. Articulate assumptions clearly. When stuck, think through the problem methodically. At Staff level, evaluators want to see mature thinking about long-term technical strategy, not just solving the immediate problem. Discuss how you'd involve senior engineers in the design process and how you'd communicate architectural decisions to stakeholders.

Focus Topics

Database and Storage Design

Selecting appropriate databases (SQL, NoSQL), storage systems, caching strategies. Understanding consistency models, sharding, replication.

Practice Interview

Study Questions

Failure Modes and Resilience

Designing for failure, redundancy, disaster recovery, and graceful degradation. Understanding cascading failures and mitigation strategies.

Practice Interview

Study Questions

Large-Scale System Design

Ability to design systems handling billions of requests, petabytes of data, or serving millions of users. Understanding distributed systems, consistency, availability, and partition tolerance.

Practice Interview

Study Questions

Architectural Trade-offs and Constraints

Understanding how to balance latency, throughput, consistency, availability, cost, and maintainability. Evaluating technology choices within organizational constraints.

Practice Interview

Study Questions

System Evolution and Technical Strategy

How to evolve systems over time, plan for growth, manage technical debt, and guide long-term technical direction.

Practice Interview

Study Questions

Behavioral and Leadership Interview - People Management

45 min5 focus topicsbehavioral

What to Expect

Deep dive into your experience managing teams, mentoring engineers, handling difficult situations, and developing talent. Expects behavioral examples of team leadership, conflict resolution, performance management, and career development. For Staff level, focus on mentoring senior and experienced engineers, building strong team culture, navigating complex organizational dynamics, and developing future leaders.

Tips & Advice

Use the SPSIL framework: Situation, Problem, Solution, Impact, Learning. Prepare 6-8 strong behavioral examples covering: managing underperformers, developing high performers, navigating conflict, building team culture, mentoring senior engineers, and handling organizational change. For Staff level, emphasize strategic impact: how your leadership decisions influenced team effectiveness, career development of senior team members, and organizational alignment. Discuss how you coach senior engineers through complex decisions. Show comfort with ambiguity and ability to balance competing priorities. Prepare examples of decisions you'd make differently and what you learned. Demonstrate emotional intelligence and ability to read situations.

Focus Topics

Handling Difficult Team Situations

Managing underperformers, navigating conflict between team members, addressing behavioral issues, and making tough personnel decisions.

Practice Interview

Study Questions

Career Development and Growth Opportunities

Creating clear career paths, identifying development opportunities, coaching engineers through growth, and advocating for promotions.

Practice Interview

Study Questions

Cross-functional Team Leadership

Leading teams that span multiple disciplines, managing matrix relationships, and building alignment across organizational boundaries.

Practice Interview

Study Questions

Building and Scaling High-Performing Teams

Experience growing teams, maintaining culture during growth, attracting senior talent, and building teams greater than sum of parts.

Practice Interview

Study Questions

Mentoring Senior and Staff-Level Engineers

Experience developing experienced engineers' careers, guiding their technical and leadership growth, and preparing them for advancement.

Practice Interview

Study Questions

Behavioral and Leadership Interview - Googleyness

45 min5 focus topicsculture fit

What to Expect

Assessment of your alignment with Google's core values and cultural principles. Evaluates decision-making approach, inclusivity, ownership mentality, collaboration style, and how you embody Google's 'do the right thing' philosophy. Questions probe your values, ethical stance, how you handle ambiguity, and commitment to innovation. For Staff level, expect probing into how you influence culture, make principled decisions under pressure, and contribute to Google's mission.

Tips & Advice

Googleyness at Staff level means demonstrating principled leadership and cultural influence. Prepare behavioral examples showing: taking the right action even when difficult, fostering inclusivity and psychological safety, maintaining ownership while collaborating, embracing ambiguity and change, and contributing to Google's broader mission. For Staff level, emphasize how you influence culture on your team and across teams. Discuss difficult decisions where you chose principles over expedience. Show awareness of Google's values around transparency, data-driven decision-making, and innovation. Prepare for hypothetical scenarios testing your values (e.g., 'How would you handle project reassignment just before completion?'). Demonstrate growth mindset, willingness to learn from mistakes, and commitment to helping others succeed.

Focus Topics

Ownership and Accountability

Taking responsibility for outcomes, following through on commitments, and holding self and team accountable without blame.

Practice Interview

Study Questions

Growth Mindset and Learning

Openness to feedback, learning from failures, adapting to new situations, and helping others grow.

Practice Interview

Study Questions

Ethical Decision-Making and Values

How you navigate ethical dilemmas, stand up for principles, balance short-term pressure with long-term integrity.

Practice Interview

Study Questions

Inclusive Leadership and Psychological Safety

Creating environments where diverse voices are heard, building psychological safety, and actively fostering inclusion on teams.

Practice Interview

Study Questions

Decision-Making Under Ambiguity

Approach to making sound decisions with incomplete information, balancing speed and quality, and establishing decision frameworks.

Practice Interview

Study Questions

Behavioral and Leadership Interview - Strategic Impact and Technical Influence

45 min5 focus topicsbehavioral

What to Expect

Evaluation of your ability to drive complex cross-functional initiatives, influence technical strategy, navigate organizational politics, and create impact beyond your immediate team. Questions probe your strategic thinking, vision setting, stakeholder management, and ability to lead in matrix organizations. For Staff level, expect deep discussion of significant initiatives you've led, how you influenced company direction, and how you managed competing priorities.

Tips & Advice

Prepare detailed examples of significant initiatives you've led or influenced that had company-level impact. Use the SPSIL framework but focus on strategic outcomes: business impact, stakeholder alignment, technical influence, and organizational change. For Staff level, emphasize how you navigated complexity, managed senior stakeholders, influenced technical direction, and created lasting impact. Discuss how you identified strategic opportunities, built coalitions across teams, and executed against ambitious goals. Prepare examples showing: complex project management, stakeholder influence, technical strategy setting, and long-term impact. Show comfort managing upward and across organizational boundaries. Discuss how you balance immediate execution with long-term strategy. Demonstrate vision and ability to inspire others around ambitious goals.

Focus Topics

Managing Competing Priorities and Constraints

Navigating situations with limited resources, competing priorities, and multiple stakeholders with different goals.

Practice Interview

Study Questions

Stakeholder Management and Influence

Building relationships with senior stakeholders, understanding their priorities, managing expectations, and creating alignment across groups.

Practice Interview

Study Questions

Technical Strategy and Direction Setting

Influencing company or organization-level technical direction, making strategic technology choices, planning technical evolution.

Practice Interview

Study Questions

Leading Complex Cross-Functional Initiatives

Managing projects involving multiple teams, departments, or organizational units. Coordinating stakeholders, managing dependencies, and delivering results.

Practice Interview

Study Questions

Organizational Impact and Long-Term Thinking

Creating initiatives that have lasting impact on organization, building capability for the future, contributing to organizational excellence.

Practice Interview

Study Questions

Frequently Asked Engineering Manager Interview Questions

Team Leadership and DevelopmentEasyTechnical

48 practiced

Define psychological safety in the context of an engineering team. Provide three concrete actions a manager can take in the next 30 days to increase psychological safety and two leading indicators you would track to evaluate progress.

System Design and ReliabilityHardTechnical

153 practiced

Create an API versioning and compatibility strategy for a platform used by thousands of third-party clients. Include lifecycle policies (deprecation windows), compatibility guarantees, migration incentives, and automated tests you'd require before removing an API version.

Sample Answer

**Approach & goals**As an Engineering Manager I’d design a predictable, low-friction API lifecycle that minimizes client disruption while enabling platform evolution: clear versioning, semantic compatibility guarantees, generous deprecation windows, migration incentives, and automated safety gates before removal.

**Versioning & compatibility**- Use semantic versioning for major breaking releases (v1, v2) and date-stamped minor releases for non-breaking additions.- Guarantee: within same major version, maintain backwards-compatible changes (additive fields, optional params). Any breaking change requires a new major version.- Compatibility matrix published and machine-readable (OpenAPI + compatibility metadata).

**Lifecycle / deprecation policy**- Supported window: 24 months from major version GA.- Deprecation notice: 12 months prior to sunset (email, dashboard, webhook).- End-of-life: after 24 months; 3-month final grace period with rate-limited access and paid/enterprise extended support option.

**Migration incentives**- Provide migration guides, SDK upgrades, code snippets, automated migration tools (lint-fixers), and a “compatibility bridge” middleware for common changes.- Offer a migration sprint: dedicated engineering office hours, and temporary priority support for high-value clients.

**Automated tests & safety gates before removal**Require passing on:- Contract tests: OpenAPI schema validation and generated request/response fixtures for top 95% of endpoints.- Consumer-driven contract tests (Pact) from critical clients.- Integration smoke tests across staging and canary traffic.- Backwards-compatibility diff report and automated regression suite.- Telemetry: no active client traffic for 90 days OR explicit client consent; otherwise block removal.- Approval workflow: automated test results + product and legal sign-off.

**Trade-offs & metrics**- Trade increased maintenance for stability; measure client migration rate, number of support tickets, and usage decay per version.This strategy balances predictability, developer experience, and operational safety while empowering product evolution.

Psychological Safety and Inclusive CultureEasyTechnical

28 practiced

As an Engineering Manager, how do you define psychological safety for your engineering teams? Explain the concept in your own words, describe why it matters for software delivery and innovation, and list three concrete behaviors you would role model each week to build it.

Learning Agility and Growth MindsetEasyTechnical

59 practiced

Describe how you run a blameless postmortem focused on learning. Include a proposed agenda, facilitation techniques to keep the discussion blameless and evidence-based, methods to capture and prioritize action items, and steps to ensure those actions are assigned, tracked, and adopted into team practice.

Architecture and Technical Trade OffsHardTechnical

36 practiced

You discover a senior engineer is proposing complex eventual-consistency logic to hide failures from customers. As the EM, how do you evaluate whether additional complexity is justified and how do you decide between transparency (surface errors) versus protective complexity (automated hiding)?

Trade Off Analysis and Decision FrameworksHardTechnical

33 practiced

Design a sensitivity-analysis plan for a weighted decision model that compares moving to microservices versus refactoring the monolith. Explain which weights and assumptions you would vary, how you would sample the parameter space, which variables you expect to have the most influence, and how you'd summarize the results for executives.

Sample Answer

**Approach overview (why & goal)**I’d treat the weighted decision model as a probabilistic investment decision: vary uncertain inputs, quantify how often microservices wins vs. refactor, and identify which assumptions change the recommendation. Goal: give leadership a clear probability, sensitivity drivers, and break‑even thresholds.

**Which weights & assumptions to vary**- Business/value weights: importance of time‑to‑market, reliability, scalability, developer productivity, cost.- Quantitative assumptions: migration cost, ongoing O&M cost delta, developer ramp time, velocity impact (story points/week), defect rate, downtime cost, customer churn impact, infrastructure cost elasticity, schedule risk.- Model structure: assumed linearity of productivity gains, amortization period, discount rate.

**Sampling strategy**- Use Latin Hypercube or Monte Carlo (10k runs) to sample plausible distributions (triangular or Beta for bounded estimates, Normal for symmetric).- Encode correlations (e.g., higher velocity gains correlate with higher initial disruption).- Perform one‑way and two‑way deterministic sweeps for key variables to find break‑even points.

**Expected high‑influence variables**- Time‑to‑market / velocity impact- Total migration cost and duration (including hidden integration effort)- Ongoing operating cost delta and reliability/downtime risk- Developer productivity / churn during transition

**Analysis & visuals for execs**- Tornado chart ranking drivers by impact on net present value (or weighted score).- Probability summary: P(microservices > refactor), expected value difference, 90% confidence interval.- Break‑even table: threshold values where recommendation flips.- Scenario cards: conservative, base, aggressive with recommended decision and risk tradeoffs.- One‑slide recommendation: succinct verdict, top 3 risks, mitigation actions, and which assumptions to validate first.

**Operational next steps I’d propose**- Rapid validation experiments: prototype a service to measure real velocity and infra cost.- Update model with measured data and re-run sensitivity to reduce decision uncertainty.

Team Leadership and DevelopmentMediumTechnical

53 practiced

Design a manager development program for first-line engineering managers (0–2 years in role). Describe curriculum topics, cadence (workshops/mentoring), success metrics, and how you would pilot and scale the program across multiple teams.

Sample Answer

**Clarify goals & audience**- Goal: accelerate first-line EMs (0–2y) to reliably deliver team outcomes, coach engineers, run hiring/reviews, and retain talent.- Audience: new EMs with technical background, 6–10 reports typical.

**Program overview**- 6-month blended cohort program: monthly thematic workshops + weekly micro-learning + biweekly peer-practice + 1:1 mentoring.- Cohort size: 8–12 managers.

**Curriculum (by month)**- Month 0 (onboarding): role expectations, KPIs, time allocation.- Month 1: effective 1:1s, feedback, coaching skills, career conversations.- Month 2: hiring & interviewing for ICs, hiring scorecards.- Month 3: execution & delivery: OKRs, sprint health, dependency management.- Month 4: technical leadership: architecture reviews, tech debt prioritization, code review culture.- Month 5: performance management & calibration, promotion writing.- Month 6: stakeholder influence, upward management, scaling teams.

**Cadence & formats**- Monthly 2.5h workshop (case exercises, role-plays) + pre-work (30–60m).- Weekly 20–30m micro-lessons (videos, templates).- Biweekly 90m peer-practice groups for role-play and problem-solve.- Assigned mentor (senior EM) with monthly 1:1.- Office hours with HR/Staff Engineers quarterly.

**Success metrics**- Leading: attendance, workshop NPS, coaching skill assessment (observed 1:1 rubrics), hire quality (interviewer calibration).- Lagging (3–12m): direct-report engagement delta, manager retention, time-to-hire, sprint predictability (commit vs done), promotion rate of reports, 360-manager scores.- Targets set vs baseline; monthly dashboards.

**Pilot & scaling**- Pilot: 2 cohorts over 6 months (16–24 EMs) drawn from two product areas; include control group for key metrics.- Collect feedback, measure metrics at 3 & 6 months, iterate content.- Scale: create train-the-trainer for senior EMs and L&D, bake content into LMS, publish playbooks/templates, run rolling cohorts every quarter. Maintain cohort intimacy via local peer groups and virtual centralized curriculum; automate reporting via HRIS and engineering metrics dashboards.

**Trade-offs & risks**- Time cost vs impact: mitigate by micro-learning and manager time-budgeting.- Consistency across teams: enforce core curriculum but allow team-specific electives.

This plan balances practical skill practice, mentorship, and measurable outcomes to raise manager effectiveness quickly and sustainably.

System Design and ReliabilityEasyTechnical

80 practiced

As an Engineering Manager, explain the difference between SLI, SLO, and SLA. Using a customer-facing payment API as an example, describe specific SLIs you would track, propose SLO targets (include measurement windows), and explain how SLAs should influence priority and escalation policies.

Psychological Safety and Inclusive CultureMediumTechnical

21 practiced

A junior engineer is publicly blamed in a team chat for an outage and is visibly shaken. As an Engineering Manager, craft both a private response to the engineer and a public message to the team that preserves psychological safety while being transparent about the incident and next steps.

Sample Answer

**Approach / intent**I would immediately de-escalate, protect the engineer’s psychological safety, and keep the team informed about the outage and next steps without finger-pointing. Below are a private message (to the junior engineer) and a public message (to the team), with rationale.

Private message to the engineer (DM / 1:1)- Hi — I saw the chat. I’m really sorry that happened; that was unhelpful and stressful. You’re not alone in this — we’re going to handle the incident and the follow-up together.- Right now, take a few minutes if you need them. When you’re ready, let’s meet 1:1 for 30 minutes so I can hear what happened from your perspective and make sure you’re supported.- I will pause public discussion about who did what and will handle communications with leadership. If you want, I’ll join the postmortem and speak on context.- If you’d like time off or need to escalate this behavior, I’ll support you through HR and follow-up with the person who blamed you.- You did the right thing by raising the issue (or following the runbook). We’ll focus on learning and systems, not blame.

Public message to the team (team channel)- Team — quick update on the outage: services X and Y were impacted between T1–T2; mitigation is completed and we’re restoring traffic now.- We’re pausing the public chat discussion about individual actions. Our priority is a blameless investigation to identify contributing factors, fix the root cause, and improve processes.- Immediate next steps: - Incident triage summary document will be posted in #incidents by EOD. - Postmortem meeting scheduled: [date/time]; everyone involved is invited to contribute facts and suggestions. - Action items will include mitigations, runbook updates, and any required training.- If anyone feels uncomfortable about how this conversation unfolded, please DM me — we expect respectful, solution-focused communication.- Thank you to everyone who worked on mitigation. We’ll share a full summary after the postmortem.

Rationale- Private message preserves trust and gives immediate emotional/administrative support.- Public message restores order, focuses on systems/processes, avoids naming/blame, and outlines transparent next steps so accountability is systemic, not personal.

Learning Agility and Growth MindsetHardTechnical

52 practiced

Design a playbook for converting postmortem findings into durable organizational learning. The playbook should specify how to convert root causes into training modules, process changes, checklists, and follow-up audits; define an ownership model and timelines; and include documentation templates and measurable ways to track adoption and prevent regressions.

Sample Answer

**Overview / Objective**Create a repeatable playbook that turns each postmortem into lasting learning: training, process changes, checklists, and audits — with clear owners, timelines, templates, and measurable adoption metrics.

**Steps**1. Triage & Categorize (0–3 days)- Owner: Incident Lead- Output: Root-cause mapped to buckets (skill gap, process, tool, design, org).- Template: one-line RCA + evidence + severity + recurrence risk.

2. Decide Remediation Types (3–7 days)- Rules: - Skill gap → training module - Process gap → SOP + checklist - Tool/automation → backlog ticket + runbook - Design flaw → design review + standards update

3. Create Artefacts (7–21 days)- Owners: Engineering Manager for training/process; Tech Lead for code/tool changes.- Training: 30–60 min module, learning objectives, quiz, recorded demo.- Checklists/SOPs: step-by-step with owner, inputs, outputs, rollback steps.- Templates: add to repo/wiki; include “why” and telemetry to watch.

4. Rollout & Mandatory Acknowledgement (21–35 days)- Delivery: team training session + LMS assignment.- Requirement: completion and passing quiz within 2 weeks.- Update sprint/backlog for engineering tasks.

5. Audit & Metrics (30, 90, 180 days)- Owners: QA Lead / Eng Manager- Metrics: - Completion rate (target 100% within 2 weeks) - Quiz pass rate (>90%) - Policy adherence checks from audits (sampled ops incidents) - Recurrence rate of same RCA (target 0 within 90 days) - Mean time to detect/resolve similar incidents- Audit cadence: 30-day follow-up, 90-day process audit, 6-month retrospective.

**Ownership model & timelines**- Incident Lead: initial RCA (0–3d)- Eng Manager: remediation decision, training sign-off (3–10d)- Tech Lead: implement code/tool fixes (sprint)- Documentation Owner (rotation): publish SOP/checklist (7–21d)- QA/Compliance: audits (30/90/180d)

**Templates (summary)**- RCA header: incident id, summary, timeline, root causes, evidence- Remediation card: type, owner, due date, acceptance criteria, linked artifacts- Training module: objectives, slides, demo link, quiz questions, success metric

**Prevent regressions & continuous improvement**- Automate detection where possible (alerts, linting, CI checks).- Make remediation a Definition of Done for related PRs.- Quarterly incident review forum to capture meta-lessons.- Penalize no-follow-through: link performance goals to remediation completion.

Example: postmortem showed missing capacity test → created 1-hr training on load testing, added pre-release checklist item “run smoke load test,” implemented CI job to run reduced load tests, tracked recurrence (0 at 90d), completion 100% within two weeks.

Practice Engineering Manager questions across all topics

Want to create your own tailored preparation guide using our deep research?

Get Started for Free

Interview-Ready Courses

Visual-first, interactive, structured learning paths

Browse Engineering Manager jobs

AI-enriched listings across hundreds of company career pages

Explore Jobs

Google Staff Engineering Manager Interview Preparation Guide

Interview Process Overview

Interview Rounds

Recruiter Screening

What to Expect

Tips & Advice

Focus Topics

Career Motivation and Fit

Practice Interview

Study Questions

Cross-functional Collaboration Experience

Practice Interview

Study Questions

Management Philosophy and Leadership Style

Practice Interview

Study Questions

Technical Leadership and Strategic Influence

Practice Interview

Study Questions

Technical Phone Screen

What to Expect

Tips & Advice

Focus Topics

Technical Mentorship and Knowledge Sharing

Practice Interview

Study Questions

Scalability Challenges and Solutions

Practice Interview

Study Questions

Technical Decision-Making and Trade-offs

Practice Interview

Study Questions

Technical Project Leadership

Practice Interview

Study Questions

System Architecture and Technical Depth

Practice Interview

Study Questions

System Design Interview

What to Expect

Tips & Advice

Focus Topics

Database and Storage Design

Practice Interview

Study Questions

Failure Modes and Resilience

Practice Interview

Study Questions

Large-Scale System Design

Practice Interview

Study Questions

Architectural Trade-offs and Constraints

Practice Interview

Study Questions

System Evolution and Technical Strategy

Practice Interview

Study Questions

Behavioral and Leadership Interview - People Management

What to Expect

Tips & Advice

Focus Topics

Handling Difficult Team Situations

Practice Interview

Study Questions

Career Development and Growth Opportunities

Practice Interview

Study Questions

Cross-functional Team Leadership

Practice Interview

Study Questions

Building and Scaling High-Performing Teams

Practice Interview

Study Questions

Mentoring Senior and Staff-Level Engineers

Practice Interview

Study Questions

Behavioral and Leadership Interview - Googleyness

What to Expect

Tips & Advice

Focus Topics