What is your process for writing post-mortems, and are they shared publicly?
How responsive are people to emails/Slack over the weekends and after 6pm?
What is your build process like?
What kind of diversity programs are there at the company?
What is the most common reason engineers have left this company?
Will I be working with anyone who is remote, or who works from home on a regular basis?
On a scale from 1 to it's-literally-the-worst, how much do you hate giving out your email address?
How often do you open up your inspector tool to bypass annoying shit on websites?
What will happen if you give me your email address?
Want more questions?
Get my full list of questions, and an update every week about engineering teams that are hiring.
Patient engagement platform tailored to underserved people groups
Remote (Global - Requires Overlap with EST)
High Quality Code Base
Work/Life Balance
Team is Diverse
Flexible Work Arrangements
Product-Driven
Continuous Delivery
Actively Practices Inclusion
Ideal for Parents
At CareMessage, we’re building a platform that helps millions of underserved patients improve their health with preventive care and appointment reminders, local resources, and health coaching through text messaging. Given the real-world implications, writing high-quality code that we can ship quickly and sustainably is paramount. Starting with the technical interview process, we require engineers to code. Similarly, we expect them to write tests to cover their code. We have between 95-100% code coverage on our repositories and are thoughtful about how we maintain tech debt, reviewing it regularly and following a defined process to pay it down. Last but not least, we use Ansible and Terraform to maintain our infrastructure as code to minimize misconfiguration issues and have a CI/CD build pipeline that runs in under 20 minutes upon merge. All engineers participate in an on-call schedule, but since we have such a high-quality code base, that means there are rarely major issues.
1 Open Positions
Customer Comes First
Team is Diverse
Committed to Personal Growth
Safe Environment to Fail
Start-to-Finish Ownership
High Quality Code Base
Continuous Delivery
Continuous Feedback
We’re solving a problem we’re intimately familiar with, giving our product and business a unique edge. Traditionally, when deploying applications in production, developers are forced to pick between two extremes: expensive yet simplistic platforms, or complicated, do-it-all-yourself services. Instead, Render takes care of all the laborious work upfront, minimizing the amount of thinking, reading, and clicking Render customers need to do. This makes it easy to get up and running quickly while simultaneously allowing applications to scale and increase in complexity over time, preventing a transition to DIY infrastructure. For example, during the height of the pandemic, many high-growth startups relied on Render to address rapidly changing business needs. And when Heroku ended its free tier, we made it easier than ever to migrate apps over to Render. We’re giving precious time back to our customers so they can focus on what really matters to their business. This clear product-market fit has enabled us to scale quickly – with over 10.5B requests served monthly and 1M+ services created; we’re not slowing down.
We rely heavily on customer feedback and treat Render customers the way we'd like to be treated. We read every tweet, respond to questions from our community, and keep track of what our users need to be successful on Render. Moreover, all our full-stack engineers participate in on-call and support engineering rotations. Customer service is core to UX and a big differentiator in a crowded market like ours.
3 Open Positions
Payment operations software for money movement
San Francisco, New York City, or Remote (US)
Product-Driven
High Quality Code Base
Customer Comes First
Work/Life Balance
Committed to Personal Growth
Flexible Work Arrangements
Promotes from Within
Modern Treasury allows businesses to move money with confidence. Specifically, it’s an API and web application that allows teams to manage the funds in their corporate bank accounts. To give an example: when Airbnb just started out, they didn’t have much business yet, so their founders used hacky solutions like uploading CSVs to their bank portal. However, once there were many thousands of venues and stays, mistakes likely started piling up. (Like missing error notifications when some subset of the payments failed.)
Had Modern Treasury existed then, companies like Airbnb might have used our software as the interface between them and their core bank accounts. Instead, they had to integrate directly with banks that use decades-old mainframe technology, requiring custom work for each bank. As of this writing, Airbnb has a money team of ~150 engineers (>10% of their total engineers) who maintain their integrations with banks all over the world. With Modern Treasury, we’re streamlining payment operations within one interface, helping companies like Gusto and ClassPass reconcile over $2B in funds every month (and growing!).
Product-Driven
Impressive Team Members
Flexible Work Arrangements
Engineering-Driven
Customer Comes First
Creative + Innovative
Work/Life Balance
Ideal for Parents
Before starting Sphinx, we were senior government employees at the Department of Defense, where we ran an in-house software consulting agency for the Air Force. We kept getting thrown massive tire fires within the space portfolio – think needing to fix GPS. Given that we all rely on GPS every second of every day, it’s pretty shocking that in reality, the infrastructure is so fragile. We founded Sphinx in order to solve a lot of the problems we encountered in government, and to bring those solutions to the commercial market.
That status quo of satellite operations is slow, manual, and expensive. This was fine when there were only hundreds of satellites in space, all with limited capabilities and operated by governments and very large corporations. But in 2022, the landscape has drastically changed. The number of satellites in space is increasing by an order of magnitude every year, and newer satellites are increasingly capable of, and sometimes require, rapid and frequent maneuvering. This new reality in space requires a new reality on the ground. Satellite operators need to be able to move vehicles quickly, in real-time – whether it’s to avoid the increasing amount of traffic in space, link up with a refueling station, or maneuver defensively against space debris.
At Sphinx, we’re solving this problem by building a vehicle-agnostic communications infrastructure to allow satellite operators to utilize diverse antenna networks. In both commercial and government use cases, we're creating a modern set of APIs that allow satellite operators to connect to Sphinx. We'll then facilitate all the connections to disparate antennas/antenna networks, and maintain them. Ultimately, our modern technology will help positively shift the paradigm of national security and enable satellite start-ups to more quickly and cheaply command and control their vehicles.
2 Open Positions
Bonded by Love for Product
Creative + Innovative
Customer Comes First
EQ > IQ
Start-to-Finish Ownership
High Employee Retention
High Quality Code Base
Product-Driven
We will always prioritize features that individual developers will love over what large enterprises request, even if it leads to less revenue. We are so developer-focused that one might describe it as an obsession! At the end of the day, whether someone is building for a side project or as a part of a team at a 1,000-person company, the day-to-day problems are the same: devs want to be able to put secrets in and get secrets out, and have it be simple and enjoyable to use.
There are several ways we solicit feedback from our customers and triage it into our roadmap, including an intercom chat, a public community forum, and shared Slack channels. We also have a company-wide product ideation meeting, where anyone on the team can voice ideas they have and thoughts about what we should prioritize for each quarter.
An example of this is when we prioritized building out custom environments ahead of a long roadmap of enterprise features. We heard time and time again that developers wanted to be able to create custom environments outside of the standard “development”, “staging”, and “production” environments, such as CI/CD or QA. We knew how much flexibility it would bring our users so we built it! We strive to always put developers first!
1 Open Positions
Customer Comes First
Safe Environment to Fail
Start-to-Finish Ownership
Promotes from Within
Work/Life Balance
High Employee Retention
Creative + Innovative
Continuous Delivery
As a young child, our CEO and co-founder, Jamie, experienced firsthand how important life insurance is when his father passed away unexpectedly. Thanks to his dad’s planning, his family was able to have financial stability during one of the hardest periods of their lives. At Ladder, we’re on a mission to make life insurance easy, accessible, and empowering with a digital solution. Given the importance of this real-world issue, it’s safe to say that our customers are at the heart of everything we do. In other words, we’re not building for building’s sake. Engineers are encouraged to ask questions, such as “what are we solving for and how does it impact users?” to understand what the higher level intent is behind every decision.
Our roadmap is directly informed by customer needs. For instance, we wanted to reward customers who have healthy lifestyles, and thus a lower mortality risk. This led us to create an iOS App where customers can sync their steps and get a discount for living an active lifestyle.
We also extensively use FullStory, a tool that provides videos of how our customers are interacting with our product. These are shared in our #fullstory Slack channel, where engineers can gain valuable insight into what’s working well, improve pain points, and catch bugs before they become bigger problems. In addition to assigning different engineers to various FullStory videos every day, we also do quarterly week-long on-call rotations so engineers are never far from our end users.
1 Open Positions