Backend Engineer

• Our engineers are responsible for prioritizing, conceptualizing, co-designing, building, testing, and engaging users for any concept we are building out.
• We’re generalists in encouraging each other to experience the full stack,
• but we’re also aware of each other’s preferences in the stack.
• We hope our engineers have more longevity than any one tool we use,
• but here is a sampling of our current thoughts about technology: We live on Python/Django and TypeScript/React.
• We store blobs in Amazon’s S3, munch on them in Amazon’s EC2, develop in Docker, and deploy containers to Amazon’s Elastic Beanstalk.
• We believe PostgreSQL should be the first system you consider when thinking about persisting structured data.
• We clean and centralize data in Amazon’s Redshift, and are able to answer almost any question in SQL.
• We leverage AI in our product and our internal tooling, and faced with a landscape in constant flux, try to pick the right model or agent on a task-by-task basis.
• We have near-full test coverage on the backend, and are making progress on our frontend and integration tests.
• We set up continuous integration and deployment because, while this model comes with its own pains, we’ve disliked being on fixed release schedules on previous projects.
• We like to move fast and support point-in-time recovery :).

B12

Full Stack Engineer – Backend Emphasis