About the Position
EquipmentShare's goal is to be the best platform for contractors to rent and manage their assets. We're looking for an experienced back end engineer to help build out this platform. On the back end, almost all of our work is in Python.
Example situations that you could build tools for:
We're looking for people who don't need to be managed. We'll point you in the right direction, and give you the freedom to make decisions and execute. We're a startup, and everyone wears many hats. Most of us have areas that we have ownership of, but as a team we're very flexible.
Communication is especially important for a remote team. You need to detach your ego from your ideas. When communicating by text, you assume the sender has good intentions. You know that text is a poor medium to convey emotions, and you're not quick to anger with someone offers honest criticism. Similarly, you know that words have meaning, and you choose them wisely.
You care about best practices, and you continuously try to improve yourself. You value automated testing, and you understand that it's important to be able to make changes without fear of uncaught regressions.
You should have several years of development experience, and be comfortable working with a team that moves very quickly.
We've operated as a remote team from the beginning, and each person is encouraged to work in an environment where they're comfortable. Most of the engineering team lives around Kansas City or Columbia, Missouri but we don't spend much time in the office. We do have a lot of flexibility in our schedules, but currently we're only considering applicants who live within 2 hours of Central timezone. At this time we are only open to residents of the USA.
We don't like to draw out the hiring process. Assuming everything goes well, we'll respond to your application within 48 hours to schedule a video call. Next up is a group interview, where you'll get a chance to meet 3-4 other developers. We'll talk about your past work, your opinions, and how you might approach potential problems. After that, we'll do a pair programming session. This consists of 2 hours working with one of our developers to implement a potential feature in one of our projects. The last step is a meeting to discuss working together.
Compensation, Benefits, and Perks