DOL’s H-1B ‘Project Firewall’ Aligns with New EEOC Guidance

Note: This article is for general informational and publishing purposes only. It is not legal advice, and employers should consult qualified counsel before changing immigration, hiring, or compliance practices.

The phrase “Project Firewall” sounds like something a cybersecurity team would install right before lunch and then blame for everyone’s Wi-Fi problems. But in the employment immigration world, the Department of Labor’s H-1B “Project Firewall” is not about blocking suspicious emails from a prince with a bank account. It is about protecting U.S. workers, tightening H-1B compliance, and placing employers’ visa-related hiring practices under a much brighter federal spotlight.

The timing matters. The U.S. Department of Labor launched Project Firewall as an H-1B enforcement initiative designed to safeguard the rights, wages, and job opportunities of highly skilled American workers. Soon after, the Equal Employment Opportunity Commission updated educational materials emphasizing that national origin discrimination can include preferring foreign workers, including workers with a particular visa status, over American workers. Together, these developments send a clear message: employers cannot use immigration programs as a shortcut around fair hiring rules.

For companies that depend on global talent, this does not mean the H-1B program is suddenly a forbidden fruit wrapped in red tape and anxiety. The H-1B program remains an important pathway for hiring highly skilled foreign professionals in specialty occupations. What has changed is the enforcement tone. Agencies are signaling that they will look closely at whether employers are following H-1B rules, paying required wages, recruiting fairly, and avoiding job advertisements or screening practices that appear to favor temporary visa holders over qualified U.S. workers.

What Is DOL’s H-1B Project Firewall?

Project Firewall is the Department of Labor’s enforcement initiative focused on H-1B program compliance. The initiative is led through the Wage and Hour Division, which enforces labor condition application requirements and other H-1B obligations. Its stated purpose is to protect highly skilled U.S. workers from unfair displacement and to ensure that employers do not misuse the H-1B visa process.

In plain English, Project Firewall asks a simple question: when an employer uses the H-1B program, is it doing so because it truly needs specialized talent, or is it quietly using the system to avoid hiring, paying, or retaining qualified American workers? That question is not new, but the initiative gives it a sharper enforcement edge.

The H-1B program applies to employers seeking temporary foreign workers in specialty occupations that generally require highly specialized knowledge and at least a bachelor’s degree or equivalent. Employers must typically make wage and working-condition commitments through the labor condition application process. These rules are intended to protect both H-1B workers and similarly employed U.S. workers. In other words, the law does not invite employers to play “musical chairs” with livelihoods while the federal government provides the playlist.

How the EEOC Guidance Fits the Same Enforcement Puzzle

The EEOC’s updated guidance focuses on national origin discrimination. Under Title VII of the Civil Rights Act of 1964, employers may not discriminate against applicants or employees based on national origin. The EEOC has emphasized that these protections apply to all national origin groups, including Americans. That is where the connection to Project Firewall becomes especially important.

The EEOC’s materials explain that national origin discrimination may include job advertisements or employment practices that prefer workers from a particular country or workers with a particular visa status. Examples include “H-1B only,” “H-1B preferred,” or similar wording that discourages U.S. workers from applying. A job posting may look like a few harmless lines on a recruiter’s screen, but in compliance terms, one careless phrase can become a very expensive sentence.

Project Firewall focuses on H-1B program integrity. The EEOC guidance focuses on discriminatory employment practices. The overlap appears when visa preference becomes a proxy for excluding American workers or disadvantaging applicants based on national origin. That is why employers should not treat immigration compliance and anti-discrimination compliance as separate islands. They are more like neighboring cubicles: different nameplates, same office gossip.

Why “H-1B Preferred” Can Create Legal Trouble

Many employers use shorthand in job postings because recruiters are moving fast, hiring managers are impatient, and everyone wants a software engineer who knows twelve programming languages, loves documentation, and can start yesterday. But shorthand can be risky when it signals a preference for a visa category rather than job qualifications.

A lawful job advertisement should focus on skills, education, experience, location, work authorization, and any legitimate legal requirement. It should not suggest that only H-1B workers, OPT workers, or other temporary visa holders are welcome unless a specific legal basis applies. “Must be authorized to work in the United States” is very different from “H-1B only.” The first addresses work authorization generally; the second may exclude U.S. citizens, lawful permanent residents, refugees, asylees, and other protected workers who are already authorized to work.

Example: The risky job ad

Imagine a technology staffing company posts: “Java Developer needed. H-1B candidates preferred. No citizens.” That language is not merely clumsy; it waves a compliance red flag large enough to be seen from the break room. It may suggest that the employer is discouraging American workers or other protected workers from applying.

Example: The safer job ad

A safer version would say: “Java Developer needed. Bachelor’s degree in computer science or related field preferred. Three years of enterprise Java experience required. Must be authorized to work in the United States.” This version focuses on the actual job requirements instead of visa status. It is less dramatic, yes, but employment law rarely rewards dramatic flair.

Project Firewall and Coordinated Federal Enforcement

One reason employers are paying attention is that Project Firewall is not just a slogan. The Department of Labor has described a coordinated approach involving federal partners such as the EEOC, the Department of Justice Civil Rights Division, and U.S. Citizenship and Immigration Services. That means a questionable hiring pattern may not stay neatly inside one agency’s inbox.

A DOL investigation may focus on H-1B wages, labor condition application compliance, displacement, recruitment, or retaliation. An EEOC inquiry may focus on whether U.S. workers were treated less favorably because of national origin. The Department of Justice’s Immigrant and Employee Rights Section may examine citizenship status or immigration status discrimination in hiring, firing, recruitment, or referral for a fee. USCIS may evaluate petition-related issues. The employer, meanwhile, may be trying to remember who approved that job ad six months ago. Spoiler: nobody remembers, and the shared drive has seven folders named “Final.”

This multiagency posture increases the importance of documentation. Employers should be able to explain why a role requires certain skills, how candidates were sourced, how applicants were evaluated, whether U.S. workers were considered fairly, and whether visa-related language was legally necessary. Compliance should not depend on panic archaeology after a government letter arrives.

What Employers Should Review Now

The practical takeaway is not “stop hiring foreign talent.” The better takeaway is “hire carefully, document honestly, and do not build shortcuts that exclude protected workers.” Employers that use the H-1B program should review recruitment, immigration sponsorship, compensation, and recordkeeping practices before an agency does it for them.

1. Audit job postings and recruiter templates

Companies should review job advertisements, email templates, LinkedIn messages, applicant tracking system filters, and third-party staffing instructions. Look for phrases such as “H-1B only,” “OPT preferred,” “visa candidates only,” “citizens need not apply,” or any language that could discourage protected workers. The same caution applies to coded language that may not mention H-1B directly but produces the same exclusionary effect.

2. Train recruiters and hiring managers

Recruiters often sit at the compliance front line. They are the people writing job posts, screening applicants, communicating with staffing vendors, and translating vague manager requests into public-facing language. Training should explain what can and cannot be said about work authorization, sponsorship, citizenship, national origin, and visa status.

3. Revisit H-1B wage and LCA compliance

Project Firewall places renewed attention on whether employers are paying required wages, honoring working conditions, and maintaining proper records. Employers should confirm that H-1B workers are paid at least the required wage, that job duties and work locations match filings, and that public access files and related records are accurate.

4. Examine displacement and recruitment practices

H-1B-dependent employers and willful violator employers may face additional obligations involving nondisplacement and good-faith recruitment of U.S. workers. Even employers not classified as H-1B-dependent should be careful when layoffs, benching, outsourcing, or visa hiring occur close together. The optics matter, but the facts matter more.

5. Watch third-party staffing arrangements

Vendors, staffing agencies, and subcontractors can create risk. An employer may have polished internal policies, but if a vendor posts discriminatory ads on its behalf, the compliance headache may still come knocking. Contracts should require lawful recruiting practices, and companies should monitor vendor job postings and referral patterns.

What Workers Should Understand

Workers should know that federal employment protections do not disappear because immigration is involved. U.S. workers may have claims if they are excluded from opportunities because an employer prefers temporary visa holders. Foreign workers may also have rights if they are underpaid, retaliated against, or used as cheaper labor in violation of H-1B rules. The point is not to pit workers against each other. The point is to keep the system honest.

The best version of high-skilled immigration is not a cage match between American workers and foreign professionals. It is a lawful labor system where employers recruit fairly, pay properly, and use visa programs for legitimate talent needs. When employers cut corners, both U.S. and foreign workers can lose.

Why This Matters for the Technology Sector

The technology industry will feel much of the pressure because it has long relied on H-1B talent for engineering, data science, software development, cybersecurity, product management, and other specialized roles. But this issue is not limited to Silicon Valley, cloud platforms, or companies whose office snacks have better branding than most small businesses.

Healthcare, finance, higher education, consulting, manufacturing, and research organizations also use H-1B workers. Any employer that sponsors foreign professionals should treat Project Firewall and the EEOC guidance as a reminder to modernize compliance practices. That means aligning immigration, HR, legal, recruiting, payroll, and vendor management teams. When those departments operate separately, small mistakes can become big problems.

The Business Case for Fair Hiring

Fair hiring is not just a legal requirement; it is a business advantage. Companies that recruit broadly are more likely to find excellent candidates. Companies that document decisions are better prepared for audits. Companies that train managers reduce risk before it becomes litigation. Companies that respect both U.S. workers and foreign workers build stronger teams.

There is also a reputational angle. In a competitive labor market, workers talk. Applicants share screenshots. Former employees post reviews. A job ad that appears to exclude U.S. workers or exploit visa workers can travel across social media faster than an office rumor about free pizza. Employers should assume that public-facing hiring language is exactly that: public.

Common Mistakes Employers Make

One common mistake is confusing sponsorship preference with skill preference. A company may want candidates who already have experience in a specialized technical environment. That is fine. But expressing that preference through visa status instead of skills can create problems. Another mistake is assuming that a staffing agency “handles all that.” Government agencies may not be impressed by the phrase “we outsourced the mistake.”

A third mistake is failing to update old templates. A recruiter may copy a job post from 2021, paste it into a new listing, and accidentally revive language that should have been buried with the company’s abandoned ping-pong table. Employers should regularly review templates and applicant tracking system fields to ensure they do not screen based on improper criteria.

Finally, employers sometimes overlook retaliation risks. If a worker complains about H-1B misuse, discriminatory job postings, unequal treatment, or wage issues, the employer must handle that complaint carefully. Retaliation can turn a manageable compliance issue into a much larger legal problem.

Practical Compliance Checklist

Employers can start with a practical checklist. First, remove visa-preference language from job postings unless it is legally required and reviewed by counsel. Second, train recruiters on national origin, citizenship status, and immigration-related discrimination. Third, document objective hiring criteria. Fourth, review H-1B wage, worksite, job duty, and public access file obligations. Fifth, monitor vendors and staffing partners. Sixth, create a process for escalating complaints. Seventh, keep immigration counsel and employment counsel in the same conversation, preferably before the fire drill begins.

The goal is not to create paperwork for paperwork’s sake. The goal is to show that hiring decisions are based on lawful, job-related criteria. If an agency asks questions, a clean record can answer faster than a nervous executive with a spreadsheet and a dream.

Experiences and Real-World Lessons from H-1B Compliance

In real workplace compliance conversations, the biggest problems often begin with ordinary decisions. A hiring manager says, “Find me someone who already has an H-1B.” A recruiter hears, “Prioritize visa workers.” A staffing vendor posts the job quickly. Nobody intends to create a federal enforcement issue. Everyone intends to fill the role. But intent does not erase impact, especially when the public job ad tells qualified U.S. workers they are not welcome.

One practical lesson from H-1B compliance is that language discipline matters. A company may have a lawful need for candidates who can work in the United States without delay. That can be expressed in a neutral way. But when the language shifts from work authorization to visa preference, risk enters the room wearing shoes and carrying a clipboard. Recruiters should be trained to ask: Are we describing a job requirement, or are we describing a preferred immigration category?

Another lesson is that immigration teams and HR teams need to collaborate early. In many organizations, immigration sponsorship is handled by legal or global mobility, while recruiting is handled by talent acquisition. If those teams do not communicate, job ads may promise things the immigration team cannot support, or recruiters may screen candidates in ways that create discrimination concerns. A short internal review process can prevent long external investigations.

Documentation also becomes a lifesaver. When employers can show consistent interview notes, objective scorecards, wage records, LCA postings, recruitment efforts, and lawful reasons for candidate selection, they are in a stronger position. When records are missing, inconsistent, or stored in someone’s personal inbox labeled “misc stuff,” the company has made its own defense harder than necessary.

Employers should also learn from enforcement patterns. Federal agencies have repeatedly focused on job advertisements that restrict opportunities based on citizenship, immigration status, or visa categories without legal justification. These cases show that compliance risk is not limited to final hiring decisions. The recruitment funnel itself matters. If a worker is discouraged from applying, excluded by screening criteria, or routed through a more burdensome process because of national origin or citizenship status, the employer may face scrutiny even before an offer is made.

For foreign workers, the experience can be complicated. Many H-1B employees are highly skilled professionals who contribute significantly to U.S. businesses and communities. They also depend on employer compliance. If an employer underpays them, changes worksites without proper steps, misstates job duties, or retaliates when concerns are raised, the worker may feel trapped. Strong enforcement should protect lawful visa workers from exploitation while also protecting U.S. workers from unfair exclusion.

For U.S. workers, Project Firewall and the EEOC guidance may offer reassurance that federal agencies are paying attention to discriminatory hiring practices. But the healthiest labor market is not built by blaming foreign professionals. It is built by holding employers accountable for lawful recruitment, honest wage practices, and transparent decision-making. Workers should compete on skills, experience, and qualifications, not on whether a recruiter thinks a particular visa category is more convenient.

The strongest companies will treat this moment as a chance to improve. They will update job ads, train managers, review vendors, clean up records, and build a culture where compliance is not the department of “no,” but the department of “do it right the first time.” That may not sound glamorous, but neither does explaining a bad job posting to three federal agencies before coffee.

Conclusion

DOL’s H-1B Project Firewall and the EEOC’s updated national origin guidance point in the same direction: federal agencies are watching how employers use visa programs and how those practices affect American workers. The message is not anti-talent, anti-immigration, or anti-business. It is pro-compliance.

Employers can still hire skilled foreign professionals, sponsor H-1B workers, and compete globally. But they must do so without excluding qualified U.S. workers, underpaying visa workers, misusing job ads, or building recruitment systems that favor one immigration category over another without legal justification. The safest path is clear: write neutral job postings, evaluate candidates fairly, pay required wages, document decisions, and train the people who touch the hiring process.

Project Firewall may sound dramatic, but its practical lesson is simple. If a company’s hiring system depends on a hidden preference for visa workers, it is time to rebuild the system before regulators bring their own tools.