Logistics Analyst - Control Tower

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "About The Team", "What We Are Looking For", then bullet list of responsibilities (Vehicle Movement & Dispatch Coordination etc.), then Required Qualifications, Desirable Qualifications, Success Criteria, Pay (salary range), Benefits (annual bonus, equity compensation, benefits), Schedule (in-person work at least 3 days per week). Also maybe "About the role" heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We have content for: - About the role: could be "What We Are Looking For" paragraph describing role. That's substantive. - Responsibilities: the bullet list under "Vehicle Movement & Dispatch Coordination", "Data Exchange & Systems Coordination", "Warehousing & Reverse Logistics", "Stakeholder Alignment & Communication", "Continuous Improvement". Those are duties. - Requirements: could be Required Qualifications. - Qualifications: maybe Desirable Qualifications? Or we could combine Required and Desirable under Qualifications? But instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Required Qualifications and Desirable Qualifications. Could map Required Qualifications to Requirements, Desirable Qualifications to Qualifications (or Skills). Also we have Success Criteria maybe could be under Skills? But better to treat Success Criteria as maybe a separate section? Not listed but we could omit if not matching headings. However we need to preserve all substantive information; we can include Success Criteria under maybe a heading like "Performance Expectations" but not allowed headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exhaustive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. We can also add other headings if needed, but better to stick to those. Success Criteria could go under Requirements or Qualifications? Might be considered part of Requirements? But it's more about performance metrics. Could treat as "Skills"? Not really. Could create a section "Performance Expectations" but not in list. Might be okay to add but risk deviating. Safer to incorporate Success Criteria into Responsibilities or Requirements? Probably better to add a section "Performance Expectations" but not in examples; but instruction says use those headings for section headings (e.g.) meaning you can use those or similar? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests those are the expected headings. I'd include only those that have content. Thus sections: - About the role: from "What We Are Looking For" paragraph(s) describing role. - Responsibilities: bullet list of duties. - Requirements: Required Qualifications. - Qualifications: Desirable Qualifications (maybe also include Skills? but we have no separate skills list). Could also include Success Criteria under Qualifications? Might be okay. - Benefits: mention annual bonus, equity compensation, benefits. - Pay: salary range $87,000 - $139,000 per year. - Schedule: in-person work at least 3 days per week, up to 5 days per week based on operational needs. We also have "Who We Are" and "About The Team" maybe could be part of About the role? But we could incorporate into About the role section as introductory paragraphs. The instruction: do NOT repeat the job title as a heading (the page already shows it). So we can have About the role heading and then include paragraphs about Aurora mission, team, etc. That's fine. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out sections like "Working at Aurora", "Our commitment to safety", "Our commitment to inclusion", etc. Also remove "For the latest news from Aurora, visit aurora.tech or follow us on LinkedIn." That's boilerplate? It's maybe okay to keep? It's not substantive about role. Likely remove. Also remove "For roles based in Pittsburgh, PA: The salary range..." we keep salary range. Also remove "Aurora’s pay ranges are determined by role, level, and location..." maybe keep as part of Pay section? It's somewhat generic but still about pay. Could keep but it's not specific detail; but it's still about pay determination. Might be okay to keep as part of Pay section. Also remove "The successful candidate will also be eligible for an annual bonus, equity compensation, and benefits." Keep under Benefits. Also remove "Working at Aurora..." etc. Also remove "Our commitment to safety", "Our commitment to inclusion", etc. Also remove "For California applicants..." etc. Also remove "If you need assistance..." etc. Now craft HTML. Structure:

About the role

... paragraphs combining Who We Are, About The Team, What We Are Looking For ...

Responsibilities

• Vehicle Movement & Dispatch Coordination: Coordinate the movement of all Aurora vehicles across the network, including end-of-line truck transport, service moves, and inter-site transfers; triage competing priorities in real time, separating immediate fires from emerging risks and sequencing work to match; navigate supplier and carrier portals and data exchanges to schedule, track, and confirm vehicle movements
• Data Exchange & Systems Coordination: Manage internal and external data exchanges across NetSuite, EDI, JIRA, and partner systems so that information stays accurate and timely; partner with Implementation Teams as critical system needs arise, representing logistics requirements in ERP, EDI, and JIRA work; actively seek out and test new technology, including AI tools, automation, and emerging NetSuite functionality, and bring forward ideas for how it can improve Control Tower operations before being asked; adopt new tools quickly to manage processes where no safety net or established workflow exists
• Warehousing & Reverse Logistics: Coordinate warehousing activity and reverse logistics flows across Aurora sites and third-party partners; keep material and vehicle status visible to the stakeholders who depend on it
• Stakeholder Alignment & Communication: Serve as the connective layer between logistics execution and stakeholder orgs that lack direct visibility into logistics systems; communicate risk, delay, and cost exposure proactively when disruptions such as customs holds, freight delays, or vendor issues affect downstream teams; engage directly with internal and external partners by phone, Slack, and email, often under time pressure
• Continuous Improvement: Develop continuous improvement plans that close existing gaps and prevent new ones; design interim solutions for foreseeable issues while current priorities are handled

Requirements

• 5+ years in logistics, dispatch, transportation, or supply chain operations, ideally in a fast-changing industry with shifting priorities at the task and project level
• A demonstrated track record of proactively adopting new technology (AI tools, automation, NetSuite, or similar) and championing it with peers, not just using it when required
• Proven ability to switch rapidly across multiple tasks, projects, stakeholders, and deliverables while keeping accurate recall of details and status
• Experience navigating supplier and carrier portals and data exchanges for vehicle or freight movements

Qualifications

• Thick skin and an eagerness (not just willingness) to engage with external and internal partners, often by phone
• Comfort making autonomous decisions in time-sensitive situations
• Meticulous organization
• Familiarity with EDI, JIRA, customs, freight, or vehicle transport operations

Maybe also include Success Criteria under Qualifications? Could add as another bullet list under Qualifications? But we already have Qualifications heading; we could add Success Criteria as a separate section? Not in list. Could incorporate into Qualifications as additional bullets: "Success criteria include..." but that might be mixing. Perhaps better to add a separate section "Performance Expectations" but not in examples. However instruction says "Prefer a few substantive sections over many thin ones." So we could merge Success Criteria into Qualifications or Requirements. I'd add them under Qualifications as additional bullets. Thus Qualifications bullets include both desirable qualifications and success criteria. Let's list: - Thick skin and an eagerness (not just willingness) to engage with external and internal partners, often by phone - Comfort making autonomous decisions in time-sensitive situations - Meticulous organization - Familiarity with EDI, JIRA, customs, freight, or vehicle transport operations - Vehicle movements are coordinated reliably, with issues caught and resolved before they affect downstream schedules - Stakeholders trust Control Tower status updates and use them to make decisions - Data exchanges across internal systems and external partners stay accurate and current - Emerging issues are identified early and have interim solutions ready before they become fires - Continuous improvement plans produce measurable progress toward supply chain maturity - New tools and technologies are regularly identified, piloted, and adopted to improve Control Tower speed, accuracy, and scale That seems okay. Now Benefits section:

Benefits

• Annual bonus
• Equity compensation
• Comprehensive benefits (health, dental, vision, etc.)

But we need to preserve exact wording: "The successful candidate will also be eligible for an annual bonus, equity compensation, and benefits." So we can put that as a

or list. Pay section:

Pay

For roles based in Pittsburgh, PA: The salary range for this position is $87,000 - $139,000 per year. Aurora’s pay ranges are determined by role, level, and location. Within the range, the successful candidate’s starting base pay will be determined based on factors including job-related skills, experience, qualifications, relevant education or training, and market conditions. These ranges may be modified in the future.

Schedule section:

Schedule

Aurora expects in‑person work at least 3 days per week, with some roles requiring more frequent in‑office presence, up to 5 days per week, based on operational needs.

Now About the role paragraph: combine Who We Are, About The Team, What We Are Looking For. Let's craft:

Aurora’s mission is to deliver the benefits of self‑driving technology safely, quickly, and broadly. The Aurora Driver will create a new era in mobility and logistics, bringing a safer, more efficient, and more accessible future to everyone. At Aurora you will tackle massively complex problems alongside passionate, intelligent individuals, growing as an expert while expanding your knowledge.

The Supply Chain Operations team manages the end‑to‑end logistics backbone for Aurora's autonomous trucking hardware and vehicle programs, covering inventory, shipping and receiving, ERP operations, campus logistics, vehicle movement, and cross‑functional supplier management across Pittsburgh, Bozeman, Mountain View, and Texas.

The Control Tower Analyst is the real‑time coordination hub for Aurora's supply chain. This role coordinates the movement of all vehicles, manages internal and external data exchanges, keeps internal stakeholders aligned, and directs warehousing and reverse logistics activity across the network — functioning like air traffic control. You will switch between tasks, projects, stakeholders, and deliverables every few minutes, prioritizing active fires, emerging risks, and items that can wait, designing solutions for the latter before they arise. Beyond daily execution, you will build continuous improvement