Support and enhance Lyft's Oracle Fusion Order-to-Cash systems as a techno-functional engineer

Lyft is hiring a Business Systems Engineer to support and continuously enhance the Order-to-Cash lifecycle within Oracle Fusion Cloud (or R12), bridging Finance/Supply Chain business stakeholders and technical implementation. The role wants 4-5 years of hands-on Oracle Financials/Supply Chain implementation experience, SQL/PL/SQL and OTBI reporting skills, and comfort working month-end close support calls while reporting to a senior Business Systems Engineer.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Oracle Fusion Order-to-Cash configuration and support
SQL/PL/SQL and OTBI reporting for ERP issue diagnosis
Translating business requirements into ERP solution architecture
Month-end close support and stakeholder communication under pressure
FBDI data migration and SOX compliance support
Working within a team structure reporting to a senior engineer

Common question themes

Describe an Order-to-Cash issue you diagnosed and fixed in Oracle Fusion

Walk through how you've used SQL/PL/SQL or OTBI to solve a reporting problem

Tell me about supporting a month-end close under time pressure

How have you translated a business stakeholder's requirement into an ERP configuration

Describe your experience with FBDI data migration

How do you communicate technical tradeoffs to non-technical finance stakeholders

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