Full Stack Engineer - Core Team (Remote)

Slight is looking for a full stack 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 Full Stack Engineer and Core Team member you will:

  • Develop, build and interact with Slight’s services, APIs, and frontend interfaces to create a product that empowers data experts to easily share analytical work as data applications with broad audiences
  • Lead and align engineering effort across the tech stack to build, deploy, and monitor seamless and performant data-native user experiences and product features
  • Leverage your generalist expertise to envision and build powerful third-party integrations, for example, enabling interactions with data apps built on Slight directly from Slack
  • As one of our first hires, be a technical leader and help drive our engineering culture through teaching, communication and practice
  • In particular, as a Full Stack Engineer, you will play a key role in communicating — both internally and to the public — how our entire range of technologies interact and work together to deliver great experiences

Requirements

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 a broad subset of the technologies listed in the Stacksection below, with an initial focus on 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.

  • Are excited about and experienced with end-to-end development of data-intensive applications, from building reliable server-side and API logic to frontend components and UIs that delight users
  • Have the ability and vision to synthesize services, processes and systems spanning our entire technology stack to design and craft intuitive and empowering user experiences
  • Have experience deploying and monitoring containerized, cloud-based applications
  • Are familiar with databases and 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
  • 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!

Stack

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