diff --git a/docs/pages/careers/react-engineer-docs-infra.md b/docs/pages/careers/react-engineer-docs-infra.md
index ec7dcbe68cfeb3..671c744ab77e7d 100644
--- a/docs/pages/careers/react-engineer-docs-infra.md
+++ b/docs/pages/careers/react-engineer-docs-infra.md
@@ -47,7 +47,7 @@ And just like the products themselves, the documentation should reflect our fund
 Our internal Docs-infra team currently shares responsibility for this domain, and they've developed features such as [autogenerated](https://x.com/olivtassinari/status/1783894370011213869) OG images, multi-tab component demos, [speed](https://github.com/mui/material-ui/pull/40314) performance improvements, and more.
 
 There are so many other features we'd like to implement, and projects we could draw inspiration from (for example, [Nextra](https://nextra.site/))—but the existing team (each of whom spends most of their time on one of our product engineering teams) simply doesn't have the bandwidth to take on bigger and more ambitious projects.
-For example, we could offer visitors the ability to toggle the design language they want to view the docs in; add automatic conversion of demos to Tailwind CSS; use AI to provide component demo customization; and so much more.
+For example, we could offer visitors the ability to toggle the design language they want to view the docs in; automatically convert demos styled with CSS-in-JS to Tailwind CSS; use AI to provide more examples of component demo customization; and so much more.
 
 That's why we're looking for a skilled JavaScript developer to own the docs infrastructure as their full-time responsibility.
 
@@ -101,7 +101,6 @@ You can find the other perks and benefits on the [careers](https://mui.com/caree
 ## How to apply
 
 [Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/673f3178-56f4-47fd-bd2b-6dcba57758aa/application?utm_source=ZNRrPGBkqO)
-(will add the link once we publish the role also on Ashby)
 
 Don't meet every requirement?
 Apply anyway!