How do you handle disagreements with your manager about technical decisions? I’ve learned to pick my battles and always come with data instead of opinions when I do push back. It doesn’t always work, but it at least keeps the conversation productive. How do you approach it?

Do you think the best engineers are the ones who spot problems early or the ones who solve them quickly? I’m starting to think spotting them early creates far more value.

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?

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?

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?