# Databricks consulting in Seattle, WA > Cloud software on the Eastside, commerce at global scale and the aircraft Boeing assembles in Everett and Renton, the very abstract and the very physical in one metro. Whichever side you work on, governance, evaluation and what a system costs to keep running tend to come up in the first meeting rather than the last. Canonical: https://www.techfabric.com/databricks-consulting-seattle Serving: Seattle, Bellevue, Redmond, Tacoma, Everett, Kirkland, Portland Headquarters: 1530 E Williams Field Rd, Ste 201, Gilbert, AZ 85295. No office in Seattle. --- ## Why Seattle work is our work Auditors keep asking where every copy of a customer lives, and with duplicates across the warehouse nobody can prove a deletion. We migrate the estate onto one governed lakehouse, with Unity Catalog lineage showing every copy, Delta making deletion provable and cost policies set as tables move. Washington's My Health My Data Act sharpens that here, for online retailers as much as Bellevue software companies and First Hill clinics. ## Work a buyer here would recognise Online orders end in a warehouse, where software has to keep pace with physical work. At Funko, the warehouse management system was built to cut operating expense, reduce reliance on manual work and double throughput efficiency, and operational efficiency doubled. ## In Washington, a shopping basket can be health data Seattle sits under Washington's My Health My Data Act, which reaches well past hospitals to the online retailers of South Lake Union and the warehouses of the Kent Valley. Infer a health condition from a shopping basket and you hold consumer health data, which needs consent to collect or share and must be deleted on request, backups included. Consumers can sue under the state's Consumer Protection Act. ## Questions ### Can a Seattle company under cap-and-invest keep its emissions data on Databricks? Yes, and we'd make the compliance figure the first thing it produces. Washington's program, which started on 1 January 2023, covers businesses emitting the equivalent of 25,000 metric tons of carbon dioxide or more a year, and each must obtain allowances equal to its emissions, according to the Department of Ecology. We'd land fuel purchases and meter reads in Delta and calculate emissions with factors held in a versioned reference table, so a recalculation after a factor changes can be explained line by line. Each reporting year gets a snapshot table, and each figure keeps the IDs of the purchases and reads behind it, so a verifier's question goes back to the source records. Sources: [the Department of Ecology](https://ecology.wa.gov/air-climate/climate-commitment-act/cap-and-invest) ### What would an airline or travel company in Seattle put on Databricks first? Disruption. We'd stream flight status into Delta and join it to bookings, so the operations desk sees who's affected and what rebooking will cost before a gate agent has to ask. Seattle-Tacoma International handled about 52.7 million passengers in 2025, with international travelers up to about 7.1 million, the Port of Seattle reports. We'd expect booking, flight and baggage events to arrive in different shapes at different speeds, so each feed gets its own ingestion job and a freshness check, and the disruption view shows how old its newest record is. Sources: [the Port of Seattle](https://www.portseattle.org/page/airport-statistics) ### Can a Seattle utility put smart meter data on Databricks safely? Yes, by keeping identity apart from the reads. A utility like Seattle City Light, community-owned and not-for-profit since the city's citizens created it in 1902, answers to the public, and interval meter reads at city scale suit a lakehouse well. We'd land the reads in Delta and keep customer identity in a separate table behind Unity Catalog masks, so analysts get load and outage views that never show an address. When a public records request asks who saw what, the audit system tables and grant history give you the access record to work from. Sources: [Seattle City Light](https://www.seattle.gov/city-light/about-us) ### How do you handle deletion and retention across a commerce estate? As a platform capability rather than a policy page. Retention rules and deletion requests act on the event log and the projections derived from it, so a deletion is a real operation with a record rather than a job somebody runs and hopes about. ## What databricks consulting covers ### Migration off Snowflake, Synapse and Teradata Run through TechFabric Airlift, with executable playbooks for twenty-seven source platforms, signed migration certificates, and a cutover you can reverse at two in the morning. ### Unity Catalog governance Catalogue and schema design, a grant model expressed through groups, row filters and column masks, and lineage that survives a refactor. The boundary your agents and Power BI inherit. ### Lakeflow pipelines Ingestion and Lakeflow jobs with schema evolution handled rather than hoped for, medallion boundaries drawn on purpose, and jobs that recover instead of restarting from zero. ### Databricks Apps and agents Applications that run inside the workspace under their own service principal, and agents on Unity Gateway that inherit catalogue permissions instead of routing around them. ### Genie and AI/BI Metric definitions agreed with the person who owns the number, and a benchmark suite Genie has to keep passing, so the answer holds up when finance checks it. ### Cost that somebody can defend Cluster policies, warehouse sizing, file layout and the queries that actually pay. Instrumented at build time rather than discovered on an invoice. ## Working with us from Arizona Arizona does not observe daylight saving, so from March to November we are on the same clock as you and from November to March we are an hour ahead. Either way the working day overlaps almost completely. Most delivery is remote or hybrid. We travel for discovery, workshops and the opening weeks of a build.