Describe project impact and critical feedback
Company: Databricks
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Onsite
Prepare for two behavioral prompts commonly asked in a software engineering onsite interview:
1. **Describe a project you are proud of**
Explain the business or technical problem, your specific role, the key decisions you made, the challenges you faced, and the measurable impact of the project.
2. **Describe a time you received critical feedback**
Explain the situation, what the feedback was, how you responded in the moment, what actions you took afterward, and what changed as a result.
In both answers, emphasize ownership, collaboration, judgment, and learning.
Quick Answer: This question evaluates behavioral and leadership competencies such as ownership, collaboration, communication, judgment, problem-solving, and receptiveness to critical feedback through recounting project impact and responses to criticism.
Solution
A strong behavioral answer should be structured, specific, and reflective. The easiest framework is **STAR**: Situation, Task, Action, Result.
**1. For the project question**
Interviewers want to learn:
- what scale of problems you handle
- whether you personally drove meaningful work
- how you make technical decisions
- whether you measure impact
A good structure:
- **Situation**: What problem existed? Why did it matter?
- **Task**: What were you responsible for?
- **Action**: What did you design, implement, or coordinate? Why those choices?
- **Result**: Use metrics if possible: latency reduced, revenue increased, incidents decreased, developer time saved, and so on.
- **Reflection**: What would you improve if you did it again?
What makes this answer strong:
- clear ownership without exaggerating team work
- technical depth matched to your level
- measurable outcome
- thoughtful hindsight
Common mistakes:
- spending too much time on background
- saying only what the team did
- giving no metric or outcome
- choosing a project where your role was unclear
**2. For the critical feedback question**
Interviewers are testing coachability, self-awareness, and maturity.
A good structure:
- **Situation**: Describe a real moment when feedback was difficult but fair.
- **Feedback**: State it plainly. Do not soften it so much that it sounds fake.
- **Response**: Show that you listened rather than becoming defensive.
- **Action**: Explain the concrete steps you took to improve.
- **Result**: Show what changed in your behavior, relationships, or outcomes.
- **Reflection**: Explain how you now prevent the same issue.
Good themes include:
- communication was too brief or too blunt
- you did not align stakeholders early enough
- you over-engineered a solution
- you moved too fast without enough testing
- you were not delegating or documenting effectively
Avoid answers where:
- the feedback was obviously wrong and you dismiss it
- the example makes you look unethical or careless
- there is no real behavior change
**3. Recommended delivery style**
- Keep each answer to about 2 to 3 minutes.
- Be concrete and concise.
- Mention both technical and interpersonal dimensions.
- End with what you learned.
**4. Sample answer outline**
For the project prompt:
- Problem: a manual deployment workflow caused frequent release delays
- Role: you led the backend implementation
- Actions: designed automation, added rollback support, coordinated with infra and QA
- Result: reduced deployment time from 40 minutes to 8 minutes and cut failures by 60%
- Reflection: would have involved security review earlier
For the feedback prompt:
- Feedback: teammates said your design reviews were too detailed and slowed decisions
- Response: you asked for examples and clarified expectations
- Actions: started sending short pre-reads, separating major concerns from minor comments, and timeboxing review meetings
- Result: faster review cycles and better collaboration
- Reflection: learned to adapt communication depth to audience and urgency
This combination shows impact, humility, and growth, which is exactly what interviewers look for.