Ohio - Columbus

Senior Software Engineer - Fullstack with Rust

USD 110K–270K / yearRemoteSeniorBackend engineering

RustSQLReactCustomer successCRM

Original posting ↗Apply ↗Company job board ↗Save Follow new Rust jobs in Telegram

Senior Software Engineer - Fullstack with Rust is an open role at Veeva Systems, a company in food, drinks and consumer goods. The role is remote, and the posting gives Columbus, United States as the location. Our labels mark it as a senior-level role in backend engineering. Technologies named in the posting: Rust, React and SQL. It asks for 7+ years of experience. Visa sponsorship is not offered. Veeva Systems has 46 open positions on this site, 8 of them in IT and engineering.

Posted 9 days ago · Last checked 2026-11-14

About Veeva Systems

Food, drinks and consumer goods Non-tech company with an IT team 46 open positions, 17% in IT and engineering. Most open roles: Strategy, consulting and analysis (22), Healthcare (10), Product and design (10).

All open jobs at Veeva Systems →

Similar jobs

Backend Engineer Quindar · Denver, COUSD 120K–180K / year Senior Backend Engineer - Performance - IrelandTeleport · Ireland (Remote)EUR 134K–177.1K / year Director of Backend EngineeringCoupang Internal · Seattle, USAUSD 159K / year Director of Backend EngineeringCoupang · Seattle, USAUSD 159K / year (1632) Principal Backend Engineer (Java and Golang)Nortal · Latin America - RemoteRemote Software Engineer (Backend, Infrastructure Focus)Kira · New York or San FranciscoUSD 165K–195K / year Senior Java DeveloperASSYST, Inc. · Austin, TX Staff Software Engineer, BackendArcher · San Jose, California, United StatesUSD 175K–215K / year

271 open backend engineering jobs in the United States 419 open remote backend engineering jobs All open jobs at Veeva Systems →

Workplace	Remote
Seniority	Senior
Role	Backend engineering
Countries	United States
Languages	RustSQL
Employment type	Full-Time
Key facts	Stack: Rust, SQL, React · Experience: 7+ years · Remote · Visa sponsorship: no

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