Frontend Engineer - Core Team (Remote)
Slight is looking for a frontend engineer to join us in building a product focused on all areas of interaction between data teams and domain experts. See our about page for more on our mission and product vision.
At this early stage, you will also join the Slight Core Team. The Core Team will be comprised of individuals who collectively have deep technical expertise, proven leadership skills (or potential), and a track record and shared enthusiasm for building new technologies from the ground up.
We’re a remote-first company with a high focus on autonomy, work-life balance, and flexibility. We are open to all applicants between one hour west and six hours east of Eastern Time . For more information about working with us, see our values and benefits pages. We strongly encourage applications from people whose backgrounds are considered non-traditional in tech.
As a Frontend Engineer and Core Team member you will:
- Develop and build initial product features and have a key role in determining our overall product trajectory
- Lead the development of our core web application and UI, for example, by building reusable React components to power data-intensive apps and writing frontend logic to help users build reliable and powerful, intuitive data applications that empower less technical users to generate data-driven insights
- Leverage your deep frontend expertise to build performant and intuitive data-native interactions across all Slight user interfaces, e.g., web application, Slack, etc.
- As one of our first hires, be a technical leader and help drive our engineering culture through teaching, communication and practice
We are hiring for strengths, not eliminating based on weaknesses. Thus while we’re looking for very strong candidates, we have minimal hard requirements.
We don’t have an explicit experience requirement, although because we’re extremely early and quite small, engineers early in their technical career are unlikely to be a great fit for us right now.
We do require that you have strong proficiency in at least one programming language, and you must be willing to learn and get up to speed early with Typescript and React.
You would be a great fit for this role if you:
These are genuinely not requirements, and most can be grown into with the role.
- Have previous experience engineering data-intensive interfaces and web applications
- Are comfortable building typed, reactive frontend applications in Typescript and React
- Enjoy thinking about how backend API performance and limitations influence frontend architecture and you are motivated by finding creative client-side solutions when performance is a constraint
- Are familiar with SQL/analytical query writing or are enthusiastic to learn
- Love learning new technologies and concepts, even when it feels daunting
- Have strong intrinsic motivation: while our combination of salary, equity, and benefits should be competitive, we further believe our company’s nature is well-suited to those motivated by autonomy, mastery and purpose
Added bonus if you:
- Prioritize clean, well-documented code-bases
- Are interested in communicating with the broader engineering community through technical blog posts and talks at meetups and conferences
- Have experience deploying cloud-based applications
- Are comfortable with container technologies or are willing to learn
- Are familiar with OpenAPI
- Have experience setting up frontend/UI testing environments
As a start-up, the work is always evolving so don't be discouraged to apply if you have some but not all of the listed great to haves!
As part of the core team, you will have a strong say into what this becomes. You are not assumed to be familiar with all of the below, and some of it may not apply to you (although that is mostly up to you) but eventually you may touch many of these systems:
- Typescript and React on the frontend (with Next.js), along with Tailwind CSS and Stitches
- Rust as the primary backend language, along with Go and Node.js for some services - typically because an excellent SDK exists for some purpose like Slack integration. Primarily we love Rust for its Enums (we even use the Typescript flavor on the frontend)… This is only 60% a joke
- Inter-service communication is JSON-based REST to the front end and typically gRPC among the backends
- PostgreSQL for our databases, Docker for deployment
- R and Python support is a big part of our future product plan, even if not used in the application code itself