There are other ways to phrase this, but many of them seem stigmatizing of early career professionals. It's an employer's/industry's responsibility to have systems which can appropriately metabolize their labor and accelerate their skills development over the coming years.
-
-
Show this thread
-
If you need to discourage early career professionals from doing material engineering work because that could break things at your shop, a) your not-early career professionals need to do some systems work and b) you need to rethink your hiring strategy, urgently.
Show this thread -
For related reasons I am glad that I work with systems which make it possible but an extra click for me to locate employee tenure, because "Will X remember the (fake) May 2016 incident?" is work-relevant but "Are they senior enough to listen to?" should be discouraged.
Show this thread -
(Clarification: I think that "Our company is immature and, accordingly, we only hire senior engineers because their seniority/experience is a substantial percentage of our controls against things going off the rails." is a legitimate business decision.)
Show this thread -
(The capitalist in me says "You realize that it is basically inevitable that your blended cost for engineers then exceeds that of every firm which has invested in onboarding early career professionals, which set includes all of AppAmaGooBookSoft, right.")
Show this thread
End of conversation
New conversation -
-
-
Sometimes my more experienced colleagues argued with me if I called myself "junior" because of how valuable my skills are. I switched to "early career" and it works perfectly. I never mean to convey "I can't do that," I only ever intend to contextualize my experience or goals.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.