Product Engineer - Fullstack

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.

Skills: React, GraphQL, JavaScript

Note that the listed role is merely an approximation. If you're a talented hacker but don't really fit the requirements then get in touch anyways.

Roles & Responsibilities

• Work with designers and product managers to build delightful user experiences
• Talk to users and iterate on product
• Ideate new products and services that helps us make coding more accessible
• Work with platform engineers to build IDE services and plugins

Key Qualifications

• 2+ years frontend or fullstack experience
• Able and enjoys writing maintainable CSS
• Good product and design sense
• Experience architecting and maintaining large JS apps
• Comfortable with SQL and database abstractions
• Comfortable debugging production systems (instrumentation, monitoring, etc)
• Self-directed and comfortable working autonomously

Bonus Points

• Expert React.js and GraphQL programmer
• Experience building libraries and frameworks
• Experience building a developer tool (it can be personal dev)

Job Location:

SF (onsite preferred) Remote (currently only open to +/-4 hours from pacific timezone)

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.