Cette offre d'emploi n'est plus disponible
À propos
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: 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.
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. To that end, we need a strong front-end engineer who'll help us meet this demand while pushing the bar for quality and user experience even higher. Our Tech Stack
Frontend: Next.js, TypeScript, and Tailwind
Backend: Node and Python
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 the questions: In what situations will a React component re-render?
What are the differences between flexbox and grid layout in CSS. When would you use each?
What are Web Workers for and in what situations are they helpful?
How would you create a drop-shadow effect using Tailwind?
If you have a solid answer for thesewithout reference to documentationthen we should chat! Location And Travel
We have a lovely office in Oakland, CA, but we don't all work from there all the time. It's important to us to spend time with our teammates, however, so we ask that all Elicians spend 1 week out of every 6 with teammates. We have a quarterly team retreat, normally in and around the SF bay area.
We have quarterly co-working weeks (offset from the team retreats) in our Oakland office.
If you come to the retreats and co-working weeks, you'll meet our expectations for in-person time!
There is flexibility around the specifics here: if you're not sure you can make this work, get in touch.
What You'll Do
You'll Own
Building Elicit into a product researchers can't live without You'll work with a modern front-end stack (React, TypeScript, Chakra, Tailwind) to 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 be the biggest advocate for keeping Elicit's bar high for smooth user workflows and making sure Elicit looks great and is a delight to use. We want somebody on our team who'll remain obsessed with a high quality user experience, and can hold us accountable to balancing that with shipping rapidly and pursuing new features.
You'll contribute to discussions around UX, system design, and architecture.
Projects You'll Contribute To
You can view some 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 and hack days, and you've demoed something you've worked on during a team sync.
You've added some documentation, how-to guides, diagrams, or other resources meant to help us and new hires in the future.
You've suggested an improvement to our development process.
Your First Quarter
You're flying solo With the context you've gained, you're able to implement changes independently and you're comfortable making big, impactful decisions in the course of your work.
You've developed an area of expertise Our engineering team is just a few people, so each person quickly becomes a go-to resource in some area of the tech. Within your first quarter, we expect that there's a part of Elicit you'll become the domain expert for that others reach out to for support when working in this area.
You actively research and improve the product
Compétences linguistiques
- English
Avis aux utilisateurs
Cette offre a été publiée par l’un de nos partenaires. Vous pouvez consulter l’offre originale ici.