Architect and govern Workato-based enterprise automation, including LLM-powered workflows, at Coinbase scale

Coinbase's Enterprise Applications Integrations team is hiring a Workato Developer/Architect to design recipes, connectors, and automation frameworks connecting enterprise systems like Salesforce, NetSuite, Workday, and Snowflake, with a specific mandate to integrate LLM services into business processes responsibly. Interview centers on iPaaS/Workato architecture depth, ETL/ELT pipeline design, and judgment about governance and secure AI usage in automation.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Coinbase uses an AI-driven initial screening interview for qualified applicants before human interview rounds, per the posting's AI Disclosure.

What this interview tests

Workato recipe design, custom connectors, error handling, governance
Integration patterns for enterprise systems (Salesforce, NetSuite, Workday, Snowflake)
ETL/ELT pipeline development through iPaaS tooling
Responsible integration of LLM/AI services into business workflows with human oversight
Diagnosing and reducing technical debt in a live integration ecosystem

Common question themes

Walk me through a Workato recipe or automation you built, including how you handled errors and governance

Describe a custom connector or complex integration you architected and why you chose that pattern

How would you design a framework for using an LLM in a business process while keeping human oversight and compliance

Tell me about an ETL/ELT pipeline you built or supported through an iPaaS platform

How have you identified and reduced technical debt in an integration ecosystem

How candidates describe it

Real Software Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Coinbase Software Engineer interviews

All Coinbase interviews