Why Scarlet? We believe in an exciting future where software is ubiquitous in healthcare, delivering better outcomes for everybody. Scarlet’s mission is to hasten the transition to universally accessible and affordable healthcare by safely Increasing the quantity, quality and access to Medical Software.

What problem does Scarlet solve? Unfortunately, the current regulatory environment wasn’t designed for software: • Getting regulatory approval can be so daunting and time-consuming that some smaller innovative projects never get off the ground. • It can delay the first release of software by years. • It can slow subsequent software iterations to the same pace at which drugs and hardware medical devices are improved.

How does Scarlet solve the problem? We have built Scarlet from the ground up to certify https://www.fda.gov/medical-devices/digital-health-center-excellence/software-medical-device-samd. Scarlet has the regulatory approval to certify medical software. Scarlet’s product enables its customers to achieve swift regulatory approval and perform frequent subsequent software updates. Intriguing… what are the details of the technical solution and how is it different from the status quo? The traditional solution to this problem is decidedly non-technical. To prove that a release is ready for certification, software builders submit documentation. Like a lot of documentation. Think 1,000 page long PDFs. Our technical solution is non-traditional. When using Scarlet, software builders still have to submit a lot of information. It’s the law. And every time they change something, they have to add more documentation and make sure all the existing documentation references that new documentation. But instead of wrangling a giant PDF, when using Scarlet, they submit each change as a single small file. These files have some special sauce. On the surface, they look like Markdown, making them familiar to people who are used to the usual paper-based submission flow. But actually, they’re a special dialect of Markdown, which we call Slang:tm: - short for The Scarlet Language. One of the amazing things about Slang is that Slang files can be linked together. Users think they’re just typing information into a file, but actually, they’re populating a huge graph of connected files. We can query that graph to understand how new data relates to old data and whether there are any inconsistencies. When things don’t all line up, when the data they’re submitting would prevent them from getting certified, we can give them feedback. Because we think of Slang as a language and because our customers are editing files, it made sense to us to implement the Slang tooling as a VS Code Extension, with an LSP Server backend (ClojureScript and Clojure, respectively). That lets our users have a great editing experience. They get version control, diffs, and lots of other stuff for free, from the editor. But it also lets us augment their experience with all of our knowledge about what their edits actually mean, and how they relate to all the existing documentation. We can help them with auto-completion, navigation, renaming, and many other goodies. Most importantly we can provide feedback in the Problems pane when they’ve entered something incorrectly. Small changes, kept consistent with automated checks. Sound familiar? A bit like a good software development flow? This is why we think we can cut a process that typically takes a year or more down to a week or less. This is how Scarlet is going to radically change the pace of software innovation in medicine.

What principles do we emphasise in our team? • Small team/Big impact: We strive to make an outsized impact relative to the size of our team. • Openness: Proactively sharing context, so we can all make good choices • Problem-centricity: Framing our conversations in terms of problems and striving to define and prioritise them well These three principles empower us to be unreasonably effective whilst enjoying: • Flexible working ◦ Remote-first ◦ No prescribed hours ◦ No holiday tracking • Low/no scheduled meetings ◦ No stand-ups, retrospectives or agile ceremonies ◦ We get together in real life twice a year for a week at our offices in London or Amsterdam • Asynchronous collaboration ◦ We have rich async discussions ◦ We flexibly have 1:1s with each other as and when it makes sense • Extremely High Trust and Autonomy ◦ Nobody just implements prescribed solutions handed to them by someone else. ◦ We all solve problems, own our choices and trust and respect each other.

It was nice to meet you at the JUXT-fest :)

What does our hiring process look like? • (1) Reach out to me here in Clojurians Slack with your GitHub, LinkedIn/CV • (2) We’ll do a quick sanity check on the possibility of a fit on our side ◦ Here are some of the things which might be exciting early indications of a potential mutual fit: ▪︎ 10++ years of professional experience ▪︎ Highly regarded contributions in OS projects ▪︎ Experience building dev-tools ▪︎ Passion/motivation to solve problems in healthcare ▪︎ Strong reference from a well-regarded source • (3) We’ll enable you to do a sanity check on the possibility of a fit on your side ◦ … we’ll share a bunch more stuff for you to peruse: ▪︎ 🍿 Introduction to Scarlet video (10 mins) ▪︎ 📽️ Product demo videos ▪︎ 📚 Product docs ▪︎ :playground_slide: Access to a demo account • (4) An intro call with me ◦ An opportunity for you to ask me all your questions about what you’ve seen so far and anything else ◦ An opportunity for me to ask you a few questions about where you’re coming from, what your superpower(s) is/are, and what you need from your environment to be able to wield them at maximum strength • (5) A call with a future teammate ◦ An opportunity for technical and cultural questions from both sides • (6) Technical challenge ◦ Your choice from ▪︎ An open-source contribution. We’ll compensate you for up to a few days of the time you spend on it. If you’ve very recently done any of the following anyway - great! Just send us that! • Solve a non-trivial problem in an open-source project • Spin up in an open-source project you’re unfamiliar with and send us some stuff that demonstrates your impact • Create a new open-source project that solves a problem you care about ▪︎ A pair programming session with a member of the team • (7) Call(s) with the (one or two) remaining future teammates that you’ve not met yet ◦ An opportunity for technical and cultural questions from both sides • (8) Call with my co-founder James

How does Scarlet think about compensation? Scarlet is a well-funded early-stage company, that has raised >$9M in funding and has paying customers. Scarlet strives to pay top-of-market compensation. That is, we aspire for compensation to be greater than, or at least equal to the next best alternative (anywhere in the world). Scarlet is still at an early stage compared to many other companies. In practice, that means that it’s not possible to match the very top of the market yet. So, Scarlet benchmarks against the top of the market and sets compensation as close to that level as possible. Then compensation is reviewed and adjusted every 6 months, with the goal of getting to the top of the market as quickly as possible.

Jamie is great and the company is a fantastic place to work. Highly recommend getting in touch!

that’s quite a strong pitch you have there (including team!)

what does ICs means?

@U03DVASRFFD not that I'm in any way related/involved in this company, but I assume they mean Individual Contributor - term often used to differentiate from manager positions.

That’s right, thanks @UV0GCSY3G! 🙇 Apologies for the acronym, I have de-acronimified it in the post!