- $100k - $150k
- 0.1% - 0.5%
We’re looking for someone with backend engineering experience, ideally in Django, who has a passion for building stable, well-tested code.
Our Platform team is small and highly collaborative. We seek to continuously improve our systems to reduce toil for ourselves and others. The work we do enables our sales team to match customers with the right real estate agent within a matter of minutes.
We do a lot of pair programming. We also limit time spent in meetings by having
no meeting days twice per week. Effective meeting prep is our friend -- we often end meetings early once the objective is accomplished.
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.
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.