Modernizing the PropTech supply chain
Phoenix (Gilbert), AZ or Austin, TX or Remote (US/Canada)
It’s safe to say that at Sibi, shipping is our heartbeat. We love quick iterations that refine our assumptions based on our learnings. That said, it’s not a madhouse. We lean heavily on feature flags and testing in production. If something goes wrong, we’re able to simply turn it off. We view everything we write as a hypothesis, and the goal is always to validate our assumptions in tiny bits and learn from each iteration. At the end of the day, if something goes wrong, recovery time is always more important to us than perfection. We work hard to create an environment where it’s safe to fail (see above).
Shipping code is the most visible way that engineers contribute to the success of Asana, and doing so in a fast and sustainable way is key.
Shipping fast starts with serious investment in tooling, such as continuous deployment with multiple pushes per day. It also takes focus and flow, like the kind you can have during our “No Meeting Wednesdays.”
But shipping fast and sustainably takes more than just effective work. When we’re focused, we write higher-quality code, and this translates to less technical debt, faster iteration, and less time fighting fires. While lots of hours in the office lead to the illusion of a lot of work, it often results in just a lot of energy spent treading water.
This is a long-term investment against the pervasive misconception that shipping fast means working unsustainably. Software isn’t going anywhere, and Asana’s engineering culture aims to support people to work well for decades to come.
33 Open Positions
Patient engagement platform tailored to underserved people groups
Remote (Global - Requires Overlap with EST)
We often ship to production multiple times a day and invest in automated testing, monitoring, and reporting (we use CircleCI for CI/CD). Engineers own their code’s quality throughout the software development process and we avoid latency by keeping CI under 30 minutes. When Jeremy (VP of Eng) first started, it was taking an hour and a half. We invested resources, refactored, and it now takes around 12-15 minutes to run our full test suite, build, and deploy.
1 Open Positions
As a company, we thrive on solving interesting, complex problems with creative solutions that thrill our users. In this industry, so much is new and we rely on our partners to tell us what they need, what problems they’re facing, and how we can best help them grow. As Alexandra, our Senior VP of Partner Success says, “There’s always a curveball that comes our way – like new tax rules going live that we need to accommodate or an operator wanting to launch delivery for the first time. What unites us at Jane is meeting these challenges head on with optimism and excitement.”
On the engineering team, we work on sprints primarily around planning, but we push to production every day. We strive to efficiently prioritize the features in our development pipeline and deploy as quickly as possible. The quicker we have a feature out, the quicker we can start iterating to provide our users with the functionality they really want. That’s not to say we’re not pragmatic! We take test coverage seriously. Millions of end users depend on our app, so if a bug happens during checkout, we’re losing people real business.
Still, we’re not fearful about deploying (and deploying quickly) because we trust our deployment process. Abe and Andy are always on-call and everyone else on the engineering team is on a weekly rotation. If you’re on-call, you’ll cycle in to help with our error alert feed. This helps expose everyone to different parts of the codebase, yet everyone has support should they need help figuring out an issue.
1 Open Positions
We have built a continuous integration system and strongly believe that our shipping velocity differentiates us from our peers. As an engineer, you can expect to push to production multiple times a day. We have a lightweight process to ship through the different stages of our pipeline and no explicit separate release is needed.
We also run a mature test suite on all code commits, which we monitor continuously with failures fixed within a certain SLA. Tests take minutes to run with an expectation that they should be fast, reliable, and not the long pole to pushing features.
Check out our roadmap, which we recently introduced to detail features as they are rolled out. We keep a tight feedback loop with our users, and build all features with them in mind.
10 Open Positions
Part of our first sprint on every project is to push an MVP version of their product. We do this through multiple avenues, whether it’s using Netlify Deploy, GitHub Actions, or TravisCI. Our chosen method of delivery depends on the client team and their product, but we believe it’s the most important step for getting the feedback we need and streamlining our development process.
Our approach to continuous delivery is a core part of our product development process. From the beginning, we’ve invested in multiple levels of automated testing, monitoring, and reporting. For example, we build on Blaze, which allows for fast, deterministic builds. We use Kubernetes to have parallel builds and we have a test leaderboard where we remove flaky tests. Engineers are responsible for owning their code’s quality throughout the software development process. Pull requests are approved by one reviewer and then automatically merged into the queue and deployed. We also actively use A/B tests and feature flags to get code safely into production quickly and often.
We raised a $100M Series D in October 2021 and are excited about modernizing the insurance industry. If working in a fast-paced, mission-driven environment speaks to you, we encourage you to check out our open roles!
Want to List Your Company?
Submit a team profile!
Select 8 Values
Contact me (Lynne 👋)
Qualify Your Values
Reach Thousands of Devs
Find Value-Aligned Candidates
Have Meaningful Initial Conversations
Don't Fill Roles, Hire Teammates
You can post as many job openings as you want.