===About Tempo Automation=== The transition from mainframes to PCs transformed software development by making it possible for software engineers to do 100 versions of their code in a day. Electrical engineers still have a mainframe-like experience when developing electronics. After designing a board, they send it off to a factory, wait a week (or weeks), then get the board back to see the quality of their work. Our goal is to deliver the PC to electrical engineers. We imagine that every electrical engineer with have a Tempo robot on his or her desk where he or she can immediately test out his or her designs.
===What we’re hiring for=== We’re looking to bring on our second full time software engineer to help develop the robot’s software. Your job will be to be to build the software that runs the robot which spans the gamut from low level control systems, writing CAD parsers, and roughing out the front end user interface. A good candidate is clever, adaptable, and flexible.
===What we look for in people=== Robotics requires flexible generalists with a strong math and science background. We want engineers who can pick up technologies quickly, and are capable of debugging across a large stack of software, electrical, and mechanical systems. People who are makers -- robotics is a multidisciplinary field and we value those who have primary skills in one field but complementary skills from other fields. If you’ve switched fields a couple time or have a diverse backgrounds (e.g. dual degrees, changed fields between grad and undergrad) we want to chat. Interest in manufacturing technology. If you geek out over tools, robots, technology, and how it is made we should chat. Those with a strong C/C++/Python experience running on Linux. Javascript and shell scripting capabilities are a big plus. Sysadmin/DevOps skills are also highly desired. Robotics relies heavily on geometry and mathematics. Individuals with backgrounds in computer graphics, VR, AR, gaming, AI, and machine learning are highly desired. Experience building consumer or physical products is a big plus. We’re shipping software on a robot. If you are an embedded developer who has shipped a physical product we should chat. Familiarity or interest in some of the following frameworks/technologies/packages is a big plus but not required: Bottle/Flask
- Meteor
- Robot Operating System (ROS)
- OpenCV
- Point Cloud Library (PCL)
- Numpy/Scipy/PySerial/Pandas/Kivy
- Open Graphics Rendering Engine (OGRE)
- D3/WebGL
- MongoDB
- Eagle/Altium/KiCad general EE CAD