How to Navigate and Research the Mercury News Obituary Archive
The San Jose Mercury News has published obituaries in the Bay Area since the late 1800s, and the digital archive they've built around Silicon Valley figures is one of the more useful historical resources available online. It isn't polished. The search interface is clunky, and the timeline feature they added a few years back doesn't always render correctly on mobile. But if you're researching someone who worked in tech here, it's worth knowing how to work with it. What makes this archive useful is its chronological span. You can trace deaths from engineers at Fairchild Semiconductor in the 1960s through early employees at companies like Sun Microsystems, Cisco, and Apple, right up to current listings. The timeline view organizes these by decade, which helps when you're trying to understand who died in a given period and what companies they were associated with. I've used it repeatedly for genealogy work and local history projects. Here is how I approach the archive when I need specific information.
Start at the Mercury News obituary section and look for the search or archive tools. They changed their site layout a couple times, so the entry point moves around. If you know the person's full name, use the search bar. Filter results by date range to narrow things down. Obituaries are usually posted within 24 to 48 hours of death, though sometimes they lag by a few days for less prominent figures. The timeline feature groups obituaries chronologically. You can click through decades. I find it most useful when cross-referencing with other sources. For example, when researching former Intel employees who passed away in the early 2000s, I'd pull the relevant decades from the timeline, note names, and then verify against company histories and LinkedIn records. One problem I run into repeatedly is that the site sometimes returns duplicate entries for the same person. This happens when an obituary gets reprinted or syndicated to other locations under slightly different dates. The workaround is to check the URL carefully and compare the publication dates. Usually the original posting has the earlier date. I also keep a simple spreadsheet with the person's name, date of death, and the Mercury News article URL so I can deduplicate manually.
Another issue is incomplete indexing. Names with hyphens, middle initials, or slight spelling variations from different sources don't always match up. If a search for "Robert J. Noyce" returns nothing, try "Robert Noyce" or "Bob Noyce." The search algorithm isn't sophisticated enough to handle those variations automatically. I've spent time on names where the obituary lists one spelling and the search index uses another because the family provided different information than what appeared in public records. The obituaries themselves vary widely in quality and length. Some are full essays with detailed career summaries. Others are a paragraph or two generated from basic family-submitted information. People who worked at well-known companies tend to get more coverage. Anonymous or contract workers often receive shorter notices. This isn't a flaw in the database—it's just how newspaper obituary budgets work. You get what families and companies are willing to pay for, plus whatever editorial judgment gets applied. For researchers, there are a few things worth knowing that aren't obvious from using the site alone.
Get the Full Details
First, the Mercury News sometimes publishes guest or sponsored content that looks like an obituary but isn't filed through their standard newsroom process. These are usually marked differently or have odd formatting. If something looks like an advertorial dressed up as a death notice, verify it against other sources before citing it. Second, the archive doesn't include all local obituaries. Some families choose to publish only in alternative papers or through funeral home websites. If someone from the Santa Clara Valley died but has no Mercury News listing, check the Mountain View Citizen, the Palo Alto Daily Post, or funeral home pages directly. The coverage gap is real and affects how complete your research appears. Third, the timeline feature was a relatively recent addition and hasn't been fully integrated with the main search system. You can't easily search within a specific decade through the timeline. You have to browse decade by decade. This is slow if you're looking for someone who died between 1995 and 2005. My workaround is to use the main search with date filters instead, then manually cross-reference the results against the timeline for context.
The archive is searchable but not downloadable as a single dataset. If you need bulk data for analysis, you'll have to scrape or request it through the newspaper's archives department. They don't offer a public API. I've contacted them directly for research purposes and gotten responses, but the turnaround is measured in weeks, not hours. For most people doing personal research, this limitation doesn't matter. For academic projects or data analysis, it's a real bottleneck. What I find most valuable about these obituaries is the contextual information they contain. Beyond dates and names, many include details about specific projects, collaborators, and company divisions. A 1998 obituary for a Fairchild engineer might mention work on particular chip designs. A 2004 notice for a Cisco employee might reference specific products or acquisitions. These details often don't appear elsewhere and can fill gaps in professional histories. The obituary section also captures regional history that mainstream tech histories sometimes miss. Workers from smaller companies, support staff, and people who didn't become famous still get remembered here. If you're studying the everyday structure of Silicon Valley rather than just its CEOs, these entries are essential primary source material.
I should mention the limitations plainly. The archive isn't comprehensive. It favors well-to-do families who can afford lengthy paid notices. It skews toward men in prominent technical roles because that's who died first and whose families were more likely to submit detailed content. The search tools are dated and sometimes broken. The timeline doesn't link properly to individual articles on every page load. And access to older records may require a subscription or account creation depending on how the site has restructured over the years. If you need better searchability, consider combining this with other databases. Genealogy sites like Ancestry often have obituary indexes that include Mercury News content. LinkedIn obituary features also capture some of the same information with different search capabilities. Using multiple sources simultaneously catches gaps that any single archive misses. The practical takeaway is that the Mercury News obituary timeline is a solid starting point but rarely a complete answer. It works best when you use it alongside company histories, personal papers, and other local newspaper archives. The information is real and valuable, but treating it as definitive will lead to incomplete or occasionally incorrect conclusions about who was involved in Silicon Valley's development over the decades.
