Katkat
Back

Explain a past project and critique a prior team

LinkedInSoftware Engineer · Technical Screen
MediumSoftware EngineerTechnical ScreenBehavioral & Leadership

Last updated

This question evaluates communication of technical ownership, system architecture reasoning, and leadership competencies such as collaboration, conflict resolution, and influencing change within a Software Engineer role.

Interview prompts

  1. Project deep dive: Pick a past project you worked on and walk through it end-to-end. Be ready to use a whiteboard to explain architecture, trade-offs, and your specific contributions.
  2. Team reflection: What problems did you observe in your previous team/org (process, collaboration, code quality, ownership, etc.)? What would you change, and how would you influence that change as a junior engineer?

What to cover

  • Your role, scope, and impact.
  • Key technical decisions and why.
  • A challenge or conflict and how you handled it.
  • Lessons learned and what you would do differently.