1

Rust Library Jobs in Austin, TX (NOW HIRING)

Senior Machine Learning Engineer

Austin, TX · On-site +1

$121K - $160K/yr

Proficiency in programming languages and libraries common to machine learning; excellence in Python ... Go, Rust, C++, Java, Scala, etc.) * Proficiency with modern software engineering tools and ...

... libraries (e.g. NIXL, NCCL, UCX, MPI, NVSHMEM), and GPU accelerated systems, with track record of ... Proficiency in programming languages such as C, C++, Rust and Python. Ways to stand out from the ...

Senior Software Engineer

Austin, TX · On-site +1

$160K - $200K/yr

Excellence in Go, C++ (17 or higher), Java (11 or higher), C# (9 or higher), or Rust * Proficiency ... Comfort with integration of deep learning libraries (e.g., PyTorch, TensorFlow) * Experience ...

... libraries like TensorFlow, PyTorch, and scikit-learn) and systems programming (e.g., Go, Rust, C++, Java, Scala, etc.) * Proficiency in the design and delivery of algorithms, data structures, and ...

next page

Showing results 1-20

Rust Library information

See Austin, TX salary details

$9

$15

$19

How much do rust library jobs pay per hour?

As of Jul 9, 2026, the average hourly pay for rust library in Austin, TX is $15.12, according to ZipRecruiter salary data. Most workers in this role earn between $13.37 and $15.96 per hour, depending on experience, location, and employer.

What is the difference between Rust Library vs Rust Developer?

AspectRust LibraryRust Developer
Required CredentialsKnowledge of Rust programming, library development experienceProficiency in Rust, software development skills, possibly a degree in computer science
Work EnvironmentTypically works on creating, maintaining, or documenting Rust librariesDevelops software applications using Rust, may work on libraries as part of projects
Employer & Industry UsageOpen-source projects, tech companies, software firmsTech companies, startups, software development firms
Search & Comparison IntentLooking for roles related to creating or maintaining Rust librariesSeeking software development roles involving Rust programming

In summary, a Rust Library focuses on developing and maintaining reusable code components in Rust, often within open-source or collaborative projects. A Rust Developer, however, is a broader role involving designing, coding, and deploying software applications using Rust, which may include working with or creating libraries as part of their responsibilities.

What are popular job titles related to Rust Library jobs in Austin, TX? For Rust Library jobs in Austin, TX, the most frequently searched job titles are:
What job categories do people searching Rust Library jobs in Austin, TX look for? The top searched job categories for Rust Library jobs in Austin, TX are:
What cities near Austin, TX are hiring for Rust Library jobs? Cities near Austin, TX with the most Rust Library job openings:
Senior Systems Test Sofware Engineer

Senior Systems Test Sofware Engineer

Saronic Technologies

Austin, TX • On-site

$109K - $142K/yr

Full-time

Re-posted 3 days ago


Job description

Job Summary:
Saronic Technologies is a leader in revolutionizing autonomy at sea, dedicated to developing state-of-the-art solutions that enhance maritime operations through autonomous and intelligent platforms. The Systems Software Test Engineer will own and drive the testing strategy for the software stack on Saronic vessels, ensuring mission reliability by implementing various testing approaches and collaborating with cross-functional teams.
Responsibilities:
• Own and drive the test initiatives for Saronic's system software, including the HITL test catalog and station orchestrator, HITL-VM bridge framework, NixOS-based VM integration test suite.
• Design and roll out a unified test strategy that combines our primary tools: Rust unit and property tests, VM-based integration tests, HITL-based tests, and replay/simulation based scenario tests into a single decision tree so that the right test type covers the right risk class at the right cost.
• Build out property-based and deterministic simulation testing across the software stack. Expand coverage to the libraries where invariants matter most (planners, trackers, schedulers, state machines, codecs, IPC framing, certificate/identity stacks) and introduce a shared invariant-testing pattern that other engineers can adopt.
• Stand up fuzz testing infrastructure from scratch. Identify high leverage surfaces, write the harnesses, get them running continuously, and triage or resolve findings.
• Expand the HITL test catalog. Drive coverage into areas currently underserved, expanding VM based integration tests to exercise real hardware paths.
• Treat HITL stations as a first class product. Partner to keep stations healthy, observable, and reproducible; harden the CI scheduler pipeline that owns reservations and execution across multiple physical stations; reduce flake; improve the test result dashboard and analytics that engineers rely on.
• Inject faults, not just inputs. Build out chaos and fault injection capabilities, process kills, network partitions, time skew, CAN bus jamming, sensor dropouts that complement our existing test types and that property tests and HITL tests can both consume.
• Build interfaces between our onboard test infrastructure and our cloud infrastructure test artifact storage, MCAP capture and replay, metrics collection and storage, fleet-data fetch, and the existing CI plumbing so that an engineer can author one test and run it locally, in CI, on a HITL station, or against historical fleet data with minimal friction.
• Work hands-on with engineers across the company to catch real bugs. Pair with feature owners on test plans during design reviews, write the hard tests yourself, and travel to test sites to see your tests in action on real boats when needed.
• Document everything. Maintain the test infrastructure architecture docs, runbooks so that other engineers can keep adding good tests without needing your hands on the keyboard.
• Design, develop, and maintain software systems, using NixOS, for autonomous navigation, control, and communication of surface vessels.
• Collaborate with hardware engineers to integrate software with vessel systems, ensuring seamless operation.
• Implement algorithms for controls and sensor fusion.
• Optimize network communications for low bandwidth/high latency environments.
• Conduct software testing and validation to ensure reliability and performance in real-world maritime environments.
• Participate in code reviews and maintain high coding standards, ensuring scalability and maintainability of software.
• Troubleshoot and debug complex software issues, providing timely resolutions.
• Document software designs, processes, and test results for compliance and knowledge sharing.
• Stay updated on industry trends, emerging technologies, and best practices in autonomous systems.
Qualifications:
Required:
• 5+ years of professional software engineering experience, with substantial time spent owning test infrastructure, V&V strategy, or reliability for a non-trivial production system (robotics, autonomous vehicles, distributed systems, embedded, networking, or similar).
• 8+ years of equivalent experience, including architecture and cross-functional leadership of a verification or platform reliability function.
• Strong programming skills in Rust and/or C++, plus comfort with Python for test orchestration, data analysis, and CI tooling.
• Hands-on experience building and operating one or more of: hardware-in-the-loop test rigs, fuzz harnesses, property-based test suites, deterministic-simulation frameworks, or large-scale simulation/replay pipelines.
• Track record of treating test infrastructure as a real codebase.
• Strong systems intuition: you can read an unfamiliar daemon, find the invariants it actually depends on, and write tests that fail before the bug is fixed.
• Excellent debugging and root-cause analysis skills, with a passion for both 'firefighting' and 'fire prevention'.
• Comfort working in a fast-paced startup environment where the test strategy needs to be designed and shipped, not just discussed.
Preferred:
• Direct experience in deterministic simulation testing.
• Experience with fuzz testing.
• Experience with proptest, quickcheck, or other property-based testing crates.
• Experience with NixOS tests, Nix flakes, and Cargo↔Nix integration.
• Familiarity with robotics middleware and IPC patterns (ROS/ROS2, Zenoh, Redis pub/sub, MCAP).
• Familiarity with embedded Linux, low-level serial protocols (RS-232, CAN, SPI, I²C), and networking fundamentals (TCP/IP, UDP, QUIC, VPNs/overlays, PTP/PPS).
• Experience operating CI at scale (e.g., Buildkite, GitHub Actions).
• Experience with sensor fusion, controls, path-planning, or perception evaluation.
• Familiarity with maritime, aerospace, or other safety-critical operations; knowledge of DoD standards and regulations relating to software development is advantageous.
• A bias toward writing the tooling that lets engineers find their own bugs, rather than being the gatekeeper.
Company:
Saronic is building cutting-edge unmanned surface vehicles that enable maritime security and domain awareness by combining best-in-class hardware, software and artificial intelligence into one scalable, fully integrated platform. Founded in 2022, the company is headquartered in Austin, USA, with a team of 1001-5000 employees. The company is currently Late Stage.