Career change at 40: what your experience is worth

Three fears do most of the damage. The first is age, the sense that employers want someone younger. The second is pay, the assumption that changing fields means going back to the bottom. The third is identity, and it is the one people say least about: “I am an operations manager” has answered the question of who you are for 20 years, and “what else would I be” has no answer yet.

Take them in order. Employers weigh whether your experience prepares you for the responsibilities in the new role, and that is a question your record can answer. The pay fear attaches to full restarts, and the rest of this guide is about avoiding one. As for identity, a title cannot show every team, budget, customer, system, or problem you have managed in a long career, which is why the next section sets titles aside.

Set the titles aside and list the work itself. Somewhere in those years you hired people and lived with the results, and you trained new coworkers because you were the one who knew how things worked. You have run a budget, defended one, or delivered inside one that was too small. Vendors, customers, landlords, your own management: you have negotiated with all of them. You fixed failures you did not cause, calmed clients who had every right to be angry, and met deadlines through reorganizations, outages, and short staffing. Then the company switched software and you learned it, and switched again and you relearned it.

Every item on that list is a requirement in some job posting right now, in fields you have never worked in. That is the material a change is built from, and none of it expires when you leave the industry where it happened.

A full restart changes everything at once: new industry, new function, new vocabulary, entry-level standing. Change one half and keep the other, and most of your experience stays in play. The options below are ways to do that.

Make an inventory of outcomes, one line for each result you can stand behind: a cost you cut, a team you kept staffed through a hard year, a customer you kept when they were ready to leave. Use that list for search terms and for interview examples.

Then search for duties, not job names: vendor negotiation, inventory planning, training program. Read each posting for the work it describes, whether or not you have held the title, and keep every posting that describes work you have already done. The duties and requirements that recur across your saved postings show which roles match your experience most closely, whatever those jobs are called.

Your network is 20 years deep. Former coworkers, customers, and vendors are now spread across companies and industries you have no other way into. Tell them what you are looking for in the destination’s language, the duties and the field, so they can recognize a fit when one crosses their desk.

Begin with roles that keep either your current function or your current industry. Part of that job is already yours on day one, and posted pay may stay closer to your current pay than it would in a full restart. A full restart should be a deliberate choice made after reading the postings, never the default.

Interviewers will ask why you are changing now. They are checking that you have a plan, so give them one honest sentence that points forward: you want the next 10 years in work built around the part of your last job you were best at. Then give evidence that you already do pieces of the new work. The candidate for the training role has onboarded new hires for a decade, and the candidate for the vendor role has used the product for years. Reason first, then evidence, and no apology.