Hacker News new | past | comments | ask | show | jobs | submit login

What would be some attributes or examples of a good answer?



Not OP, but explaining that they have specific feature targets and timelines to try out an idea / land certain customers. They understand that they are sacrificing time in the future by rushing now. Whether they actually understand that is not always a given.

On the flip side, I have also heard fast paced implied to mean "you will work 60-80 hours a week because we have unreasonable timelines and expectations". I passed on those, naturally.


Good answers are something like “we don’t have many gatekeepers. if you need a compute instance, just spin one up in Terraform.”

bad answers:

* (interviewer guffaws) * “work hard / play hard” * implying significant overtime


"We only test in production"




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: