Figma about page examples

The about page is where someone goes when they have half decided to trust you and want a reason not to change their mind. Prospects check it before a demo, candidates check it before applying, journalists check it before quoting you, and all three are looking for the same thing: evidence that real people run this company and that it does what the homepage claims.

Which is why an about page full of mission statements and no facts reads worse than no about page at all.

What an about page is actually for

Users arrive with concrete questions, and Nielsen Norman Group's research on About Us content lists them plainly: what the organisation does, where it is, who runs it, and what it stands for. The same research is blunt about what damages trust, and stock photography of people who do not work there is near the top of the list.

NN/g's companion piece on About Us summaries adds the structural point: answer the obvious questions on the page itself rather than scattering them behind four sub pages. These layouts are built for that, which is why the story sections are short and the proof sections are large.

Story first, then proof

Most of these examples open with a header section and a short narrative, often a content section splitting the story into two 576px columns of rich text rather than one intimidating block. Then the evidence arrives: a metrics section with the numbers that matter, a social proof logo strip, testimonials, and in one layout a press mentions section.

A specific number beats an adjective every time. A founding year, a headcount, a country count and a customer number, all in one line, do more for credibility than three paragraphs about passion. The metrics block is the cheapest section on the page to fill and the one readers quote back to you.

People and hiring do the heavy lifting

Nearly every example here carries a team section, and most pair it with a careers section listing open roles. That combination is a fair signal of what about pages are used for in practice: half company introduction, half recruiting page.

Several also close with a contact block or a short FAQ, so a reader who finishes with a question has somewhere to go rather than a dead end above the footer. It is worth deciding which audience the page is really for before you order the sections, because a candidate wants the team and the roles near the top, while a prospect wants the numbers and the customer logos first, and no single order serves both equally.

Placeholder avatars and company logos fill the gaps until the real headshots and customer marks arrive, which is usually later than anyone plans for.

Two breakpoints, two themes, one system

Every layout exists as a 1,440px desktop page and a 375px mobile version, and the whole set is drawn again in dark mode. The mobile versions are designed rather than squeezed: two column story text becomes one column, the team grid restacks, and metrics that sat in a row of four become a column.

Since each page is assembled from the same marketing sections used across the kit, reordering them is a matter of moving frames, and dropping the careers block onto a page that did not have one takes about a minute.

When the page moves into code, Untitled UI React about pages are open source, built with Tailwind CSS from the same sections, so the story, metrics and team blocks you arranged in Figma have direct counterparts in the build.