[Note: we are currently fully staffed for this role, but expect to be hiring for additional team members in the near future. So, we likely won't review/respond quickly, but we WILL look here first when we crank up the hiring machine again.]
Dapster is looking for a Lead Embedded Systems Software Engineer to join our small-but-powerful team. This is an impact opportunity -- we’re very much still an early-stage startup, and you will be working on our foundational technology and products.
About Dapster: Dapster is focused on bringing AI-fueled robotic picking solutions to market. We recently landed a large pilot with a top retailer -- effectively dilution-free funding to develop our core technology.
If you want to do interesting work with a sharp, experienced and humble team, and share in the upside that comes with joining at the earliest stages, we’d love to talk to you. The quick details:
What will you do? Broad ownership of the inner workings of the entire Dapster robotic system (we can go into much more detail live).
What are we looking for?
Excellent C/C++ and Python programming skills in a Linux environment.
Experience writing/maintaining driver-level code for different types of sensors, actuators and communication interfaces like WiFi/BlueTooth, and handling the early signal processing for these devices.
Ability to quickly get up to speed with an unfamiliar device by reading its specification, register map, driver api, and integrate it into the product.
Excellent communication skills
Ability to quickly put together a circuit to electrically interface different devices.
A strong academic and work record (e.g. BS CS/EE with 5+ years of experience or MS CS/EE with 3+ years of experience) or commensurate work experience
Other nice-to-have’s:
Prototyping and soldering skills.
Experience as part of the development team for at least 1 full version of a shipping embedded device.
Dapster is a remote-friendly, hybrid workplace. We maintain a development lab in Palo Alto, CA, and occasionally travel to client sites (mainly Phoenix, AZ). Roles requiring interaction with our physical robots likely entail more in-office work than not. Other roles can be structured to your preferences.
Interested in learning more? Let’s start a conversation -- you can apply directly below or reach out to Scott (one of our founders) with any questions at [email protected].
