Designing excellent experiences for developers

We’re a group of curious makers and doers, working hard to make Gatsby the most intuitive way to build for the web.

Meet the Team

Nachiket Kumar

Nachi is an Atlanta based product designer, dad to 2 kids and an aspiring farmer who's enthusiastic about the intersection of technology and food. At Gatsby, he works on the user experience and interface of Cloud, as well as other interesting projects in the pipeline. Fun fact: he spent 6 years in an immunology lab before becoming a designer.

Rena Kuai

Rena is an ex-product manager turned product designer who currently resides in Dallas, TX with her husband and cat, Tony Montana. She's passionate about helping others transition into design and mentoring women and minorities in tech. Besides design stuff, she likes running / lifting weights, traveling (and travel hacking), and watercolor painting in her free time.

Shannon Soper

After years of discussing, with anyone willing to listen, the particular failings of poorly designed things, Shannon discovered she could get paid for this strange hobby. Other hobbies: joking w/ family & friends, asking her cute dog "how did you get so cute?", optimizing the kitchen cooking utensil arrangement, keeping a dream journal, reading novels, and hiking w/ hubs.

Flo Kissling

Located in Frankfurt (am Main, Germany), Flo is always feeling like an a** when writing about himself in third person ;-). A fan of incremental changes, he works on Gatsby's design system, with occasional escapism to front end development. He is curious about almost everything, loves reading, is a hobbyist photographer … and doesn't "totally suck."

Jeremy Barnes

Though a designer by trade, Jeremy began an adventure into coding in late 2017. He has a special passion for the Venn diagram of design and development relationships, and how each of these fields can make him better in the other. At the heart of it, he loves to create and bring visions to life, overseeing and enhancing the end to end process of design to development.

    You?

    From open source frameworks to low code tools to SaaS deployment services, Gatsby is rapidly expanding. As we venture into new territories, it's essential that we have passionate and thoughtful designers creating coherent customer experiences. Like what you hear? Be sure to check out our careers page for new design opportunities.

    Our Design Principles

    Gatsby Design’s approach to design and product considerations

    .01

    Design for scale

    Build flexibility and growth into your designs. Create shareable and reusable interface patterns that can be used across multiple surfaces. Expect that the scenario you are designing for today may only hold a fraction of the content that it could eventually.

    .02

    Know our users and goals

    Have a strong awareness of our strategic approach. Understand the larger business goals and more specefic user goals of any given scenario. Seek data and user research to better understand what our users want and where their pain points are.

    .03

    Consider the ecosystem

    Be a total designer, and think about the platform as a whole, not just your individual design scenario. Consider all of the ways in which your design may show up in the Gatsby world, and how it resonates with Gatsby's existing design patterns.

    .04

    Leverage and extend

    Build on the work of others and enhance it. Leverage existing design component libraries and Gatsby product UX patterns to create consistent work. Change and evolve these components as necessary.

    .05

    Do more with less

    Focus on the essentials. Minimize user choices, eliminate unnecessary user tasks, and autoprovision user input. Use interface content, over the interface chrome, to surface interactions. If possible, reduce user clicks. Create responsive systems that anticipate user needs and assist them during errors.

    .06

    Design is never done

    Designs always have the capacity to improve and should be thought of as a work in progress. When we ship features, the question is not, "is it done?", but rather, we should continue to seek opportunities for improvement and areas of refinement.