Senior Robotics Solutions Engineer

PackageX is building the Physical Logistics Execution Platform for enterprise teams operating across manufacturing sites, distribution centers, warehouses, retail locations, and logistics-heavy environments.

Our platform uses Vision AI, workflow automation, mobile execution, and integrations to help companies digitize, execute, and verify physical operations at the point of work, creating trusted evidence of what happened across their operations.

Our operating model is simple: Execution. Verification. Evidence.

PackageX is extending its platform from perception into action. Our systems identify, classify and verify what is happening on a warehouse floor. We are now closing the loop, taking that output and driving the physical equipment that acts on it.

We are hiring a Senior Robotics Solutions Engineer to lead that work in the field. You are the person who walks into an enterprise distribution center, understands their automation cell in depth, designs the integration between their robotics and our platform, and then builds it.

This is a senior, customer facing engineering role. You will spend real time on customer floors alongside distribution directors, industrial engineers and IT leadership, trusted to represent PackageX technically without supervision. Between site visits, you build.

We are starting with palletizing and pallet sorting applications in high volume distribution, and expanding from there into case and tote auditing, pick and pack validation, and material handling equipment

▪ Production experience programming and commissioning industrial robotic arms. Yaskawa Motoman, Fanuc, ABB, KUKA or Universal Robots. Coursework and hobby platforms do not count here.

▪ Fluency in robot motion. Kinematics, frames and tool center points, path planning, singularities, payload and reach limits, collision avoidance, and pattern logic for palletizing and depalletizing.

▪ You have used a teach pendant in anger, and you know exactly why a pendant program and a cell actual behaviour drift apart over years of production.

▪ Real functional safety knowledge. ISO 10218 and ISO TS 15066 where collaborative operation applies, risk assessment methodology, safety rated monitored stop, category and performance level reasoning, and safety PLCs. You can explain to a plant engineer why your design is safe, and stay standing under cross examination.

▪ Controls integration experience. PLCs, industrial protocols, sensors, conveyors, sortation, and the electrical realities of a working cell.

▪ ROS or ROS 2 in production. Equally useful: you know when ROS is the wrong answer for an industrial cell, and you say so.

▪ Strong Python and C++ on the robot side.

▪ Production services in TypeScript, Node, Go or Python, and fluency with event driven integration. REST, gRPC, MQTT, WebSockets.

▪ Able to stand up a functional operator UI in React or similar without a designer holding your hand.

▪ Comfortable working next to computer vision systems. You do not need to train models. You do need to reason about latency, confidence thresholds, false positives, and what a vision system uncertainty means for a machine that is about to move.

▪ You are genuinely good in a room. You can talk to a distribution director about throughput and cost, then walk twenty feet and talk to a maintenance technician about why the gripper drops every fortieth pallet. Both of them should want to talk to you again.

▪ You interview well. You ask the question behind the question, you notice when an answer is a guess wearing the clothes of a fact, and you keep pulling until you have the real constraint. Undocumented systems give up their secrets to people who are patient and specific.

▪ You have delivered onsite for enterprise customers and you understand what it costs them to have you on their floor. You work around their shift patterns, not the other way around.

▪ You write things down in a way that another engineer, and a customer executive, can act on.

▪ You can tell your own leadership that a scope is not achievable in the timeline. Early, with evidence, before it becomes a crisis.

▪ You think about the second customer while building for the first. Which parts of this belong in the PackageX platform as reusable robotics capability, and which parts are honestly bespoke to one cell.

▪ You can hold a commercial constraint in your head while making a technical choice, and explain the trade to someone who is not an engineer.

▪ You have opinions about what we should not build.