Katkat

practice a little every day, paws crossed ♡

Software Engineer Interview Questions

Practice 9403 coding, system design and machine learning questions from 546 companies, sorted by role, topic and interview round. Every question has step-by-step hints, a code runner that supports 8 languages and an AI mentor; members also get the full solution walkthrough.

9403
Questions
546
Companies
11
Topics
8
Languages

Showing 301–330 of 748 results

  • DoorDashMediumSoftware Engineer
    Defend an Ownership Project with Measurable Impact

    Tests an engineer's ability to demonstrate end-to-end ownership, justify architectural trade-offs under constraints, and prove business or operational impact using credible metrics.

    Behavioral & LeadershipTechnical ScreenOwnershipSystem ArchitectureMetrics & Impact
  • DoorDashMediumSoftware Engineer
    Demonstrate leadership and team development

    Demonstrate leadership and team development evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    Behavioral & LeadershipTechnical Screen
  • DoorDashMediumSoftware Engineer
    Describe a Project End-to-End

    This question evaluates a candidate's ability to demonstrate end-to-end project ownership, technical decision-making, cross-functional communication, and measurement of business impact, and is commonly asked to assess how an individual explains their role, trade-offs, launch outcomes, and lessons learned.

    Behavioral & LeadershipTechnical Screen
  • DoorDashMediumSoftware Engineer
    Describe your most impactful recent project

    A DoorDash software-engineering onsite behavioral question asking you to walk through your most impactful recent project: the problem, your specific role, measurable impact, a key technical decision and its trade-offs, how you handled scaling and reliability, a risk or failure you hit, and what you'd do differently. Includes a structured STAR-plus-deep-dive framework and a worked real-time-dispatch example.

    Behavioral & LeadershipOnsite
  • DoorDashMediumSoftware Engineer
    Discuss Projects and Planning Improvements

    This question evaluates ownership, product understanding, end-to-end project leadership, cross-functional collaboration, and the ability to quantify impact within behavioral and leadership competencies for software engineers.

    Behavioral & LeadershipTechnical Screen
  • DoorDashMediumSoftware Engineer
    Discuss feedback, help, and conflict

    This question evaluates interpersonal and leadership competencies such as receiving and acting on constructive feedback, mentoring or helping colleagues, and managing conflict within engineering teams (Behavioral & Leadership).

    Behavioral & LeadershipTechnical Screen
  • DoorDashMediumSoftware Engineer
    Discuss project experience and teamwork

    Discuss project experience and teamwork evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    Behavioral & LeadershipOnsite
  • DoorDashMediumSoftware Engineer
    Explain AI Tool Use, Model Selection, and Engineering Validation

    Explain practical AI use across coding and summaries, with honest contribution measures, task-specific model choices, validation, and cost awareness.

    Behavioral & LeadershipOnsite
  • DoorDashMediumSoftware Engineer
    Explain Performance, OKRs, Failure, and Project Learning

    This question tests your ability to navigate complex project lifecycles by evaluating your ownership of OKRs, your response to significant failure, and your capacity for introspective learning.

    Behavioral & LeadershipOnsiteLeadershipOKRsBehavioral
  • DoorDashMediumSoftware Engineer
    Explain Project Impact from Prototype to Shared Ownership

    Describe a proud project's impact, evidence of time saved, transition from prototype to supported use, and cross-functional ownership.

    Behavioral & LeadershipOnsite
  • DoorDashHardSoftware Engineer
    Explain Why You Are Changing Roles

    This question tests your ability to articulate a clear career trajectory, demonstrating that your move is driven by professional growth rather than dissatisfaction with your current situation.

    Behavioral & LeadershipOnsiteCareer StrategyCommunicationProfessionalism
  • DoorDashHardSoftware Engineer
    Explain an AI-Assisted Project

    Tests your ability to articulate the engineering realities of an AI- or LLM-driven project, focusing on rigorous evaluation, production guardrails, failure modes, and personal ownership rather than high-level buzzwords.

    Behavioral & LeadershipOnsiteBehavioralAI & MLSystem Reliability
  • DoorDashHardSoftware Engineer
    Explain conflict resolution and growth

    This question evaluates collaboration, ownership, technical leadership, conflict resolution, incident management, decision-making, and the ability to learn from and prevent mistakes.

    Behavioral & LeadershipOnsite
  • DoorDashMediumSoftware Engineer
    Explain handling conflicts and learning from mistakes

    This interview question evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer for Explain handling conflicts and learning from mistakes states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    Behavioral & LeadershipOnsite
  • DoorDashHardSoftware Engineer
    Handle a payment-service incident with resource spikes

    Handle a payment-service incident with resource spikes evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    Behavioral & LeadershipTechnical Screen
  • DoorDashEasySoftware Engineer
    How do you discuss mistakes and trade-offs?

    This question evaluates competency in accountability, leadership, incident management, and product/operational decision-making within the Behavioral & Leadership domain for software engineers.

    Behavioral & LeadershipOnsite
  • DoorDashMediumSoftware Engineer
    Investigate a Surge of Incorrect-Delivery Complaints at Scale

    Triage thousands of delivery complaints using rates, joined operational data, focused sampling, mitigation, and evidence of recovery.

    Behavioral & LeadershipOnsite
  • DoorDashHardSoftware Engineer
    Present Your Proudest Project

    Tests your ability to articulate a high-impact technical project end-to-end, highlighting architectural ownership, difficult trade-offs, rollout execution, and quantifiable business impact.

    Behavioral & LeadershipOnsiteBehavioralLeadershipSystem Design
  • DoorDashMediumSoftware Engineer
    Project Deep Dive: Technology Choices, Trade-offs, Hindsight and Working with PMs

    A DoorDash project deep dive and hiring manager conversation about a project you are proud of. It probes why you chose your technologies, which alternatives and trade-offs you weighed, the challenges you faced, what you would change, and how you worked with other teams and product managers.

    Behavioral & LeadershipOnsite
  • DoorDashMediumSoftware Engineer
    Recover a Project That Has Gone Off Track

    This question assesses a candidate's ability to demonstrate leadership, analytical rigor, and project management skills when facing technical or execution failures.

    Behavioral & LeadershipTechnical ScreenLeadershipProject ManagementCommunication
  • DoorDashMediumSoftware Engineer
    Resolve Disagreement, Use Feedback, and Grow Engineering Judgment

    Discuss technical disagreement, constructive feedback, concrete growth practices, and how varied perspectives contribute to accountable team decisions.

    Behavioral & LeadershipOnsite
  • DoorDashHardSoftware Engineer
    Resolve a Workplace Conflict

    Tests your ability to navigate high-stakes technical or cross-functional disagreements constructively using data, empathy, and active listening to achieve a durable outcome.

    Behavioral & LeadershipOnsiteBehavioralLeadershipConflict Resolution
  • DropboxMediumSoftware Engineer
    Describe Your Most Complex Project

    This question evaluates a candidate's communication, leadership, ownership, and problem-solving competencies, specifically probing technical depth in system architecture, trade-offs, collaboration, risk management, and measurable impact.

    Behavioral & LeadershipOnsite
  • DropboxMediumSoftware Engineer
    Describe surprising project learnings

    This question evaluates reflective project ownership, leadership, decision-making, communication, and the ability to derive actionable lessons from surprising findings in substantial software engineering work.

    Behavioral & LeadershipOnsite
  • EightfoldaiMediumSoftware Engineer
    Explain Employment Status, Promotions, and Departures

    This question assesses a candidate's professional communication skills, specifically their ability to articulate career progression and the rationale behind job transitions clearly and constructively.

    Behavioral & LeadershipHR ScreenBehavioralCommunicationCareer-Growth
  • EliseAIEasySoftware Engineer
    Describe Something a Previous Engineering Team Did Not Do Well

    A behavioral question asking what a previous engineering team did not do well. Tests whether a candidate can name a specific, fixable weakness, explain its cost and systemic cause, describe their own part in improving it and stay constructive without blaming former colleagues.

    Behavioral & LeadershipTechnical Screen
  • EliseAIMediumSoftware Engineer
    Explain a Technical Decision and Transferable Team Practice

    This question assesses the candidate's ability to articulate technical trade-offs, reflect on past architectural decisions, and demonstrate maturity in implementing new engineering processes within an existing team culture.

    Behavioral & LeadershipTechnical ScreenLeadershipCommunicationEngineering Process
  • EliseAIEasySoftware Engineer
    Introduce Yourself and Explain What You Want in Your Next Engineering Role

    The opening of a software engineer phone screen: give a concise introduction of yourself and explain what you are looking for in your next role. Tests narrative structure, the choice of specific highlights that set up a technical deep dive, and motivation that is backed by evidence and fits the role.

    Behavioral & LeadershipTechnical Screen
  • EliseAIEasySoftware Engineer
    Walk Through a System You Built: Key Technical Decisions and the Hardest Part

    Describe a technical system you implemented at a previous company, the technical decisions you made along the way and the hardest part of the work. Tests clear ownership, trade-off reasoning between real alternatives, technical depth under probing and honest reflection on what was difficult.

    Behavioral & LeadershipTechnical Screen
  • EvenUpMediumSoftware Engineer
    Answer common recruiter behavioral questions

    This set evaluates interpersonal and behavioral competencies—communication, self-reflection, stress management, and the ability to translate technical ideas—within the Behavioral & Leadership domain for a Software Engineer role.

    Behavioral & LeadershipOnline Assessment