Full Stack Software Engineer

Who you are

• Bachelor's degree in computer science, computer engineering, or a related field, or equivalent practical experience (bootcamp plus portfolio, research, or shipped projects are fine)
• Comfortable writing software in TypeScript or Rust and component-based UI (React or similar). You can read other people's code and leave it better than you found it
• A track record of picking up a new tool, language, or domain and becoming useful with it, whether through a class project, internship, research, open source, or something you built because you wanted it to exist
• Project or professional experience with Rust, React, TypeScript, or Python
• Exposure to desktop wrappers (Electron, Tauri), backend development, or databases
• Coursework or projects touching networks, operating systems, or distributed systems
• Experience pairing with AI coding tools and being honest about what they got wrong

What the job involves

• Parallel Systems is seeking a Software Engineer I to join our Interfaces team
• The Interfaces team builds the software people use to operate, monitor, and manage our vehicles and fleet, including our main operator application and the product surfaces that will grow into enterprise customer software
• This is a junior role with real ownership
• You do not need years of production experience, but you do need high agency, clear communication, and the hunger to learn fast
• We care more about how you work than how many years you have been paid to work
• Build and improve the operator and customer product platform in TypeScript, React, and Rust
• Ship features in our Electron operator application
• Work with product and vehicle/systems engineers to turn operational needs into clear, reliable interfaces
• Own features end-to-end: understand the user, implement, test, document, and follow through after merge
• Grow into full-stack product work as we expand enterprise software, including data models, APIs, and the performance and reliability of software that talks to the real world
• What Success Looks Like:
• After 30 Days: You've set up your environment, learned how operators use our application, and shipped your first changes to the software platform. You're asking good questions early and building relationships with product and vehicle/systems engineers
• After 60 Days: You've owned a feature end-to-end, from understanding the operator's need through implementation, testing, documentation, and follow-through after merge. You're reading and improving code across the Interfaces codebase
• After 90 Days: You're a reliable contributor to the operator application, independently identifying and fixing problems without waiting to be assigned. You've started contributing beyond the UI, such as data models, APIs, or performance and reliability improvements for our enterprise software