Nintendo of America is looking for a Digital Archivist, Historical Systems, a specialist role dedicated to the records behind older Nintendo games, platforms and hardware. The position is based in Redmond, Washington, and its remit is not simply to store old files: it is to create an organized structure for technical records, engineering documentation, source materials and institutional knowledge tied to legacy systems.
That is a substantial assignment for a company that has released roughly 11,000 games over its lifetime. The job description frames the work around three connected goals: preservation, organization and accessibility of historical hardware and software information. In plain terms, Nintendo wants historical material to remain findable and usable rather than becoming a pile of files whose existence is known only to a handful of long-serving experts.
The listing is a notable signal that the work surrounding old games goes much deeper than keeping a playable copy on a shelf. A game’s history can include the software itself, but also the technical documents that explain how a system worked, development materials, records of decisions and the knowledge held by people who worked on it. Nintendo’s prospective archivist would be asked to establish the framework that brings those pieces into a more dependable order.
What Nintendo is hiring this archivist to do
The role calls for the design and implementation of a structured framework for legacy information. It would cover historical Nintendo hardware and software, along with documentation and other supporting materials. The eventual archivist is expected to work with subject-matter experts from engineering, product development, legal and business teams.
That cross-team requirement matters. Historical game material does not necessarily arrive in one uniform format or from one department. Engineering records may answer technical questions about an old platform; product-development records may provide another part of the story; legal and business teams may be involved in the rules and processes governing records. The position is therefore built around making a shared system that can be used across those disciplines.
The intended result is a set of standards and procedures that keeps historical information discoverable, usable and preserved for future generations. The wording does not promise a public museum, a consumer-facing retro-game initiative or any newly playable releases. It describes an internal archival and information-management function. That distinction is important: organizing a company’s historical record can support many kinds of future research and decision-making, but the listing itself does not say how, or whether, specific materials would be released publicly.
Archiving is more than saving a file
The central terms in the job listing are easy to blur together, but they describe different parts of the work.
- Preservation means maintaining material so it remains available over time. In this role, that includes historical software and hardware information as well as supporting records.
- Organization means arranging those materials in a consistent system instead of leaving them scattered across disconnected collections or dependent on individual memory.
- Accessibility here means that appropriate people within the organization can locate and use historical information. It does not, by itself, mean public access.
- Metadata management is the practice of managing descriptive information about other materials. A useful record might identify what an item is, what system or project it relates to, and how it can be located within an archive.
- Information architecture is the design of the structure people use to navigate and understand a body of information. For a legacy archive, it is the logic that makes records consistently arranged rather than merely collected.
Those disciplines explain why the role seeks expertise in archives, metadata management, information architecture and research. The work is as much about building a reliable map as it is about housing the territory. A historical record can be technically retained but still be difficult to use if it lacks context, consistent descriptions or a sensible way to connect related materials.
Related coverage includes Nintendo Seeks Digital Archivist to Organize Its Legacy Games and Hardware Records.
For game history, that problem has particular weight. Hardware and software are interconnected, and the surrounding documentation can be necessary to explain both. The listing explicitly includes legacy systems and platforms, placing the job’s focus on the broader technical and institutional record rather than treating individual games as isolated artifacts.
Why the framework is the important part
It would be easy to read “digital archivist” as a straightforward digitization job. The description points to something broader. Nintendo is asking for a structured framework and for standards and processes. Those phrases suggest an ongoing system for handling historical information, not a one-time effort to transfer files from an older format to a newer one.
A standard gives people a common method for describing and handling material. A process makes that method repeatable. Together, they can reduce the risk that useful knowledge is difficult to locate simply because it was recorded differently by different teams or stored without clear connections to related projects. The job’s emphasis on discoverability is therefore practical: information has limited value to future researchers or teams if they cannot tell that it exists, determine what it concerns or find it when needed.
The inclusion of institutional knowledge is especially revealing. That phrase refers to knowledge held within an organization, including context that may not be obvious from a technical record alone. The listing does not detail how Nintendo plans to capture or document that knowledge, but it recognizes that a legacy system’s history is not limited to the hardware and software artifacts themselves.
For enthusiasts, the immediate lesson is one of scope. The preservation of games is not only about cartridges, discs, consoles or executable code. It can also involve design and engineering records, source materials and the organizational context that makes them intelligible. Nintendo’s position puts all of those pieces within the same archival conversation.
A 12-month contract with specialized qualifications
Nintendo of America lists the role as a 12-month contract position paying $35 to $55 per hour. It prefers candidates with a bachelor’s degree in library and information science, archives, museum studies, information management, history, technical communication or a related field, while noting that equivalent professional experience may also be considered.
The range of preferred disciplines fits the work described. Archives and library and information science address the stewardship and retrieval of records. Information management and information architecture speak to the systems used to organize them. History concerns the interpretation and documentation of the past. Technical communication is relevant when complicated technical material needs to be structured and understood by the people who rely on it.
None of that makes the post a conventional game-development job. It is an information and preservation role located at the intersection of game history, technical documentation and organizational practice. The ideal candidate must be comfortable with research and record systems, while also collaborating with specialists who understand the original hardware, software and business context.
What this means for preservation—and what it does not yet mean
The opening is meaningful because Nintendo occupies a major place in the history of video games and has a vast catalogue behind it. Putting dedicated effort into legacy documentation and systems records acknowledges that the company’s earlier work requires active organization if it is to remain useful over time.
It also arrives in a wider environment where preservation advocates and enthusiasts have pushed for more attention to the medium’s historical record. The Video Game History Foundation, founded in 2016, was created to preserve and teach video-game history. Its work has included efforts toward the United States’ first dedicated library for studying that history and preserving game source code.
Source code, broadly, is the human-readable set of instructions used to create software before it is turned into a form a system can run. The reference to source-code preservation helps illustrate why preservation extends beyond a retail copy of a game. A playable release and the materials involved in creating it are different historical objects, with different research value and preservation needs.
Nintendo’s new role should not be read as a guarantee of surprise game discoveries, archival releases or access to old development material. The job description makes no such promises. Still, a better-organized record can make it easier for an institution to understand what it has. That is the foundational, less glamorous part of archival work—and often the part that makes future research possible.
Recent collecting news offers a reminder that unfamiliar historical material can still surface. Earlier this year, a collector found 97 copies of an unreleased version of Super Mario Bros. Duck Hunt; five were graded a perfect 10 by PSA. That discovery concerns physical copies found by a collector, not Nintendo’s archive, but it underscores how incomplete the visible record of game history can be. Documentation and structured records do not eliminate surprises, yet they give an organization a much stronger basis for understanding its own past.
The focus on legacy records also fits a broader industry conversation about how old games are understood and revisited. For another perspective on the relationship between original works and modern reinterpretation, see why Capcom began its modern Resident Evil remakes with RE2 instead of the original.
The practical takeaway
Nintendo’s Digital Archivist, Historical Systems posting is a concrete move toward making its older hardware and software information easier to preserve, locate and use. The most consequential part is not an implied vault of secret games; it is the proposed infrastructure of metadata, standards, processes and collaboration around technical and historical materials.
For a company with thousands of releases and a long hardware history, a durable framework can help ensure that records remain connected to their context rather than fading into obscurity. The listing is only for a 12-month contract, and the public does not yet know the archive’s eventual outputs. But the position establishes a clear priority: Nintendo is seeking dedicated expertise to organize knowledge about its legacy systems before that knowledge becomes harder to recover.






