Skip to main content

Software Engineer III, Core Data (multiple openings)

Posted 7 days ago

googleMadison (WI)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Software Engineer III, Core DataMid Experience driving progress, solving problems, and mentoring more junior team members; deeper expertise and applied knowledge within relevant area.
Minimum qualifications: Bachelor's degree in Computer Science, Engineering, Mathematics, Information Systems, or a related field and 2 years of experience in the job offered or in a Software Engineer-related occupation. Position requires 2 years of experience in the following: Software development with C, C++, Java, Python, C#, Ruby, Rust, or Go; Data structures, algorithms, unit testing, source management, software requirements collection, software module design, and operating & debugging production cloud infrastructure; and In one of the following: Machine learning infrastructure, Data analysis using SQL, Information retrieval and ranking, Web UI design & implementation with javascript or typescript, API design for cloud infrastructure, or optimizing low-level CPU & memory operations at the machine instruction / cache-line level.
About the job: The Core team builds the technical foundation behind Google's flagship products. We are owners and advocates for the underlying design elements, developer platforms, product components, and infrastructure at Google. These are the essential building blocks for excellent, safe, and coherent experiences for our users and drive the pace of innovation for every developer. We look across Google's products to build central solutions, break down technical barriers and strengthen existing systems. As the Core team, we have a mandate and a unique opportunity to impact important technical decisions across the company.
Responsibilities: Write software product or system code. Design software modules and participate in design reviews with peers and stakeholders to decide amongst available technologies. Review code developed by other developers and provide feedback to ensure best practices (e.g., style guidelines, checking code in, accuracy, testability, and efficiency). Participate in software testing, e.g. develop unit tests and release tests. Contribute to existing documentation or educational content and adapt content based on product/program updates and user feedback; and Triage product or system issues and debug/track/resolve by analyzing the sources of issues and the impact on hardware, network, or service operations and quality.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this