iOS Engineer at Google (2026): Bazel, Abseil, Style Guide, L Levels

What Google publishes about the role

Google's iOS roles are posted at google.com/about/careers as Software Engineer with iOS or Mobile specialty. The product surfaces:

• Google Maps iOS: One of the largest iOS apps Google ships. Heavy on rendering performance, large code-shared C++ surface for the map engine.
• Gmail iOS: Older codebase with significant Objective-C; modernising to Swift. Calendar / Tasks adjacency.
• Google Photos iOS: Photo processing pipeline shared with Android via C++ libs. ML adjacency through on-device model conversion.
• YouTube iOS: Standalone team. Video player heavy. Shared with the YouTube backend org.
• Google Drive / Docs iOS: Productivity-suite iOS clients.
• Gemini iOS: The Apple-facing Gemini app. Newer team, more modern Swift and SwiftUI than the legacy apps.
• Firebase / AdMob / Google Sign-In SDKs: Developer-facing iOS frameworks. Public, open-source, broadly adopted.

Google's mobile engineering blog content lives across developers.googleblog.com, the Firebase blog (firebase.blog), and the Google Open Source blog (opensource.googleblog.com) where Bazel-rules_apple updates are announced.

The interview: algorithmic emphasis with iOS-specific deep-dives

Google's iOS interview shape:

1. Recruiter screen. Career timeline, level calibration.
2. Technical phone screen (1–2 rounds). 45 minutes each. Algorithmic problems on Google Docs (no syntax highlighting). Pure Swift fine.
3. On-site (4–5 rounds):
   • Two coding rounds — algorithmic, harder than the screen. Trees, graphs, dynamic programming, occasional bit manipulation. Google's coding bar is the highest of FAANG by reputation.
   • One system design round at L5+ — distributed-systems leaning even at iOS interviews. Common asks: design Google Maps offline tiles, design Drive sync, design an iOS push system at planet scale.
   • One iOS-specific round — UIKit / SwiftUI / lifecycle / memory / threading / occasionally architecture.
   • One behavioral / Googleyness round.
4. Hiring committee. Decisions go to a hiring committee, not just the interviewers. Adds 1–2 weeks to the timeline.
5. Team match. Similar to Meta — candidates can match with multiple teams that have headcount.

The Google-shaped specifics: algorithmic rigor is highest. iOS-specific knowledge matters but the bar to clear is coding fluency at the level Google expects of all SWEs — iOS is not a separate easier track. System design at iOS interviews still leans distributed-systems, which differs from Meta's mobile-specific shape and Apple's framework-design shape.

The Google iOS stack: Bazel, Abseil, the Style Guide

Google's iOS apps don't run on a stock Apple stack. Three systems define the shape:

# BAZEL — Google's open-source build system. Apps build via rules_apple.
# BUILD file (Starlark, Python-like syntax)
load("@build_bazel_rules_apple//apple:ios.bzl", "ios_application")
load("@build_bazel_rules_swift//swift:swift.bzl", "swift_library")

swift_library(
    name = "FeedKit",
    srcs = glob(["Sources/**/*.swift"]),
    deps = [
        "//Apps/Common/UI:UICore",
        "//Vendor/Abseil:absl_strings",
    ],
    module_name = "FeedKit",
)

ios_application(
    name = "GoogleApp",
    bundle_id = "com.google.app",
    families = ["iphone", "ipad"],
    infoplists = ["//Apps/Resources:Info.plist"],
    minimum_os_version = "17.0",
    deps = [":FeedKit"],
)
# rules_apple: github.com/bazelbuild/rules_apple
# Bazel: github.com/bazelbuild/bazel

// ABSEIL — Google's C++ common library.
// Performance-critical iOS work bridges Swift to Abseil-based C++.
// SE-0344 (Direct C++ interop, Swift 5.9+) made this ergonomic.

// In a C++ shared library used by Google Maps iOS:
#include <absl/strings/str_split.h>

std::vector<std::string> ParseTileKey(absl::string_view key) {
    return absl::StrSplit(key, '/');
}

// On the Swift side — direct interop, no Objective-C bridging
import TileParserCpp  // C++ module

func segments(of key: String) -> [String] {
    let cppView = std.string(key)
    let result = TileParserCpp.parseTileKey(cppView)
    return result.map(String.init)
}

The Google iOS Style Guide is publicly maintained at github.com/google/styleguide/blob/gh-pages/objcguide.md (Objective-C) and github.com/google/swift/blob/main/style/Swift.md (Swift). The Swift guide is one of the most thorough public iOS style guides; Google engineers are expected to read it on onboarding and follow it daily. Specific norms: explicit type annotations on stored properties, no force-unwraps in production code, NSError-bridging conventions for legacy Objective-C interop.

Compensation: California pay transparency, L5 reality

Google is California-headquartered, subject to SB-1162 pay-transparency. Per levels.fyi/companies/google/salaries/software-engineer (2026 data):

Google's pay-transparency-required range on a typical Senior iOS posting in California is around $189k–$280k base, plus stock and bonus. Stock vests on a non-uniform schedule (33%/33%/22%/12% over 4 years historically; check current postings). Refreshes happen at the annual cycle.