Skip to content

Commit dad4d10

Browse files
committed
add par
1 parent 700a2e9 commit dad4d10

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

_posts/2026-02-08-smes.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,9 @@ date: 2026-02-08
55
tags: ai tech
66
---
77

8-
I documented internal [Search](https://developers.google.com/search/docs/fundamentals/how-search-works) infrastructure at Google for about five years, from 2018 to early 2023. (From 2023 until my resignation in December 2024, I worked on content strategy and operations for [AI Overviews](https://blog.google/products-and-platforms/products/search/new-ways-to-connect-to-the-web-with-ai-overviews/). Similar skillset, but very different output.) For a few of those years, my primary focus was Local Search, the system behind what happens when you search for "coffee shops near me" and get a map with pins and business listings. It's one of those features that seems simple from the outside but is genuinely complex underneath, pulling from both Google Maps and Google Search infrastructure.
8+
I documented internal [Search](https://developers.google.com/search/docs/fundamentals/how-search-works) infrastructure at Google for about five years, from 2018 to early 2023. (From 2023 until my resignation in December 2024, I worked on content strategy and operations for [AI Overviews](https://blog.google/products-and-platforms/products/search/new-ways-to-connect-to-the-web-with-ai-overviews/). Similar skillset, but very different output.)
9+
10+
For a few of those years, my primary focus was Local Search, the system behind what happens when you search for "coffee shops near me" and get a map with pins and business listings. It's one of those features that seems simple from the outside but is genuinely complex underneath, pulling from both Google Maps and Google Search infrastructure.
911

1012
Documenting Local Search was hard. A single page could require three or four SME meetings—the classic technical writer ritual where you interview an engineer, take notes, draft something, and iterate until it's accurate. Committing to a page, learning the system, writing it up, and getting approval took a minimum of one week and often way longer.
1113

0 commit comments

Comments
 (0)