1

Chromium Developer Jobs in California (NOW HIRING)

We're looking for top-tier engineers who understand browser internals, are not fazed by the ... Contributions to WebKit, Chromium, Mozilla or other browser components. Additional Information All ...

Software Engineer, Web Layer

San Francisco, CA ยท On-site

$255K - $405K/yr

Are a strong C++ developer, especially with experience in browser environments like Chromium and Electron. Since this role is more backend focused, general knowledge of web development and TypeScript ...

Software Engineer, Web Layer

San Francisco, CA ยท On-site

$255K - $405K/yr

Are a strong C++ developer, especially with experience in browser environments like Chromium and Electron. Since this role is more backend focused, general knowledge of web development and TypeScript ...

... DevOps. Shipping follows the Chromium release train, with a stable release roughly every four weeks across the Canary, Dev, Beta, and Stable channels. Those two cadences do not line up on their own.

About The Role As a Senior Frontend Engineer at Zoo, you'll play a crucial role in the development ... Understanding of browser internals across major browsers (Chrome, Firefox, Chromium, Brave, etc ...

Environmental Health and Safety Engineer

Long Beach, CA ยท On-site

$76K - $100K/yr

Engineering & Project Management: * Review facility design changes and capital projects to ensure ... chromium or cadmium, and ergonomic challenges) and interpret results to drive improvements.

Senior Software Engineer, Frontend

Los Angeles, CA ยท On-site +1

$145K - $195K/yr

Our platform combines a modern, cloud-native CAD environment with AI-powered engineering workflows ... Understanding of browser internals across major browsers (Chrome, Firefox, Chromium, Brave, etc ...

$276K - $289K/yr

Navigate the evolving browser ecosystem-including Chromium, WebExtensions APIs, Safari and Firefox ... Partner deeply with Advanced R&D, threat research, data science, and engineering teams to translate ...

Showing results 21-40

Chromium Developer information

What is a Chromium developer?

Chromium Developers are software engineers who contribute to the development and maintenance of the Chromium project, the open-source web browser project that forms the basis for Google Chrome and other browsers. They work on browser features, performance improvements, bug fixes, and security enhancements. Chromium Developers may work for companies like Google or contribute as independent open-source contributors, collaborating with a global community to improve web browsing experiences.

What are the key skills and qualifications needed to thrive as a Chromium developer, and why are they important?

To thrive as a Chromium Developer, you need advanced proficiency in C++, strong understanding of browser architectures, and experience with open-source development, often supported by a degree in computer science or a related field. Familiarity with version control systems like Git, build tools such as GN, and debugging tools like gdb are typically required. Excellent problem-solving, collaboration, and communication skills set standout developers apart in this field. These skills and qualities are vital for efficiently contributing to a complex, collaborative project that impacts millions of users.

What are some common challenges Chromium developers face when integrating new features into the browser?

Chromium Developers often encounter challenges such as ensuring cross-platform compatibility, maintaining high performance, and adhering to strict security standards when integrating new features. The codebase is large and complex, requiring thorough testing to avoid regressions and unintended side effects. Collaboration with other teamsโ€”such as security, user interface, and testing teamsโ€”is essential to ensure that new features align with Chromiumโ€™s architectural guidelines and user experience expectations.

What cities in California are hiring for Chromium Developer jobs?

Cities in California with the most Chromium Developer job openings:

Infographic showing various Chromium Developer job openings in California as of September 2026, with employment types broken down into 84% Full Time, 7% Part Time, 1% Temporary, and 8% Contract. Highlights an 76% Physical, 5% Hybrid, and 19% Remote job distribution.

AI Engineer Engineering San Francisco + 5

San Francisco, CA โ€ข On-site

Other

Posted 13 days ago


Job description

# AI Engineer## CategoryEngineering## Available in* San Francisco* London* Beijing* Shanghai* Shenzhen* Qingdao## About PhinomenonPhinomenon is built by browser and cloud veterans: our founders are behind FydeOS (a Chromium-based OS trusted by millions) and QingCloud (one of China's earliest API-first IaaS platforms, founded in 2012). Fresh off a healthy, eight-figure Series A raise, we have the runway to dream big without panicking about next week's payroll. With folks working from San Francisco, London, Beijing, Shanghai and Shenzhen, we are proudly global and friendly to your time zone, with overlapping hours so we can all actually talk. We ship fast and ship hard, but burnout is so last decade: we bake in wellness stipends, mandatory recharge days and flexible schedules, because great code comes from healthy lives. No timecards, no surveillance software, no weekend team-building. We'd rather hand you the best tools money can buy (Claude Max, ChatGPT Business and Cursor Ultra come standard) and trust you with them. We don't fetishise years of experience, degrees or big-tech logos, and fresh graduates are more than welcome: show us what you have built and how you think. If you want to build the nextgen browser that actually, you know, gets you, while still enjoying your evenings and maintaining upright posture, welcome home.## About the RoleAs an AI Engineer at Phinomenon, you build the AI system behind Phi Browser, all of it. Agents are infrastructure too: the same person who designs phi-agent's planning loops, tool use, and record-to-skill workflows should understand the local-first memory and knowledge systems those agents draw on, and be able to ship the APIs, data layers, and UIs that carry them to users. You'll work with frontier models and open protocols (MCP and friends), engineer for on-device constraints where every megabyte is someone's laptop, and ship weekly into a product people live in all day. The goal is simple to say and hard to build: a browser that's genuinely on your side. Your browser friend, not another company's data funnel.## Responsibilities* Build phi-agent's core loops: planning, tool use, skill execution, and graceful recovery when the web fights back* Develop browser-native agent capabilities: tab and workspace control, page understanding, record-to-skill workflows* Design and build the memory and knowledge systems underneath: local-first storage, ingestion to clean Markdown, hybrid retrieval, and proactive resurfacing* Ship the full stack that carries it (APIs, data layers, and web UIs), owning features end to end* Integrate and evaluate frontier LLMs; own context engineering and the cost/latency/quality trade-offs, including BYO-LLM paths* Expose Phi's capabilities to third-party agents via MCP and emerging open standards* Harden the AI surface against prompt injection, adversarial pages, and content poisoning; safety is a feature, not a patch* Instrument everything: evals, telemetry, and benchmarks that prove the system is actually getting smarter## Requirements* Show us AI systems you've actually built: agents, RAG/retrieval pipelines, or LLM-powered products in real use. We don't count years, degrees, or logos, and a new grad with a serious agent project is very much in the running.* Strong TypeScript or Python, and the range to move between agent logic, storage and retrieval internals, and UI without waiting for someone else* Hands-on fluency with modern agent patterns: function calling, planning loops, memory, evaluation harnesses* Pragmatic model sense: you know when to reach for a frontier model, a small one, or no model at all* Respect for user data as a design constraint: exportability, reversibility, local-first performance on consumer hardware* A security-aware mindset: every webpage is potentially hostile input to your agent* A bias for shipping: weekly releases don't scare you; unvalidated cleverness does## Nice to Have* Experience with Chromium/CDP, Playwright, or other browser-automation internals* Familiarity with SQLite/FTS, embedded vector stores, or local-first architectures (CRDTs, file-sync)* Contributions to open-source agent frameworks or the MCP ecosystem* Experience building eval pipelines for non-deterministic systems* You've built and abandoned your own second-brain system, and know exactly whyAnd should the future prove entirely too exhausting, there is a switch to disable all AI features. No offense will be taken. #J-18808-Ljbffr