What’s the greenest flag you’ve seen in an engineering team’s culture? For me it’s when senior engineers ask questions in public channels instead of always having the answers. It normalizes not knowing everything and makes it way easier for junior folks to speak up without feeling like they’ll be judged.

How do you know when it’s time to leave a job vs. stick it out and push through a rough patch? For me it comes down to whether the core reasons I took the role are still intact. If the work is still interesting and the people are decent, a rough patch is survivable. But if I’m dreading Mondays every single week, that’s usually a signal worth listening to.

What’s one engineering “best practice” that you think is actually overused or applied in situations where it doesn’t add much value? For me, it’s excessive documentation on very small, low-risk changes. Documentation is important, but I’ve seen teams spend more time documenting simple fixes than implementing them. Where do you draw the line?

Do you think engineers spend enough time thinking about the user experience of internal tools? I’ve seen teams tolerate painful internal systems that they’d never ship to customers.

Obviously, no one expects a newly graduated hire to know everything during their first week, but early impressions stick. Question for the managers and senior engineers on here: What can a new grad do in those first few days to make you incredibly glad you hired them? What sets them apart early on?