[Draft] Do Not Merge. Initial styling of a react.dev/careers page

[elicwhite]

We are exploring having a react.dev/careers page with open positions we are hiring for. The primary reason is that Meta job postings can only be generic pipeline roles, which can't refer to React or be specific to our role. We only get to engage with engineers who applied to Meta with no specific intent to work with the React team. That also means that many people who would be fantastic for our roles would never apply. Having a react.dev/careers page will let us put up specific front pages and hopefully reach better candidates and getting more active engagement. All Meta applications will still go through Meta's career portal. This scope could theoretically expand in the future to include roles on the core team hosted by other partner companies.

Putting this page together to prepare for when we have positions to hire for and validate the design first.

The content prose in this PR doesn't make any sense, it has snippets from different random job postings. None of which are reflective of roles we are considering hiring for.

I'm looking for feedback on the design elements: site footer, careers sidebar, careers landing page, role description / apply.

I also need to have a version of the careers page that shows a message when we have no open positions (while being able to leave code in the codebase as an example for the next person to see how to add one.

Preview

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
19-react-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 13, 2024 0:43am
react-dev	✅ Ready (Inspect)	Visit Preview		Aug 13, 2024 0:43am

[github-actions[bot]]

Size changes

## 📦 Next.js Bundle Analysis for react-dev This analysis was generated by the [Next.js Bundle Analysis action](https://github.com/hashicorp/nextjs-bundle-analysis). 🤖 ### Five Pages Changed Size The following pages changed size from the code in this PR compared to its base branch: Page | Size (compressed) | First Load | |---|---|---| | `/404` | `104.78 KB` _(🟡 +519 B)_ | 208.98 KB | | `/500` | `104.78 KB` _(🟡 +519 B)_ | 208.97 KB | | `/[[...markdownPath]]` | `106.69 KB` _(🟡 +580 B)_ | 210.88 KB | | `/errors` | `104.99 KB` _(🟡 +518 B)_ | 209.18 KB | | `/errors/[errorCode]` | `104.97 KB` _(🟡 +518 B)_ | 209.16 KB |

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[elicwhite]

Feedback received offline:

Add the Meta logo to make it even more clear that this is a Meta role.

Consider adding a note at the top noting that this is a generic meta job posting and applying is through Meta.