Make the problem clear
Start with the context and constraints. Understand the problem before proposing a solution.
Ami connects mechanics, electronics, software and human experience. We welcome people who think deeply, care about details, and want to advance both the product and the organisation behind it.

Start with the context and constraints. Understand the problem before proposing a solution.
Value testing, records and reflection, including experiments that did not work.
Explain interfaces and trade-offs so engineering, design and operations can understand one another.
Respect users, privacy and safety boundaries. Do not build expectations on unverified capabilities.
These are our recruitment directions. Levels, openings, location, compensation and working arrangements are to be confirmed in discussion. Expand a group to see its work areas.
Humanoid structures, CAD, assembly, centre of gravity and manufacturability; turn designs into buildable, maintainable systems.
Discuss this areaActuators, joint selection, transmissions, torque and reliability; translate motion requirements into drive designs.
Discuss this areaControl circuits, power, driver boards, sensors and electrical safety; connect signals and power throughout the device.
Discuss this areaMCUs, device firmware, communications and hardware interfaces, with attention to timing, state and fault handling.
Discuss this areaKinematics, joint trajectories, balance and motion safety; make movement controllable and testable within defined limits.
Discuss this areaHardware–software integration, whole-system testing, fault isolation and validation; connect individual modules into a coherent system.
Discuss this areaClient interactions, device connectivity, state synchronisation and error feedback; make the experience clear and usable.
Discuss this areaService APIs, session and task orchestration, data flows and observability; connect applications, models and devices.
Discuss this areaSpeech recognition, synthesis and evaluation, considering noise, pauses, latency and natural expression.
Discuss this areaWork toward in-house model research through data quality, training, adaptation, evaluation and inference optimisation.
Discuss this areaStudy interaction boundaries, risk detection, exit mechanisms and privacy, alongside access control and security testing.
Discuss this areaUser research, interaction flows, visual interfaces and usability validation; turn complex capabilities into clear experiences.
Discuss this areaTest cases, hardware–software regression, defect tracking and quality records; make issues reproducible and improvements measurable.
Discuss this areaContent, brand communication, channels, user feedback and events; communicate product value and progress accurately.
Discuss this areaFinancial records, budget and cost coordination, documentation and processes; provide clear information for business decisions.
Discuss this areaCandidate communication, recruitment coordination, organisational support and people administration; connect individual growth with team needs.
Discuss this areaYou can introduce your relevant experience and transferable skills. Suitability for a particular role needs discussion of the actual work; this page does not imply an offer.
If the conversation progresses, your contact details will be used to discuss the area, your experience and next steps. Sending an email does not guarantee an interview or offer; response timing depends on the actual conversation.
Contact is by email. There is no on-site CV upload or application-status tracker. You review and send the email yourself, attaching only what is relevant.