Skip to main content

Skild AI

Full Stack Engineer (Frontend & Android Focus)

San Mateofull-timemidAdded today

About this role

Skild AI seeks a Full Stack Engineer to build web and Android interfaces for monitoring robotic fleets, emphasizing real-time 3D visualization, offline-resilient networking, and performance optimization across diverse hardware platforms.

What you'll do

  • Design and develop responsive, high-performance web and Android applications for fleet monitoring and control
  • Implement 3D visualization tools rendering maps, point clouds, and real-time robotic perception
  • Engineer robust data synchronization layers for network-denied or intermittent connectivity environments
  • Optimize rendering pipelines and application logic for varied hardware from workstations to mobile devices
  • Work across the full stack with emphasis on TypeScript/JavaScript frontend integration with backend APIs
  • Collaborate with robotics researchers and ML engineers to define APIs supporting real-time visualization

What they're looking for

  • JavaScript/TypeScript
  • React and modern frontend frameworks
  • 3D graphics (WebGL, Three.js, Pixi)
  • Android development (native or cross-platform)
  • Backend development and API integration
  • Database design and management
  • Docker containerization
  • Offline-first architecture and state management
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

Skild AI

Skild AI builds software and systems for general-purpose robotic intelligence, including simulation environments for training, manipulation controllers, perception stacks, and foundation model integration. The company is hiring simulation engineers, robotics engineers, controls specialists, computer vision researchers, and application engineers to develop and deploy production-ready autonomous robot systems.

View all jobs at Skild AI

Likely interview questions

  • Walk us through your experience building 3D visualizations in the browser—which libraries have you used and what performance challenges did you encounter?
  • Describe a time you architected an offline-first system. How did you handle data synchronization and conflict resolution?