Own Lyft's Oracle FCCS/ARCS/EDMCS consolidation and reconciliation systems end to end

Lyft is hiring a Business Systems Engineer to administer and architect its corporate Oracle EPM Cloud stack — FCCS, ARCS, Data Exchange, and EDMCS — powering financial consolidation, reconciliation, and close. The role sits at the intersection of finance and engineering, needing deep hands-on configuration skill (business rules, reconciliation frameworks, SQL/Groovy/EPM Automate) plus the judgment to translate Finance's requirements into technical solutions. Toronto, hybrid 3 days/week, 5+ years of Oracle EPM experience expected.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

FCCS: business rules, translation overrides, intercompany eliminations
ARCS: reconciliation frameworks, automated data loads
EDMCS metadata governance and integration with Oracle ERP/EPM Cloud
SQL, Groovy scripting, and EPM Automate for custom solutions
Troubleshooting production EPM incidents (metadata, data loads, mappings)
Translating Finance/Accounting requirements into technical EPM solutions

Common question themes

Walk through an FCCS business rule or intercompany elimination you built

Describe an ARCS reconciliation framework you designed from scratch

How have you used Groovy scripting or EPM Automate to automate an EPM workflow

Tell me about a production EPM incident you diagnosed and resolved

How do you explain a technical EPM/close issue to a Finance stakeholder

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