ROLE
General software engineering
Compare expectations across career stages →
These are the same questions found in the library, grouped here by the capability each one mainly examines.
1313 questions
Extended questions 901–950 of 1313 on this page.
F · People and organization building30
- If you are to take on something broader and someone else will take over your position, how do you prepare in advance so that your work can be picked up rather than going wrong after you leave?
- You plan to hand a leadership role to a deputy, but they have only observed reviews and have not independently made a high-impact decision. What would you validate before transition?
- When you delegate a decision to someone on your team, how do you make clear the decision rights they hold, the context they get, and the situations that must be escalated?
- A front-line lead who has run a core team for three years says they want to leave. What do you do in the first week, and what do you deliberately not do?
- A lead who carries key responsibility may leave next year. How do you decide between developing someone internally, hiring externally, or a mix of both? How do you allocate succession opportunities fairly, and look after both those not chosen and those who step in temporarily?
- You handed a team to a new lead, but members still bring disputes to you and partners keep asking you to decide. How would you make decision rights actually move?
- If you were away from the team for a week, which important decisions would the team still make well, and which would stall? How would you close the gap?
- A direct report openly disagrees with one of your decisions or raises concerns about your management. How would you understand the disagreement, assess its evidence, and decide what to change or uphold?
- A team member’s recent work has repeatedly fallen below role expectations, and earlier feedback has not led to improvement. How would you create and carry out a fair, measurable performance improvement plan?
- After taking over a team, several people raise concerns about one member’s collaboration, including blame shifting or resistance to agreed work. How would you verify what is happening, address any confirmed behavior, and protect the team while you learn more?
- Two people on your team are in conflict. How do you judge what is going on? How do you separate fact, position, and emotion, and when do you decide directly versus let them settle it themselves?
- A strong-willed, technically good developer on your team dislikes writing unit tests and reviews carelessly. Talking to them directly may annoy them. What rules or mechanisms would you use to change the behavior, and how do you make them open and fair to everyone?
- When the business declines or the industry is in a slump and morale is low, how do you keep delivering without letting the team fall apart? How do you tell the team the truth and still give them reason to keep going?
- How do you clarify an employee’s needs and your outcome expectations in a one-on-one? What would you avoid deciding on the spot?
- You are rolling out a new policy and front-line staff raise substantial concerns. How do you determine whether the issues come from the policy design, implementation conditions, or the change itself; decide what to adjust; and check whether the policy works as intended?
- A team member complains that collaboration is poor. How would you turn that into a problem the team can discuss and act on?
- How do you keep the core talent on your team? How do you notice early that someone wants to leave, and when someone really does, how do you keep the team from being hollowed out?
- Your team received a poor performance rating this year, year-end bonuses shrank across the board, and promotion slots were cut. Two key members on the team are starting to look for opportunities outside. How do you talk with them and manage expectations, and what non-material ways do you use to keep them?
- A technically strong contributor ships quickly but often bypasses review and shuts down colleagues. Others begin avoiding collaboration. How would you assess the situation and act?
- After growing from six to fourteen people, the team still uses its old division of work. Members disagree on architecture decisions, operations support, and quality ownership. How would you reset the team agreement?
- With the same problem, when do you give the answer directly and when do you let the other person work it out? How does your approach differ for a newcomer, a core member, and a team lead?
- The business requests a short timeline and sustained overtime from your team. How would you clarify the goal and constraints, assess the impact on capacity and delivery risk, and negotiate a workable path forward?
- Without identifying the employee, describe a recent case where someone on your team was not meeting an important expectation. What specific feedback or correction did you provide, and what happened afterward?
- A team member says their workload is too heavy and current priorities cannot be adjusted. How would you understand the work, assess capacity and constraints, and agree on a fair next step?
- An engineer quietly reduces failures in backend systems, while another frequently presents cross-team work and is better known to leadership. You calibrate development opportunities. How do you prevent visibility from replacing impact?
- How do you coach someone newly made a team lead to move from doing the work to leading others who do it? Where do they most easily get stuck, and how do you help?
- Someone tells you "I want to grow faster." How would you turn that into a concrete growth milestone?
- Someone on the team has become tired or complacent and their output has clearly dropped. How do you judge whether the cause is workload, lack of growth, personal circumstances, or lost confidence in the team, and what do you do?
- A contributor delivers reliably in a familiar system but misses deadlines and needs help in a new domain. How do you distinguish a reasonable learning curve from a performance issue requiring formal action?
- Technology moves fast. As the team's technical lead, how do you keep the team from losing external market competitiveness by long maintaining the company's aging in-house systems? How do you balance business stability against each person's market value as an engineer?
No questions in this section match your target. ·
H · Professional responsibility and work style20
- A user issue requires product, engineering, and operations, but each team completes its local tasks while the overall result still misses the goal. How would you name a coordinator and drive the issue to resolution?
- The final pre-launch test has intermittent failures, and a lead wants to hide the results to avoid delaying approval. What would you do?
- A deduplication change makes conversion look higher, but historical data has not been recalculated. How would you present the result?
- In promotion calibration, you cite evidence supporting a teammate but later realize a relevant project issue was omitted. How would you correct it?
- A public update describes a result completed by several people as one person’s contribution, damaging trust. How would you verify the facts and respond?
- An operations review shows shorter average handling time but longer waits for a small high-risk group. A partner wants to report only the average. How would you respond?
- Retention improves after changes by product, operations, and customer success. How would you explain your contribution without overstating causality?
- The team exceeds its goal and you prepare to report management impact. Team members say they solved the key problems themselves. How would you describe your role accurately?
- A project slips due to estimation errors; information was incomplete, incentives favored optimistic commitments, and you failed to escalate. How would you describe responsibility?
- Task completion improves after a redesign, alongside copy, performance, and support-training changes. How would you describe design’s role?
- A data platform has no direct revenue, but several teams use it to improve analysis and operations. How would you describe platform contribution and its limits?
- A business partner asks you to change security settings on a shared service you do not own. How would you respond and move the issue forward?
- A teammate often handles nonurgent issues late at night and expects immediate replies, while no on-call rules exist. How would you respond?
- A customer asks the team to export unauthorized user data to speed diagnosis, while policy requires approval. How would you respond?
- A colleague asks you to approve a customer-data change on their behalf, but you lack authority and context. What would you do?
- Two teammates disagree on implementation but can still collaborate; one asks you to decide. How would you choose the level of intervention?
- You own a critical delivery, and a new urgent request adds work without capacity changes. How would you respond?
- You learn in an interview that the role requires frequent night on-call, while you value a stable schedule. How would you understand the requirement and assess fit?
- The role holds you accountable for cross-functional outcomes but provides no resource authority or escalation path. What would you clarify before deciding?
- A partner plans to describe an unverified analysis in public materials as a “customer-validated result” and asks you to confirm the technical wording. How would you respond?
No questions in this section match your target. ·