Have you worked here before, and why they ask

The short answer

It is a rehire and records check, not a test of memory or an invitation to explain a complicated history. Answer honestly, including any time you spent there as a contractor or an intern, since those often count even though people forget to mention them. Most of the time a truthful yes costs you nothing at all.

What the question is actually checking

Companies keep records, and this question exists to connect a new application to any record that might already exist. That matters for a few practical reasons: some companies have formal rehire eligibility rules tied to how a previous employment ended, some just want to avoid creating a duplicate employee record in an HR system that already has one, and some are simply routing your application to a manager who might already know you. This question exists in some form at nearly every company with more than a handful of employees, because the alternative, having no way to check, creates real operational problems: duplicate benefits enrollments, confusion over tenure-based eligibility, or a rehire walking back into a role a formal policy was written specifically to prevent. None of that is about testing your honesty for its own sake. It is closer to reconciling two records than interrogating your past.

The part almost everyone forgets

The most common mistake is answering no too quickly because the question sounds like it means "were you a full-time employee," and a summer internship or a short-term contract role does not feel like it counts. On most forms, it does. If you did any paid work for that company under any arrangement, a contract, a fellowship, an internship, a temporary role through an agency, the honest answer to this question is yes, and it is worth pausing to actually think back rather than answering on reflex.

Why contract and agency roles count too

The confusion is not limited to internships. A lot of contract work happens through a staffing agency or a consulting firm, which means the company you actually worked inside of, day to day, is not the same as the company that technically employed you or paid you. From the hiring form's perspective, what matters is whether you worked at that company, not who signed your paycheck. If you spent six months embedded on a team at the company that is now asking, through whatever arrangement got you there, the honest answer is yes, even if your offer letter at the time came from a different name entirely.

If the honest answer is yes and it is complicated

Sometimes a previous stint did not end cleanly, or the circumstances are not something you want to relive on an application form. The field itself is not asking for that story, only for the fact. Answer yes if it is true, and let any explanation happen later, in a conversation with an actual person, if it comes up at all. Most of the time it will not, because most returns to a former employer are entirely unremarkable from the company's side: a former intern applying for a full-time role, someone who left on good terms coming back a few years later, a contractor converting to full-time. The question exists to catch these ordinary cases, not to flag every one of them as a problem.

What a yes actually triggers

In practice, a yes usually triggers nothing more dramatic than someone checking an internal record, confirming dates and role, and moving on. Some companies use it to loop in your previous manager for an informal reference, which, if that previous stint went well, works in your favor rather than against it. A minority of situations involve a formal rehire policy, sometimes tied to a waiting period, sometimes tied to how the prior role ended, and those cases would surface regardless of how you answer this specific field, since the record already exists. Answering no does not make the record disappear. It just adds an inconsistency on top of whatever the record already shows.

Why this matters less than it feels like it should

Of the seven recurring screener questions covered in the seven screener questions you keep answering, this is one of the lowest-stakes to answer honestly. It is a records question, not a character judgment, and a truthful answer, whatever it is, gives the company exactly the information the field was built to collect. Overthinking it tends to cost more time than the question itself deserves, especially compared with questions like work authorization or sponsorship, where an inaccurate answer creates real problems later on.

Consider how ordinary a yes actually is in practice. Former interns reapplying for full-time roles, contractors converting after their assignment ends, employees who left for a different opportunity and later come back, these are not edge cases a company built its hiring process around avoiding. In most organizations, a returning face is a known quantity, which can just as easily work in your favor as against it, since a hiring manager already has more information about how you actually perform than they would have about a completely new applicant.

If your situation is more complicated than the field allows

If part of what is complicating your answer is that you are currently employed somewhere else and weighing whether to reconnect with a past employer without your current one finding out, that broader challenge, running a search quietly while still employed, is covered in job searching while still employed. The prior employment field itself does not need to know any of that context. It only needs an honest yes or no. Either way, the field only needs the fact. Save the story, if there is one, for a conversation with an actual person, on your terms, not a text box that was never built to hold it.

For the rest of what a typical application form asks alongside this question, see what ATS application forms actually ask for.

iapplyai.app keeps a record of your real employment history, internships and contract work included, so this question gets the same accurate answer every time it comes up, worded however the next form happens to ask it.