Own Oracle Fusion ERP technical solutions across Lyft Finance and Supply Chain systems

This is a Technical Business Systems Engineering role supporting Lyft corporate Finance and Supply Chain systems, building Oracle Fusion Cloud integrations, reports, and automations that keep month-end close, SOX compliance, and bank transmissions running reliably. The interview centers on hands-on Oracle Fusion technical depth including OTBI, BI Publisher, FBDI, OIC, and SQL and PL-SQL, plus the operational discipline of supporting finance close cycles and audits.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Oracle Fusion Financial and Supply Chain module technical depth
Integrations with boundary systems such as tax engines, billing, banking, and payment gateways
SQL and PL-SQL for data extraction, transformation, and validation
Month-end and period-close support under time pressure
SOX compliance evidence and audit support
Oracle environment management across Dev, Test, UAT, Prod, patches, and upgrades

Common question themes

Walk me through an integration you built between Oracle Fusion Financials and an external system

Describe supporting a time-sensitive month-end close and how you resolved an issue under pressure

How have you used OTBI, BI Publisher, or FBDI to build a finance reporting solution

Tell me about writing SQL or PL-SQL for a data validation or migration task

How do you gather and present evidence for SOX controls during an audit

Describe managing an Oracle Fusion Cloud environment refresh or quarterly update

How candidates describe it

Real Business Systems 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 Lyft Business Systems Engineer interviews

All Lyft interviews