San Francisco, CA 94158, United States

Software Engineer III

USD 150K–182K / yearMidSoftware engineering (general)

C#GolangJavaMySQLReactPhD

Original posting ↗Apply ↗Company job board ↗See this job in Telegram

Software Engineer III is an open role at Uber Freight, a company in logistics. The job is based in San Francisco, United States. Our labels mark it as a mid-level role in software engineering (general). Technologies named in the posting: MySQL, React, C#, Golang and Java. It asks for 3+ years of experience. Visa sponsorship is not offered. Uber Freight has 46 open positions on this site, 4 of them in IT and engineering.

Posted 5 days ago · Last checked 2026-11-09

About Uber Freight

Logistics Non-tech company with an IT team 46 open positions, 9% in IT and engineering. Most open roles: Operations and admin (18), Finance and legal (7), Customer success and support (5).

All open jobs at Uber Freight →

Similar jobs

Information Extraction EngineerRed Cell Partners · Remote, USAUSD 135K–170K / year Sr. Product Engineer – ArcGIS Solutions Web Development Esri · Remote Eligible, USUSD 93.6K–159.3K / year Staff+ Software Engineer, Safeguards Evals Anthropic · San Francisco, CA; Seattle, WAUSD 320K–485K / year Software Engineer in TestExiger · McLean, Virginia, United States; Richmond, Virginia, United StatesHybrid Sr. Transmission & Generation Planning Engineer (PE)SpaceX · Bastrop, TXHybrid Systems Engineering Intern - Summer 2027Skydio · San Mateo, California, United StatesUSD 47 / hour Senior Manager, Software Engineering (Graphics) - League of LegendsRiot Games · Los Angeles, USA Senior Software Engineer - SearchHinge Health · San Francisco-HQUSD 164K–217K / year

4,417 open software engineering (general) jobs in the United States All open jobs at Uber Freight →

Workplace	Workplace not stated
Seniority	Mid
Role	Software engineering (general)
Countries	United States
Languages	C#GolangJava
Key facts	Stack: C#, Golang, Java, MySQL, React · Experience: 3+ years · Visa sponsorship: no

The full description is on the original posting. Labels are set automatically and can be wrong. About the data