Historical Sponsorship vs. Current Job Requirements

Yes. Salesforce’s profile reports 3,432 certified H-1B LCA filings across FY2025 and the partial FY2026 disclosure window. Its current profile snapshot also reports 8 negative language signals among 552 active U.S. postings. These facts describe different records and can both be true.

A company may support immigration filings for some roles, teams or existing employees while another requisition limits new sponsorship. The aggregates do not identify which explanation applies to a flagged posting. A transfer exception or pathway-specific condition can be particularly important.

The table below keeps each employer’s current inventory denominator visible. Its share view is the share of profile-reported postings with an extracted negative signal, not an employer-wide refusal probability.

On November 9, 2026, the original Amazon Jobs listing for the Seattle Amazon Finance Rotational Program, requisition 10597230, stated that visa sponsorship was unavailable for that opening. The source is listed below. This dated example may outlast the employer’s listing.

Openbound’s Amazon profile separately reports certified H-1B LCA and PERM activity for matched employer entities. Those filings and the job advertisement measure different things. For this application, use the posting’s restriction, confirm the employing entity and ask recruiting whether there is any exception for the specific immigration pathway you need.

The posting review is an editorial example outside the original ten-profile snapshot. The charts and dataset dates still refer to the original sample.

Salesforce: 8 / 552 profile-reported active U.S. postings (1.4%) have negative sponsorship language. The same profile has 3,432 certified H-1B LCA filings in FY2025–FY2026, with FY2026 data only through June 30. The current-language denominator and the historical-filing unit are separate.

Workday: 10 / 174 profile-reported active U.S. postings (5.7%) have negative sponsorship language. The same profile has 580 certified H-1B LCA filings in FY2025–FY2026, with FY2026 data only through June 30. The current-language denominator and the historical-filing unit are separate.

Atlassian: 3 / 163 profile-reported active U.S. postings (1.8%) have negative sponsorship language. The same profile has 508 certified H-1B LCA filings in FY2025–FY2026, with FY2026 data only through June 30. The current-language denominator and the historical-filing unit are separate.

The other seven profiles report zero positive and negative posting-language counts under the snapshot renderer. That describes extracted language, not a company policy of saying yes to sponsorship. It also does not validate every role classified Likely or Highly likely.

Openbound’s five visa classifications combine multiple evidence inputs. This study uses the separate posting-language counts, not the Unlikely bucket as a proxy for refusal. An estimate can reflect limited history or other negative evidence, while a qualified statement can require a more careful reading than a single label suggests.

This distinction matters when comparing the new study with Openbound’s earlier archived software/data report. That report found that some jobs at verified-history employers lacked favorable classifications. It did not count explicit refusals. This profile study addresses a narrower question: whether current negative posting language is present alongside historical filing activity.

First, read the current employer posting. Save the requisition ID, source URL, date checked and exact authorization wording. Separate a general work-authorization requirement from explicit sponsorship language, and note any conditional transfer or visa-category exception.

Second, identify the employing entity. A recognizable parent brand, a vendor that uses its software, and a staffing firm are different employers. Check which legal entities are included in the filing evidence and whether the role or worksite matches the relevant records.

Third, ask recruiting a concrete question: “For this requisition and employing entity, what immigration support is available for my situation, including any new sponsorship or transfer conditions?” A historical filing total cannot substitute for that current answer.

Silence means the question remains unresolved in the captured language. Historical evidence can justify putting the employer on a research shortlist, but it cannot establish that this opening provides support. Zero extracted negative signals should not be restated as “all jobs sponsor.”

A posting that explicitly excludes the support you need deserves a different response from one that simply does not discuss it. Read the exact conditions before spending time on an application. If the source posting changes, the current version and a dated recruiter confirmation matter more than an older snapshot.

Choose a role for its relevance to your skills, then evaluate its current requirements. Use the table to spot where company history and posting language need to be reconciled, not to rank employers by personal visa odds.

Keep a small evidence log for each application: source URL, requisition, legal employer, worksite, wording, history coverage and recruiter confirmation date. This makes conflicting or stale information easier to resolve.

Follow the live company-profile links for today’s openings. The research is a dated snapshot and will not remove the need to read the current job.