Robotics Software Architect (Philippines)

We are seeking a Robotics Software Architect to lead the design, integration, and governance of the software architecture required to transform technology from a prototype status into a field-deployable, configurable, and supportable solution across variable customer environments.

This role is architectural and system-driven, not purely programming-focused. The successful candidate will serve as the critical bridge between commercial deployment requirements and engineering design, ensuring that both software and hardware systems are developed with deployment realities in mind.

The Robotics Software Architect will define and own the software architecture required to meet deployment minimum standards for robotic arms working in industry with AI-enable cameras, lighting, sensors, and edge computing systems, ensuring that field installation is an adjustment, calibration, and commissioning activity—not a redesign effort.

This individual will lead the deliberate development of the architecture that enables:

• Repeatable deployment across customer configurations
• Structured field commissioning and calibration workflows
• Remote diagnostics, monitoring, and support
• Safe, stable, and governed operation in real-world environments

Key Role Description

This is not a computer vision or model development role. This role is for an engineer who:

• Design systems that deploy, not just systems that work in a lab
• Can work across software, mechanical, robotics, and operations teams
• Owns architecture decisions across robotics, controls, data, and operations
• Translates commercial deployment constraints into engineering requirements
• Ensures the product can be installed, calibrated, supported, and scaled without software rework

 Roles and Responsibilities: Framed around a minimum software deployment readiness standards:

1. Software Architecture Ownership for Deployment Readiness

• Ensure software developed supports installation → adjustment → calibration → verification → operation → support lifecycle
• Define modular, scalable system design that prevents per-site software rewrites

2. Systems Integration Across Robotics, Vision, and Customer Environment

• Architect integration between robot arms, cameras, lighting, sensors, and edge computing systems
• Ensure alignment between:
• Physical configuration variability
• Software configuration and state modeling
• Define interfaces between:
• Robotic arm operations/AI-enable camera monitoring
• Customer monitoring/safety systems

3. Geometry/State/Configuration Architecture

• Define a site-aware geometry and state model that captures:
• Robot kinematics and safe zones
• Camera and lighting alignment
• Customer workstation geometry and variability
• Establish a configuration management system that:
• Enables repeatable deployments
• Eliminates hard-coded site dependencies
• Supports version-controlled, validated site configurations

4. Field Commissioning & Calibration Framework

• Architect-guided workflows for:
• Installation setup
• Field calibration (robot, camera, lighting, workspace)
• Acceptance testing and verification
• Ensure all deployment-critical adjustments:
• Are achievable with standard tools
• Are software-supported, not engineering-dependent
• Support repeatable recalibration capability without mechanical rework

5. Deployment-Oriented Controls & Workflow Architecture

• Design system-level workflow coordination across:
• Robotic actions
• Inspection steps
• Operator interactions
• Exception handling
• Ensure software controls support repeatable task execution across customer sites

6. Remote Diagnostics, Monitoring & Support

• Define architecture for:
• Remote system visibility
• Diagnostics and health monitoring
• Controlled recovery and support workflows
• Ensure systems can be supported without requiring on-site engineering intervention

7. Safety, Exception Handling & Escalation Logic

• Architect system states including:
• Normal operation
• Calibration / commissioning
• Fault and recovery
• Safety stop and hazard escalation
• Integrate:
• Customer alert and safety systems
• Hazard detection / escalation logic (future-state ready)

8. Data Architecture & Governance

• Define how system data is:
• Collected (images, logs, calibration, events)
• Stored and retained
• Used for performance monitoring and improvement
• Treat system data as a strategic deployment and performance asset

9. Deployment Readiness & Change Governance

• Define and enforce criteria for:
• Deployment readiness
• Field acceptance
• Ongoing performance validation
• Establish:
• Version control
• Configuration tracking
• Change approval processes
• Ensure continuous improvement without destabilizing deployed systems

Deliverables:

Within the first 90 days, the Software Architect should help deliver:<