Pigment CSS technical challenge @ MUI

This challenge is part of the hiring process for the Staff Engineer - Pigment CSS positions at MUI. The idea is to make as much progress as possible under a given time constraint (2-3 hours).

Why are we doing this?

At MUI, because we are a DevTools company, we put a lot of accent on the quality of the work on the tools we create. We started to work on Pigment CSS because we wanted to solve the main problems developers face: the performance of their apps and the support for React Server Components, without compromising their developer experience. The idea of this challenge is to test out how deep you can go into solving technical problems that will help us achieve these goals. We want to get a glimpse of how you will perform in the role.

Context about MUI

MUI's objective is to become the UI toolkit for React developers. We're unifying the fragmented ecosystem of dependencies into a single set of simple, beautiful, consistent, and accessible React components.

Our mission is, ultimately, to make building great UIs and web apps a breeze ⎯ quicker, simpler, and accessible to more people. At the end of the day, it's about writing less code.

Pigment CSS plays a critical role in this, as performance is one of the main criteria for building great UIs.

Head to our Handbook to learn more.

The challenge

The objective of the challenge is to implement a build-time transpilation of a React code to generate CSS and associate that CSS with its respective React elements. The code you will write could be used inside a zero-runtime CSS-in-JS library that focuses on the basic use-case of how people may style their components.

Here is the example code that you can start from:

import { styled } from '@pigment-css/react';

const Div = styled('div')({
  border: '1px solid black',
});

export default function App(props) {
  return (
    <Div
      {...props}
      sx={{
        ...props.primary ? { background: 'blue' } : { background: 'red' },
      }}
    />
  );
}

Your goal is to transform the styled and the sx calls into a valid CSS and a transformed JavaScript code that can later be used by a simple JavaScript runtime after the CSS is already extracted. The resulting output should look something like this:

JavaScript

import { styled } from '@pigment-css/react';
import './styles.css';

const Div = styled('div')({
  className: 'hashed-string1',
});

export default function App(props) {
  return (
    <Div
      {...props}
      className="hashed-string2"
      style={{
        '--primary-var': props.primary ? 'blue' : 'red',
      }}
    />
  );
}

CSS

.hashed-string1 {
  border: 1px solid black;
}

.hashed-string2 {
  background: var(--primary-var);
}

We encourage you to think of more complex scenarios on how the styles and the sx input can be created and incorporate those in your solution. If time permits, you can also try to add support for tagged-template literal syntax, eg:

const Title = styled.h1`
  font-size: 1.5em;
  text-align: center;
  color: #BF4F74;
`;

When sending the challenge, you can include some input examples that you used as a test-cases.

Work environment

To save you time, we created a working environment. You can install this environment by following these steps:

• clone the repo: git clone [email protected]:mui/tech-challenge-pigment-css.git
• install the dependencies: pnpm install
• start Vite: pnpm start
• open http://localhost:5173/

You can find the source of this URL in src/App.jsx. Your goal is to implement the utils/transform.js function that is responsible for doing the transformation. You can use the example code from above in the Input code textarea and check the results of the generated JavaScript and CSS.

Submission

Instructions:

• DO NOT fork / host your project on a public repository.
• Please send us a zip file containing this project using the upload link that we have provided by email (with the .git folder).
• To significantly reduce the size of the archive, remove the /_node_modules_/ folder.
• If you don't have the upload link, you can send it to [email protected].

We're excited and looking forward to seeing what you'll create! Good luck 🚀