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?

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 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 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.

I'm a senior IC with over six years at my company, and nearing the end of my career. There are only two others at my level in our department. When I resign, how much notice is appropriate? Also, does it make a difference if I'm resigning for early retirement versus moving to a competitor?