Senior Software Engineer, Operations Tools & Al Enablement

The posting, as Serve Robotics wrote it

At Serve Robotics, we’re reimagining how things move in cities. Our personable sidewalk robot is our vision for the future. It’s designed to take deliveries away from congested streets, make deliveries available to more people, and benefit local businesses.

The Serve fleet has been delighting merchants, customers, and pedestrians along the way in Los Angeles, Miami, Dallas, Atlanta and Chicago while doing commercial deliveries. We’re looking for talented individuals who will grow robotic deliveries from surprising novelty to efficient ubiquity.

WHO WE ARE

We are tech industry veterans in software, hardware, and design who are pooling our skills to build the future we want to live in. We are solving real-world problems leveraging robotics, machine learning and computer vision, among other disciplines, with a mindful eye towards the end-to-end user experience. Our team is agile, diverse, and driven. We believe that the best way to solve complicated dynamic problems is collaboratively and respectfully.

JOB OVERVIEW

Build practical software that makes Robotics Operations more effective. We are looking for a proactive engineer with a product and entrepreneurial mindset: someone who discovers opportunities, anticipates pain points, and turns them into useful, reliable software. You will deliver improvements quickly and own the tools we rely on, including applications originally built with Al-assisted coding.

You will be an engineer embedded with Operations, taking initiative to understand how teams work and where software can make the biggest difference. You will observe workflows, ask questions, and use feedback and data to uncover unmet needs, including problems users have learned to work around. You will help shape what gets built, rather than wait for a fully defined task list. Think like a product owner and execute as an engineer. Connect everyday friction to the bigger picture: delivery quality, operator effectiveness, and the ability to scale. Choose focused improvements that create meaningful value, test assumptions early, and adapt as you learn. We value initiative, product judgment, and demonstrated impact over the length of an engineering résumé alone. Some solutions will start as lightweight prototypes or Al-generated applications. Your job is to bring the engineering judgment needed to make them dependable: understand the code, fix defects, improve the design where needed, add appropriate tests and monitoring, and support the application as operational needs and underlying systems change. You will personally build, ship, and maintain production code. Al-assisted development is encouraged, but you must be able to evaluate the output, debug it independently, and take responsibility for its behavior in production. You will work across several programming languages. Our primary system is Elixir-heavy. Previous Elixir experience is not required, but you should be ready to learn quickly and become productive developing and mai
[…]
equired. This role is centered on building and supporting software for Operations, rather than managing a program or coordinating other engineers' delivery.

Preferred Experience, Qualifications, and Skills

• Experience with operator-facing applications, workflow automation, dashboards, or fleet and robotics tools.
• Full-stack development experience, including user interfaces, services, APls, and data integrations.
• Previous experience developing applications in Elixir.
• Experience taking a prototype or lightly engineered application into dependable operational use.
• Effective use of Al coding assistants, with examples of reviewing, correcting, testing, and maintaining their output.
• Experience owning a product or internal tool from discovery through adoption and iteration, or building useful solutions in an entrepreneurial environment.
• Experience helping non-technical teams adopt Al tools responsibly.
• Robotics, autonomous vehicles, logistics, delivery, or other technology-enabled field operations experience.

What success looks like

• Operations receives useful improvements in short iterations, with feedback shaping subsequent work.
• Important needs and risks are surfaced early, with solutions initiated before they become urgent requests or recurring incidents.
• Tools are adopted and deliver measurable value, with low-value ideas changed or stopped based on evidence.
• Cross-functional partners have clear ownership and fewer surprises as tools and underlying systems evolve.
• High-value internal applications have clear technical ownership and dependable support.
• Al-built tools become easier to understand, test, change, and maintain.
• Changes to shared engineering systems cause fewer avoidable disruptions to Operations tools.
• Teams spend less time on repetitive work and recurring software issues.
• Al adoption produces practical benefits without compromising data handling, reliability, or engineering standards.