Senior Software Engineer (Agentic Search) – Web Rendering (Chromium) (opens in a new tab) Zurich

pbAbout Nebius: /b /ppNebius is leading a new era in cloud infrastructure for the global AI economy. We are building a full-stack AI cloud platform that supports developers and enterprises from data and model training through to production deployment, without the cost and complexity of building large in-house AI/ML infrastructure. /ppBuilt by engineers, for engineers. From large-scale GPU orchestration to inference optimization, we own the hard problems across compute, storage, networking and applied AI. /ppListed on Nasdaq (NBIS) and headquartered in Amsterdam, we have a global footprint with RD hubs across Europe, the UK, North America and Israel. Our team of 1,500+ includes hundreds of engineers with deep expertise across hardware, software and AI RD. /ph3bThe Product /b /h3pIn a rapidly evolving world, trust in AI depends on AI agents being grounded in fresh, verified real-world data. Search is the foundation that makes this possible. We are building an agent-native search platform designed specifically for AI systems rather than human users. Our product provides programmatic, low-latency, and observable search APIs that AI agents use to retrieve, filter, and reason over real-world information at scale. /ph3bThe Role /b /h3pWe are looking for a Senior Software Engineer to work on the rendering infrastructure of a novel search engine tailored for agentic AI consumption. /ppIn this role, you will focus on loading modern web pages in a browser that we patch and build ourselves, so that content is rendered completely and reliably at a cost that works across billions of pages. You will work inside Chromium to remove what we do not need, make the rest faster and cheaper, and keep our build current as Chromium moves. Your work ensures that high-quality content is consistently available to the indexing and retrieval systems downstream. /ppbIn this position, your responsibility will be to /b /pulliChange Chromium in its heavy core (Blink, the V8 integration, the compositor, the network service) to cut CPU, memory and startup cost per page /liliStrip Chromium down for agent workloads: skip what nobody needs, such as image and media decoding, web font downloads, and rasterization and GPU work where no one needs pixels, while keeping what page scripts depend on to run correctly (style, layout, animation frames, observers), and work out what breaks, or renders differently, when you do /liliKeep the browser compatible with the web: make sure that what we remove does not change how the sites we load behave or render /liliProfile and tune fleets of browsers: the process model, memory per renderer, startup, isolation and crash handling /liliBuild the production system around it: how browsers are launched, pooled, recycled and monitored /li /ulpbYou may be a good fit if you /b /ppHave 5+ years of experience building production systems, and are an expert in several of the following areas. /ppbInside the browser /b /pulliStrong C++ in a large, performance-critical codebase, ideally Chromium, Blink or V8, or a comparable browser engine (Rust is a plus) /liliChromium architecture: the process model, Mojo IPC, the rendering pipeline (DOM, style, layout, paint, compositing), and the network service /liliBuilding, debugging and shipping custom Chromium builds: the build system, tracing, crash analysis, and maintaining patches across releases /li /ulpbPerformance and systems /b /pulliProfiling CPU, memory and I/O for browser fleets, with tools such as perf, tracing and flame graphs /liliLinux process isolation and resource management, concurrency, and memory management /liliHave run browsers in production, or built the infrastructure that does, and can describe where the time and memory went /li /ulpbStrong candidates may also have experience with /b /pulliContributions to Chromium, Blink, V8, Firefox, WebKit or another browser engine /liliBuilding or maintaining a patched browser that you wrote the patches for /liliBrowser instrumentation, including the Chrome DevTools Protocol /liliWorking familiarity with how modern frontend frameworks render (SSR, CSR, streaming, hydration) /liliDistributed systems, Kubernetes, and Go or Python /li /ulpbThe kind of problems you will work on /b /pulliCut the cost of loading a page in half. Where do CPU and memory go, and what would you change in the browser? /liliTurn off the GPU and image decoding for agent workloads. What breaks, and what changes in how pages load and render? /liliA page runs a script that never yields. How do we detect and stop it without help from the page? /liliChromium ships a new version. How do we bring a large set of patches forward in days, not weeks? /liliDecide when a page is finished, for pages with analytics beacons, long polling and endless scrolling. /li /ulpWe conduct coding interviews as part of the process. /ppbBenefits Perks: /b /pulliCompetitive compensation /liliCareer growth and learning opportunities /liliFlexibility and ownership /liliCollaborative and innovative culture /liliOpportunity to work on impactful AI projects /liliInternational environment and talented teams /li /ulpbWhat's it like to work at Nebius: /b /ppFast moving- Bold thinking- Constant growth- Meaningful impact- Trust and real ownership- Opportunity to shape the future of AI /ppbEqual Opportunity Statement: /b /ppNebius is an equal opportunity employer. We are committed to fostering an inclusive and diverse workplace and to providing equal employment opportunities in all aspects of employment. We do not discriminate on the basis of race, color, religion, sex (including pregnancy), national origin, ancestry, age, disability, genetic information, marital status, veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by applicable law. /ppApplicants must be authorized to work in the country in which they apply and will be required to provide proof of employment eligibility as a condition of hire. /ppIf you need accommodations during the application process, please let us know. /p #J-18808-Ljbffr