You found an employer you like and three of its openings look plausible. Before you send all three, it helps to know what happens on the other side: in most applicant tracking systems you are one candidate record, and every application you file hangs off it. The recruiter rarely sees one application in isolation. They see the list.
One record, several applications
Most applicant tracking systems are built around two objects: the person and the requisition, which is the internal name for an open job. When you apply, the system usually matches you to an existing person by email address, then attaches a new application to that record. Apply three times with one login and the usual result is one profile with three rows under it, each showing the job, the date and the current stage.
So a recruiter who opens your profile for the marketing analyst role tends to see, at a glance, that you also applied for the CRM specialist role on Tuesday and the office manager role on Wednesday. Some employers configure their system so that recruiters only see their own requisitions, and a few hide past activity for privacy reasons. I would not plan around that. Assume the full list is visible.
The general layout of that screen, with its notes, tags and stage history, is covered in our piece on what recruiters see inside a candidate record. This article is about one row of it multiplying. And if you ended up with two separate records because you used two email addresses, that is a different problem with its own fix.
What the list says about you
A list of applications is read as a statement of intent, whether you meant it as one or not.
Neighbouring roles read as focus. Data analyst, senior data analyst and business intelligence analyst in one department tell a simple story: this person wants this kind of work here and is flexible about the exact seat. Recruiters often like that, because it gives them room to place you. Two levels of one job family work too, as long as your experience plausibly fits both.
Scattered roles read as not knowing what you want. Financial analyst, sales team lead and office manager in one week tell a different story. The recruiter has no idea which one you would accept, which one you are good at, or whether you read any of the postings. It also raises a practical doubt: if hired into one, would you be asking to move out within months?
There is a middle case, and it is the common one. Two roles in different functions that share a real thread, say customer support lead and customer success manager, can look coherent if your CV makes the thread obvious. The list alone will not explain it. Your documents have to.
The recruiter does not judge the count first. They judge whether the applications could all belong to one career.
Several recruiters, one set of notes
In a larger employer each requisition usually has its own recruiter and its own hiring manager. Your three applications may land on three desks. That sounds like three independent chances, and partly it is.
But the record is shared. In many systems a note left by one recruiter ("strong on SQL, vague on why us") is visible to the next one who opens your profile, and so are interview feedback forms if the employer keeps them at candidate level. Recruiters in one team also talk. "Are you looking at this person too?" is a normal message between colleagues, and the usual outcome is that one of them takes the lead while the others wait.
So be consistent across conversations. If you tell one recruiter that the analyst role is your clear first choice and tell another the same thing about the operations role, assume both statements will meet. It is fine to be interested in two roles. Say so to both recruiters, in the same words, and say which one you would pick if offered both.
Salary expectations follow the same logic. Different roles can justify different figures, but a wide gap with no explanation looks careless when both numbers sit in one record.
A rejection on one role does not always touch the others
Candidates often assume that one "no" closes the whole file. Usually it does not. In most systems a rejection is recorded against the application, not against the person, so the other applications keep their own status and move at their own pace. You can receive a rejection email for one role on Monday and an interview invitation for another on Thursday. Nobody made a mistake.
Two caveats. Some rejection reasons do travel: if a recruiter marks you as lacking a work permit or a required certification, a colleague reading the record will draw the obvious conclusion for their own role. And some employers close every open application in bulk when one process ends, by policy or by habit. If a role you cared about goes quiet right after a rejection elsewhere at that employer, a short polite question to the recruiter is reasonable.
The reverse also happens. When you reach a late stage for one role, the other applications are often paused or closed so that two teams are not competing for you. That is a good sign, not a penalty.
One CV for all of them, or one per application
Each application normally keeps the documents that came with it. So a recruiter may be able to open the CV you sent for role A and the CV you sent for role B, one after the other. Some systems instead overwrite the profile CV with the latest upload, which means the version written for the third role is the one everyone reads. From the outside you cannot tell which setup you are dealing with.
That uncertainty settles the question. Tailor, but keep the facts fixed. Across versions, these must match exactly:
- job titles, employers and dates
- degrees and certifications
- the figures you quote for results
What can change is emphasis: the summary at the top, the order of the bullets, which projects get three lines and which get one. A recruiter comparing two versions should think "same person, different angle". If the title of your current job differs between the two, they think something else.
For neighbouring roles, one well-built CV is often enough and avoids the comparison entirely. For roles in different functions, a version per application is worth the effort. If your history lives on LinkedIn, a tool like Postulit can produce a tailored CV for each application from that one profile, which keeps the dates and titles identical while the emphasis moves.
Caps, and asking instead of applying again
How many is too many? There is no universal figure. Some employers publish a maximum per candidate over a set period, and some enforce it in the system by blocking the next submission. Others have no rule at all. Look in three places before you guess: the FAQ on the careers site, the text of the application form itself, and the confirmation email, which sometimes states the policy. If nothing is written down, two or three closely related roles is a defensible range. Past that, you are asking the recruiter to do your sorting for you.
Often the better move is not a new application at all. If you are already in contact with a recruiter for one role and a sibling role appears, write to them:
"I saw the opening for the pricing analyst role in the same team. The revenue analyst role is still my first choice, but I would be glad to be considered for both. Should I apply separately, or can you add me?"
Many recruiters can attach an existing candidate to another requisition in a few clicks, and a candidate passed along by a colleague usually gets a closer look than a cold entry in the queue. You also show that you understand how their process works, which a third silent application does not.
Before you apply to a second role at one employer, write down the single sentence that explains why both make sense for you. If you can write it, apply, keep the facts in both CVs identical, and tell each recruiter about the other application. If you cannot, pick the role you would actually accept and put the saved effort into that one.