> Markdown version of [/jobs/ext/1313706-senior-software-engineer-handheld-data-collection-systems](https://www.wearedevelopers.com/jobs/ext/1313706-senior-software-engineer-handheld-data-collection-systems). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Engineer, Handheld Data Collection Systems - **Company:** ANVILS AND ROBOTS LLC - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Cloud Computing, Data Infrastructure, Sensor Fusion, Software Engineering, Technical Data Management Systems, Information Technology - **Published:** July 17, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=b54be5524b3a7c05 ## About the Role * You have genuine, provable depth in at least one of the following, along with familiarity with several of the others: + Perception/robotics systems (SLAM, VIO, sensor fusion, mapping) + Embedded application development: you have gotten real applications built, deployed, and running reliably on constrained or embedded hardware + Cloud scale pose estimation or perception pipeline engineering: building systems that turn sensor data into trustworthy estimates reliably at scale + ML workflow, training, and deployment engineering + Physical AI and robot learning deployment, for example VLA style policies, getting a trained model to actually make a robot do something * You can operate as a team of one across teams you don't manage, building enough technical credibility in each domain to know when something's actually wrong versus just unfamiliar to you. * You default to shipping the smallest thing that actually closes an integration gap, rather than hacking something bespoke every time or overbuilding a general platform nobody's asked for yet. * Based in or willing to relocate to Taiwan, the USA, or Trinidad & Tobago. This is the same role and scope regardless of location., * Master's degree in robotics, computer science, electrical engineering, or a related field - or a bachelor's with equivalent hands-on depth. A PhD is not required; this is a product integration role, not a research role. * Years matter less to us than trajectory. The typical shape is 3-5 years of engineering experience, but 2-3 unusually fast-growing years count fully if they were spent working directly alongside a staff or principal engineer on a shipped robotics or perception product. Our ideal candidate has been the second chair on a real integration effort - watched how the cross-team calls get made, made a growing share of them under a senior engineer's cover - and is ready to own the whole thing for the first time. ## Description * You have done systems or product integration work for a robotic or perception based product before. You have been the person who made disparate technical pieces (hardware, perception, software, sometimes ML) work together into something a real user relied on. This matters more than depth in any single domain., * Not a role where you'll personally develop the core SLAM algorithms, train the models, or design the chip. Those are owned by dedicated specialist engineers and teams. Your job is integration and systems and product judgment across their work, not doing their jobs for them. * Not a management role. No direct reports today. You will drive alignment and technical decisions across teams you have no formal authority over. The "tech lead" part of this role is earned through judgment and trust, not a title. * Not a narrow software engineering role focused on one clean layer of the stack. If you want to specialize in a single domain and hand off everything else, this isn't the right fit. * Not a role with mature ML and data infrastructure to inherit. Where that does not exist yet, you are building it, not maintaining someone else's. ## Related Videos - [Robots 2.0: When artificial intelligence meets steel](https://www.wearedevelopers.com/videos/1452-robots-2-0-when-artificial-intelligence-meets-steel) - [Robots are coming into the wild! Full-Stack Robotics Engineers, be ready!](https://www.wearedevelopers.com/videos/479-robots-are-coming-into-the-wild-full-stack-robotics-engineers-be-ready) - [Beyond Dashboards: Fixing Text-to-SQL with Semantic RAG](https://www.wearedevelopers.com/videos/2036-beyond-dashboards-fixing-text-to-sql-with-semantic-rag) - [Green Cloud Computing](https://www.wearedevelopers.com/videos/592-green-cloud-computing) - [Data: The Deciding Factor in AI Success](https://www.wearedevelopers.com/videos/100310-data-the-deciding-factor-in-ai-success) - [Code to Road in < 12 hours](https://www.wearedevelopers.com/videos/1082-code-to-road-in-12-hours) ## Related Articles - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this)