Skip to main content

Pickle Robot

Backend Software Engineer – Software Architecture

Charlestown, MA$120k–$177kfull-timemidAdded 1 month ago

About this role

Pickle is seeking a Backend Software Engineer to join their Software Architecture team, specializing in scalable systems for robotic workflows. This role involves collaborating with robotics engineers to develop backend services while emphasizing code quality, system design, and effective communication.

What you'll do

  • Design and build backend services for robotic systems
  • Collaborate with robotics engineers on project execution
  • Own projects end-to-end and ensure high code quality
  • Contribute to the overall strategy and architecture
  • Communicate effectively with team members
  • Impact the performance of autonomous robots in warehouses

What they're looking for

  • Strong software engineering experience
  • Proficiency in backend development
  • Knowledge of system design
  • Experience with robotic infrastructure
  • Ability to work independently
  • Clear communication skills
  • Solid understanding of code quality practices
  • Familiarity with performance optimization

Benefits

  • Hybrid work model with in-office days
  • [unknown]
  • [unknown]
  • [unknown]
  • [unknown]
  • [unknown]
Apply with Autofill

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 Robot

Likely interview questions

  • Tell us about a time you designed and owned a backend system end-to-end. How did you approach scalability and what trade-offs did you make?
  • Describe your experience working with robotics, hardware, or low-level systems. How comfortable are you debugging issues that cross software and hardware boundaries?