Skip to main content

Path Robotics

Software Engineer, C#

Columbus, OhiomidAdded today

About this role

Path Robotics seeks a Software Engineer to build React-based front-end interfaces for an AI-driven robotic welding platform, including a cloud authoring tool and factory-floor operator HMI. You'll work across the full stack with TypeScript, three.js, Node.js, and C# in a modern cloud environment.

What you'll do

  • Design and develop React and TypeScript front-end features for customer platform and operator interfaces
  • Build and maintain reusable components in a shared Nx monorepo with MUI and Redux Toolkit
  • Create 3D visualizations using three.js for parts, welds, and robot scenes
  • Collaborate with back-end engineers on Node.js and C# service endpoints
  • Conduct code reviews and ensure quality through automated testing and CI/CD
  • Troubleshoot technical issues and ship features safely using feature flags

What they're looking for

  • React and TypeScript
  • three.js or WebGL for 3D graphics
  • Node.js and/or C# back-end development
  • Git and CI/CD pipelines (GitHub Actions)
  • Docker, Kubernetes, and AWS infrastructure
  • State management and component architecture
  • Relational databases
  • Web accessibility standards

Benefits

  • Daily free lunch
  • Flexible PTO
  • Comprehensive medical, dental, and vision coverage
  • 6–14 weeks paid parental leave depending on circumstances
  • 401(k) retirement plan
  • Employee referral bonuses
Apply on the employer's site

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

Path Robotics

Path Robotics develops autonomous robotic welding systems with adaptive motion planning and AI-driven capabilities for manufacturing. The company is hiring welding engineers, mechanical engineers, machine learning engineers, and technical marketing engineers to advance its mobile robotic welding solutions.

View all jobs at Path Robotics

Likely interview questions

  • Walk us through a time you optimized a React component for performance in a production application—what metrics did you track?
  • How have you handled state management at scale in a monorepo, and which patterns have you found most effective?