You don't know what you don't know.

Nobody teaches this in school.

Nobody tells you that the resume format matters as much as the content.

You assumed if you had the right experience, the right skills, the right education, you'd get a callback.

You didn't realize a robot reads your resume first.

And that robot doesn't care how nice your resume looks.

It cares whether it can actually read the text at all.

The problem: Most people format resumes to look good to human eyes, not knowing a machine reads it first. Here's exactly how to format your resume so ATS software can actually process it correctly.

Here's how to format your resume to be ATS-friendly, step by step:

STEP 1: Choose the right file format

Use: .docx (Word document) or .pdf

How to decide between them:

• If job posting doesn't specify: .docx is generally the safest choice since some older ATS systems parse Word documents more reliably than PDFs
• If posting specifically requests PDF: Use PDF, but make sure it's text-based, not an image

How to verify your PDF is text-based:

Open it and try to click-and-drag to select text.

If you can highlight individual words, it's fine.

If you can only select the whole page as one image block, it won't work. Recreate it in Word and export properly.

Never use: .pages, .odt, or other uncommon formats unless specifically requested.

STEP 2: Structure your document in a single column

What to do:

Write everything top to bottom, left to right, in one continuous column.

No side-by-side sections. No sidebar with skills while experience runs down the main area.

Why:

ATS reads in a linear pattern. Multiple columns often get read out of order or merged together incorrectly, scrambling your information.

Simple test:

If you could print your resume and read it in a straight line from top-left to bottom-right without jumping around, it's properly structured.

STEP 3: Put your name and contact info in the main body, not the header

What to do:

Type your name, phone number, email, LinkedIn URL, and location as the very first lines of the actual document body.

Do not use Word's "Header" feature (the area that repeats at the top of every page).

Why:

Many ATS systems skip headers and footers entirely, treating them as non-content decoration. If your contact information only exists there, the system might import your resume with a blank name field.

Format example:

John Smith
(555) 123-4567 | [email protected] | linkedin.com/in/johnsmith | Chicago, IL

Plain text, centered or left-aligned, right at the top of the body.

STEP 4: Use standard section headers

What to do:

Label your sections with conventional, expected terms:

• Summary
• Experience (or Work Experience)
• Education
• Skills
• Certifications

Why:

ATS systems are often programmed to look for these specific standard terms to correctly categorize your information. Creative alternatives like "My Journey" or "What I Bring to the Table" may not get recognized as the section they represent.

Format tip:

Make headers bold and slightly larger than body text, but keep them as normal text, not stylized graphics or text boxes.

STEP 5: Format your work experience consistently

What to do:

For each job, use this consistent structure:

Job Title
Company Name | Month Year - Month Year
- Accomplishment-focused bullet point
- Accomplishment-focused bullet point
- Accomplishment-focused bullet point

Why consistency matters:

If every job entry follows the identical pattern, the ATS can reliably extract job titles, company names, and dates across your entire work history without confusion.

Date format specifically:

Pick one format and use it everywhere: "January 2020 - March 2023" or "01/2020 - 03/2023"

Don't mix formats between different jobs on the same resume.

STEP 6: Create a distinct, clearly labeled Skills section

What to do:

Under a header labeled "Skills," list your relevant hard skills as plain text, separated by commas or in a simple bulleted list.

Skills
Microsoft Excel, SQL, Python, Salesforce, Project Management, Data Analysis, Google Analytics

Why:

Many ATS systems specifically scan for a dedicated skills section to quickly match against job posting requirements. If your skills are only mentioned within job description paragraphs, the system might not extract them as clearly.

Include both versions of terms when relevant:

"Search Engine Optimization (SEO)" covers you whether the system searches for the abbreviation or full term.

STEP 7: Use simple, standard bullet points

What to do:

Use the standard round bullet (•) available in Word's bullet list feature.

Avoid:

Arrows (→), stars (★), checkmarks (✓), or custom symbols as bullets.

Why:

Standard bullets convert reliably across systems. Special characters sometimes render as strange symbols, question marks, or blank spaces when the ATS processes them.

Keep bullet structure simple:

One level of bullets under each job. Don't create sub-bullets or nested indentation levels, as this can confuse parsing logic.

STEP 8: Choose a standard, readable font

Use one of these:

• Arial
• Calibri
• Times New Roman
• Georgia
• Helvetica

Font size:

10-12pt for body text, 14-16pt for your name/headers.

Avoid:

Script fonts, decorative fonts, or anything unusual you downloaded for style. These can cause character encoding issues when the ATS converts your document to plain text internally.

STEP 9: Avoid all graphics, images, icons, and charts

What to remove:

• Skill level bars or graphics
• Profile photos
• Icons next to section headers
• Logos or decorative design elements
• Charts or infographics representing any information

Why:

ATS cannot read images. Any information conveyed only visually is completely invisible to the system, even if it looks impressive to a human viewer.

If you want to show skill proficiency:

Write it as plain text: "Excel (Advanced)" or "Spanish (Conversational)"

STEP 10: Skip tables and text boxes entirely

What to avoid:

Using Word's "Insert Table" feature to organize information.

Using "Insert Text Box" for any content, including sidebars or callout sections.

Why:

These elements are often treated as separate objects rather than part of the main text flow. Many systems either skip them completely or read their content in an unpredictable order relative to the rest of your resume.

Instead:

Use simple paragraph formatting and standard bullet lists for everything.

STEP 11: Format your Education section simply

What to do:

Education

Bachelor of Science in Marketing
University Name | Graduation Year

Keep it simple:

Degree, field of study, school name, graduation year (or expected graduation year).

Optional additions (if relevant):

GPA (if strong and recent graduate), relevant coursework, honors.

Avoid:

Elaborate formatting, graphics representing your GPA, or unusual layouts for this section.

STEP 12: Include a Certifications section if applicable

What to do:

Certifications

PMP (Project Management Professional) | 2022
Google Analytics Certified | 2023

Why this helps:

If job posting requires specific certifications, having them clearly labeled in their own section makes them easy for the system to identify and match.

STEP 13: Name your file professionally

What to do:

Save your file as: "FirstName_LastName_Resume.pdf" or "FirstName_LastName_Resume.docx"

Avoid:

"Resume.pdf," "MyResumeFinal2.docx," or "Untitled document.pdf"

Why:

While this doesn't affect ATS parsing directly in most cases, it creates a poor impression for the human reviewer who eventually sees your file, and helps you stay organized when submitting to multiple companies.

STEP 14: Keep margins standard

What to do:

Use standard margins: 0.5 to 1 inch on all sides.

Avoid:

Extremely narrow margins to fit more content, or unusually wide margins that create excessive white space.

Why:

Standard margins ensure consistent conversion when the document gets processed by different systems.

STEP 15: Test your finished resume before submitting

Method 1: Plain text test

Copy your entire resume text. Paste it into Notepad (Windows) or TextEdit in plain text mode (Mac).

Read through it. Does it look organized? Can you clearly identify each section? Or is it jumbled and confusing?

Method 2: PDF text selection test

If using PDF, try clicking and dragging to select text throughout the document.

Can you highlight individual words everywhere? If yes, you're good. If some sections won't select, there's a formatting issue there.

Method 3: Use a free or paid ATS checker

Tools like Jobscan can upload your resume alongside a job posting and show you exactly how well it parses, plus specific formatting warnings.

COMPLETE ATS-SAFE RESUME TEMPLATE:

[Your Name]
[Phone] | [Email] | [LinkedIn URL] | [City, State]

Summary
[2-3 sentence paragraph summarizing your experience and value]

Skills
[Skill 1], [Skill 2], [Skill 3], [Skill 4], [Skill 5], [Skill 6]

Experience

[Job Title]
[Company Name] | [Month Year] - [Month Year]
- [Accomplishment with metric/result]
- [Accomplishment with metric/result]
- [Accomplishment with metric/result]

[Job Title]
[Company Name] | [Month Year] - [Month Year]
- [Accomplishment with metric/result]
- [Accomplishment with metric/result]

Education

[Degree]
[School Name] | [Year]

Certifications
[Certification Name] | [Year]

WHAT THIS TEMPLATE LOOKS LIKE COMPLETED:

Sarah Johnson
(555) 987-6543 | [email protected] | linkedin.com/in/sarahjohnson | Austin, TX

Summary
Marketing professional with 5 years of experience in digital campaign management and content strategy. Proven track record of increasing engagement metrics and driving revenue growth through data-informed marketing initiatives.

Skills
Google Analytics, SEO (Search Engine Optimization), Content Strategy, Salesforce, HubSpot, Social Media Marketing, A/B Testing, Adobe Creative Suite

Experience

Marketing Manager
Bright Solutions Inc. | March 2021 - Present
- Increased email campaign engagement by 35% through segmented targeting strategy
- Managed $200K annual digital advertising budget across Google Ads and social platforms
- Led cross-functional team of 4 to launch product rebrand, resulting in 20% increase in brand recognition

Marketing Coordinator
Clearview Marketing | June 2019 - March 2021
- Developed content calendar resulting in 40% increase in organic website traffic
- Coordinated social media strategy across 4 platforms, growing follower base by 15,000

Education

Bachelor of Arts in Communications
University of Texas at Austin | 2019

Certifications
Google Analytics Certified | 2023
HubSpot Content Marketing Certification | 2022

Notice:

• Single column throughout
• Standard section headers
• Consistent date formatting
• Plain bullet points
• No graphics, tables, or text boxes
• Skills clearly separated
• Contact info in main body

This resume would parse cleanly through virtually any ATS system.

COMMON QUESTION: "Won't this look boring?"

Yes, somewhat.

But this version is for the ATS-scanned application process specifically.

Once you're past that stage:

• Your LinkedIn profile can have more visual personality
• A portfolio website can show creative design skills
• If networking directly with a hiring manager who requests your resume via email (bypassing ATS entirely), you could send a more visually designed version

For the actual online application through a company portal or job board: Always prioritize this clean, ATS-safe format first.

BOTTOM LINE:

ATS-friendly formatting isn't about making your resume worse.

It's about making sure the system can actually read what you've written before a human ever gets the chance to be impressed by it.

The 15-step checklist:

1. Right file format (.docx or text-based PDF)
2. Single column layout
3. Contact info in body, not header
4. Standard section headers
5. Consistent experience formatting
6. Clear, distinct skills section
7. Simple standard bullet points
8. Standard fonts
9. No graphics or images
10. No tables or text boxes
11. Simple education formatting
12. Clear certifications section
13. Professional file naming
14. Standard margins
15. Test before submitting

Follow this structure, and your resume will actually reach human eyes.

Then your qualifications can speak for themselves.

Have you tested your current resume format? Try the plain text test right now and see what comes through.

For more honest resume and job search strategy:
Connect with Job Seekers Guide on LinkedIn

You wrote a beautiful resume.

Nice columns. Modern font. A little graphic showing your skill levels.

It looks professional in Word.

But when the ATS tried to read it, half your information turned into gibberish.

Your name ended up in the wrong field.

Your last three jobs got merged into one blob of text.

Your skills section got skipped entirely.

The system couldn't parse your information.

So it scored you low.

Or worse, it scored you as having no relevant experience at all, even though you clearly do.

The problem: Most rejected resumes aren't rejected because of qualifications. They're rejected because of technical formatting mistakes that prevent the ATS from reading them correctly in the first place.

Here are the ATS mistakes most job seekers make:

MISTAKE 1: Using tables or columns for layout

What this looks like:

Two-column resume with skills on the left, experience on the right.

Or a table format for your work history.

Why it breaks ATS:

Most ATS systems read left to right, top to bottom, in a single stream.

When you use columns, the system often reads across both columns simultaneously, jumbling your job titles with unrelated skills or dates from the other column.

Real example:

Your resume shows:

Left column: "Python, SQL, Excel"
Right column: "Marketing Manager, 2020-2023"

ATS might read this as: "Python SQL Excel Marketing Manager 2020-2023" as one confused string, or skip sections entirely.

Fix:

Use single-column, linear format. Boring, but functional. Save the creative column layout for a PDF you send directly to a human after you've already gotten the interview.

MISTAKE 2: Putting critical information in headers or footers

What this looks like:

Your name and contact info in the document header.

Your page numbers or "References available upon request" in the footer.

Why it breaks ATS:

Many ATS systems don't scan headers and footers at all. They're treated as decorative, not content.

Real example:

If your name and phone number are only in the header, the ATS might import your resume with a blank name field. Recruiters searching their database by name will never find you.

Fix:

Put your name, contact information, and any critical details in the main body of the document, not in header/footer sections.

MISTAKE 3: Using text boxes for any content

What this looks like:

A stylish text box highlighting your "Core Skills" or a sidebar summary.

Why it breaks ATS:

Text boxes are often treated as separate objects, not part of the main text flow. Many systems skip them entirely or read them in a completely different order than intended.

Real example:

Your entire "Summary" section is in a text box at the top. ATS parses your work experience first because it never registers the text box content at all.

Fix:

Avoid text boxes entirely. Use standard paragraph and bullet formatting within the normal document flow.

MISTAKE 4: Non-standard section headers

What this looks like:

"My Journey" instead of "Experience"

"What I Bring" instead of "Skills"

"The Good Stuff" instead of "Qualifications"

Why it breaks ATS:

ATS systems are often programmed to look for standard section headers to categorize your information correctly.

Real example:

If your work history is under "My Professional Journey" instead of "Experience" or "Work History," some systems may fail to recognize it as your employment section at all, potentially leaving that entire section unparsed.

Fix:

Use standard, expected headers: "Experience," "Education," "Skills," "Summary," "Certifications." Creative header names might look nice to humans but confuse machines.

MISTAKE 5: Images, graphics, or icons representing information

What this looks like:

A skill bar graphic showing "Excel: 90%"

A small icon next to each job title

A photo or logo integrated into the design

Why it breaks ATS:

ATS cannot read images. Any information conveyed only through graphics is completely invisible to the system.

Real example:

You have a nice visual chart showing proficiency levels for 8 different software programs. ATS sees zero skills listed because none of that information exists as actual text.

Fix:

Represent everything in plain text. If you want to show proficiency levels, write it out: "Excel (Advanced), Photoshop (Intermediate)."

MISTAKE 6: Unusual or decorative fonts

What this looks like:

Fancy script fonts for your name.

Unusual sans-serif fonts you found online.

Why it breaks ATS:

Some fonts don't convert properly to the plain text format ATS systems use internally. Certain character encodings can become garbled or unreadable.

Real example:

A stylized font renders your job title as strange symbols or missing letters in the ATS system's backend, even though it looks fine in your PDF viewer.

Fix:

Stick to standard fonts: Arial, Calibri, Times New Roman, Georgia, Helvetica. Boring but reliable.

MISTAKE 7: Saving as an image-based PDF instead of text-based PDF

What this looks like:

You designed your resume in Canva or a similar visual tool and exported it as PDF.

Why it breaks ATS:

Some design tools export PDFs as essentially "pictures" of text rather than actual selectable, readable text. ATS can't extract any information from an image-based PDF.

Real example:

Your beautifully designed Canva resume looks perfect visually, but when the ATS tries to parse it, it finds zero readable text content at all.

How to check:

Open your PDF and try to select/highlight text with your cursor. If you can't select individual words and copy them, it's likely image-based and ATS can't read it.

Fix:

Create resumes in Word or Google Docs, then export to PDF. This typically preserves actual selectable text rather than converting to image format.

MISTAKE 8: Inconsistent date formatting

What this looks like:

"Jan 2020 - Present" for one job

"01/2021-03/2022" for another

"2019-2020" for a third

Why it breaks ATS:

Inconsistent formatting can confuse the system's ability to calculate your total years of experience accurately, potentially causing it to underestimate your background.

Real example:

If the system can't clearly parse your employment dates, it might calculate you have 2 years of experience when you actually have 6, causing you to be filtered out for requiring "5+ years."

Fix:

Pick one consistent date format throughout: "Month Year - Month Year" (e.g., "January 2020 - March 2023") and use it everywhere.

MISTAKE 9: Using abbreviations without full terms anywhere

What this looks like:

Only writing "PM" instead of ever spelling out "Project Manager."

Only writing "CX" instead of "Customer Experience."

Why it breaks ATS:

If the job posting searches for "Project Manager" but your resume only says "PM," the exact match might not register depending on how sophisticated that particular ATS is.

Fix:

Include both versions somewhere: "Project Manager (PM)" ensures you're covered regardless of which term the system searches for.

MISTAKE 10: Special characters and symbols

What this looks like:

Using ★ or ✓ or → as bullet points instead of standard bullets.

Using em-dashes or unusual punctuation excessively.

Why it breaks ATS:

Some special characters don't convert properly and can appear as strange symbols, question marks, or blank spaces in the parsed version.

Fix:

Use standard bullet points (•) and basic punctuation. Save creative symbols for your personal website or portfolio.

MISTAKE 11: Submitting resume as .pages or unusual file format

What this looks like:

Uploading a Mac Pages file (.pages) or unusual format instead of standard .docx or .pdf.

Why it breaks ATS:

Many systems simply cannot process uncommon file formats, resulting in immediate rejection or complete failure to parse anything at all.

Fix:

Always save and submit as .docx or .pdf unless the application specifically requests something different.

MISTAKE 12: Contact information formatted unusually

What this looks like:

Phone number formatted as "call me at five five five, one two three, four five six seven"

Email address as an image or unusual format

Why it breaks ATS:

Systems expect standard formatting for contact fields: (555) 123-4567 or 555-123-4567 for phone, standard email format for email.

Fix:

Use conventional formatting: Standard phone number format, standard email address, straightforward text.

MISTAKE 13: File name that's unprofessional or generic

What this looks like:

"Resume.pdf" or "MyResumeFinal2.docx" or "Untitled document.pdf"

Why it matters:

While this doesn't break the ATS parsing itself, it can create a poor impression when a human eventually reviews your file, and some systems use file names in their organizational categorization.

Fix:

Name your file: "FirstName_LastName_Resume.pdf" for clarity and professionalism.

MISTAKE 14: Not including a skills section as a distinct, clearly labeled area

What this looks like:

Weaving all your skills only into job description bullets, without any standalone "Skills" section.

Why it matters:

Many ATS systems specifically look for a clearly labeled skills section to quickly extract and match against job requirements. Without this, the system may miss skills that are only mentioned in context within your job descriptions.

Fix:

Always include a distinct "Skills" section listing relevant hard skills, even if you also mention them contextually elsewhere.

MISTAKE 15: Overly complex, multi-level formatting

What this looks like:

Nested bullet points with sub-bullets under sub-bullets.

Multiple different indentation levels throughout.

Why it breaks ATS:

Complex nested structures can confuse the parsing logic, sometimes causing entire sections to be misread or skipped.

Fix:

Keep bullet structure simple: One level of bullets under each job, no complex nesting.

HOW TO TEST YOUR RESUME FOR ATS COMPATIBILITY:

Method 1: Plain text conversion test

Copy your entire resume text.

Paste into Notepad (Windows) or TextEdit in plain text mode (Mac).

What to look for:

Does it look organized and readable? Or is it a jumbled mess with missing sections, merged text, or strange gaps?

If it looks bad in plain text, it will likely look bad to an ATS too.

Method 2: PDF text selection test

Open your PDF resume.

Try clicking and dragging to select text.

What to look for:

Can you select and highlight individual words? If yes, it's a proper text-based PDF. If you can only select the entire image as one block, it's image-based and unreadable by ATS.

Method 3: Use Jobscan or similar ATS testing tool

Upload your resume alongside a job posting.

What to look for:

Beyond keyword matching, these tools often flag formatting issues specifically, like "tables detected" or "headers/footers contain critical information."

THE SIMPLE ATS-SAFE TEMPLATE STRUCTURE:

Name
Phone | Email | LinkedIn URL | City, State

Summary
[2-3 sentences, plain paragraph format]

Skills
Skill 1, Skill 2, Skill 3, Skill 4, Skill 5, Skill 6

Experience

Job Title
Company Name | Month Year - Month Year

• Bullet point describing accomplishment
• Bullet point describing accomplishment
• Bullet point describing accomplishment

Job Title
Company Name | Month Year - Month Year

• Bullet point describing accomplishment
• Bullet point describing accomplishment

Education

Degree
School Name | Year

Certifications (if applicable)
Certification Name | Year

This structure is boring visually.

But it works reliably across virtually every ATS system.

THE BALANCE: ATS-FRIENDLY VS VISUALLY APPEALING

Common concern:

"If I make it this plain, won't it look boring to actual humans?"

The reality:

Once your resume passes the ATS and reaches human eyes, clean and simple formatting is still generally preferred over cluttered, graphic-heavy designs.

The strategy:

Save visual creativity for:

• Your LinkedIn profile (humans view this directly)
• A portfolio website
• A designed PDF version you send AFTER getting a human contact, when appropriate

For the actual ATS-submitted resume: Prioritize function over form.

REAL EXAMPLE: BEFORE AND AFTER

BEFORE (Fails ATS):

• Two-column layout with skills sidebar
• Name and contact info in header
• Skill proficiency shown as colored bar graphics
• Fancy script font for section headers
• Saved as image-based PDF from design tool

Result: ATS parses as nearly empty document. Candidate never sees human eyes despite strong qualifications.

AFTER (ATS-Optimized):

• Single column, linear format
• Contact info in main body, not header
• Skills listed as plain text
• Standard Calibri font throughout
• Saved as proper text-based PDF from Word

Result: ATS successfully parses all sections, matches relevant keywords, candidate moves forward to human review.

Same qualifications. Same experience. Different technical execution. Completely different outcome.

BOTTOM LINE:

Getting rejected doesn't always mean you're unqualified.

Sometimes it means the system never actually read your information correctly in the first place.

The fix isn't about being less impressive. It's about being technically readable.

Priority checklist:

✓ Single column layout

✓ No headers/footers for critical info

✓ No text boxes

✓ Standard section headers

✓ No images/graphics for information

✓ Standard fonts

✓ Text-based PDF (not image-based)

✓ Consistent date formatting

✓ Both abbreviations and full terms included

✓ Standard bullet points and punctuation

✓ Proper file format (.docx or .pdf)

✓ Clear, distinct skills section

✓ Simple bullet structure, no complex nesting

Fix these technical issues first. Then focus on keyword optimization and content strength.

Both matter. But if the system can't read your resume at all, perfect keywords won't save you.

Have you tested your resume for ATS compatibility? Try the plain text test today and see what you find.

For more honest resume and job search strategy:
Connect with Job Seekers Guide on LinkedIn

You've heard stories.

People spending 20 hours on a "take-home test" and never hearing back.

People finding their exact idea implemented at the company months later.

But you've also heard: This is just how hiring works now. Everyone does assessments.

So which is it?

Is this assignment reasonable?

Or are you about to hand over free labor to a company that was never going to hire you?

You stare at the document.

You don't know how to tell the difference.

The problem: Take-home assignments have become standard in hiring. But there's a real line between a fair skills assessment and exploitation. Most people don't know how to tell which side of that line they're on.

Here's how to tell if an assignment is reasonable or exploitative:

THE CORE QUESTION TO ASK YOURSELF

Reasonable assignment: Tests whether you CAN do the job.

Exploitative assignment: Actually DOES the job, for free, using real company problems.

Everything else builds off this distinction.

FACTOR 1: Time required

Reasonable:

1-3 hours total.

Respects that you have a life, current job, other applications.

Exploitative:

5+ hours, sometimes 10-20 hours.

Framed as "shouldn't take too long" but realistically requires a full day or more.

How to check:

Time yourself doing a similar task normally. If assignment would realistically take you 6+ hours to do well, that's a red flag regardless of what they claim it "should" take.

FACTOR 2: Whether it uses real company problems or hypothetical scenarios

Reasonable:

"Here's a sample dataset, analyze it and show your approach."

"Design a mockup for a fictional app called TaskFlow."

Generic, reusable scenario not tied to their actual business.

Exploitative:

"Here's our actual Q3 marketing data. Build us a real campaign strategy."

"Here's our current codebase. Fix this actual bug in our actual product."

Uses real business problems that provide genuine value regardless of hiring outcome.

How to check:

Ask yourself: "If I completed this perfectly, would the company benefit from this work even if they never hired me?" If yes, that's exploitative by design.

FACTOR 3: Whether the assignment resembles something you'd typically be paid for

Reasonable:

A coding challenge similar to what you'd solve as practice, not client-facing work product.

Exploitative:

A full marketing plan, a complete design system, a finished piece of client-ready work.

How to check:

Would a freelancer normally charge money for this exact deliverable? If yes, you're being asked to provide paid-level work for free.

FACTOR 4: How many companies typically ask for this level of assignment

Reasonable:

Most companies in your field ask for similar-scope assessments (this varies significantly by industry).

Exploitative:

This company's ask is dramatically more extensive than typical practice for this type of role.

How to check:

Search: "[Role type] interview assignment normal length" or ask in relevant professional communities/subreddits what's typical.

FACTOR 5: Whether they offer any compensation for extensive work

Reasonable:

For longer assignments (rare, but sometimes legitimate for senior/specialized roles), some companies offer a stipend.

Exploitative:

Extensive work requested with zero compensation offered or considered, especially when clearly beyond reasonable assessment scope.

How to check:

If assignment genuinely requires significant time (4+ hours), it's reasonable to ask: "Given the scope of this project, is there compensation available, or can we discuss reducing scope to a more representative sample?"

FACTOR 6: What happens to your work afterward

Reasonable:

Companies with ethical practices will tell you your work won't be used regardless of outcome, or they'll ask permission if they want to reference anything.

Exploitative:

No clarity on this. Or worse: you later discover your solution or similar concepts implemented in their actual product/strategy.

How to check:

Directly ask: "Will this work be used by the company in any capacity regardless of the hiring decision?" Their answer (or discomfort answering) tells you a lot.

FACTOR 7: Where you are in the process when asked

Reasonable:

Assignment comes after initial screening, when you're both seriously considering fit, usually mid-process.

Exploitative:

Assignment required immediately upon application, before any human conversation has even happened, functioning as a filter for a pool of desperate applicants providing free work.

How to check:

If you're asked to complete extensive work before having spoken to a single human at the company, that's a significant red flag about the process design.

FACTOR 8: How specific the deliverable is to their exact business

Reasonable:

"Design a login flow for a generic e-commerce app."

Exploitative:

"Design a login flow specifically for our actual product, incorporating our actual brand guidelines and user research."

How to check:

Genuinely generic assignments can be reused for any candidate; company-specific assignments only benefit that one company directly.

REAL EXAMPLES: REASONABLE VS EXPLOITATIVE

REASONABLE EXAMPLE 1 (Software Engineering):

"Complete this coding challenge on HackerRank: implement a function that reverses a linked list. Should take about 45 minutes."

Why it's reasonable:

• Standard practice in industry
• Generic technical skill assessment
• Reasonable time investment
• Doesn't solve any real company problem
• Same challenge given to all candidates

EXPLOITATIVE EXAMPLE 1 (Software Engineering):

"Here's access to our staging environment. Please fix these three actual bugs in our production codebase and submit a pull request."

Why it's exploitative:

• Uses real company code
• Actual bug fixes have real business value
• Significant time investment likely required
• Company benefits directly from your solution
• Provides free technical labor

REASONABLE EXAMPLE 2 (Marketing):

"Here's a fictional product launch scenario. Walk us through how you'd approach the first 30 days of marketing strategy. Keep it to a 1-page outline."

Why it's reasonable:

• Hypothetical scenario, not their real product
• Limited scope (1 page)
• Tests strategic thinking process
• Reusable for any candidate

EXPLOITATIVE EXAMPLE 2 (Marketing):

"We're launching our new product line next quarter. Please create a comprehensive 90-day marketing strategy including channel mix, budget allocation, and content calendar."

Why it's exploitative:

• Uses their actual upcoming product launch
• Comprehensive scope requiring significant hours
• Directly usable business asset
• Essentially free strategic consulting

REASONABLE EXAMPLE 3 (Design):

"Redesign this generic mobile banking app screen (we'll provide mockup files) focusing on improving the user flow for account transfers."

Why it's reasonable:

• Generic/fictional app, not their actual product
• Focused, specific task
• Reasonable scope
• Tests design thinking without extracting real value

EXPLOITATIVE EXAMPLE 3 (Design):

"Here's our actual app. Please redesign our onboarding flow, incorporating our brand guidelines, and present it as if pitching to our executive team."

Why it's exploitative:

• Uses actual product and brand assets
• Presentation-ready deliverable
• Significant time investment
• Directly usable by company regardless of hiring outcome

WHAT TO DO WHEN YOU RECEIVE AN ASSIGNMENT:

Step 1: Assess scope honestly

How long will this realistically take you, not their stated estimate?

Step 2: Determine if it's using real company problems

Is this generic/hypothetical, or does it use their actual business, product, or data?

Step 3: Research typical practice for your field

Ask in professional communities: "Is a [X-hour] assignment normal for [role type] interviews?"

Step 4: If reasonable, complete it professionally

Do good work, submit on time, move forward with the process.

Step 5: If borderline, ask clarifying questions

"I want to make sure I'm scoping this appropriately. Approximately how many hours should I budget for this?"

"Will this work be used by the company in any way regardless of the hiring outcome?"

Step 6: If clearly exploitative, you have options:

Option A: Decline respectfully

"I appreciate the opportunity, but this assignment appears to require significant unpaid time working on what looks like an actual business problem. I'd be happy to discuss a scoped-down version or a paid trial arrangement instead."

Option B: Negotiate scope

"This is a comprehensive request. Could we reduce scope to a smaller sample that still demonstrates my approach, perhaps limited to [specific smaller piece]?"

Option C: Request compensation

"Given the scope of this project, would the company consider a stipend for the time investment, similar to a paid trial project?"

Option D: Complete a limited version

Do a partial, clearly-labeled "sample approach" rather than a fully comprehensive solution, demonstrating capability without providing the complete deliverable.

INDUSTRY-SPECIFIC NORMS TO KNOW:

Software Engineering:

Reasonable: 1-3 hour coding challenges, algorithm problems, small isolated features.

Red flag: Full feature implementation in their actual codebase, multi-day projects.

Marketing/Content:

Reasonable: Sample campaign concept for hypothetical product, short writing sample.

Red flag: Complete strategy for their actual upcoming launch, extensive content calendar for their real brand.

Design:

Reasonable: Redesign exercise using generic or provided sample app/product.

Red flag: Complete redesign of their actual product ready for stakeholder presentation.

Data Analysis:

Reasonable: Analysis of provided sample dataset (often anonymized or publicly available).

Red flag: Analysis of their actual proprietary business data with real recommendations implemented.

Consulting/Strategy:

Reasonable: Case study analysis of hypothetical or well-known public company scenario.

Red flag: Actual strategic recommendations for their real current business challenges.

THE HONEST TRUTH:

Some level of assessment is genuinely reasonable and standard practice across most industries now.

The line isn't about whether they ask for ANY work sample.

The line is about:

• Scope (hours required)
• Real vs. hypothetical business application
• Whether they benefit regardless of hiring outcome
• Compensation for extensive asks
• Transparency about how work will be used

Trust your instincts, but verify with research.

If something feels like too much, check what's typical in your field before assuming it's just standard practice you should accept without question.

Your time and expertise have value.

Reasonable companies understand this and design assessments that respect it while still gathering the information they genuinely need to make a hiring decision.

Have you been asked to complete an assignment that felt exploitative? What made you realize it crossed the line?

For more honest job search protection and strategy:
Connect with Job Seekers Guide on LinkedIn

You never got the job.

You never got paid.

You gave them a real solution to a real problem.

For free.

They used it.

You're left wondering: Was this ever a real hiring process? Or was this always about getting free consulting work out of desperate candidates?

You feel used.

Because you were.

The problem: Some hiring practices aren't just inefficient or disorganized. They're exploitative by design. Learning to recognize these patterns protects your time, your ideas, and your dignity throughout the process.

Here are the hiring practice red flags that signal exploitation, not just disorganization:

RED FLAG 1: Extensive unpaid "test projects" that solve real business problems

What this looks like:

"Before we move forward, we'd like you to create a full marketing strategy for our Q3 launch" (unpaid, using real company data/problems).

Why it matters:

There's a difference between a reasonable skills assessment (a sample problem, 1-2 hours) and extracting genuine consulting work disguised as an "interview task."

How to spot the difference:

Reasonable: "Here's a hypothetical scenario, walk us through your approach" (1-2 hours max, generic scenario)

Exploitative: "Here's our actual current problem, give us your actual strategy" (4+ hours, real business application)

What to do:

Ask directly: "Will this work be used in any capacity by the company regardless of hiring decision?" If they're cagey about this answer, that's telling.

RED FLAG 2: Multiple rounds of "final" interviews that keep extending

What this looks like:

"This is the final round" - then another round gets added. Then another. Each time framed as "just one more."

Why it matters:

This reveals either genuine indecision at leadership level, or a pattern of using candidates' continued hope and investment to extract more free evaluation time without commitment.

What to do:

After the second time "final round" isn't actually final, ask directly: "Can you give me a clear picture of exactly how many more steps remain in this process?"

RED FLAG 3: Salary negotiation happens only after you've rejected other opportunities

What this looks like:

They know you have competing offers. They ask you to decline those first "to show commitment" before finalizing your offer with them.

Why it matters:

This is a manipulation tactic that removes your leverage entirely before they've committed anything concrete to you.

What to do:

Never decline other opportunities until you have a written, signed offer in hand. This is a firm boundary worth holding regardless of pressure.

RED FLAG 4: Verbal offer followed by mysteriously vanishing communication

What this looks like:

"We're excited to offer you the position!" (verbally, on a call)

Then: Written offer never arrives. Follow-ups go unanswered. Eventually, silence.

Why it matters:

Verbal offers aren't legally binding in most cases. Some organizations use this to test the market, string candidates along, or simply have poor internal follow-through without accountability.

What to do:

Always request written confirmation immediately after any verbal offer: "That's wonderful to hear! Could you send that over in writing so I can review the details?"

RED FLAG 5: Consistently negative or belittling feedback style during interviews

What this looks like:

Interviewers who seem to enjoy making candidates uncomfortable, dismissing answers without explanation, or using aggressive "stress testing" beyond reasonable assessment.

Why it matters:

While some roles genuinely require composure-under-pressure evaluation, there's a difference between assessing this skill appropriately and interviewers simply being unprofessional or enjoying power dynamics.

What to do:

Notice if this behavior seems purposeful (stated as part of assessing a specific skill) versus just generally disrespectful. The latter is a preview of management style if hired.

RED FLAG 6: Requiring extensive personal information before any real assessment of qualifications

What this looks like:

Application requires detailed personal history, family information, or invasive questions before you've even had a substantive conversation about the actual role.

Why it matters:

Legitimate hiring processes assess qualifications first, personal/logistics details later (usually post-offer for background checks).

What to do:

Be cautious of applications requesting excessive personal detail (beyond standard demographic EEOC questions, which are optional) before any real evaluation of your skills has occurred.

RED FLAG 7: Bait-and-switch on job scope during final negotiations

What this looks like:

Throughout interviews: "This role focuses on strategic planning."

Final offer conversation: "Oh, and there will also be significant administrative and operational duties we didn't mention."

Why it matters:

This reveals either poor internal communication about the actual role, or intentional minimization of less desirable aspects until you're emotionally committed.

What to do:

Request a written, detailed job description as part of your offer letter, explicitly outlining responsibilities discussed throughout the process.

RED FLAG 8: Discriminatory patterns in who advances through rounds

What this looks like:

You notice (through LinkedIn research or direct experience) that certain demographics consistently don't advance past initial rounds despite comparable qualifications.

Why it matters:

This is illegal discrimination, not just poor practice. Pattern recognition here matters both for your own protection and broader awareness.

What to do:

Document your experience with dates and details. If you suspect discrimination, resources exist through EEOC (eeoc.gov) for formal complaints.

RED FLAG 9: Reference checks conducted without your knowledge or consent

What this looks like:

You discover (often through a mutual contact) that the company reached out to people at your current employer without your explicit permission, potentially jeopardizing your current job.

Why it matters:

Standard practice requires your consent before checking references, especially current employer contacts, since this could create serious professional risk for you.

What to do:

Always explicitly state: "Please don't contact my current employer without my prior approval" early in the process, in writing if possible.

RED FLAG 10: Pressure to sign restrictive agreements before you've seen full compensation details

What this looks like:

"Please sign this NDA and non-compete agreement" presented before you've received the actual offer letter with salary and benefits.

Why it matters:

You should understand the complete picture of what you're agreeing to work for before signing legal documents that restrict your future options.

What to do:

Request the full offer package first. Legal agreements can be reviewed and signed after you understand complete compensation and role details.

RED FLAG 11: Hiring manager unable to answer basic questions about team structure or reporting lines

What this looks like:

"Who would I report to?" gets a vague or shifting answer throughout the process.

Why it matters:

This often indicates organizational instability, recent restructuring chaos, or that the position itself may be in flux (or may not be as solidified as presented).

What to do:

If basic structural questions can't be answered clearly by the final interview stage, this is worth directly addressing before accepting any offer.

RED FLAG 12: Consistent pattern of "we'll circle back" without follow-through

What this looks like:

Every question you ask about specifics (start date, team dynamics, growth path) gets deferred with "we'll circle back on that" and never actually addressed.

Why it matters:

This pattern, repeated across multiple questions and interactions, often indicates either disorganization at a systemic level or intentional avoidance of specifics that might concern you.

What to do:

Keep a list of unanswered questions. Before final acceptance, insist on getting clear answers to all of them.

RED FLAG 13: Asking you to complete DEI/diversity paperwork disconnected from actual inclusive practices

What this looks like:

Extensive diversity questionnaires and stated commitment to inclusion, but interview panels remain homogeneous and no substantive culture questions get honest answers.

Why it matters:

This can indicate performative rather than genuine commitment to inclusive practices, worth noting as a broader culture signal.

What to do:

Ask direct questions: "Can you tell me about diversity within leadership specifically?" Listen for concrete answers versus deflection.

RED FLAG 14: Excessive scrutiny of employment gaps without allowing context

What this looks like:

Repeated, almost accusatory questioning about any gap in your work history, without genuine interest in the actual circumstances or context.

Why it matters:

This can signal a rigid, judgmental culture that may not accommodate normal life circumstances (health issues, caregiving, layoffs) with appropriate understanding.

What to do:

Notice whether questioning feels like genuine curiosity or judgmental interrogation. The latter often previews how the company handles employee life circumstances generally.

RED FLAG 15: Rescinding offers after acceptance without adequate notice or explanation

What this looks like:

You've accepted, possibly given notice at current job, then receive notification the offer is being withdrawn with minimal explanation or support.

Why it matters:

While this can occasionally happen due to genuine business circumstances (hiring freezes, budget cuts), the manner of communication and support offered reveals company values significantly.

What to do:

If this happens, document everything. Some jurisdictions have legal protections around promissory estoppel if you made significant decisions based on the accepted offer (like quitting your job). Consult an employment attorney if this occurs.

HOW TO PROTECT YOURSELF THROUGHOUT THE PROCESS:

Document everything:

Keep dated notes of conversations, promises made, and commitments discussed.

Get things in writing:

Verbal promises mean little. Request written confirmation of significant commitments.

Set boundaries early:

State clearly what you will and won't do (unpaid extensive work, reference checks without consent, etc.)

Trust patterns over isolated incidents:

One red flag might be circumstantial. Multiple red flags together reveal genuine organizational patterns.

Know your rights:

Understand basic employment law protections in your jurisdiction regarding discrimination, reference checks, and verbal agreements.

Don't be afraid to walk away:

If exploitation patterns emerge clearly, your time and dignity are worth more than uncertain opportunity with a company already showing poor practices.

BOTTOM LINE:

Not every hiring hiccup reveals exploitation. Sometimes it's genuine disorganization or unintentional oversight.

But certain patterns cross the line from "imperfect process" into genuine exploitation:

• Extracting real, unpaid work
• Manipulating your leverage and options
• Bait-and-switch tactics on fundamental details
• Discriminatory patterns
• Violating basic professional courtesy around consent and communication

You deserve a hiring process that respects your time, your work, and your basic dignity throughout.

If a company can't manage that during the process when they're trying to impress you, it reveals significant information about what working there will actually be like.

Have you experienced any of these exploitative hiring patterns? What happened?

For more honest job search protection and strategy:
Connect with Job Seekers Guide on LinkedIn

You check your application history.

Yep. Applied 4 months ago.

Never heard back.

Here it is again.

Exact same posting.

Exact same requirements.

You wonder: Is this actually open? Or is this just... always posted?

You almost apply again anyway.

Because what else are you supposed to do?

But you're starting to notice a pattern across multiple companies.

Postings that never seem to go away.

Postings that feel like they're not really looking for anyone.

The problem: Some job listings aren't fake in the scam sense, but they're not real opportunities either. They're evergreen, decorative, or abandoned. Learning to read the listing itself helps you stop wasting effort on positions that were never actually available.

Here's how to spot red flags in the job listing itself:

RED FLAG 1: The posting has been live for an unusually long time

What this looks like:

Most job boards show "Posted X days ago" or "Posted X months ago."

If it says "Posted 6 months ago" and it's still marked active: Something's off.

Why it matters:

Real openings typically get filled within 30-60 days in most industries.

A posting open for 6+ months usually means one of three things: they already filled it and forgot to remove it, requirements are unrealistic so nobody qualifies, or it's not a real opening at all (job bank building).

How to check:

Look at the "posted date" field on the job board.

If the platform doesn't show this, search the exact job title + company name to see if you can find when it originally appeared online.

RED FLAG 2: The exact same posting reappears repeatedly

What this looks like:

You've seen this identical listing before, disappeared for a while, now it's back with the same text.

Why it matters:

This pattern often indicates one of two things: genuinely high turnover in that specific role (worth investigating why), or the position gets "posted" periodically to maintain a candidate pipeline without any real intent to hire right now.

How to check:

Keep a simple log of jobs you've applied to. If you notice repeats, that's useful information about that specific listing's reliability.

RED FLAG 3: Listing has generic, copy-paste language with no company-specific details

What this looks like:

"We are seeking a motivated individual to join our dynamic team in a fast-paced environment. Responsibilities include various administrative and operational tasks."

No mention of specific tools, specific team, specific projects.

Why it matters:

Real hiring managers write postings based on actual needs. They mention specific software, specific team structure, specific current projects.

Generic template language often signals HR posted this without real input from anyone who actually needs the role filled.

How to check:

Compare this posting to others from the same company. If every single posting uses identical generic language, this is templated, low-effort posting, potentially disconnected from actual hiring intent.

RED FLAG 4: No specific hiring manager or team mentioned anywhere

What this looks like:

Posting never mentions who you'd report to, what team you'd join, or any named contact.

Just "Apply now" with no human attached to the process.

Why it matters:

Real open positions usually have someone internally who requested the hire and is waiting for the right candidate. Complete absence of any human element in the posting can suggest disconnected process or non-urgent (possibly non-existent) need.

How to check:

Look for any mention of team lead, department, or reporting structure. Its absence alone isn't definitive, but combined with other flags, it matters.

RED FLAG 5: Requirements list is either extremely long or contradictory

What this looks like:

15+ required qualifications for an entry-level role.

Or: Requires "5+ years senior leadership experience" but salary listed suggests junior-level pay.

Why it matters:

Extremely long requirement lists often mean the posting was created by combining wishlists from multiple stakeholders, without realistic expectation anyone will meet all criteria. This isn't necessarily a scam, but it may signal the position is aspirational rather than urgent.

How to check:

Count actual "required" (not "preferred") qualifications. More than 8-10 hard requirements for a single role is often unrealistic and suggests the posting isn't grounded in practical hiring needs.

RED FLAG 6: The application process leads to a black hole with no ATS confirmation

What this looks like:

You submit application. No confirmation email. No application ID number. Nothing indicating it was received.

Why it matters:

Legitimate hiring systems (Workday, Greenhouse, Lever, etc.) almost always send automatic confirmation.

Complete silence on receipt, not just silence on progress, can indicate the application isn't actually going anywhere functional.

How to check:

Check spam folder first. If genuinely no confirmation exists anywhere, this is worth noting as a red flag for that specific posting.

RED FLAG 7: Job appears on aggregator sites but not on company's actual career page

What this looks like:

You find the job on Indeed or ZipRecruiter, but when you go to the company's own website careers section, this role doesn't appear there.

Why it matters:

Legitimate open positions are almost always posted on the company's own site, in addition to any external boards.

Absence from their own career page while present on random aggregators can suggest outdated syndication (job aggregator scraped it long after it was actually filled or removed) rather than truly active hiring.

How to check:

Always cross-reference: search "[Company name] careers" directly and see if the exact role appears there currently.

RED FLAG 8: Salary range is dramatically wider than reasonable

What this looks like:

"$45,000 - $150,000" for the same role.

Why it matters:

This range is so wide it's essentially meaningless. It often signals the posting was created without real budget clarity, or the range was inflated to attract more applicants regardless of actual hiring plans.

How to check:

Compare the range width to typical postings in your field. A reasonable range is usually within 15-25% spread (e.g., $65K-$80K), not 200%+ variance.

RED FLAG 9: The role has been posted at the same company for the "same" position under different titles

What this looks like:

"Marketing Coordinator" posted in January.

"Marketing Associate" posted in March, nearly identical description.

"Junior Marketing Manager" posted in May, same responsibilities again.

Why it matters:

This pattern suggests either they can't decide what they actually need (disorganization) or they're continuously "auditioning" the market without real commitment to hiring at any specific level.

How to check:

If you're tracking a company you're interested in, note when similar roles repeat under different titles over several months.

RED FLAG 10: Interview scheduling becomes impossible or endlessly delayed after applying

What this looks like:

You get initial positive response ("We'd like to schedule a call").

Then scheduling drags on for weeks with no actual interview happening.

Why it matters:

While this can occasionally reflect genuine internal delays, a pattern of enthusiasm without follow-through often indicates the position isn't a real priority, or budget approval hasn't actually happened yet despite the posting being live.

How to check:

If initial scheduling takes more than 2-3 weeks with repeated rescheduling and no clear reason given, treat this as a signal about how seriously this specific opening is being pursued.

RED FLAG 11: Job description reads like a wish list, not a real role

What this looks like:

"This person will transform our entire go-to-market strategy, lead cross-departmental innovation, and single-handedly drive 300% growth."

Why it matters:

Real job descriptions describe realistic, specific responsibilities. Grandiose, vague, aspirational language often indicates the posting was written by someone imagining an ideal future state rather than describing an actual current need.

How to check:

Ask yourself: Could I explain to a friend exactly what this person does day-to-day based on this description? If not, it's likely more aspiration than reality.

RED FLAG 12: No clear indication of urgency or timeline anywhere

What this looks like:

No mention of when they hope to fill the role, no application deadline, completely open-ended.

Why it matters:

Real hiring needs usually have some timeline pressure (project starting, team member left, growth targets).

Complete absence of any urgency signals can suggest low priority or ongoing "just in case" posting rather than active need.

How to check:

This alone isn't damning, but combined with other flags (like extremely long posting duration), it adds to the pattern.

HOW TO USE THIS INFORMATION PRACTICALLY:

Step 1: Before applying, do a 5-minute check

• Check posting date
• Cross-reference company's own career page
• Scan for generic vs. specific language

Step 2: If 2-3 red flags present, apply but manage expectations

Don't invest hours customizing resume/cover letter for a posting showing multiple warning signs.

Submit efficiently, move on to other opportunities, don't wait around hoping.

Step 3: If 4+ red flags present, consider skipping entirely

Your time is valuable. Redirect effort toward postings with cleaner signals.

Step 4: Track patterns over time

Keep simple notes on companies/postings that show these patterns repeatedly. This becomes useful personal intelligence for future searching.

WHAT A HEALTHY, LIKELY-REAL LISTING LOOKS LIKE:

✓ Posted within last 30 days

✓ Specific team, tools, and responsibilities mentioned

✓ Reasonable, focused requirement list (5-8 core items)

✓ Salary range within reasonable spread

✓ Also appears on company's own career page

✓ Application confirmation received promptly

✓ Interview scheduling happens within days, not weeks

✓ Named hiring manager or department referenced

BOTTOM LINE:

Not every red flag means a job is fake or a scam.

Sometimes it just means the posting is stale, disorganized, or low-priority.

But your time matters.

Multiple red flags together mean:

• Lower likelihood of actual response
• Higher likelihood of wasted effort
• Better to redirect energy elsewhere

Use this as filtering, not absolute rejection.

Some legitimate opportunities will show one or two flags due to genuine circumstances.

But when the pattern stacks up, trust it and move your energy toward postings that show real signals of active, genuine hiring intent.

Have you noticed a job posting that kept reappearing or never seemed to go anywhere? What tipped you off?

For more honest job search strategy and insight:
Connect with Job Seekers Guide on LinkedIn

You Google the company name.

A few results show up.

But you're not sure what you're even looking for.

Is a working website enough to prove it's legit?

Is having a LinkedIn page enough?

You don't know which tools actually verify a business is real.

You don't know where to check if a company is registered.

You're about to hand over personal information based on a gut feeling.

That's not good enough.

The problem: Most people don't know that free, official tools exist to verify if a company is a real, registered business. You don't have to guess. You can actually check.

Here's how to verify an employer is legitimate:

TOOL 1: State Business Search

What it does:

Every state maintains a public database of registered businesses.

If a company is legally operating, it should be registered in the state where it claims to be headquartered.

How to use it:

Search: "[State name] State business search"

Example: "California State business search"

Enter the company's exact legal name.

What you're looking for:

• Does the company exist in the database?
• Is the registration status "Active" (not dissolved or suspended)?
• Does the registered address match what they've told you?
• When was it registered? (Very recent registration for a company claiming years of history is a red flag)

Real talk:

This is one of the most reliable free verification tools. Legitimate businesses are legally required to register. If nothing comes up, that's a significant red flag.

TOOL 2: Better Business Bureau (BBB)

What it does:

Tracks business complaints, ratings, and accreditation status.

How to use it:

Go to bbb.org

Search company name.

What you're looking for:

• Does the company have a BBB profile?
• What's their rating?
• Are there complaints, and what do they say?
• Is the business accredited?

Real talk:

Not every legitimate small business has a BBB profile, so absence alone isn't definitive. But if a profile exists with numerous scam-related complaints, that's a serious red flag.

TOOL 3: LinkedIn Company Page Verification

What it does:

Shows company size, employee list, posting history, and general legitimacy signals.

How to use it:

Search company name on LinkedIn.

What you're looking for:

• Does a company page exist?
• How many employees are listed? (Does it match claimed company size?)
• Are there real people with consistent work history listed as employees?
• How long has the page existed?
• Does the page have regular posts/activity?

Real talk:

Check if listed employees have profiles that look established (not created last week with no connections). Click on a few "employees" and verify they seem like real people with genuine work history.

TOOL 4: Company Website Domain Age Check

What it does:

Reveals how long a website domain has existed.

How to use it:

Go to whois.com or who.is

Enter the company's website URL.

What you're looking for:

• When was the domain registered?
• Company claims to be established for 10 years, but domain was registered 2 months ago? Red flag.
• Domain registered very recently combined with aggressive hiring? Worth extra caution.

Real talk:

This tool is free and takes 30 seconds. Very useful for catching freshly created scam websites designed to look legitimate.

TOOL 5: Glassdoor Company Reviews

What it does:

Employee reviews, salary information, interview experiences.

How to use it:

Search company name on Glassdoor.

What you're looking for:

• Does the company have reviews at all?
• Are reviews from people describing realistic work experiences?
• Do any reviews mention scam experiences or "never got paid"?
• Consistent negative patterns about specific practices?

Real talk:

Very small or brand-new companies might not have reviews yet, which isn't necessarily a red flag alone. But if reviews exist and describe scam patterns, take that seriously.

TOOL 6: Google Maps/Street View Address Verification

What it does:

Shows you what actually exists at the claimed business address.

How to use it:

Enter the company's claimed address into Google Maps.

Use Street View to see the actual location.

What you're looking for:

• Does a real office building exist there?
• Is it a UPS Store/mailbox rental location (red flag for company claiming to be headquartered there)?
• Is it a residential address for a company claiming to be a large corporation?
• Does the building signage match the company name?

Real talk:

This catches a surprising number of scams. Many fake companies list addresses that turn out to be empty lots, mailbox stores, or unrelated businesses.

TOOL 7: SEC EDGAR Database (for publicly traded companies)

What it does:

If a company claims to be publicly traded, this verifies their actual SEC filings.

How to use it:

Go to sec.gov/edgar/search

Search company name.

What you're looking for:

• Does the company have actual SEC filings?
• Do financial details match what they've claimed?

Real talk:

Only relevant if company claims public trading status. Most job scams involve smaller companies, so this won't always apply, but it's useful for verifying larger company claims.

TOOL 8: Google Reverse Image Search (for "employee" photos)

What it does:

Checks if photos used (company photos, employee headshots) are stolen from elsewhere online.

How to use it:

Right-click any photo (recruiter headshot, office photos) and select "Search image with Google" or use images.google.com

What you're looking for:

• Does this exact photo appear elsewhere under a different name?
• Is this a stock photo being used as a "real employee"?

Real talk:

Scammers often steal LinkedIn profile photos or use stock images. This tool catches that instantly.

TOOL 9: State Licensing Board (for licensed professions)

What it does:

If job involves licensed profession (healthcare, real estate, legal, financial services), verifies actual licensing.

How to use it:

Search: "[State] + [profession] + licensing board"

What you're looking for:

• Is the company/individuals properly licensed for claimed services?

Real talk:

Particularly important for financial services jobs, healthcare roles, or anything requiring specific state licensing.

TOOL 10: Reddit and Scam-Specific Forums

What it does:

Real people sharing real scam experiences.

How to use it:

Search: "[Company name] + scam" on Google

Check r/Scams, r/jobs, industry-specific subreddits

What you're looking for:

• Multiple independent reports describing the same scam pattern?
• Consistent details matching your own experience?

Real talk:

If multiple people report identical experiences (same interview questions, same requests for money, same red flags), that's strong evidence of a pattern, not coincidence.

TOOL 11: Company Registration Number Cross-Check

What it does:

If company provides an EIN (Employer Identification Number) or business registration number, you can verify it.

How to use it:

For EIN verification: IRS.gov has some verification tools for certain purposes, or you can cross-reference through business registration databases.

What you're looking for:

• Does the number correspond to the actual company name?
• Is it a valid format?

Real talk:

This is more advanced verification, useful when something feels off but other checks seem inconclusive.

STEP-BY-STEP VERIFICATION PROCESS:

Quick check (5 minutes):

1. Google company name + "reviews"
2. Check LinkedIn company page exists
3. Verify address on Google Maps
4. Check domain age (whois.com)

If quick check raises concerns, deeper check (15-20 minutes):

1. State business search
2. BBB profile check
3. Glassdoor reviews
4. Reverse image search on any photos provided

If still uncertain:

1. Search "[Company name] + scam" specifically
2. Check relevant Reddit communities
3. Request a phone/video call to verify real human interaction

REAL EXAMPLE: Verification in Action

Situation:

You receive a job offer from "Meridian Financial Solutions," claiming to be a 15-year-old financial services company.

Verification steps taken:

1. State search: Company found, but registered only 3 months ago (Red flag - contradicts "15 years" claim)
2. Domain age check: Website domain registered 2 months ago (Red flag - matches recent registration, contradicts long history claim)
3. LinkedIn page: Exists, but only 3 "employees" listed, all with profiles created within the last month, minimal connections (Red flag)
4. Google Maps address check: Address is a UPS Store mailbox location, not an actual office (Red flag)
5. Reverse image search on "CEO" photo: Same photo appears on a stock photo website under a different name (Major red flag)

Conclusion: This combination of verification results confirms this is very likely a scam operation, not a legitimate 15-year-old financial company as claimed.

Time invested: 20 minutes

Potential harm avoided: Identity theft, financial fraud, wasted time

WHAT LEGITIMATE VERIFICATION LOOKS LIKE:

Real company example:

1. State Business Search: Registered 12 years ago, status active, address matches
2. Domain age: Website registered 11 years ago
3. LinkedIn: 200+ employees listed, consistent work histories, active company posts
4. Google Maps: Real office building matching company signage
5. BBB: Accredited, positive rating, legitimate complaint responses
6. Glassdoor: Hundreds of reviews describing realistic work experiences

This pattern of consistent, verifiable information across multiple sources indicates legitimate operation.

WHEN VERIFICATION ISN'T POSSIBLE (Small/New Companies):

Not every legitimate opportunity will pass every single check.

Genuinely new small businesses might have:

• Limited online presence (but should still have SOME verification)
• Few Glassdoor reviews (but should have basic company registration)
• Smaller LinkedIn presence (but real address, real registration)

The key difference:

Legitimate new small businesses will still have:

✓ Proper state business registration

✓ Real address (not mailbox store)

✓ Willingness to do phone/video interviews

✓ No upfront payment requests

✓ Reasonable, verifiable claims about company history

Scam operations typically fail MULTIPLE verification points simultaneously, not just one.

BOTTOM LINE:

You don't have to guess if a company is legitimate.

Free tools exist to verify:

1. State business registration
2. BBB complaint history
3. LinkedIn company presence
4. Domain registration age
5. Glassdoor reviews
6. Physical address reality
7. Photo authenticity

Takes 5-20 minutes total.

Protects you from:

• Identity theft
• Financial fraud
• Wasted time and energy
• Emotional manipulation

The golden rule:

If multiple verification checks raise red flags simultaneously, trust that pattern over any single positive signal.

Legitimate companies want you to feel confident and safe applying. They won't discourage verification. Scam operations often do, through urgency tactics or evasiveness.

Have you used any of these tools to verify a company? What did you find?

For more honest job search safety and strategy:
Connect with Job Seekers Guide on LinkedIn