Stay solid always, and maintain the good 👍 work
1
Stay solid always, and maintain the good 👍 work
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 was the biggest mistake you made early in your career that ended up teaching you a valuable lesson? One of mine was assuming everyone interpreted requirements the same way I did. Learning to ask clarifying questions saved me from a lot of rework. What’s yours?
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.
đź’ If you were let go from your job tomorrow, what's the first thing you'd do?
I've been stuck in a pure maintenance cycle for six months, and I'm starting to feel like a script-runner instead of an engineer. I'm trying to move into a senior-level job, and I worry about stagnating, but I'm not sure what to do. Is this a common issue with engineers who hope to level up?