工程师年终评审如何争取晋升：从默默苦干到主动开口

This article is crossposted from IEEE Spectrum ’s careers newsletter. Sign up now to get insider tips, expert advice, and practical strategies, written i n partnership with tech career development company Parsity and delivered to your inbox for free! Hard work rarely speaks for itself. When I landed my first job as a software engineer, I had a simple plan: Work hard and somebody would notice. Eventually a manager would tap me on the shoulder and hand me a promotion (probably with a nice little speech). That plan stalled my career for about five years. I switched jobs twice, kept my head down, read a stack of programming books, and sometimes pulled 12-hour days. I was never promoted. At my third job, out of frustration, I started interviewing at other companies and almost immediately got an offer for a senior engineer role. So I went back to my job and quit. My team was blindsided. I liked my manager and the people I worked with, and they came back with a counteroffer. Then someone from HR asked me, “Why didn’t you just ask us?” Honestly, it never occurred to me. I took the counteroffer and stayed. Three jobs in, I finally got promoted, and all it took was asking (in the most dramatic way possible). Today, I would take a different approach. Year-end review discussions are a great time to push for a promotion. But at most companies, raises and promotions are largely settled before the formal review conversation happens. If the year-end review is the first time your manager hears you want a promotion, you’re usually too late. Now is a great time to start the conversation. Hard work is invisible by default Engineers tend to believe good work speaks for itself. It rarely does. Your manager is juggling a team, a roadmap, and their own boss. They see a fraction of what you do, and the work they don’t see might as well not exist when raises get decided. Perception is reality, so you have to shape it. That means learning to brag a little. A “brag document” is a running list of what you accomplished, when, and why it mattered. Add to it every two weeks or once a month, and write each entry so your manager’s manager would understand it. Engineers tend to write things like “migrated the billing service.” A better entry reads “migrated the billing service, which cut failed payments by 30 percent and unblocked the Q3 pricing launch.” If there’s no number, name who benefited and how. Include the work people forget to count, too: handling incidents, mentoring new hires, interviewing candidates, and writing the docs everyone else relies on. If you helped your team adopt AI tools this year, write that down. (It counts as leadership, whether or not anyone called it that.) The document does two jobs. It gives you ammunition when you make your case, and it gives your manager something to ctrl + c then ctrl + v when they argue for you in meetings you’ll never attend. Just ask Bragging builds the case. Asking forces action. If your goal is a promotion or a raise, you might ask: “What would it take for me to get to [the next level] in the next year?” A good manager will give you an outline that can turn into a plan. Push for specifics until you have deliverables you can work toward, then send a short recap email so the plan exists somewhere besides your manager’s memory. (Managers change jobs too.) When the answer is “no” Sometimes the answer will still be “not this year,” and the reason may have nothing to do with you. Budgets get frozen, promotion slots get capped, and decisions get made above your manager’s head where even a manager who wants to help can’t. Don’t read too much into that. But be honest with yourself, too. Most of the time, a no means there’s something you aren’t doing yet. Find out what it is instead of guessing for five years like I did. Asking costs you one slightly awkward conversation. Sitting back and waiting to be noticed can cost you years. —Brian I Used AI to Fake a Scientific Paper. Here’s What Happened Don’t try this at home: To better understand the risk AI slop poses to scientific publishing today, IEEE Spectrum contributor Benjamin Skuse put IEEE’s research integrity checks to the test by submitting two entirely AI-generated papers. “Science has a spam problem. And the spam filter is getting clogged up…” Read more here . Why Engineers Should Brave Capitol Hill Policy change doesn’t just come down to paid lobbyists—lawmakers want to hear from working experts, too. One engineer shares what he learned from his first two visits to Capitol Hill. Read more here . Community Colleges Put New Workers Into Semiconductor Jobs Fast Could community colleges help fill the coming talent shortage in the U.S. semiconductor industry? Alternatives to four-year university degrees are a promising option for the technicians who will be needed to run new fabs. Read more here .