Pickle Robot
Backend Software Engineer – Autonomy
About this role
Pickle is seeking a Backend Software Engineer to enhance their autonomy team by developing scalable backend systems for robotic workflows. This role emphasizes collaboration with robotics engineers and demands a focus on code quality, system design, and the intersection of software engineering and robotics.
What you'll do
- Design and build backend services for robotic systems
- Collaborate with robotics engineers
- Ensure high code quality and system performance
- Contribute to scalable task planning systems
- Work closely with hardware components
- Own significant parts of the codebase
What they're looking for
- Backend engineering expertise
- Strong software development practices
- Knowledge of robotics infrastructure
- Ability to work in a collaborative environment
- Focus on system design and performance
- Experience with scalable systems
- Proficiency in coding languages relevant to backend development
- Understanding of hardware-software integration
Benefits
- Impact on real-world robotic operations
- Collaboration with a tight-knit engineering team
- Opportunities for professional growth
- Hands-on experience in robotics
- Exposure to innovative technology in production environments
- [unknown]
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.
Pickle Robot
Pickle Robot builds warehouse automation robots and the software infrastructure to operate them at scale. The company is hiring simulation engineers, robotics software engineers specializing in ML and grasping, DevOps engineers, and backend engineers to develop cloud-based systems, robotic workflows, and human-robot interaction platforms.
View all jobs at Pickle RobotLikely interview questions
- Can you describe your experience designing scalable backend systems? How did you approach performance optimization and reliability?
- Tell us about a time you worked closely with hardware engineers or a team outside software. How did you bridge the gap between their needs and your technical implementation?