# Describe a time when your project failed | Aced

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/questions/932/time-when-project-failed
Source observed: 2026-11-04T21:42:47.953Z
Last checked: 2026-11-04T21:42:47.953+00:00
Indexed: 2026-11-05T03:12:34.058+00:00

---

# Describe a time when your project failed

We provide interview-preparation resources through Aced, formerly Exponent. This page covers a behavioral interview question asking candidates to describe a project failure. A founder of a SaaS startup shares an answer to the related prompt, “tell me about a time you failed.” Questions like this are often asked at Amazon to assess fit with Amazon’s Leadership Principles.

[All Questions](https://www.aced.io/questions)

## Question details

- **Category:** Behavioral
- **Reported interviews:** 22
- **Reported last asked:** a month ago
- **Roles associated with this question:** Software Engineer (6), Product Manager (6), Data Scientist (2), Forward Deployed Engineer, Engineering Manager, QA Engineer, Machine Learning Engineer
- **Companies associated with this question:** Meta (4), Amazon (2), Microsoft (2), Apple, Grammarly, Revolut, Patreon, Uber, Anduril, GE Aerospace, Walmart Labs, Discord, Block, Accenture, Expedia
- **Saved by:** 188 users

## Membership access

Detailed company statistics for this question require an upgrade. Membership includes:

- 100+ expert answer videos
- Access to all courses
- Peer-to-peer practice
- Private Discord community
- Full question database

[Upgrade](https://www.aced.io/upgrade?src=questions) · [Upgrade now](https://www.aced.io/upgrade?src=questions)

## Interview experiences

We show 13 shared interview experiences connected with this question.

1. **[Apple · a month ago](https://www.aced.io/experiences/apple-senior-software-engineer-interview-a33f8a)** — Software Engineer, Senior / L5  
   “The process was very fair and there was a clear emphasis on communication and culture fit. Everyone I interviewed with was very pleasant and encouraging. My one complaint would be the sense that the recruiter was not helpful or informative when it came to preparing me on what to expect. Technical rounds emphasized practical ability and had strong correlation to the responsibilities of the role.”

2. **[Grammarly · 3 months ago](https://www.aced.io/experiences/grammarly-senior-software-engineer-interview-d9d0e6)** — Software Engineer, Senior / L5  
   “Straightforward process; recruiters were very nice and helpful; Didn't provide any feedback but I got rejected after the onsite”

3. **[Revolut · 5 months ago](https://www.aced.io/experiences/revolut-data-scientist-interview-ac4820)** — Data Scientist  
   “good, the process had been very through with a coding round as well.The coding was more on implemneting and solving ML problem”

4. **[Patreon · 6 months ago](https://www.aced.io/experiences/patreon-senior-data-scientist-interview-8016f8)** — Data Scientist, Senior / L5  
   “Not that hard, pretty easy SQL coding challenge. Have to run the SQL live in a Python NB. The behavioral was also pretty easy and mostly about past projects and failures and probing more on resume.”

5. **[Uber · 7 months ago](https://www.aced.io/experiences/uber-staff-software-engineer-interview-6b1b44)** — Software Engineer, Staff / L6  
   “I got in through a referral, had a lightweight recruiter call, then an initial coding screen, and then a five-round final. The final was two coding rounds, one system design, one past-project round that turned into a behavioral deep dive, and one straight behavioral. What stood out was how much Uber cared about technical depth over polished cross-functional storytelling, especially for a staff role. Even the coding rounds felt like they wanted system-design-style tradeoff thinking, and they gave me the Number of Islands variant in the final coding round.”

6. **[Amazon · a year ago](https://www.aced.io/experiences/amazon-senior-forward-deployed-engineer-interview-ed3136)** — Forward Deployed Engineer, Senior / L5  
   “What went well: interesting questions, everybody kind and smart. What didn't go well: I should have prepared more to tell about business impact.”

7. **[Anduril · a year ago](https://www.aced.io/experiences/anduril-senior-software-engineer-interview-06e1cb)** — Software Engineer, Senior / L5  
   “I felt this was a hard interview to prepare for. there are not a lot of question banks out there for Anduril. I also only encountered new problems.”

8. **[Meta · a year ago](https://www.aced.io/experiences/meta-facebook-senior-product-manager-interview-758791)** — Product Manager, Senior / L5  
   “Overall pretty straightforward, their interviews are pretty standard and are not there to surprise you. Recruiter and interviewers were professional.”

9. **[GE Aerospace · a year ago](https://www.aced.io/experiences/ge-aerospace-product-manager-interview-08ebcd)** — Product Manager, Mid Level / L4  
   “The process was relatively straightforward. The hiring manager was very conversational and introduced himself. It felt like we were just having a chat. I was an internal hire so I might have had it easier than someone who would have interviewed from outside.”

10. **[Walmart Labs · a year ago](https://www.aced.io/experiences/walmart-labs-software-engineer-interview-751680)** — Software Engineer, Mid Level / L4  
    “The interview process was well-structured and fairly rigorous compared to others I’ve experienced. I appreciated that the recruiter clearly communicated expectations upfront, which helped me prepare in the right direction. The technical rounds were challenging but relevant to the role, and the interviewers were professional and engaging.”

11. **[Block · 2 years ago](https://www.aced.io/experiences/block-senior-product-manager-interview-8c5cfa)** — Product Manager, Senior / L5  
    “Answered effectively, they were looking more for an international experience (Asia) and the job description didn't mention”

12. **[Amazon · 2 years ago](https://www.aced.io/experiences/amazon-software-engineer-intern-interview-9beb3b)** — Software Engineer, Intern  
    “Overall, the interview process was well-structured and a positive experience. The interviewer was professional and approachable, and the questions provided a good opportunity to demonstrate my technical and problem-solving skills. I particularly appreciated the collaborative nature of the discussion. One area for improvement would be allowing slightly more time for discussing alternative approaches and testing edge cases. Overall, I appreciated the experience and the opportunity to interview with the team.”

13. **[Accenture · 3 years ago](https://www.aced.io/experiences/accenture-qa-engineer-interview-aa7f21)** — QA Engineer, Mid Level / L4  
    “The recruiter is good , friendly and patient Always briefing about what would the next roles look like”

## Community answers

No answers have been contributed by the community yet.

## Related questions

- [Describe a time when a project lacked key information.](https://www.aced.io/questions/2147/handling-project-lacking-information)
- [Describe a time when your values were tested.](https://www.aced.io/questions/2060/describe-time-when-values-were-tested)
- [Tell me about a time when data failed you.](https://www.aced.io/questions/1346/time-data-failed-you)

## Related courses

### [Machine Learning Engineer Interview Prep](https://www.aced.io/courses/ml-engineer)

![Machine Learning Engineer Interview Prep](https://images.ctfassets.net/x78yjrjc11pq/6UfkHxUyLQVfDHSfLNQtWa/1be1539a65b4f6f15201f5b573c0a578/ML_Engineer_Interview_Prep_Course.jpeg?w=800&h=800&fm=webp&q=75)

We help candidates pursue machine learning roles at Meta, Google, Amazon, Apple, Microsoft, Nvidia, and other companies through mock interviews, frameworks, and advice from senior candidates. The course covers ML system design, core concepts, coding, behavioral interviews, and more.

### [Engineering Management Interview Prep](https://www.aced.io/courses/engineering-management)

![Engineering Management Interview Prep](https://images.ctfassets.net/x78yjrjc11pq/5AqarwlCDWmr0W7AbMJFwp/16862dab13471f5eb8728b27eb2fbc07/engineering_management_track_compressed_bbabaec4a6__281_29_9a9687c1fb.jpeg?w=800&h=800&fm=webp&q=75)

We help candidates pursue engineering manager roles at Meta, Google, Amazon, Microsoft, Stripe, and other companies through mock interviews, frameworks, and advice from senior candidates. The course covers system design, people management, project retrospectives, behavioral interviews, and more.

## Practice and submission

Use [Practice with AI](https://www.aced.io/practice/ai/new?type=Behavioral&question=time-when-project-failed&src=questions) to practice this behavioral question. Submitting an answer marks the question complete.

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F932%2Ftime-when-project-failed&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F932%2Ftime-when-project-failed). Opening a form does not execute a tool.