UFORCE - Senior Software Engineer
Requirements
• 6+ years of backend or full-stack engineering experience delivering production systems. • Strong hands-on experience with Node.js and React in production environments. • A product-focused approach: you understand user needs and turn complex workflows into practical, usable software. • Experience building and operating API-first services, including versioning, backward compatibility, and contract-driven development. • Practical experience with Docker and Kubernetes, including deployments, debugging, and operational monitoring. • Strong end-to-end engineering ownership, from discovery and technical design to rollout and continuous improvement. • Ability to work closely with users, translate operational feedback into technical requirements, and validate whether a solution delivers the intended outcome. • Clear written and verbal communication, particularly when explaining interfaces, constraints, and technical trade-offs across teams. • A practical approach to debugging and reliability, supported by useful telemetry, clear documentation, and follow-through. • What success looks like • Key pre-flight and post-flight workflows are automated, reducing manual steps and reliance on tribal knowledge. • Mission readiness and turnaround time improve, with clear before-and-after measurements. • Operators can complete routine configuration and mission setup independently, using consistent workflows and practical guardrails. • Teams have reliable operational data and review workflows to identify bottlenecks and prioritize improvements. • Delivered capabilities work in real field conditions and are supported by useful telemetry, concise runbooks, and clear ownership. • The nature of combat has changed. • Tomorrow’s battlefield success depends on autonomy, speed, and adaptability. • And UFORCE is ready.
Responsibilities
• Build and improve pre-flight and post-flight workflows, including automated checks, configuration, mission package handling, log capture, and post-mission data synchronization. • Develop operator-facing interfaces and guardrails that make routine workflows intuitive, consistent, and less dependent on engineering intervention. • Standardize configuration and mission setup patterns to reduce manual work and variation between crews and platforms. • Build operational analytics that help teams understand readiness, workflow performance, turnaround time, and the impact of connectivity constraints. • Work directly with operators to identify friction, translate field feedback into requirements, and validate improvements in real operational workflows. • Design and maintain APIs, schemas, and event models that enable reliable integrations and parallel development across teams. • Own delivery from discovery and technical design through implementation, rollout, observability, and iteration. • Make architectural trade-offs explicit, balancing product needs with compatibility, deployment constraints, and supportability in the field. • Create concise runbooks, checklists, and troubleshooting guidance that help crews operate independently and reduce avoidable errors. • Unblock teammates and partner teams through clear interfaces, ownership boundaries, and practical engineering standards.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT