I tend to think most hiring managers are smart enough to know that it takes more than a few bad programmers to make a spectacular failure. Personally, as the manager, I'd ask about the project and listen carefully to the answer. It would tell me a lot about the person (perhaps more than a litany of successes). As a potential applicant, be prepared with an answer that shows you have an understanding of the whole project life cycle and not just your piece. Show that you can critically evaluate the project without resorting to name calling or finger pointing. I don't think you have to worry about it being a career ender.