Software Engineer & Employee #4

About Smartcuts

Chrome extension to turn clicks & keystrokes into no-code automations

Tech

We use [ReasonML](https://reasonml.github.io/), [ReScript](https://rescript-lang.org/), [Next.js](https://nextjs.org/), [Vercel](https://vercel.com/), [GraphQL](https://graphql.org/), and the serverless db [Fauna](https://fauna.com/). Our choices come from a preference for strongly typed, functional languages and for serverless architectures -- choices that allow us to focus on the necessary, not the incidental, complexity of the problem space. Some of the interesting engineering and design challenges in this problem space? - How do you design a product that doesn't expose engineering concepts to users? - How can you design an algorithm that can reliably locate elements on a page, without asking the user to specify css selectors? - How can you leverage AI to automatically detect and extract structured records from a web page?

The role

We are building a new kind of automation product that will be the first of its kind -- a product that gives everyday, non-technical users superpowers to automate any repetitive work, on any website, without code ([1 minute video](https://bit.ly/3v7hHRp)). To do this, we have to solve challenging engineering problems. You're a software engineer who loves taking the lead on solving difficult algorithmic challenges. Ideally you have some past experience with web APIs, since our core tech is all about automating work in the web. Bonus points if you have experience working with [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) or have an impressive mastery over the DOM and its nuances. Experience with some or all of our technology stack is ideal but not necessary. We use [ReasonML](https://reasonml.github.io/), [ReScript](https://rescript-lang.org/), [Next.js](https://nextjs.org/), [Vercel](https://vercel.com/), [GraphQL](https://graphql.org/), and the serverless db [Fauna](https://fauna.com/). Our choices were built on a preference for strongly typed, functional languages and for serverless architectures -- choices that allow us to focus on the necessary, not the incidental complexity of the problem space. Some of the interesting engineering and design challenges in this problem space? - How do you design a product that doesn't expose engineering concepts to users? - How can you design an algorithm that can reliably locate elements on a page, without asking the user to specify css selectors? - How can you leverage AI to automatically detect and extract structured records from a web page?