How to Level Up
Join the DZone community and get the full member experience.Join For Free
i regularly hear from and read about technologists in a career rut. unless one is both lucky and adept at predicting the future, experiencing some temporary stall can happen to professionals at any career stage. it may be the feeling of being stuck in an unchallenging role, feeling burdened by an undesirable skill set, or trapped in a company that seems difficult to escape.
career stagnation in technology could be defined as a prolonged period characterized by limited project variety, no advancement or even lateral movement, few tangible accomplishments, and little exposure to any emerging trends. some managers are aware that workers in these situations generally leave, so the managers may proactively try to satisfy staff by shuffling teams and providing more interesting tasks. many managers have to focus on deliverables and may give little thought to the career development of their charges, perhaps throwing money at retention problems instead of providing challenges.
to “ level up ” could mean a promotion into management or technical leadership, a new start at a firm with increased opportunity, a role with autonomy and decision-making responsibility, or the ability to make significant improvements to skills and marketability. people that think about the leveling up concept often know what they want (or sometimes what they don’t want ), but don’t necessarily see the best paths to get there .
leverage the skills you have to get the skills you want
most professionals view their current skills as a means to getting new jobs, but it’s useful to also think about skills as the key to acquiring other new skills. this tactic is most relevant when a skill set is dated and a previously strong marketability level is now questionable. some will attempt to make a clean and immediate break from their old technologies or responsibilities into the new, usually with mixed results.
as an example, many cobol programmers tried to enter the stronger java job market following y2k. some applied to jobs with no java experience hoping their cobol years would be deemed transferrable, while others pursued certifications and self-study to ideally be viewed as a somewhat “experienced” hire. one overlooked strategy was to approach companies that were using both cobol and java in some capacity, with the understanding that the candidate was willing to write cobol if provided the ability to also work with java.
most job seeking technologists have at least one ability that will help them contribute immediately to any other team or organization. it could be an obscure technical skill, leadership experience, or domain knowledge. even if the skill is not something the person wants to use forever, it could be a key component to getting hired. try to identify companies that may be looking for some specific expertise you can provide, even if it isn’t the most attractive tool in your bag, and be transparent about your willingness to do that less desirable work in exchange for exposure to skills that are in demand.
for those in the most stagnant of technical environments, taking on independent projects or open source may be the best way to gain experience and increase marketability. it’s usually preferable to learn new things on the job (because money), but being proactive about your career and keeping abreast of current marketable technologies will also show initiative to potential employers. the level up from personal projects almost always comes from an employment change.
sometimes to level up you need to take a step back – or sideways
careers aren’t always linear, and the expectation that trajectory needs to follow a strict continuous and incremental level of responsibilities is perhaps naive and potentially dangerous. job seekers are often prone to placing too much weight on a position’s salary or ( gasp ) title without fully considering the position’s potential opportunity as it relates to future marketability and career development. somewhat frequent movement between jobs is accepted in our industry, so positions can be viewed as stepping stones to future opportunities.
when evaluating new roles, whether with a current employer or another firm, imagine what a three or four year tenure in that role at that company will look like on future résumés. will the skills likely to be acquired or improved in that role be marketable and transferrable to other firms? accepting positions that come with lateral responsibility and compensation is usually a wise long-term decision when provided a more favorable learning and growth environment.
Published at DZone with permission of Dave Fecak, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
A Data-Driven Approach to Application Modernization
The Role of AI and Programming in the Gaming Industry: A Look Beyond the Tables
What Is Envoy Proxy?
13 Impressive Ways To Improve the Developer’s Experience by Using AI