What you'll do
Become a skilled user of the Hivemind SDK and its autonomy modules, building with the same tools the development teams and our customers do.
Conduct knowledge elicitation and applied human factors and front-end analysis with developers as users of the Hivemind SDK, tools such as Forge and Commander, and with other HMIs.
Translate developer, operator, and customer needs into design and development requirements that SDK and HMI teams can implement and test.
Specify HMT requirements for developer-facing and operator-facing interfaces, and review proposed designs against them.
Assess whether delivered tools, code, and systems satisfy the stated user and HMT requirements, and document gaps with recommended remedies.
Define acceptance criteria and evaluation methods for HMT requirements, and maintain traceability from developer and operational need through requirement, acceptance and robustness testing.
Develop and maintain HMT design and development guidance, documentation, and training materials that developers can apply without you in the room.
Represent HMT in design reviews, architecture decisions, and trade-off discussions, making the HMT case in engineering terms.
Convert recurring friction in the development toolchain and the HMIs it produces from one-off complaints into durable, prioritized requirements.
Roll up your sleeves and work alongside the development team as needed, implementing requirements in the code yourself, and working through integration and API issues alongside them, so that effective HMT is built into the user experience from the outset.
Feed implementation constraints and technical realities back into HMT design and experimentation, so that requirements stay buildable.
Support field events and operator engagements, and carry what you learn there into requirements for the development teams.
Travel to company, test, demonstration, and customer locations to conduct project work (approximately 40%). Required qualifications: Engineer II: typically requires a minimum of 2 years of related experience with a Bachelor's degree; or 0 years and a Master's degree; or a PhD without experience. Senior Engineer: typically requires a minimum of 3–5 years of related experience with a Bachelor's degree; or 2–4 years and a Master's degree; or 2 years with a PhD; or equivalent work experience.
A degree in computer science, software engineering, a related field, or equivalent practical experience, with a minor in human factors engineering, cognitive systems engineering, or human-computer interaction.
Hands-on software development experience sufficient to earn credibility with engineers, reason about feasibility and cost, and read the code and interfaces under discussion.
Proficiency in Python and C++, and familiarity with at least one other relevant language and tools, such as JavaScript, C#, HMTL, CSS, or docker.
Demonstrated experience eliciting user needs, translating them into design or development requirements that an engineering team implemented, and assessing whether the delivered system met them.
Working knowledge of human machine teaming and human factors concepts, including collaborative work requirements, and ability to reason about operator-autonomy interaction, not screens alone.
Appreciation for the methods and contributions of human factors practitioners, designers, and operators, and the ability to act as a conduit between engineering, HMT, and customer audiences.
Experience in multidisciplinary settings, and ability to work in complex, ambiguous problem spaces and produce clear and structured artifacts.
Strong teamwork and collaboration skills, and written and verbal communication skills.
- U.S. DoD Secret clearance is required, with the ability to obtain and maintain Top Secret, SCI, and/or SAP-level access. U.S. citizenship required.
- Preferred qualifications:
- Experience in an applications, integration, or solutions engineering role, working between customers and product engineering.
Experience with autonomy, robotics, or simulation software, and with build, simulation, and test toolchains.
Hands-on experience with human machine teaming, MUM-T, human-robot interaction, or applied artificial intelligence, specifically in mission autonomy applications such as UAV Groups 3–5.
Experience with mission planning, C2, and battle management concepts, processes, and doctrine, and with ground control stations or HMIs.
Experience with developer-experience research, developer productivity measurement, or qualitative study of how engineering work gets done.
Familiarity with developer platforms and workflows, such as Git, GitLab, CI/CD, or cloud-native development practices.
Familiarity with traceability methods, or with AI assurance frameworks.
Willingness to use agentic AI to speed the path from design concept to fielded product.
