Security and Infrastructure Engineer
Corbalt is a small group of technologists working to build better software infrastructure for government. We were part of the tech team that came in to help support the healthcare.gov launch and were inspired by how much everyone cared and worked hard to fix the site (from tech team members, to government contractors, and government employees), and how much progress we all made in a short time.
As we’ve continued to work with the government we focus on opportunities where we can build simple, scalable solutions to help support important government missions like helping people get health insurance (healthcare.gov) and helping ensure healthcare for vulnerable populations (Medicaid). We use innovative technology to create software infrastructure that's easy to use and develop applications that focus on addressing users core needs.
We're a small team with experience at Google, Palantir, Bell Labs, Microsoft, and Silicon Valley startups. We work remotely by default and are spread across states. We look to hire technologists who are passionate about improving public services, love working as a part of a team, enjoy consulting with clients to develop creative solutions to complex problems, and are committed to fostering a kind work environment.
We'd like to hire a software engineer with the following responsibilities, skills, and values.
- Developing software in Go and Python
- Reviewing teammates' code
- Writing design docs to communicate ideas
- Ability to own a project and push it forward
- Ability to work independently
- Experience with engineering best practices
- Growth-oriented mindset
- Intrinsic motivation to learn, grow, and do great work
- Kindness / grit / perseverance / resilience
We have a two-stage hiring process.
The first stage is an informal conversation to communicate what we're doing, clarify any questions, and gauge interest and fit.
The second stage is three components:
- a 10-20 minute presentation to the team describing what you did on a previous project. We're more interested in learning about the work you did and your experience doing it vs. learning about the project overall. For example, a possible time breakdown could be 2 minutes of project overview and 10 minutes on your role and what you did on the project. We'll also leave some time for questions and discussion at the end.
- a 45 minute conversation with another person on the team to get an additional perspective on what our work is like.
- a 4 hr mini-project where we'll work together on a problem based on something we've actually worked on. The goal of this is to get an idea of what working together is like.
Due to contractual obligations, we are only accepting candidates who live within the United States at this time.