Skip to content
Nash

Enterprise Solutions Consultant, ANZ

AustraliaRemote · Australia
FullTime · Customer Experience
POSTED 3 SEPTVERIFIED 11H AGO
Apply Ask
Role
68 days opentrue age
Posted 3 Sept
Pay
AUD 78k–AUD 140kno pay posted
Market p25–p75
AUD 78k–AUD 140k
Australia · n=37 · 365d to 6 Nov
CompanyNash →
23open roles
Opened · 30d
+0
Closed · 30d
−0
3d of snapshots · 30d window
Market
416,805open · Other
Opened · 7d
+21,8155% of open
All other
624,471open
All tracked boards · live 10 Nov · n=416,805
Visa
1H-1B LCAs · FY26
LCAs FY26 · n=1 · to 2026-06-17

ABOUT NASH

Nash is last-mile delivery infrastructure. We help the world's largest retailers and commerce companies orchestrate, optimize, and manage their delivery operations. Founded in San Francisco in 2021, backed by Andreessen Horowitz and Y Combinator, Nash works with enterprise customers across North America, Europe, APAC, and the Middle East.

Our platform sits at the center of complex delivery operations: connecting carriers, optimizing routes, managing fleets, and giving operators the visibility and control they need to run delivery at scale. We're not a marketplace. We're the infrastructure layer that makes the whole system work.

Every enterprise customer presents a different operational reality. A grocery chain running same-day delivery from hundreds of stores has different constraints than a retailer consolidating three carrier networks into one. Nash doesn't sell a fixed product off a price sheet. We design and configure the system around how each customer actually operates, then deploy with dedicated engineering and product support.

THE OPPORTUNITY

Nash's ANZ business is anchored by some of the region's largest retail and grocery brands: multi-product, multi-year partnerships in which delivery is core infrastructure. This role owns a small number of those relationships in full.

In International, customer success and solutions consulting are one seat. The person who designs the technical approach in a deal runs the launch that follows, then manages the account through adoption, performance, and renewal. You'll carry two to three enterprise accounts and the launches that come with them, from the sales cycle through go-live to the multi-year account work after it. This is one of two seats we're opening now in an established ANZ team, alongside two colleagues already in the role.

The accounts are large, the operations are complex, and the customer expects the person across the table to know their delivery operation as well as they do.

WHAT YOU'LL DO

LEAD TECHNICAL DISCOVERY AND DESIGN

Own the technical and operational depth in enterprise sales cycles for your accounts. Run discovery with the customer's engineering and operations teams, define the integration approach, configure the demonstrations and pilots that validate it, and resolve questions on architecture, data, and scale before they reach contract. The designs you produce become the launches you run, so they need to be correct at the point of proposal.

RUN LAUNCHES FROM SIGNATURE TO STEADY STATE

Own implementations for your accounts: requirements, configuration, integration, cutover, operator training, go-live, and the stabilization period that follows. Coordinate the customer's stakeholders and Nash's central engineering and specialist teams where a build requires them, and remain accountable for delivery performance until the operation runs without intervention.

MANAGE THE BOOK

Build durable relationships across your accounts, from the operators running stores and fleets to the executives funding the roadmap. Run the operating rhythm: business reviews, success plans, escalation paths. Track adoption, delivery performance, and platform health, and use them to identify what is underused, what is underperforming, and where the next workstream should be. This role carries no quota. Commercial expansion is owned by sales; this role owns the relationship, the adoption that justifies expansion, and the renewal.

FEED THE ROADMAP

Represent your customers inside Nash. Identify which gaps recur, which requests reflect one account's configuration versus a regional pattern, and what would change a customer's cost structure if Nash built it. Turn account knowledge into specific, prioritized product requests.

WHAT SUCCESS LOOKS LIKE

First 6 months

Full ownership of your accounts, with operating rhythms running and stakeholder maps built

At least one launch run from signature to steady state

Your technical designs in the proposals for every active deal on your accounts

Account health reporting that internal teams use

Source · NashFirst seen 2 NovOriginal ↗