Join us in shaping the future of how software is created.
We are an early stage software startup funded by NEA and other esteemed investors. We are creating a visual builder for React—something that is as easy to use as a design tool like Sketch/Figma but builds production-ready React components. Our mission is to simplify product development.
We have an intimate team of 5 from Google/Microsoft/Facebook, including tech leads, PhDs (MIT, UW), and ex-founders with exits.

Our team

Yang Zhang
Chung Wu
Raymond Cheng
Founding Engineer
Leo Succar-Ferré
Founding Designer

Open role: Engineer

As part of the early engineering team, you would play a critical role in not just laying the foundations for the product in its formative stages, but also heavily shaping the product direction, the engineering culture, and much more.
We are generally seeking experienced (senior+) engineers, but are also open to early-career engineers with strong coding foundations. The only skill requirement is React, but background in compilers, distributed systems, or complex frontend engineering are pluses.
Most importantly, we seek empathic individuals with highly productive coding foundations, who prize engineering quality, and who are curious and fast learners.

Challenges we work on

For us, Plasmic is an immensely fun and exciting product to build! Here is just a smattering of the challenges we’re working on:
Building a robust visual builder.
Not only do we need to build a performant, robust, and easy-to-use design tool on the web—we need to go far beyond this to allow expressing all the nuances of production components, in all of their complexity. The core editor in Plasmic Studio is a sprawling application with complex state to manage and many rich interactions—unique compared to many conventional content- or form-centric web applications.
Streamlining layout controls.
Layout is a pervasive aspect of building UIs, and we have powerful primitives in tools like CSS. But CSS is notoriously full of pitfalls, with many similar ways of accomplishing the same thing with subtle trade-offs among them. How do we unify and distill these tools into a simplified, streamlined set of concepts?
Translating free-form vector graphics.
Traditional design tools are where many designs start today, and developers are responsible for translating these designs to code. But something like Figma’s document representation has significant impedance mismatch with platforms that developers target. How do we automate as much as we can of the (highly rote) work of translating to code?
Integrating code components.
Making Plasmic usable in development teams requires the ability to work with the existing design system and component libraries that the team is already using. Code components is about letting you directly use arbitrary React components from within Plasmic Studio. This involves heavy work in language tooling, code analysis, secure/isolated code loading, and much more.
Providing guidance on accessibility.
Accessibility is key to ensuring we build high-quality and inclusive products for everyone. How do we not only enable but guide developers and designers on accessibility considerations and best practices?
And more
Support for other web frameworks, support for mobile, refining our codegen, adding transitions and animations, and much, much more!

How to apply

If this role sounds like a fit, or if you have questions about the opportunity, we would love to hear from you!
Send your CV to:
© Plasmic, Inc. 2020