Skip to main content

Netradyne

Founding Product Engineer

San Diego, California, United StatesFrom $190kmidAdded today

About this role

Netradyne is building a new Physical AI product line for workplace safety monitoring. You'll be a founding engineer owning end-to-end problems across edge devices, cloud infrastructure, and user-facing dashboards—moving fluidly between backend and frontend as the product demands.

What you'll do

  • Design and build cloud ingestion pipelines for real-time event streaming and time-series storage
  • Develop multi-tenant identity, access control, and SSO systems for multiple customer organizations
  • Create operations dashboards with real-time event feeds, alerts, and risk summaries
  • Build compliance analytics and reporting features for safety tracking and audits
  • Implement agentic features and conversational interfaces over safety data
  • Conduct customer pilots, instrument usage metrics, and iterate based on field feedback

What they're looking for

  • Full-stack systems thinking across edge, cloud, and frontend
  • Cloud platforms (AWS) and containerized deployments (Docker, Kubernetes)
  • Real-time data ingestion and time-series databases
  • Multi-tenancy and identity/access control architecture
  • Frontend frameworks and UI/UX design for operational dashboards
  • CI/CD pipelines and infrastructure automation
  • AI/ML integration and agentic systems
  • Direct customer engagement and product iteration
Apply on the employer's site

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

Netradyne

Netradyne builds products that require hands-on technical support and lifecycle management, with a focus on installation, testing, and continuous improvement. The company is hiring Product Success Engineers and other technical roles to support product development, resolve issues, and collaborate across global teams.

View all jobs at Netradyne

Likely interview questions

  • Describe a time you owned a problem end-to-end across different technical domains—how did you approach it?
  • How do you decide whether to invest in infrastructure robustness versus shipping a feature quickly?