Archer
VMS Software Engineer
San Jose, California, United States$142.8k–$220.6kmidAdded 1 month ago
About this role
Archer seeks an embedded software engineer to develop high-reliability real-time systems for electric aircraft. You'll write Modern C++ for Linux platforms, interface with hardware via drivers and protocols, and debug complex hardware-software integration issues using industry tools.
What you'll do
- Develop efficient, robust C++ code for Embedded Linux platforms
- Write drivers and manage communications over CAN, Ethernet, TCP/IP, UART, and custom protocols
- Debug hardware integration and signal integrity using oscilloscopes and logic analyzers
- Design safety-critical software with defensive coding practices and edge-case handling
- Execute within agile sprint cycles with rapid iteration and testing
- Create test automation scripts using Python and shell scripting
What they're looking for
- Modern C++ (C++11/14/17/20)
- Embedded Linux kernel and user-space development
- Python and Bash scripting
- Hardware debugging tools (oscilloscope, logic analyzer, network sniffer)
- Real-time systems and resource-constrained environments
- Driver development and protocol implementation
- CMake, Yocto, GTest, Ansible
- Problem-solving with ambiguity and creative troubleshooting
Benefits
- Base salary range: $142,800–$220,600
- Pay-for-performance culture
- Work on cutting-edge all-electric aircraft technology
- Diverse and inclusive workplace environment
- Reasonable accommodations available for applicants with disabilities
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Archer
Archer develops all-electric vertical takeoff and landing (eVTOL) aircraft for sustainable aviation. The company is hiring engineers across electrical integration, software, aerodynamics, and controls to build and validate autonomous flight systems, propulsion architectures, and aircraft design.
View all jobs at ArcherLikely interview questions
- Walk us through your experience bringing up embedded boards from scratch. What debugging tools have you used most frequently, and can you describe a particularly tricky hardware integration issue you've solved?
- Tell us about a time you had to write a custom driver or reverse-engineer a communication protocol. What was the situation, and how did you approach it?