10 Enterprise Software Companies to Check for H-1B Sponsorship (2026)

In descending observed technical-posting count, the selected employers are Oracle (572), ServiceNow (143), Databricks (119), Intuit (118), Salesforce (104), Snowflake (73), Adobe (69), Workday (59), Atlassian (55), Autodesk (14). These counts cover the software/data title families in the archived editions, not the full company vacancy total. Ties would be broken by stored company slug.

The chart shows current-at-extraction inventory for this chosen set. It is useful for deciding where to start researching relevant technical roles; it does not tell you where an applicant is most likely to receive sponsorship. A small observed cohort can reflect source coverage and taxonomy as well as hiring volume.

Use the linked employer names in the data table to inspect current evidence and source jobs. Snowflake and Databricks are grouped by their exact stored company records, rather than merging every source or subsidiary sharing the brand.

Of 1,326 selected postings, Highly likely: 894 (67.4%); Likely: 423 (31.9%); Possible: 0 (0.0%); Unclear: 6 (0.5%); Unlikely: 3 (0.2%). These labels are persisted classifications from the original dated editions. They are not observed hires, employer promises or visa decisions.

The separate verified-history test is met by 740 / 1,326 postings (55.8%). It requires verified employer identity, mapped LCA or USCIS history, and positive recent filing or approval evidence. The full product classification can use other evidence, so the two measures need not agree.

Oracle and Autodesk have favorable posting signals in these inputs but no postings with this narrower verified-history flag. That is an evidence-coverage difference in the archived dataset, not a claim that either company has never sponsored. Inspect the current employer profile before forming a policy conclusion.

The chart below measures the archived verified-history flag within each employer’s observed cohort. A zero is a missing qualifying flag under this test; it is not a no-sponsorship verdict. A full bar likewise establishes neither a blanket current policy nor a personal guarantee.

For Intuit, 112 / 118 postings had favorable signals, while 6 were Unclear. A company-level history record does not remove requisition-level uncertainty.

Compare three things for a target role: the original posting’s authorization language, attributable history for the employing entity, and the recruiter’s answer for your situation. Strong evidence in one column should not silently fill a missing answer in another.

Salesforce contributes 104 archived software/data-family postings. 103 / 104 (99.0%) had Highly likely or Likely signals; 1 was Unlikely. All 104 met the archived verified-history test. This is one employer’s technical subset, not all Salesforce careers.

Salesforce is worth investigating alongside other enterprise software businesses rather than treating one familiar brand as the entire market. The evidence supports a role-specific research process; this dataset does not identify the best company for a particular candidate.

A “Salesforce developer” job at a customer, consulting partner or staffing firm belongs to that firm. Identify the employer in the posting and evaluate its own evidence. Salesforce skills and employment at Salesforce are different search intentions.

The selected cohort’s stored workplace categories are Unspecified: 1,139 / 1,326 (85.9%); Remote: 128 / 1,326 (9.7%); Hybrid: 57 / 1,326 (4.3%); On-site: 2 / 1,326 (0.2%). Unspecified remains visible rather than being converted into on-site.

Remote is a workplace arrangement, not a sponsorship commitment or permission to work anywhere. Check the permitted U.S. states, actual worksite, employing entity and authorization requirements. Multi-location postings still count only once in this report.

We do not compare salaries or claim a remote sponsorship advantage. Source coverage and role mix differ across the ten companies; this analysis does not control for those differences or measure candidate outcomes.

Does appearing on a sponsor list mean every opening offers H-1B support? No. Past employer records and a current requisition answer different questions. An explicit restriction in the posting matters even when historical evidence is strong.

Does an LCA mean an approved H-1B visa or a new hire? No. DOL’s glossary distinguishes LCA certification from the USCIS petition determination. Filing records, approvals and people hired are different units.

What about H-1B transfers, OPT or green cards? This dataset does not establish those role-specific policies. Ask the employer about the pathway relevant to your circumstances; H-1B history does not establish STEM OPT support, E-Verify participation or a green card commitment.

Ask recruiting: “For this requisition, employing entity, worksite and start date, do you consider candidates who need H-1B support in my situation, and what support is available?” Keep the requisition ID with the answer.

Build a shortlist across several employers whose products and roles match your skills. Use observed inventory to decide where to research first, then visit the company profiles for current openings.

Record the employing entity, requisition ID, source posting, worksite and date checked. Confirm immigration support for that role before investing in a long interview loop.

Treat Highly likely/Likely as prioritization signals, Unclear as a question to resolve, and an explicit restriction as a restriction. Do not translate either a history flag or a percentage into personal success odds.