Sr. SAP Integration Architect

Auger is the autonomous operating system for supply chains — the layer that finally allows disparate systems like ERP, WMS, and TMS to work together instead of against each other. Most supply chain software surfaces problems and waits for a human to act. Auger solves them. Our AI detects disruptions, evaluates trade-offs, and executes decisions automatically — moving from signal to action in seconds, not weeks.

We eliminate the Coordination Tax: the billions in capital and time lost when disconnected systems force the best people in the business to become the Human API between planning and execution. At Auger, we design autonomy into our systems. We expect the same from our people.

• Clear ownership, not decision by consensus
• First principles over inherited patterns
• Shipping systems, not slide decks
• Fast feedback from reality, not opinions

AugerOS reads a customer's operational data, models their supply chain, and recommends decisions on allocation, sourcing, risk, and execution. Then it writes those decisions back into the systems where work gets done. For many of our enterprise manufacturing and distribution customers, that system is SAP. Getting data out and decisions back in, with the right authorization, idempotency, and audit trail, is hard, and it's central to what we deliver.

You'll be the person who makes that work. You're Auger's SAP authority. You walk into a customer's SAP team, figure out how their landscape is really configured (not how the diagram says it is), and design the ingestion and write-back approach for that engagement. When the work requires changes inside the customer's SAP, you scope it, pick and direct the specialist partners, and decide whether what they deliver is good enough to ship.

You'll sit between Auger engineering, customer SAP and IT teams, and third-party SAP partners, and you'll be the one who can tell a good design from a risky one, with the standing to say so. There's no legacy SAP playbook here. The discovery process, reference architectures, and partner bench are yours to build, and the whole company will use them.

You'll get customer-facing, architectural, contractual, and educational work in one role, on decisions that change what a customer buys, moves, and ships.

• Lead sessions with customer SAP teams to map the landscape: ECC or S/4
  
  HANA (on-prem, RISE, private cloud), instances and clients, middleware (PI/PO, Integration Suite/CPI, BTP), and existing extraction tools.
• Work out how each customer has configured and customized the objects we depend on: materials, BOMs, purchase and sales orders, deliveries, inventory, MRP, vendors, customers.
• Produce artifacts people use: landscape diagrams, object and field mappings, volume and change-frequency profiles, open-risk logs.

• Choose the right extraction pattern per customer from the full toolbox: ODP/ODQ, SLT, CDS views, OData, IDocs, BAPIs/RFCs, Datasphere and Business Data Cloud, third-party tools, file or event-driven.
• Design write-backs (POs, stock transport orders, allocations) with real attention to authorization, principal propagation, error handling, idempotency, and auditability.
• Weigh each option against the customer's licensing, SAP's API and extraction policies, security requirements, and their IT team's preferences, then drive to a design both sides sign off on.
• Work with our engineers on how SAP data lands in Snowflake, Databricks, or Fabric and maps into our data model.

• Define the work needed inside customer systems: custom CDS views, function modules, BAdIs, iFlows, authorization roles.
• Source and evaluate SAP subcontractors, review their SOWs…