- $100k - $200k
- 0.1% - 1.0%
Clever is seeking a DevOps Engineer to join our team.
As a DevOps Engineer, you will help continually improve our technical infrastructure to increase its stability. This includes stabilizing the infrastructure around our legacy WordPress website, which we are incrementally rebuilding in Gatsby. It also includes spearheading our transition to describing our infrastructure as code using Terraform and moving our Dockerized applications to our ECS cluster backed by Fargate. (We’re an AWS shop)
We’re a small team, and we value sharing context. We want everyone on the team to have an understanding of our infrastructure. To that end, we’re looking for someone with strong communication skills for this role. You should enjoy teaching and mentoring others.
- ECS backed by Fargate
- Postgres / Amazon RDS
- WordPress / php
About Clever Real Estate
We help folks save money on real estate commissions while connecting them with the best real estate agents in their area.
Our concierge team of licensed real estate experts answers customers' questions, offer advice, and learn exactly what they're looking for in an agent. We decide which agents to recommend based on customers' specific goals and needs. They get to meet each agent and decide which one they'd like to work with. They can also request to be introduced to more agents if they don't feel they've found a fit.
In all cases, our service is completely free for customers. We make money by taking a percentage of the commission made by the real estate agent. Agents happily pay this in exchange for the consistent deal-flow that we send their way.
Since our inception in 2017 we've helped homeowners buy and sell over a billion dollars in real estate, while saving over $25,000,000 in real estate fees.
We've built a product that helps consumers save thousands, while providing a consistent source of business for great agents.
We believe in shipping code frequently and measuring outcomes. We take a validated-learning approach to writing code.
We value having a bias towards action and a drive for documenting your work.
We love pair programming for sharing context, and we regularly invoke
swarming — or, flash collaboration — to unblock each other. We believe that the improvement of daily work is work, and it should be at the forefront of our minds all of the time.
Here's an excerpt from our Blameless Post-Mortem template that is particularly illustrative of our team culture:
Remember: We're trying to prepare for a future where we're as humanly fallible as we are today. It's not productive for us to come out of this meeting with a decision tobe less stupid
orbe more careful". Rather, we should try to identify fool-proof countermeasures that we can use to avoid issues in the future. This may involve an automated system or a documented process that captures organizational learning.
We should explicitly disallow the phrases
would have and
could have. It's much more productive to think about why we chose a course of action and what we'll do in the future to improve our incident prevention and response practices.
Finally, remember that this meeting is not about naming, blaming, and shaming others. It's about improving ourselves as a team."
Skip straight to final-round interviews by applying through Triplebyte.