-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[website] Add why Design Engineer for data grid #40016
[website] Add why Design Engineer for data grid #40016
Conversation
XXXXXX | ||
|
||
Overall, both our open-source community and our premium products are growing fast (x2 YoY). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved to last. This should always be secondary to why we are opening roles. Sure, it makes sense to open roles for growth if there is a larger gap to fill that people struggle with, but FIRST talk about that gap.
Netlify deploy previewhttps://deploy-preview-40016--material-ui.netlify.app/ Bundle size report |
e6265a8
to
e90e55b
Compare
We hear an even bigger pain around _design_ from developers who adopt projects specialized into one UI component, e.g. data grid. For them, it's not only the default behaviors that need to be great but also the ease of customizing the components to their needs and integrating into the rest of their application. | ||
|
||
Up until now, we solved a subset of these problems by specializing in a MUI X Data Grid that deeply integrates with Material UI. | ||
We feel that the timing is right to take a step further and invest in the design of MUI X to have the best data grid not only for Material UI but for **any** React project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strategically: It means aiming to make the data grid an entry point to the ecosystem. The vision is that the more entry points a developer has with us, the more likely he will decide to adopt everything else to benefit from native integrations, e.g. Outlook -> Microsoft Team. Gmail -> Google Workspace, iPhone -> Apple watch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some slight rephrasing/copy suggestions — otherwise, it looks good!
Co-authored-by: Danilo Leal <67129314+danilo-leal@users.noreply.github.com> Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Co-authored-by: Danail Hadjiatanasov <hadjiatanasov@gmail.com> Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com> Co-authored-by: Danilo Leal <67129314+danilo-leal@users.noreply.github.com> Co-authored-by: Danail Hadjiatanasov <hadjiatanasov@gmail.com>
Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com> Co-authored-by: Danilo Leal <67129314+danilo-leal@users.noreply.github.com> Co-authored-by: Danail Hadjiatanasov <hadjiatanasov@gmail.com>
Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com> Co-authored-by: Danilo Leal <67129314+danilo-leal@users.noreply.github.com> Co-authored-by: Danail Hadjiatanasov <hadjiatanasov@gmail.com>
I wasn't sold on why we needed this Design Engineer role for the Data Grid (more than others). But since the presentation of the goal for 2024, it now makes a lot more sense to me. I have updated https://www.notion.so/mui-org/Design-Engineer-xGrid-3b9a645faa434fe18fa8ebd5ed2fc086 accordingly.
Preview: https://deploy-preview-40016--material-ui.netlify.app/careers/design-engineer-x-grid/#why-were-hiring