good asdasdas
1
good asdasdas
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?
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?
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?
I recently switched to salary, and my workload exploded. Suddenly, everything is "urgent," so I'm working 2–3 hours of unpaid overtime at home every night. The company is billing the client for my extra hours, but I'm not seeing any of it. How do I bring this up with management? I'd rather not keep working for free.