Finance Manager, Imports Cost Automation

Do you want to build the financial foundation an entire business runs on? We are looking for a Finance leader to manage the infrastructure build out and standardization of the cost reporting, metrics, and definitions behind Amazon"s $1.2B+ US Imports network. This is not a role that maintains someone else"s reporting. You will decide how imports cost gets measured, build the pipeline that produces it, and own the network-level view leadership uses to understand why cost moved. If you are energized by ambiguity, by standardizing what has never been standardized, and by work that is foundational to the business, this is one of the highest-leverage seats in Inbound finance.

Global Logistics supports Amazon-managed Inbound transportation service offerings across Domestic and Import vendors and sellers. This role sits at the intersection of our Business Intelligence, Data Engineering, FP&A, Operations, Product and Controllership partners - building out the imports cost reporting pipeline, standardizing the definitions, metrics and KPIs the imports team reports on, and partnering with central FP&A to embed those standards in weekly business reviews, month-end close, and the OP and quarterly guidance cycles.

Key job responsibilities

• Build and own the US Imports cost reporting pipeline in partnership with Business Intelligence and Data Engineering teams, acting as the finance product owner from requirements through acceptance and validation.
• Establish and govern the metric and KPI standards for imports - cost per container, cost per unit, cost per FEU, dwell, utilization and mix ratios - defining the grain and scope boundary for each, and enforcing consistent use across Finance, Operations, and Forecasting teams.
• Support building the network-level cost bridge, decomposing volume/mix/rate variances across all eight import cost legs and reconciling bottoms-up leg builds into one auditable view each reporting cycle.
• Partner with central FP&A to standardize reporting mechanisms across weekly business reviews, month-end close and planning cycles, improving both cycle time and accuracy.
• Proactively identify unowned and misallocated cost streams - new corridors, new program launches, cross-org entitlements - quantify the exposure, and drive each to a named owner.

A day in the life

You will start your day on the network bridge, tracing an unexpected transload adjustment back to a source data field before anyone builds commentary on a number that is incorrect. You might then spend an hour with Data Engineering mapping a new charge code that is currently landing in an unallocated bucket, then give Topology the leg-level cost build for a proposed new node - not a single blended number, but the underlying input assumptions that will actually drive the decision. In the afternoon you settle a definitional conflict with central FP&A where the same cost-per-container figure does not tie between the business review and the planning file because the denominators differ, and you update the template so the decision is enforced by the mechanism instead of by your memory. Throughout, you will balance the recurring weekly and monthly review cadences against the longer-horizon work to streamline and automate recurring issues.