A strong answer should be specific, balanced, and grounded in real experience. Good themes to include: - You enjoy owning problems end to end, from user experience to backend logic. - Working across the stack helps you move faster and reduce handoff friction. - Seeing both frontend and backend trade-offs makes you a better engineer. - You like building product intuition because you can connect user needs to technical decisions. - You still respect depth and know when to partner with specialists. A strong structure: 1. Start with your core motivation. 2. Give one or two concrete examples. 3. Explain why this makes you more effective on a team. 4. Close by tying it back to the role. Example answer: "I am interested in full-stack engineering because I like solving user-facing problems completely, not just one layer of them. I enjoy thinking about how frontend interaction, API design, data flow, and performance all affect the final user experience. In past projects, I found that being comfortable across the stack helped me iterate faster, debug issues more effectively, and make better trade-offs. For example, when a page felt slow, I could look at both the React rendering path and the backend response shape instead of optimizing in isolation. I also like that full-stack work builds strong product intuition because you see how technical choices directly impact users. That said, I value depth as well, and I enjoy collaborating with specialists when a problem needs deeper expertise. Overall, full-stack work fits how I like to build: with broad ownership, strong cross-functional collaboration, and a focus on delivering complete product outcomes."