Senior Software Engineer
- Silicon Valley, CA, United States
- Menlo Park, CA, United States
- Palo Alto, CA, United States
- Buck build
Want to work on something that matters? Ladder is life insurance built to be instant, simple, and smart. Life insurance is a fundamentally good product for families and communities. Unfortunately, the traditional life insurance process is unnecessarily burdensome, involving in-person meetings with agents, physical paperwork, and 6-8 weeks of waiting. This outdated process has resulted in a $16 trillion coverage gap in the United States.
We are a growing team of innovators going after this huge market by putting the user at the center of product design. We've combined a dead-simple, online application with automatic, real-time underwriting to make instant decisions and provide on-the-spot coverage.
We're looking for experienced engineers who are excited to help us reimagine what life insurance can be.
You may be a great fit even if you don't meet some or any of the following. We'd love to meet you and hear about your unique skillset!
- Implement full-stack features that directly impact our users and business
- Take ownership over our codebase and shape our technical direction
- Mentor and teach other engineers through pair programming, code reviews, and architectural discussions
- Scale our engineering processes as we grow
You may be a good fit if you have...
- Previous experience building production web applications
- Excellent communication skills, especially in a remote context
- Excitement about or previous experience being a technical leader
- Familiarity or experience with our tech stack
- Interest in reimagining consumer financial services
Our engineering values
- Ask Why?: When you are invited to solve a problem ask
why?. Ask questions. Make sure you understand what it is we are trying to achieve with the code you write. Pull in data before and after. Think critically instead of checking boxes on a github ticket. You'll figure out ways of doing things better and become a more useful member of our engineering, product, and design organization.
- End to End Ownership: Engineers solve problems. They do whatever it takes to make sure the problem is solved. Developers write the best code when they fully internalize all the externalities of their code. We want to route all the good and bad things that result from your code back to you to help you learn. When writing code it's good to be thinking about how you will test, deploy, verify, monitor, and evolve it in future iterations with new requirements. Engineers are capable of learning the tools they need to get the job done. Frontend, Backend, Data, ML, Native - whatever. It's all in 1 repo and 1 programming language - go make it happen.
- Blameless: It's important to ship code frequently. It's important to make that process fast and safe. When deploying causes things to break, we tend towards solutions that improve the process rather than telling people to
be careful(that can lead to low velocity). More generally, it's day 1, our biggest opportunities are ahead of us, let's learn as much as we can now so it will benefit us more down the road when we are at a larger scale.
- Third time's the charm: We are building the life insurance company of the future. Instead of burying ourselves in paperwork - let's automate repetitive tasks but only after doing them 3+ times so we understand them and know it's an important recurring problem.
- Bias for Action: Speed matters in business. Many decisions and actions are reversible and do not need extensive study. We value calculated risk taking.
Within one week, you'll:
- be paired with an onboarding mentor - your go-to person for all engineering questions
- begin learning about our codebase, tech stack, and business
- ship & deploy your first user-facing change to production!
Within one month, you'll:
- set up short, medium, and long-term goals with your manager be fully integrated into one of our product teams
- become comfortable with our tooling and processes
- provide feedback about our hiring & initial onboarding processes
Within six months, you'll:
- ship at least one major project from start to finish
- become the subject matter expert of a significant portion of our codebase
- improve our technical and product processes
While it's great if you're already familiar with some of these, we strongly believe that general technical proficiency is more important than knowledge of specific technologies. If the role sounds interesting, please apply even if you don't know any of these technologies!
- Frontend: Clojurescript, React, GraphQL
- Backend: Clojure, JVM
- Infrastructure: Kafka, Docker, Kubernetes, Packer, Terraform, AWS
- Data: BigQuery, Tableau, BEAM
Ladder makes it easy for anyone to buy life insurance. Life insurance is an industry that hasn't changed for many years. We're rethinking the entire process using software. Other life insurance companies prioritize agents' experiences. We're making the consumer experience great instead.
Walk out Wednesday: Every Wednesday, we randomly partition everybody in the company into groups of 3 or 4. Each group goes out for lunch in Palo Alto. It's a fun way to get to know people at Ladder.
Katas: Each month a member of the team will come up with a fun programming challenge. Engineers (optionally) build solutions to these problems. Afterwards, we discuss approaches and solutions together. Past katas have included: finding an appropriate reviewer for a change based on previous commits, building a TCP echo server, and computing transitive dependencies using our code base's dependency graph.
Game Night: We get together monthly and play a variety of board games with pizza.
- Buck build
Skip straight to final-round interviews by applying through Triplebyte.