This article is crossposted from IEEE Spectrum’s careers newsletter. Sign up now to get insider tips, expert advice, and practical strategies, written in partnership with tech career development company Parsity and delivered to your inbox for free.
Hard work rarely speaks for itself.
When Brian landed his first job as a software engineer, he operated under a simple, common plan: put in the hours, execute tasks diligently, and trust that someone would eventually notice. The underlying assumption was that a manager would inevitably tap him on the shoulder, hand him a promotion, and perhaps deliver a validating speech about his contributions.
Instead of accelerating his trajectory, that plan stalled his career for approximately five years.
During that stretch, he switched jobs twice, kept his head down, consumed stacks of advanced programming books, and occasionally pulled grueling 12-hour days. Despite the intense effort, he was never promoted. Frustrated by the lack of upward mobility at his third job, he began interviewing at other technology companies and almost immediately secured an offer for a senior engineer role.
When he returned to his current employer to tender his resignation, the team was entirely blindsided. Because he genuinely liked his manager and colleagues, the company responded quickly with a counteroffer to entice him to stay. During the ensuing discussions, someone from the human resources department asked a straightforward question that fundamentally shifted his perspective: "Why didn’t you just ask us?"
The reality was simple: it had never occurred to him.
He ultimately accepted the counteroffer and remained with the company. Three jobs into his professional journey, he finally secured a promotion, and the catalyst required nothing more complicated than asking—albeit in the most dramatic fashion possible.
Reflecting on those early years from the vantage point of his current career, he recognizes that a dramatically different approach is required. Year-end review discussions present a natural, highly effective window to push for a career advancement. However, at the vast majority of corporate organizations, financial compensation, raises, and formal promotion tracks are largely decided and locked in well before the official year-end review conversation ever takes place. If the upcoming performance review cycle serves as the first instance where a manager hears that an employee desires a promotion, the timing is almost always too late.
Consequently, experts and industry veterans emphasize that the weeks leading up to formal reviews are the ideal moment to initiate the conversation.
Hard work is invisible by default
Engineers and technical professionals frequently harbor the misconception that good work naturally advocates for itself in the workplace. In practice, that almost never happens. A typical engineering manager is constantly juggling multiple competing priorities, including team oversight, project roadmaps, shifting deadlines, and reporting to their own leadership. They inevitably witness only a tiny fraction of the actual daily output generated by each team member, and the contributions they fail to see might as well not exist when corporate leadership convenes to decide raises and promotions.
Because perception heavily dictates professional reality, employees must actively learn how to shape that perception. For many technical workers, this requires overcoming an aversion to self-promotion and learning how to articulate their value effectively.
A proven method for tracking and communicating this value involves maintaining what career coaches call a "brag document." This is simply a running, chronological log of what an employee has accomplished, when the milestone was achieved, and why it mattered to the broader organization. By updating this record every two weeks or once a month, professionals can compile a comprehensive portfolio of their impact. Crucially, each entry should be written in a way that a manager’s manager can easily comprehend without needing a deep dive into technical minutiae.
Engineers naturally gravitate toward concise, functional descriptions, such as "migrated the billing service." A far more effective entry, however, reframes the accomplishment in business terms: "migrated the billing service, which cut failed payments by 30 percent and unblocked the Q3 pricing launch." When metrics or direct performance numbers are unavailable, the description should clearly identify who benefited from the work and how their operational capacity improved.
Moreover, a comprehensive impact log must capture the foundational labor that often goes uncounted during performance evaluations. This includes handling critical system incidents, mentoring junior colleagues, interviewing prospective job candidates, and writing the internal documentation that the rest of the team relies on daily. For instance, employees who actively assisted their teams in adopting new artificial intelligence coding tools over the past year should document those efforts explicitly. Such contributions demonstrate vital leadership qualities, regardless of whether the official job title formally recognized them as a leader.
Maintaining this document serves two distinct and valuable functions. First, it provides concrete evidence and talking points when the employee makes their direct case for advancement. Second, and perhaps equally important, it gives the manager a ready-made narrative—complete with clear metrics and impact statements—that they can copy and paste into internal advocacy documents during executive compensation meetings where the employee is not present.
Just ask
Building a robust case through documented achievements establishes the foundation, but actively asking for advancement forces organizational action.
When approaching the annual review cycle with the clear goal of securing a promotion or a substantial raise, professionals are advised to pose direct, forward-looking questions to their leadership. An effective framing might involve asking: "What would it take for me to get to the next level in the next year?"
A competent, supportive manager will respond by providing a clear outline or set of expectations that can be translated into a concrete professional development plan. Employees should press for specific, measurable deliverables that they can actively work toward over the coming months. Once those milestones are established, sending a brief recap email ensures that the plan is documented somewhere permanent, safeguarding against the reality that managers themselves occasionally change jobs or transition to different internal departments.
When the answer is "no"
Even with careful preparation, thorough documentation, and direct communication, employees will occasionally encounter a negative response during their review cycles. Sometimes, the answer will simply be "not this year," and the underlying rationale may have zero connection to the individual’s actual performance or capabilities.
Corporate budgets face sudden freezes, promotion slots can be rigidly capped by executive leadership, and final decisions are frequently made far above a direct manager’s head. In such scenarios, even a well-intentioned manager who genuinely advocates for their team member’s career growth may find their hands tied by institutional constraints.
Employees are encouraged not to overanalyze or internalize these macro-level obstacles. At the same time, however, brutal honesty with oneself is necessary. In many cases, a negative response indicates that there are specific competencies or responsibilities the employee has not yet demonstrated or assumed. Identifying those missing elements directly through candid managerial feedback prevents years of unproductive guesswork.
Ultimately, initiating the conversation about professional growth costs little more than a single, potentially awkward dialogue. Conversely, sitting back complacently and waiting for hard work to be noticed organically can quietly cost an ambitious professional years of wasted time.
In related industry news, recent inquiries into research integrity highlight ongoing challenges within academic and technical publishing. To better understand the risks that automated content generation poses to modern scientific publishing, IEEE Spectrum contributor Benjamin Skuse recently put research integrity checks to the test by submitting two entirely AI-generated papers. The experiment underscored a growing concern across the scientific community: science faces a mounting spam problem, and traditional editorial filters are increasingly strained by the volume of low-quality submissions.
Meanwhile, policy advocacy remains a critical arena for technical experts, demonstrating that legislative change is not solely shaped by professional lobbyists. Lawmakers consistently express a strong desire to hear directly from working engineers and scientific experts. Reflections from technical professionals who have engaged in legislative outreach emphasize the tangible value of bringing firsthand industry perspective directly to Capitol Hill.
Additionally, educational institutions are adapting to shifting labor market demands, particularly regarding the burgeoning technology manufacturing sector. Community colleges across the United States are increasingly stepping up to help bridge the anticipated talent shortage within the semiconductor industry. By offering viable, accelerated alternatives to traditional four-year university degrees, these institutions are providing a promising educational pathway for the specialized technicians needed to operate newly established manufacturing fabrication plants.
