I'm a junior engineer, but I inherited a project mid-construction because the designer left. I wasn't around for the early phases, but now I’m running the site meetings. I'm stressed about the technical gap and being asked questions I don't know the answers to. I don't want to appear clueless in front of the clients, even though I am. Is it okay to say that I don't know, but I will get back to them? Or does that look unprofessional?

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.

My job is stable and pays decently, but I haven't picked up a new skill in over a year. I keep waiting for a reason to leave that feels urgent enough. Has anyone left a job that's comfortable but stagnant?

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.