The question posed by a software developer with a year of experience, a love for orcas, and a plan to relocate to Seattle is one we hear more often than you might think. It is the question of whether a technical skill set can be repurposed for the ocean without a complete career reset. The short answer is yes, but the longer, more practical answer requires recalibrating what "working with whales" actually means in the modern data ecosystem. Your CS background is not a detour from conservation; it is a direct on-ramp to the field's most pressing need: bridging data gaps in marine observation.
The good news is that Seattle is not a compromise location for this work. It is a hub for NOAA's Northwest Fisheries Science Center, the Applied Physics Lab at the University of Washington, and a dense network of NGOs and private firms focused on hydroacoustic monitoring, satellite imagery, and passive acoustic tracking. The job market for GIS is healthy, though it skews toward analysts rather than field scientists. A GIS certificate, particularly one that emphasizes remote sensing and spatial-temporal data integration, is a practical and credible step. It gives you the vocabulary to bridge software engineering with physical oceanography. The UW Friday Harbor program, while immersive and enticing, is designed for degree-seeking students; as a post-bac, you may find limited slots, but the experience itself is less about the credential and more about confirming whether you want to trade a keyboard for a rocking deck. That is a valid experiment, but not the only one.
What you are describing is not a single job title but a spectrum. The roles that let you stay in Seattle and work on whales are often one step removed from the animals: building the pipelines that process acoustic data, calibrating the sensors on gliders, or integrating the citizen science observations that expand our coverage of critical habitats. If your goal is to be on the water weekly, that is a different path, one that typically requires a marine biology degree and a willingness to relocate to remote coastal stations. But if your goal is to contribute to the protection of orcas in the Salish Sea, your software skills are the most direct route to making that happen. The marine studies pathway is not the only one, and for a technical professional, it is often the slowest.
Our take is this: stop asking if the job exists and start building the portfolio that proves it does. Enroll in a GIS certificate now, but pair it with a personal project that analyzes publicly available hydrophone data from the Orca Conservancy or the Salish Sea Hydrophone Network. That single project will tell you more about the work than any 10-week field program, and it will give you a concrete artifact to show hiring managers. You do not need to choose between being a computer scientist and being an ocean steward; you need to become a specialist in the intersection. The question is not whether you can live in Seattle, but whether you can translate your coding fluency into the language of climate indicators and validated, peer-reviewed data. That is the skill the field needs most, and it is the one you already possess.
Watch for roles with titles like "Data Scientist, Conservation" or "Software Engineer, Ocean Monitoring" at institutions like the Allen Institute for AI or Conservation International Northwest. They are rare, but they are not mythical. If you cannot find one, that is because the field is still maturing, and the person who designs that role for themselves, with a GIS certificate and a demonstrable project, will be the one who gets to write the job description.