Skip to main content

Stack AV

Full-Stack Software Engineer, Machine Learning Platform

Pittsburgh, PA or Remote (Remote)midAdded 2 days ago

About this role

Stack AV is seeking a Full-Stack Software Engineer to build data introspection and visualization tools for autonomous vehicle development. You'll partner across teams to design and deliver scalable solutions that help engineers and leaders analyze large-scale, multi-modal data while maintaining focus on safety and product velocity.

What you'll do

  • Define vision and roadmap for AV data introspection software with cross-functional stakeholders
  • Build and ship full-stack solutions handling video, sensor, and diverse data types at scale
  • Identify gaps in existing tools across different user personas and proactively close them
  • Lead technical discussions and drive solutions with emphasis on engineering excellence
  • Evangelize technical approaches across the company to maximize business impact

What they're looking for

  • Full-stack development (React, TypeScript, Go, Python)
  • Large-scale data handling and processing
  • SQL and NoSQL database architecture and trade-offs
  • Scalable system design and reliability
  • Design trade-off articulation and alignment
  • AI/ML integration in front-end applications
  • Cross-functional collaboration
  • Fast-paced product development
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.

Stack AV

Stack AV builds infrastructure and systems for autonomous vehicles, focusing on the computational platforms that power their operations at scale. The company is hiring Site Reliability Engineers and infrastructure specialists to optimize performance, reliability, and efficiency across their autonomous systems.

View all jobs at Stack AV

Likely interview questions

  • Describe a full-stack project where you processed large-scale diverse data types—what architectural decisions did you make and why?
  • How do you approach selecting between SQL and NoSQL solutions for a new feature, and how do you communicate those trade-offs to non-technical stakeholders?