Senior Software Engineer

About Elicit

Elicit is an AI research assistant that uses language models to help researchers figure out what’s true and make better decisions, starting with common research tasks like literature review.

What we're aiming for:

1. Elicit radically increases the amount of good reasoning in the world.
   

   • For experts, Elicit pushes the frontier forward.

   • For non-experts, Elicit makes good reasoning more affordable. People who don't have the tools, expertise, time, or mental energy to make well-reasoned decisions on their own can do so with Elicit.

2. Elicit is a scalable ML system based on human-understandable task decompositions, with supervision of process, not outcomes. This expands our collective understanding of safe AGI architectures.

Visit our Twitter to learn more about how Elicit is helping researchers and making progress on our mission.

Why we’re hiring for this role

Since launching the newest version of Elicit last fall, response has been strong. We introduced Elicit Plus, our monthly subscription plan, and added thousands of paying users in a matter of months as well as hundreds of thousands of new sign-ups. This has been energizing for our team, but we want to ship more useful functionality to our users even faster. We want to add another strong senior-level engineer to our team who’ll help us meet the demand for new features and improved performance.

Our tech stack

• Backend: Node and Python (probably shifting more to Node over time)

• Frontend: Next.js, TypeScript, and Tailwind

• We like static type checking in Python and TypeScript

• All infrastructure runs in Kubernetes across a couple of clouds

• We use GitHub for code reviews and CI

Am I a good fit?

Consider these questions:

1. What are a couple of different ways to write concurrent code in Python?

2. What are the differences between var, let, and const in JavaScript?

3. What are a couple of different web technologies to asynchronously send data from a server to a client?

4. In which situations would you use REST vs. GraphQL vs. RPC?

Strong applicants will find it easy to answer these questions.

What you'll do

You'll own

• Building Elicit into a product researchers can’t live without

  • You’ll fully own shipping useful, exciting features out to users on a weekly basis.

  • You will work on a mix of known features / fixes, prototypes to validate ideas, and exploratory projects in between.

  • Our team is small, so we expect you to appreciate the user needs underlying everything you work on. You should be comfortable making decisions and trade-offs that help us fulfill users’ needs best.

• Keeping Elicit’s bar for quality high

  • You’ll balance shipping features in the short term with building extensible and maintainable systems.

  • You will be responsible for your features in production: they need to be scalable, resilient, and easy to operate.

  • You’ll contribute to discussions around UX, system design, and architecture.

Projects you'll contribute to

You can view sample projects here.

Your first week

• Start building foundational context

  • Get to know your team, our stack, and the product roadmap.

  • You’ll get to know our company documentation and other supporting resources like Supporting Process, not Outcomes.

• Make your first contribution to Elicit

  • By the end of your first week, you’ll have completed your first Linear issue, have a PR merged into our monorepo, gained understanding of our CI/CD pipeline, and learned about our monitoring and logging tools.

Your first month

• You’ll complete your first multi-issue project

  • As you learn the ropes, you’re able to tackle more impactful projects, with input from domain experts where you need it.

• You’re actively improving the team

  • You’ll have gotten into the swing of contributing to regular team meetings a