ROLE
Frontend
Compare expectations across career stages →
These are the same questions found in the library, grouped here by the capability each one mainly examines.
1121 questions
Extended questions 851–900 of 1121 on this page.
G · Learning, adaptation, and sustained growth20
- An interviewer directly challenges your result, saying it was mostly luck or mostly the credit of others on the team. How do you respond?
- Think of a time your proposal was rejected or things did not work out. How did you separate facts, interpretation, and feeling, and when did you ask others for help?
- In an interview you hit a question you did not prepare for and freeze for a moment. What do you do next?
- A high-pressure stretch has lasted several weeks. How do you judge whether to keep going or whether you are burning effort for nothing, and what do you adjust?
- Two proposals you made have been rejected by key decision-makers, and the team is questioning your judgment. How would you review both outcomes, decide whether the problem is still worth pursuing, and restore confidence in the next step?
- In one week, support asks you to fix an unstable issue, your manager expects a committed feature, and another team invites you to a review that could prevent future rework. How would you choose what comes first and help unmet stakeholders understand the choice?
- Your role is unchanged, but new requests, routine maintenance, and a long-term goal have accumulated, and finishing everything is unrealistic. How would you define a work budget and make it visible?
- When you set goals for the next cycle, what do you find hardest, and how do you turn a goal into actions that can be checked?
- You find a neglected maintenance problem that has not caused an incident, but fixing it will take several days and will not produce an obvious short-term result. How would you decide whether to invest, secure time, and set stop or escalation conditions?
- When nobody asked, what goal did you set and drive recently, and how did you judge it was worth the investment?
- You own internal data quality with no shared defect baseline or formal business target, but errors affect several downstream teams. How would you define a goal and verify progress?
- Under what conditions could that failed project have succeeded? Could you have had those conditions at the time, and how would you design it now for a better chance?
- When you run a retrospective, how do you avoid glossing over the hard parts, switching the definitions, or making the facts sound better than they were?
- Were the improvements proposed in a retrospective actually carried out afterwards? Did each one have an owner, a date, and a way to verify it? For those not carried out, why not?
- Tell me about a time your judgment was overturned by the facts. Which parts of it were reasonable at the time, which signals were missed, and what exactly did you change afterwards?
- Pick a project you recently finished and walk through a retrospective: what did you set out to achieve, what actually happened, and what would you keep, change, or stop next time?
- Describe a consequential mistake or unexpected failure you were responsible for. How did you identify its causes and your part in it, reduce the impact, and change your future practice?
- A deployment nearly writes sensitive data to public logs, but an automated check blocks it and no customer is affected. Some say there is no incident to review. How would you handle it?
- Tell me about a project that did not succeed. Why did it fail, which causes were direct and which more fundamental, and how much of it related to your own judgment?
- If you redid this project with the same resources, how would you do it? Would you get more benefit, or stop earlier?
No questions in this section match your target. ·
H · Professional responsibility and work style30
- You deliver an analysis and proposal with substantial AI help for research, code drafts, and documentation, while you own problem framing, validation, and final decisions. How would you explain contribution to the team?
- As an important project enters promotion review, two contributors both say they proposed the key solution. The project record contains the final decision but not the discussion. As a participant or lead, how would you reconstruct events, describe contributions, and handle what remains uncertain?
- In this project, did you mainly shape direction, implement professional solutions, or coordinate delivery? How did those actions affect the specific problem and the business outcome?
- Tell me about a time you handed credit, information, or a decision to someone better placed. How did you judge that was the right move?
- Choose an outcome delivered by several teams that you need to explain in a review or promotion case. What problem did you define, which key judgments did you make, and what actions did you drive? Which contributions belong to others, and what evidence supports your account?
- If you had not been there, what would have been different? Did your contribution change a single result, or make this kind of problem easier to solve?
- Your responsibilities overlap with another team's, and it is unclear who decides and who executes. How do you confirm the boundary and keep both sides from waiting on each other?
- A partner privately shares a staffing or customer risk that may affect plans but asks you not to forward details. Decision-makers need to understand the impact to allocate resources. What would you do?
- On call, you find a data-repair script that could quickly restore a report but might overwrite changes customers just submitted. The owner is unreachable and the business asks you to act immediately. How would you separate protective steps you can take, actions requiring authorization, and escalation?
- How is your energy allocated? What should the focus of your role be, and as levels change, which things should you let go of and which must you still do yourself?
- A quarterly target was missed. A leader proposes excluding refunds and cancellations from the main conversion rate, calling it more representative of core customers. How would you assess and communicate the change?
- A customer is in a hurry and someone asks you to skip a rollback check before launch, where a failure could irreversibly damage user data. How do you judge whether this is a line that cannot be traded away, and how do you escalate it?
- You took a temporary coordination task that gradually grew into hiring, scheduling, and operations, without formal authority or capacity adjustment. How would you discuss continuing, transferring, or narrowing the scope with your manager?
- A task from your mentor leaves you with no progress after a full day and you are completely stuck. Do you keep researching alone or go to your mentor, and where do you draw the line between thinking independently and wasting time?
- A candidate wants high autonomy, while the prospective manager checks progress daily. Both consider their approach reasonable. How would you discuss decision rights, feedback cadence, and failure tolerance before hiring?
- A candidate wants new domains and broader scope within a year, but the role mainly operates a mature system reliably. How would you assess fit and describe realistic growth paths?
- What do you value most in your next role? Which of those conditions are you unwilling to compromise on, and why?
- Why did you leave your last job, or why are you considering leaving your current one? Did you try to resolve it internally, and what did you yourself weigh and give up in the choice?
- Describe how you prefer to work, such as how often you want feedback, how much authority you expect, and how you sync information. When would you adjust it for the team?
- At a quarterly review, you predicted a change would lift conversion. A later segmented experiment shows no overall lift and harm to one segment. How would you correct the conclusion?
- Tell me about a time you proactively corrected something you had said or a metric definition you had used. How did you find it, and how did you tell the people affected?
- A launch event you supported described a metric increase after release as an improvement “caused by the feature,” but the team had no control group and had not ruled out a concurrent campaign. How would you decide whether to correct the claim and work with marketing and business owners?
- You find a colleague omitted one class of refunds from business results already sent to leadership. They suggest quietly replacing the file. How would you ensure the conclusion and decision record are corrected?
- An access setting may have exposed some customers’ data to others, but scope is unconfirmed. Your manager worries early notice will cause alarm. How would you handle escalation and customer communication?
- You find a delay risk in a project you own, and your manager has been pleased with progress so far. When and how would you raise it?
- Your history includes a gap, a layoff, or a part that does not look good. How do you explain it truthfully, without avoiding it and without over-explaining?
- Your quarterly report says a target was met. You later discover that the data pipeline changed the definition of “active customer” midway through the period; recalculating with the old definition puts the result below target. How would you correct the report, inform decision-makers, and repair the process?
- Tell me about the piece of work you are proudest of. Why is it the best, what yardstick do you measure it by, and which parts were your own contribution?
- While reviewing a partner document, you find exposed customer credentials. This is outside your team’s remit, the owner is away, and the material may be public. How would you contain and hand off the risk?
- A critical delivery is falling behind on work owned by another team, so you step in and prevent a delay. This has happened three times, and people now assume you will handle it. How would you protect the current result while clarifying future owners and ways of working?
No questions in this section match your target. ·