We're building a first of its kind developer platform that can be used to learn and practice programming, build and deploy applications, and share and discuss with a community of peers. We realize this is an ambitious plan, but we think it's high time someone built this. There is no good reason for the insane fragmentation in programming tools today -- someone learning to code needs to learn at least ten disjointed tools and platforms to do anything interesting with programming.
We're on a mission to make programming more accessible by building the best, simplest, and fastest coding environment. Replit is a place to not only learn and practice programming but also to collaborate and ship applications.
We've grown to millions of users via word of mouth and a strong organic presence. However, there's still so much value to be provided to our users through each step of their journey - from onboarding all the way to engagement.
Growth engineers enable our users to unlock Replit's product capabilities (computing superpowers) and help supercharge our growth. In this role, you have an opportunity to get in at the ground level of a high-growth startup and help us build a growth muscle to crawl, walk, and run. You’ll have an immediate and long-term impact!
Note - If you're a talented engineer but don't really fit the requirements then get in touch anyway.
Most of our time is spent building two core areas of our technology -- the IDE and the container infrastructure. We created the world's fastest and first server-rendered IDE. The IDE has a small functional core -- borrowing ideas from Redux -- everything is a plugin. This architecture allows us to build an adaptable IDE where it starts very simple and grows with the user as they learn more and require more features -- this is crucial for new programmers.
As for our infrastructure, we're building a new kind of computing platform: it's Serverless in that users don't have to care about the underlying resources, but it's not Serverless in that it's stateful. This way it's interactive, and since we're focused on newcomers, it's a much more natural programming model. We're also building a filesystem abstraction that allows your working directory to travel with your container between development and production and as it goes offline and online -- a persistent and versioned working directory.