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 501–550 of 1313 on this page.
A · Professional problem solving and implementation7
- A workspace contains hundreds of items that people find by customer, status, owner, or date. Its navigation follows the company org chart, so users struggle to find things. How would you reorganize it and test findability?
- Different teams own creation, editing, and review, and their form feedback is becoming inconsistent. How would you decide which patterns to standardize and which to keep distinct? How would you check loading, empty, error, and recovery states?
- A study was commissioned to validate a new dashboard. Most users say current reports are sufficient; a few advanced users want more. The project lead wants to highlight supportive interviews. How would you summarize the findings?
- In research for a new feature, a small group of frequent users strongly supports the concept, while novice participants repeatedly fail the core task and the analytics show no clear difference. How would you interpret what each piece of evidence can tell you and decide whether to proceed, revise, or run more research?
- In a usability session, the moderator repeatedly asks whether the design is clearer, and users agree. Video shows repeated hesitation during tasks. How would you handle the evidence and next study?
- Interview participants are almost all power users and community members. Feedback on the latest redesign is positive, but retention continues to fall. How would you redesign recruitment and research questions?
- Teams are copying shared components and adding local variants, making similar features inconsistent. How would you decide which differences belong in the shared design system and which should remain team-specific? How would teams help maintain those rules?
No questions in this section match your target. ·
C · Value judgment and direction setting3
- Brand asks for low-contrast text, but users with low vision struggle to read it; increasing contrast changes the brand presentation. How would you make and validate the design decision?
- A critical flow is two weeks from launch when a review finds that keyboard users cannot complete one step. A full redesign would affect the date. How would you assess the impact, negotiate scope with the team, and explain what can be staged versus what cannot safely ship?
- After a redesign of an important flow, the expected completion rate does not improve. Support requests decline, existing users respond more positively, but new users behave worse. How would you check metric definitions and user segments, determine what effect the design had, and choose the next action?
No questions in this section match your target. ·
D · Delivery and ongoing operations4
- A key vendor has delayed an interface twice, but the project plan still uses the original date. Internal teams are building a temporary adapter in parallel. How would you reset the baseline, account for added work, and show leadership which commitments remain credible?
- Two projects' schedules collide and both need the same people. What do you do, how do you turn the conflict into options that can be discussed, and how do you get both sides to accept the result?
- Three weeks into a project you find two risks nobody owns. How do you make them manageable?
- An automated approval service stops working, so the operations team temporarily switches to a spreadsheet and limits user impact. Two weeks later, the service is still down, and the spreadsheet has inconsistent permissions and records. How would you manage the temporary process, restore automated approvals, and decide when to shut it down?
No questions in this section match your target. ·
E · Collaboration, communication, and influence36
- Describe a time engineering found a technical constraint, undefined edge state, or unexpected cost while implementing your design. How did you clarify the real constraint, negotiate behavior and scope, and confirm that the final implementation still supported the core user task?
- Someone hands you a very vague question. How do you clarify first, then give a structured answer?
- A decision is being handed to a colleague in another city to carry out. How do you keep the reason behind it from getting lost?
- A product page advertises automation accuracy without a key applicability limit, and customers have used it in purchasing decisions. After finding the issue, how would you decide whether to withdraw, correct, and notify?
- You discover an incident may affect customer data, but the affected list and restoration time are unknown. How would you organize the first notice and subsequent updates?
- You have five minutes to brief a leader on a project that is not going well. How do you structure the message?
- How do you explain something clearly enough for your manager to see its value or its problem? When they do not take it seriously at first, how do you organize what you say and choose the evidence and the timing?
- Walk someone with no background through a project you did. How do you order the telling?
- Tell me about a real time, because of insufficient up-front research, you halted or substantially overturned a plan when engineering was halfway through. How did you treat it, and how did you reassure the engineering team and rebuild trust?
- A vendor risk may affect a launch, but neither cause nor likelihood is clear. Leadership wants an answer today. How would you report facts, unknowns, safeguards, and the next update time?
- A storage migration could briefly hide some customer data, but the business owner does not know replication lag or rollback limits. How would you explain risk and enable a sound decision?
- A launch decision must be made today, but one key experiment result is missing. How would you distinguish facts, assumptions, unknown risks, and reversible options in your update?
- How do you coordinate conflicts between departments? When their goals and performance measures differ, how do you find an approach all can accept, and how do you make it stay stable over time?
- A disagreement was not resolved and the group decided to proceed with one option. What do you leave behind so it can be reviewed later?
- A partner believes you intentionally delayed a project during review; you believe you were raising risks. Both of you communicate less as a result. How would you reconstruct facts and repair collaboration?
- Suppose online business metrics are cut in half and resources are halved, and product, operations, and engineering must get through the crisis together. How do you work with the other two functions in this situation to decide what to protect, what to cut, and how to share the burden, rather than pushing blame around?
- The business sponsor insists on the original release date, but a limited rollout shows refund rates and support tickets exceeding agreed bounds. Product thinks the sample is too small, while security wants to pause. How would you turn the dispute into a decision?
- Tell me about a conflict you went through. What did each side want, and how did you handle it? Looking back, what would you do differently?
- Both teams say the other is not cooperating and the project is stuck. How would you investigate what is happening, understand each team’s account, and decide what information or agreement is needed next?
- Product blames engineering for being slow, engineering blames product for changing requirements daily, and operations blames product for missing tools and engineering for instability. How do you turn this mutual blame into everyone speaking one shared business language and taking joint responsibility for results?
- You and your manager disagree, even clash. How do you express your judgment, and how do you keep things moving when they finally disagree with you?
- A direct report says they want to work on more high-impact initiatives. How would you understand what kind of growth they want and agree on a concrete next step?
- You shared a business line’s operating context with an engineer, who then started reallocating resources on their own. How do you handle it, and how do you change how you share in future?
- You point out that a proposal lacks user evidence, and your colleague hears “you think I am not capable.” They stop engaging. How would you clarify what the feedback is about, the evidence behind it, and the next step—and check that it was understood?
- Several people say in an anonymous survey that you lock onto a conclusion early. You believe you are shortening meetings. How would you understand the feedback, verify impact, and try to change?
- A colleague repeatedly changes an interface at the last minute but believes they communicated it in chat. Partners still get blocked. How would you give feedback without debating intent?
- You have just taken over a team, and a former peer is now your direct report. Their delivery is strong, but they repeatedly interrupt others in reviews. How would you prepare for and conduct your first feedback conversation?
- Tell me about a time you received feedback that made you uncomfortable. What did you change afterward?
- Did you ever try to break out of your resource or collaboration limits, such as bringing other teams in or asking upward for larger resources? How did you make the case, and what happened?
- Product promises features, engineering promises dates, and operations promises ticket handling, but nobody owns whether customers complete the key task. How would you reset goals with these leads?
- A cross-functional review is shortened to ten minutes, and decision-makers only want to know whether launch can stay on schedule. Your evidence shows two risks with different impact scopes. How would you organize the information so they can make an informed choice quickly?
- You want to push something valuable to the team in the long run that nobody is asking for now. Why do it, how do you persuade others, do you push top-down or bottom-up, and how do you show its value?
- When would you escalate a cross-team problem to a higher level, and how would you describe it?
- Has this solution had any influence outside your organization, such as being adopted by other companies or communities, shared publicly, open sourced, or written up? What is the evidence?
- Your project depends on another team fixing a data defect. They have higher-priority work and no reporting relationship with you, but customers cannot reconcile accounts. How would you make the case and offer decision evidence?
- When you give an overall report upward, how do you present it and win more resources for the team? When different organizations have different goals, how do you connect your team's goals to theirs?
No questions in this section match your target. ·