|
|
|
|
|
|
by coopdog
4705 days ago
|
|
|
Ten years experience and programmed a critical feature of a large program? I'd say you're a senior. I don't know the culture of your company, but one thing to consider is just telling your manager that you're near burning out (I wouldn't say burned out), celebrate what you've achieved and ask for your next assignment to be a little more laid back while you recharge for the next big push. Get something you can really switch off of when you walk out the door. At most places just starting an honest conversation and telling them why something is in their best interest will get you what you want. If they really want a revolving door of burned out engineers you're better off leaving anyway. |
|
|
I'm concerned that as soon as I bring this up in any shape, I'll be labeled as a flight risk (and rightfully so). Right now based on the conversations I've had with peers on my team, others are planning to leave at the end of the release. If I am to stay on, my role will widen greatly and I'll need to (again) train others on the area. It'll be very very difficult for me to "run away" from my feature area given that I am the resident expert and probably one of the only people who has a coherent understanding of the end to end working of the system.
This is especially scary since due to my level, I don't believe I can be compensated appropriately for the amount of work and stress this situation would bring on. I've been rejected for promotion due to "length in level" before, so it is a long way uphill.
I appreciate your optimism about me being senior already (:)) but not all of those 10 years are post-undergrad experience, so I believe it counts for less in the eyes of an interviewer. I've been undergoing rigorous introspection trying to determine how my skills really stack up, but perhaps I just need to begin interviewing for different levels.