Chromium developer Sharon Yang has described how working on the browser project differs between Google and Igalia, an employee-owned open-source consultancy, highlighting both the continuity of the technical work and the friction faced by contributors outside Google.
Yang spoke at FOSSY 2026 after spending six years working on Chrome at Google and then moving to Igalia. She continues to work in the same Chromium repository and with many of the same people. Chromium is the open-source foundation used by Chrome and other browsers, while Google maintains proprietary Chrome components separately.
The organizations are radically different in scale and ownership. Google employs roughly 180,000 people, compared with around 180 at Igalia. Google is owned by investors, while Igalia is owned by its workers. Yang said Igalia also uses equal pay across roles and locations, in contrast to the broad compensation range at Google. Her talk presented those differences as a comparison rather than a complaint about either employer.
Day-to-day development still depends on much of the same infrastructure. Google and Igalia engineers communicate through shared channels, and some Igalia Chromium work is funded directly or indirectly by Google, including a project routed through the Linux Foundation. The code base and many relationships therefore followed Yang across the move.
Access is less seamless outside Google. A faster Chromium build service is immediately available to Google employees, while external contributors must request permission. Yang also encounters bug reports that should be public but remain visible only inside Google because of problems associated with an earlier tracker migration. Access can be corrected, but doing so creates recurring overhead. Relevant material may also remain in Google documents that were not shared publicly.
Those issues reflect the fact that key development tools are maintained primarily for Google’s internal needs. External users cannot always provide direct feedback or request improvements. Yang characterized the obstacles as relatively small, but sufficient to remind an outside contributor that they are separate from the organization controlling much of the project’s infrastructure.
The choice of work changes too. At Google, Yang said projects tended to follow management priorities and often emphasized new features or measurable outcomes that could support promotion cases. Igalia more often receives technically driven assignments involving code health and accumulated maintenance work. That can direct engineering attention toward tasks that are important to the project but less visible as product features.
The comparison illustrates a central tension in large open-source projects backed by dominant companies. Chromium accepts work from a wider community and supports browsers beyond Chrome, yet much of its tooling, information flow and agenda remains tied to Google. Independent firms such as Igalia can contribute substantial engineering capacity, but their developers still navigate systems designed around the project’s largest participant.
