Career change at 40: how to fill in the application

Short answer: no application form asks how old you are. It asks years of experience, current job title and employment dates, and those three fields are where a career change at forty either survives the first screen or quietly does not.

That is the whole difference. A twenty-eight-year-old and a forty-two-year-old fill in the same boxes; the forty-two-year-old has more to put in them, and more ways for the form to file it under the wrong heading. What follows is what each field is checking, what to type in it, and what the public wage data actually says about one common version of the move. The running example throughout is an Operations Manager applying to Project Manager roles.

What the form is checking, field by field

Every application is a short interrogation, and each question has a purpose that is not printed next to it. Here are the ones that matter.

Nothing in the right-hand column is your age. Your age reaches the form as a side effect of the dates, and only if you list a whole career of them.

The one field that can reject you before a person looks

Greenhouse documents three application rules an employer can attach to a custom job post question. Auto-Tag labels the profile. Auto-Advance moves a candidate "directly to a later stage in your Interview Plan based on answers the candidate provides". Auto-Reject "uses custom application questions to screen and reject candidates based on their responses", and the worked examples on that page build their conditions on answer bands like "1-2, 3-5, OR 10+ years experience".

So when a Project Manager posting asks "How many years of project management experience do you have?" and gives you a dropdown, that dropdown may be wired to a rule. Not always — Auto-Reject requires the Plus or Pro tier — but often enough that it is the field to think hardest about before you hit submit.

The answer that works is the specific one. An Operations Manager who has run vendor implementations, budget cycles and cross-team rollouts for six years has project management experience. What she does not have is six years of the title, and the question is not asking about the title.

How many years of project management experience do you have?

6 — as Operations Manager at Redlands Foods I owned three ERP rollouts end to end, including scope, vendor schedule and a $1.4M budget. The title was not "project manager"; the work was.

If the field is a fixed dropdown with no free-text box beside it, pick the band the work supports and put that sentence in the resume summary instead, where a human will meet it. A blank answer is an answer, and it is the wrong one: an unanswered required question either blocks the submit button or arrives as an empty value, and no rule reads an empty value as "will explain later".

What to put in "Current job title"

Not what you would like to be called. This box is the string a recruiter matches against months later when they search their own database for candidates, and it is also the string a hiring manager reads first in the list of applicants. Both of those uses want the same thing: the title your payroll record says, spelled the way the market spells it.

Those two can pull apart, and that is the real problem for someone changing fields at forty. Companies invent titles. "Operations Manager II", "Site Operations Lead", "Manager, Business Operations" — all payroll-true, none of them a phrase anybody searches. Put the payroll title in the field, because an offer-stage employment verification will check it against what your employer confirms, and then put the market equivalent one line into the resume where a person meets it:

Operations Manager II (Redlands Foods) — project and program delivery for four manufacturing sites

What you do not do is type "Project Manager" into the current-title field because that is the job you want. It reads as a match for about nine seconds, until the phone screen asks what your team calls you. Aspiration in a verification field is the one shortcut in a career change that reliably costs the offer rather than the interview.

Operations Manager to Project Manager: what the pay data says

This is the part career-change advice skips, so here it is flat: on the median, this move is not a raise.

General and Operations Managers vs Project Management Specialists

O*NET dates the median wages 2025, employment 2024, and projected job openings 2024-34. The education rows are what people doing the job reported the job requires.

	General and Operations Managers	Project Management Specialists
Median annual wage, 2025	$105,770	$102,320
Employment, 2024	3,712,900	1,046,300
Projected job openings, 2024-34	308,700	78,200
Reported a bachelor's degree required	27%	64%
Reported high school or equivalent	29%	6%
Job Zone	Four	Four

O*NET puts the 2025 median annual wage for General and Operations Managers at $105,770, and for Project Management Specialists at $102,320. Same source, same vintage, and the occupation being left pays more at the midpoint. If you are making this move for money, you are betting on where you land in the range rather than on the middle of it — and the range is wide. The Occupational Outlook Handbook puts the bottom 10 percent of project management specialists under $61,580 and the top 10 percent over $167,970 as of May 2025.

The education row is the one to sit with. Among general and operations managers, 29 percent of the people doing the job said high school or the equivalent is what the job requires and 27 percent said a bachelor's degree. Among project management specialists, 64 percent said a bachelor's. Crossing between those two occupations means crossing into a field where the education box on the form is more likely to be a genuine requisition minimum — which matters a great deal if your career was built on the work rather than on the credential.

Which industry you apply into moves the number more than the title change does. The handbook's median annual wages for project management specialists, May 2025:

Read that against where your operations experience already lives. A plant Operations Manager moving into manufacturing project management applies with a decade of domain knowledge into a $102,640 median; the same person applying into finance and insurance is walking toward a $120,700 median with none of it. The spread between the top and bottom rows of that table is larger than the gap between the two occupations, which is why "which industry" is a better first question than "which title".

There is a counterweight, and it is in the same handbook. For project management specialists, BLS lists typical entry-level education as a bachelor's degree and typical work experience in a related occupation as "None". The federal handbook's own classification says this is an occupation people enter without prior experience in a related one. It projects 7 percent employment growth from 2025 to 2035 — roughly 73,200 more jobs on a base of 1,094,300 in 2025.

Is a long run at one employer a problem?

No. It is the median.

Median years with current employer, by age, January 2024

Tenure climbs steeply with age. A forty-something with seven years at one company sits at the middle of their cohort, not above it.

20 to 24		1.4 yrs
25 to 34		2.7 yrs
35 to 44		4.6 yrs
45 to 54		7 yrs
55 to 64		9.6 yrs
65 and over		9.8 yrs
All workers 16+		3.9 yrs

BLS measured median tenure with a current employer at 3.9 years across all wage and salary workers in January 2024, the lowest since January 2002 and down from 4.1 years in January 2022. Split by age, the same survey looks like two different countries: 2.7 years for workers aged 25 to 34, and 7.0 years for those aged 45 to 54. Management occupations run longer again, at 5.7 years in January 2024, and public-sector workers longest of all at 6.2 years against 3.5 in the private sector.

An Operations Manager with nine years at one employer is therefore not an anomaly anyone needs explained. What the form does with those nine years is a different problem, and it is a formatting one. Nine years under a single title parses as one job, one skill set, one date range — a flat line where a career happened. If the role changed three times inside that span, list the three internal titles with their own start and end dates. That is the difference between a candidate record reading "Operations Manager, 2016–present" and one that shows a shift supervisor becoming a plant lead becoming an operations manager, which is a progression a reader takes in at a glance.

Here is what none of this data tells you. BLS publishes tenure, wages and projected openings; it publishes nothing about how often a career changer's application is selected, and there is no federal table of hiring rates by age. Tenure figures describe the jobs people currently hold, not the applications they sent and lost. Anyone quoting you a success rate for switching careers at forty is not reading it off a government page.

If the form asks for your graduation year

Type it, and do not sand your dates to hide the decade. The EEOC's guidance is that pre-employment inquiries which may indicate an applicant's age, among other protected characteristics, "if answered, should generally be avoided" — direction aimed at the employer, not a rule you can enforce from your side by leaving a required box empty. If the field is mandatory, a blank or invented year becomes a discrepancy at the background-check stage, which is a much worse problem than the one you were solving. An Operations Manager who finished a degree in 1998 types 1998; what carries the application is the ERP rollout two boxes down, not the year the registrar printed.

If the posting says "5+ years of project management" and your title never said it

Apply anyway, and answer the years question on the work. Declining to submit because a requirement was written for a title is a rejection you issue on the employer's behalf, before anyone there has read a word you wrote.

The reason to apply is not optimism, it is the skill profile. O*NET lists coordination, time management, complex problem solving, management of personnel resources and judgment and decision making among the transferable skills for General and Operations Managers, and the same five — coordination, time management, complex problem solving, management of personnel resources, judgment and decision making — among the transferable skills for Project Management Specialists. Both occupations sit in Job Zone Four, "considerable preparation needed", where O*NET's note is that most of these occupations require a four-year bachelor's degree "but some do not", and that a considerable amount of work-related skill, knowledge or experience is needed. Two occupations that share their preparation level and most of their skill list do not have a wall between them. They have a hiring manager who needs the mapping spelled out, because the form will not do it for you.

The mapping belongs in the resume bullet and the "why this role" box, written in the target occupation's vocabulary:

Operations Manager, 2019–present. Ran the ERP migration across four sites: scope, vendor selection, an 11-month schedule and a $1.4M budget, delivered two weeks late with no unplanned downtime. Managed a matrixed team of nine across operations, finance and IT.

That is a project management bullet. It was already true before you rewrote it — it was simply written in operations language.

The order to fill it in

Filling in a career-change application without tripping a rule

1. 1
   Set the target title first

   Decide which posted title you are applying under — Project Manager, Project Coordinator, Program Manager — before you touch the form. Every other answer is written for that one.

2. 2
   Answer the years question on the work

   Count years spent doing the activity the question names, not years holding the title. Where a free-text box exists, name the projects in one sentence.

3. 3
   Split the long tenure

   List internal title changes as separate entries with their own start and end dates, so the parser reads a progression instead of one static role.

4. 4
   Use unambiguous dates

   Month and year, and 'Present' for the current job. Employment dates are how total experience gets computed, and a date the parser cannot read counts as nothing.

5. 5
   Stop the history where it stops helping

   Older roles that do not support the move can end the list. Do not leave a gap inside the range you do show.

Five steps, in that order, on every application. The first one is the step people skip, and it is the one that decides the other four.

The one thing to get right

Answer the years-of-experience question for the work, in the employer's words, and never leave it blank. It is the only field on a standard application that a company can point an automatic rejection rule at, and it is the field a career changer is most tempted to fudge in one direction or the other — inflating it to clear the stated bar, or under-reporting it because the badge said Operations Manager.

If what is actually stopping you is retyping the same nine years into a fortieth Workday form, the platform fills the application fields from your resume, so your time goes into the two boxes that need a person. Everything above still applies to what you put in them.