> Markdown version of [/jobs/ext/4368595-software-engineer-ii-offboard-python-application](https://www.wearedevelopers.com/jobs/ext/4368595-software-engineer-ii-offboard-python-application). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer II - Offboard Python Application - **Company:** Latitude Inc - **Location:** Allen Park, MI, United States - **Experience:** Experienced - **Salary:** $150,320 - $225,480 - **Contract:** Permanent contract - **Skills:** Amazon Web Services, Computer Engineering, Python (Programming Language), NumPy, Kubernetes, Information Technology - **Published:** October 20, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=eef7c57efa38d6e8 ## About the Role * Bachelor's degree in Computer Engineering, Computer Science, Electrical Engineering, Robotics or a related field and 4+ years of relevant experience (or Master's degree and 2+ years of relevant experience, or PhD) * Expertise in writing Python code that's efficient, well-documented, and well-tested * 2+ years' experience writing scalable applications that execute in a cloud or HPC environment * 2+ years' experience writing software that interacts with AWS and/or GCP services * Familiarity with NumPy and scientific programming * Willingness and desire to learn how onboard and offboard components interact with each other and propose solutions to improve how developers and testers work with both systems Nice to have (optional): * C++ development experience * Experience with Kubernetes ## Description * We also can't build it all, so we want to make the framework well-documented and as self-serve as possible for others to extend it (while being there to answer questions). For example, when there's a new portion of the autonomy stack, we want that autonomy team to be able to update resim to add it in themselves so that they can iterate quickly. * In order to run logs through resim, we need to first know what logs are interesting. You'll contribute to the ecosystem of how we manage storing and searching for these logs efficiently, including how we automate indexing the interesting actors and interactions in a scene and how we determine our dataset coverage. * Once we've run resim, we want to do something with the updated logs. Frequently this involves metrics to analyze the AV's performance; these metrics could range from low-level performance of a particular detector in the stack to if the AV is meeting high-level business objectives. You'll both work on the sim/resim cloud framework implementation to make this easy for all developers to add in their metrics and support the metrics implementation themselves as needs arise.