BuildBook helps residential construction companies and their clients collaborate more effectively, make better decisions, and simplify the construction process. Builders love us because we help them minimize miscommunication that leads to costly mistakes, make more money, and delight their customers. Homeowners love us because we give them a feeling of control and help make renovation less stressful.
This industry is full of older “kitchen sink” style software products that are expensive, dated and difficult to use. Most people who need this software are non-technical and struggle on a daily basis to keep track of the details within their business. These struggles are where the errors typically come in.
Our mission is to create intuitive software that is easily adoptable by builders and their clients alike, and improves the outcomes for both sides.
Our end users are small business owners and their clients. Every change we make, every feature we add has a visible, direct impact on the bottom line of our customers. You will be able to see your work being used by real people and see the impact it has on their lives. Our success as a company is directly linked to the success of our customers. We’re only doing well if they’re doing well.
Our core technology is Ruby on Rails and ReactJS on the web, along with a React Native mobile app built on top of Turbolinks iOS/Android. You’ll be joining us in a period of rapid growth, so your primary directive will be to roll up your sleeves and build stuff.
Our goal is for our product to be invisible to our users - it shouldn’t get in the way of their work, it shouldn’t be confusing, it shouldn’t require training. That requires us to be very considerate of our experience, very collaborative in how we build our software, and very close to our customers through the sales and support process.
You’ll work closely with business, design and customer support to craft the future of our product line, and occasionally spin up wholly new products and codebases. At a minimum, you’ll need to be able to use your experience to work through ambiguity, identify issues, and offer suggestions.
Our team is small but growing, and our roadmap is full of so much more than we could ever build right now. In joining us, you’ll have an outsized impact on the success of the product and company.
We’re looking for someone who is prolifically productive - which generally means you’re quite comfortable with Rails and/or React (or something similar, like Vue), you know how to put things together, and you can get things done.
We’re looking for someone with experience creating and shipping software in a production environment, and can show us or talk to us about it. You don’t need to be a super senior expert. We have no years of experience or educational requirements. We don’t do whiteboard interviews or algorithm lottery questions. Instead, we think the strongest indicator of whether you can do this type of work is whether you’ve successfully done this type of work before.
Our company is fully remote, and has been since before COVID. Our only current limitation is that you’re based in the continental United States.
We’re looking for someone who works and communicates well with others. Building software is a collaborative process; it requires a diverse team with different types of experts who all work together regularly (and sometimes have to disagree and commit
). Teamwork like this is even more important in a distributed remote environment, where effective collaboration is a bit more challenging.
We’re looking for managers of one
. We’re too small of a company right now for a heavier structure, and self-management and self-motivation are strong characteristics of success in a remote working environment. This also means you’ll have a lot of autonomy in how to get your work done both logistically and technically.
Send us your resume, tell us a bit about yourself, and also include a short description (a few paragraphs max) about some piece of software that you were really proud of creating. It could be as small as a code snippet or large as a whole project. What did it do? What was special about it and why are you proud of it?