How to get hired as a supply chain analyst in 2026-27

"Supply chain analyst" names at least seven different jobs. Identify which one the posting means

Supply chain analyst is a container title. Underneath it sit demand planning, supply and production planning, inventory analysis, logistics and transportation, procurement and sourcing, network design, and retail replenishment. They report to different managers, run on different systems, are judged on different metrics and are tested differently in interview. One generic resume sent to all of them is the most common reason a qualified candidate hears nothing back.

You can identify the variant in under a minute from the nouns in the posting. The vocabulary is not filler. It is the hiring manager describing what they do on a Tuesday. Match the top third of your resume to it and leave the rest of your history below the fold.

The same reading answers "supply chain analyst versus logistics analyst". Logistics analyst is one of the variants below, scoped to the movement and storage of goods. Supply chain analyst can mean any of the seven. Employers use both loosely and sometimes interchangeably, so read the responsibilities and the named systems, never the title.

Two practical points about where the openings are. By headcount, planning and inventory seats inside manufacturers, distributors and retailers vastly outnumber the consulting and tech supply chain roles that dominate online advice, and they care least where you went to school. And they sit near plants and distribution centres: Columbus, Memphis, Greenville, Bentonville, Laredo, Reno and a hundred similar places rather than the cities people filter for.

One warning at the junior end. At some 3PLs, brokerages and smaller distributors, a job advertised as supply chain analyst is a coordinator role: tracking shipments, chasing POs, updating a spreadsheet somebody else designed. That is a legitimate way in and it is not analysis. Ask in the screen what the last three pieces of work this seat produced were. If the answer is a status report, you know what you are taking.

• Demand planner or demand planning analyst: forecast, WMAPE, MAPE, bias, forecast value add, consensus forecast, S&OP, promotion lift, cannibalisation, new product introduction, statistical baseline. Partners with sales and marketing, argues about optimism.
• Supply planner, materials planner or production planner: MRP, MPS, exception messages, firm planned order, lot size, lead time, BOM, capacity, changeover, purchase requisition, expedite, SAP MD04 and MB51. Partners with plants and suppliers, argues about what is physically possible.
• Inventory analyst: safety stock, service level, reorder point, min and max, days of supply, inventory turns, ABC and XYZ segmentation, excess and obsolete, cycle count, inventory record accuracy, aged stock. Partners with finance, argues about working capital.
• Logistics or transportation analyst: cost per mile, linehaul, accessorial, lane, mode shift, LTL versus truckload, drayage, parcel zone skipping, tender acceptance, carrier scorecard, freight audit and pay, TMS, OTIF. Partners with carriers and the DC, argues about premium freight.
• Procurement or sourcing analyst: spend analysis, category, RFQ and RFP, should-cost, purchase price variance, savings validation, supplier scorecard, contract compliance, tail spend, dual sourcing, landed cost. Partners with engineering and finance, argues about whether a saving was real.
• Network, distribution or supply chain design analyst: network optimisation, cost to serve, greenfield study, slotting, DC capacity, labour standards, lane volume, service footprint. Usually needs an optimisation tool and sometimes Python. Fewer seats, higher bar.
• Customer supply chain or retail replenishment analyst, mostly consumer goods: POS data, on-shelf availability, retailer portals (Walmart Retail Link, Target Partners Online, Amazon Vendor Central), OTIF compliance and chargebacks, allocation, forecast collaboration. Partners with the retailer's own planner.
• S&OP or integrated business planning analyst: the cycle calendar, demand review, supply review, executive S&OP, gap closure, assumption log, scenario pack. Rarely a first job, but worth knowing because every variant above feeds it.

What actually gates the job, and what does not

Nothing licenses this occupation. No board, no exam, no registration, no supervised hours. That cuts both ways: you can be hired next month with the right evidence, and no credential will carry you past a weak exercise.

The real gates, in the order they bind, are a recruiter's keyword match, a hiring manager's judgment that you have touched real data in a real system, and the exercise. A degree clears the first at most large employers. An internship, a co-op or an operational job clears the second. Only practice clears the third.

Certifications sit awkwardly here and most advice overstates them. For a graduating student a certification is a tiebreak that loses to an internship. For a career changer, or someone moving up from a warehouse, customer service or buying role, it is one of the few cheap ways to prove you learned the language before anyone paid you to. ASCM's CPIM covers exactly what a planning manager otherwise has to teach you: MRP logic, master scheduling, lot sizing, safety stock, DRP, capacity. Read a week of planner and materials analyst postings yourself and you will see CPIM named far more often than anything else, which beats taking anyone's word for it. CSCP is broader and reads better for an end-to-end or S&OP seat. CLTD fits logistics and 3PL work. ISM's CPSM is the procurement credential and carries a stated work experience requirement. CSCMP's SCPro appears less often in US postings than the ASCM family.

A note on names, because it trips people up. APICS is now ASCM. The rebrand happened several years ago and the old name was phased out gradually, so study guides, forum posts and some postings still say APICS. They mean the same body. Put both spellings on your resume so a filter configured in either era finds you.

Lean and Six Sigma belts are common in manufacturing supply chains and close to meaningless outside them. A green belt earned inside an employer, attached to a project with a measured result, is worth describing. A belt from a weekend course with no project is worth one line. Lead with the project and the number, not the belt.

The adjacent regulatory gates that genuinely exist: a US customs broker licence (a CBP exam plus a background check) for trade compliance seats, current dangerous goods training under 49 CFR or the IATA regulations for hazmat, a TWIC card for unescorted port access, and export control rules in defence and aerospace, where many postings require US person status as a hard filter. Training renewal cycles and rule details change, so confirm them with the issuing authority rather than a forum post. A stale answer in an interview is worse than no answer.

The Excel, SQL and Python level actually expected, stated precisely

Most first-time candidates get this wrong in both directions. Some assume they need to be a developer and spend six months on Python they will never open. Others write "proficient in Excel" and then freeze when asked to build a pivot table while a hiring manager watches.

The honest Excel floor, and it is a level to demonstrate rather than claim. Pivot tables, including grouping dates into months and adding a calculated field. SUMIFS and COUNTIFS across two or three criteria. XLOOKUP, or INDEX plus MATCH on an older build. Removing duplicates, text to columns, and cleaning a column of part numbers where some have leading zeros and some are stored as text. IFERROR. Absolute and relative references used deliberately. Mean, weighted average, standard deviation and coefficient of variation, because inventory and forecast work rests on variability. One clean chart that makes a point.

What separates candidates is Power Query and the data model: merging a demand extract with an item master, appending twelve monthly files, unpivoting a wide forecast grid into a long table, refreshing all of it with one click. A simple Power Pivot model with a few DAX measures. Data tables for a two-variable sensitivity. Solver on a small allocation or transport problem. The clearest tell that you are above the floor is behavioural, not technical: you load a 400,000 row extract with Power Query instead of pasting it into a worksheet and watching the file die. VBA is pleasant and almost never tested now.

On SQL, start with the honest point that many supply chain analyst jobs still do not need it, because data arrives as a scheduled extract from SAP, Oracle or Dynamics and the analysis happens in Excel. Where it is required the bar is modest. SELECT, WHERE, GROUP BY, HAVING, ORDER BY. INNER JOIN and LEFT JOIN, and knowing why the difference matters when you join shipments to orders and want the orders that never shipped. CASE for bucketing. Date truncation for monthly roll-ups. The standard aggregates. That is most of it. Strong adds CTEs so the query is readable, window functions (LAG for period over period, ROW_NUMBER partitioned by item to take the latest record), UNION, and enough literacy to recognise a fact table surrounded by dimensions.

Learn SQL even where the posting does not demand it, for one concrete reason. The difference between an analyst who waits three days for a BI ticket and one who answers that afternoon is visible to a manager within a month, and it is the most reliable route to senior analyst, to a planning manager seat, or sideways into analytics. It is also the cheapest skill here: the subset above is a few weekends of evenings.

Python is optional for most variants and genuinely expected in two: network design and optimisation, and anything titled supply chain data scientist. There the stack is pandas for the data work, PuLP or OR-Tools for optimisation, statsmodels or a modern forecasting library for demand. For a plain analyst seat, being able to read someone else's Python and check what it actually does is worth more than writing it badly.

How the hiring process really runs, stage by stage

Who screens you first depends on size. At a large manufacturer, retailer or 3PL it is a recruiter matching nouns: the ERP name, the planning system, Excel, SQL, forecast accuracy, the industry, sometimes a certification. At a mid-size distributor it may be the hiring manager reading resumes herself, which is better for you and means a short cover note is actually read. In front of both there is usually an automated questionnaire asking about years of experience with a named system. Answer literally and accurately. It is a filter, not a conversation, and an inflated answer is checked in the next stage.

Stage two is the hiring manager, and the title tells you which variant you are in: demand planning manager, materials manager, inventory manager, transportation manager, sourcing manager, or supply chain manager at a smaller site. This conversation is about whether you have touched real data and real constraints. Expect to be asked what system you used, what you owned weekly, and at least one question designed to find out whether you understand that the data is wrong before you clean it.

Stage three is the exercise, and it decides the hire more often than anything else. A take-home dataset, often a few thousand rows of demand history, inventory positions or shipment records, with two or three questions and a short write-up, due in one to three days. Or a live screen-shared Excel or SQL session of roughly 45 to 90 minutes, where how you approach a messy file counts as much as the answer. Or a short presentation to a panel. Live supervised formats have become more common, for the obvious reason that an unsupervised take-home proves less than it used to.

Stage four is the cross-functional panel, where the veto lives. Some combination of a sales or customer service lead, a plant or DC operations manager, a finance partner and a procurement counterpart. They are not testing your Excel. They are testing whether you will be useful and whether you will fold. A demand planner who cannot hold a position against a sales director will not improve the forecast, and the sales director in the room knows that better than anyone.

Three to six weeks is normal, with two exceptions worth planning around. Rotational and leadership development programmes at large consumer goods, pharmaceutical, retail, industrial and aerospace companies run on a campus calendar: applications typically open in late summer and close in autumn for a start the following year, and a large share of those seats go to returning interns. If you are a student, the internship is the hire. The other exception is freight brokerages and 3PLs, which hire in volume, move in days rather than weeks, and will interview you twice by phone and make an offer.

One structural fact that shapes the interview and surprises people: many of these roles are site-based, attached to a plant or distribution centre, with an early start, a Monday exception meeting and occasional time on the floor during a cycle count or a launch. Hybrid is common. Fully remote is much rarer than in adjacent analytics jobs, and where it exists it tends to sit in a corporate planning centre rather than at a site.

One thing that has changed what gets asked in 2026 and 2027. Duty rates, trade policy and sourcing economics have moved repeatedly and at short notice, and the question executives push down to supply chain is some version of "what happens to landed cost and service if this changes again". Expect at least one scenario question, and expect the right answer to be a structure (assumptions, levers, break-even, what you would do at each threshold) rather than a prediction. Never state a current duty rate or a regulatory effective date as settled fact in an interview. Name the assumption you used and say you would confirm the live rate before anyone acted on it. A trade compliance person in the room will respect that and will notice its absence.

What an entry supply chain analyst is actually measured on

Ask this in the interview, and know what the answers mean. The measures are few, named, and reviewed on a cadence: monthly in the S&OP cycle, weekly in operations. Your first-year reputation is built on a handful of numbers and one judgment about whether people trust your work.

If you plan demand, the headline measures are forecast accuracy and bias. Accuracy is usually WMAPE or MAPE, and the number is meaningless until you know the level and the lag. Item by DC at lag one is a completely different discipline from product family at national level at lag three. Bias matters more than beginners expect: a persistently high forecast builds inventory, a persistently low one builds expedite spend, and a forecast wrong equally in both directions does neither. Increasingly you are also measured on forecast value add, which compares your adjusted forecast against the untouched statistical baseline and will, on many item groups, show that human overrides made accuracy worse. That is not an insult. It is the most useful metric in the function and you should ask for it.

If you plan supply or inventory, the measures split into service and capital. Service: case fill and line fill, on-time in-full, backorder lines, and on-shelf availability if you sell through retailers. Capital: inventory turns, days of supply, excess and obsolete dollars, aged inventory, and inventory record accuracy from cycle counts. These pull against each other, which is the entire job. Anyone can hit a near-perfect fill rate with unlimited inventory, and anyone can strip inventory out by letting the shelf go empty. You are hired for the trade-off, not for either number alone.

In logistics, expect cost per unit shipped, cost per mile or per hundredweight, premium and expedite freight spend, carrier on-time performance, tender acceptance, dwell and detention, and freight invoice accuracy. In procurement, expect purchase price variance, realised savings against a baseline finance has agreed to, supplier on-time delivery and quality, and payment terms or working capital contribution.

Two measures appear on no scorecard and decide more than the ones that do. Does the room trust your number: an analyst whose forecast is overridden in every S&OP meeting is not doing the job whatever the accuracy report says. And do you escalate early: the failure managers remember is the analyst who saw a shortage three weeks out, hoped it would resolve, and raised it the day the line stopped.

Something nobody tells a first-year analyst: you will be measured on things you do not control. A promotion sales did not tell you about, a supplier fire, a port disruption, a customer who pulled an order forward a month. The skill is separating signal from noise in your own metric and saying so without sounding defensive. "WMAPE went from 29 to 41 this month, and 9 points of that is one unannounced promotion on two SKUs. Here is the change to the promotion calendar process that stops it recurring." That sentence, with your own real numbers in it, is the job.

The resume that earns you the exercise, and what gets ignored

The resume has one purpose: to get you to the exercise. It does that by showing scale, systems and a measured result. Everything else is ballast.

Scale means numbers that let a reader picture your world. SKU count, suppliers, DCs or plants, annual spend, inventory value, revenue or volume covered, loads per week. A planner who owned 1,200 SKUs across three DCs is a known quantity. A planner who "managed inventory levels" is not.

Systems means naming the software exactly as the posting spells it, one level deeper than the brand. "SAP" is weak. "SAP ECC, MM and PP, daily in MD04 and MB51" is strong, because only someone who did the work writes it. Same for Kinaxis (the platform is RapidResponse, now branded Maestro, and either spelling is recognised), Blue Yonder, o9, SAP IBP, Oracle, NetSuite, Dynamics 365 Supply Chain, Manhattan or Korber on the warehouse side, Oracle Transportation Management or another named TMS, project44 or FourKites for visibility, Coupa or SAP Ariba in procurement, Power BI or Tableau for reporting.

A measured result means a before, an after, a baseline, and the trade-off you did not sacrifice. The shape, with your own figures substituted: "Owned the weekly statistical forecast for 1,200 SKUs across 3 DCs. Cut WMAPE at item-DC lag-1 from 38 to 29 percent and reduced finished goods days of supply from 62 to 51 with no loss of case fill." Those numbers illustrate the shape; they are not a benchmark to copy. If you do not know your own baseline, find it before you leave the job, because nobody will give it to you afterwards.

What every reader skips: "proficient in Microsoft Office", "detail oriented", "team player", an objective statement, skill bars rating yourself at 80 percent on Excel, coursework with no outcome, and a certification marked "in progress" with no exam date. Delete all of it. Add the exam date if you have booked one, because a date is a commitment and "in progress" is not.

With no full-time experience, the order is: internship or co-op, then a case competition with how far you placed, then a capstone that names the sponsoring company and says whether the recommendation was adopted, then a simulation framed as a decision rather than a game. The Fresh Connection and the Beer Game are both worth citing if you describe what you decided and what it cost, and both are worthless as a line that just names them. A public-dataset project is weak unless it answers a supply chain question. Cleaning the inventory data for a campus food pantry or a student store and showing the before and after is far stronger: real data, real stakeholders, real mess.

Moving across from operations, customer service, buying or the military, translate rather than describe. Reduced pick errors becomes inventory record accuracy. Handled escalations becomes allocation and expedite decisions under constraint. Managed a route becomes transportation cost and on-time performance. Keep the operational specifics. They are an advantage, because most analysts have never stood on the floor and it shows in their assumptions.

Two mechanical things on keyword filters. Spell out and abbreviate both forms at least once: S&OP and sales and operations planning, OTIF and on-time in-full, MRP and material requirements planning, ASCM and APICS. And mirror the posting's own spelling of the system, including the version, because a filter built around "S/4HANA" will not match "S4 Hana".

What the interview really tests, with the answer shapes

Technical questions here are not trick questions. They check that you understand why a formula exists, and they almost always have a second half asking what you do when the input is wrong.

"How would you set safety stock for an item?" Cover demand variability, lead time variability, the target service level and the review period, then the caveat that matters: the formula is only as good as the lead time recorded in the ERP, which in most companies is a number somebody typed in years ago and never revisited. Ask back whether the service target is set by item, by ABC class or by customer. The answer tells you how mature the operation is.

"MAPE versus bias, and which matters more?" MAPE tells you how wrong you were. Bias tells you which direction, consistently. A forecast can have respectable MAPE and still run systematically high, quietly building inventory every month. Bias is usually the one to fix first: cheaper to correct, and it compounds.

"Turns versus days of supply?" The same information inverted. Days of supply is easier to act on at item level and easier to explain to a plant. Turns is what finance looks at. Know both and know who asks for which.

"A supplier's lead time just went from four weeks to nine. What do you do?" Answer in three horizons. Immediately: identify the exposure, expedite or allocate what is at risk, and tell the customer-facing team before they find out from a missed order. Medium term: resize safety stock and the reorder point for the new lead time, which is the step most people skip, and change it in the system rather than carrying it in your head. Long term: qualify a second source or renegotiate, and quantify what the new lead time costs in working capital so somebody can decide whether it is worth paying to fix.

"How do you decide what to expedite?" The wrong answer is whoever shouts loudest. The right answer is a rule: value at risk, customer or line impact, and whether the expedite actually recovers the date. Then say what you do when two things qualify and you can only have one, because that is the real question underneath.

"Tell me about a time the data was wrong." The most predictive question in the loop and the one candidates answer worst. Have a specific master data story: a lead time that did not match reality, a minimum order quantity nobody had updated, a unit of measure conversion off by a factor of twelve, a BOM missing a component, a duplicate item master record splitting demand in two. Say how you found it, what it had been costing, and what you changed so it would be caught next time. If you have never worked in a system, use a university or volunteer dataset. The structure of the answer is what is graded.

The exercise is scored on a shorter list than candidates assume. Did you look at the data before you trusted it, and did you say what you found (duplicate rows, negative quantities, a month of missing records, an outlier that is a data entry error rather than a real spike)? Did you answer the business question, which is almost always "what should we do", rather than describing the dataset? Is there a number attached to the recommendation, and did you name the trade-off? A clear two-slide answer with a stated assumption beats a beautiful model that never reaches a conclusion.

Behavioural questions concentrate on conflict, because the job is conflict. Expect a time you disagreed with sales about a forecast, a time you told a plant or a customer no, and a time you made an error that reached a customer. Answer with the decision and the number, not the feelings. "I held the forecast at 40,000 against a sales ask of 60,000 because the last three promotions on that item delivered 42, 38 and 44 thousand, and I showed them the three. We finished at 41. Sales still disagreed, and we agreed in the S&OP minutes to revisit if the first two weeks ran above plan." Position, evidence, outcome, and a documented route to change your mind.

Ask questions back, because the panel is your chance to find out whether the job is any good. What is forecast accuracy today, at what level and lag? Who owns the final number when demand and supply disagree? How reliable is master data, and who maintains lead times? How often does the published plan change after it is published? What does success look like at six months? A manager who cannot answer the first two is telling you something important.

Getting in without a supply chain degree, and what the job pays once you are in

Look at any working planning team and you will find economics, engineering, history and finance degrees, and people with no degree at all, sitting next to the supply chain graduates. The paths below are ordered by how reliably they work, not by how impressive they look.

The internship or co-op, converted. If you are still a student, this is the hire. Large employers fill a substantial share of entry analyst seats from their own intern cohort, and the full-time application you submit in autumn competes against people the manager already knows. Apply in summer and autumn for the following year, take the site internship over the corporate one if you get the choice, and leave with your metrics written down.

The rotational or leadership development programme. Consumer goods, pharmaceutical, retail, industrial distribution, aerospace and the larger 3PLs run them under names like supply chain leadership programme. Two or three rotations over roughly 18 to 36 months, often with a relocation requirement, and the fastest structured route to a planning manager seat. Competitive, and on a fixed calendar, so diary them.

The side door, which is how most people actually get in. Take a planner, buyer, materials coordinator, inventory control, order management, production scheduling or customer service role at a manufacturer or distributor, and move internally in 12 to 24 months. These hire on reliability rather than analytics, they teach you the system and the vocabulary at the employer's expense, and an internal candidate who already knows the item master beats an external candidate with a better degree more often than hiring advice admits. Tell your manager in month three that you want the analyst seat, and ask what would need to be true.

The freight brokerage or 3PL route. These employers hire fast, hire non-targets, and teach you freight economics, carrier behaviour and customer escalation inside a year. The churn is real and the hours can be long. Treat it as a paid two-year education, then move to a shipper-side logistics analyst seat knowing what a carrier is actually doing, which is scarce on the shipper side.

Military logistics. Army 88N, 92A and 92Y, Air Force logistics and materiel management specialties, Navy logistics specialist, Marine Corps supply and the equivalents elsewhere map directly onto this work, and many manufacturers and 3PLs recruit deliberately from them. DoD SkillBridge and similar transition programmes place people into exactly these roles. The translation is the whole task: property accountability becomes inventory record accuracy, requisition management becomes procurement and expediting, readiness rates become service level.

The internal sideways move. Finance analysts, data analysts and customer service leads inside a company that already has a supply chain function can move across by learning the planning system and volunteering for the S&OP pack. Lowest risk of all if you are already employed somewhere with a supply chain.

On pay, do the checking yourself rather than trusting an aggregator. The closest US national figure is BLS Occupational Employment and Wage Statistics under SOC 13-1081 Logisticians, which publishes median and percentile wages by state, metro and industry, so you can look up your own market instead of a national average that describes nobody. Read 13-1023 Purchasing Agents for procurement seats, 43-5061 Production, Planning and Expediting Clerks for the coordinator tier below analyst, 15-2031 Operations Research Analysts for network and optimisation work, and 11-3071 Transportation, Storage and Distribution Managers for the step up. Then read live posted ranges in pay-transparency jurisdictions, the most current signal available, and ASCM's annual salary survey, which breaks out by role and certification.

Two honest points about what you will find. Industry and metro move the number more than the title does: the same job pays differently at a pharmaceutical manufacturer, a grocery distributor and a freight brokerage in the same city. And entry pay in this function generally sits below a comparable analytics or finance seat in the same metro, which you can confirm by reading 13-1081 against 13-2051 and 15-2051 in the same BLS table. Worth knowing before you negotiate, and part of why the SQL and scenario skills matter: they are the levers that move you off the bottom of that range fastest.

Two closing points. Geography is the biggest lever a flexible candidate has, because the roles sit where the plants and DCs sit and the applicant pools there are a fraction of the size. And if you are a career changer with no operational foothold, CPIM plus one serious portfolio piece (a real dataset, cleaned, analysed, with a recommendation and a number) is a better use of three months than another generic certificate, because together they answer the only two questions a hiring manager has: does this person know the words, and can this person do the work.

What a screen is looking for

These are the terms that a resume screen, human or automated, is matching against for this role. Use the ones that are true of you, in the words the posting uses.

• Supply chain analyst
• Demand planner
• Demand planning
• Supply planning
• Materials planner
• Production planner
• Inventory analyst
• Logistics analyst
• Transportation analyst
• Procurement analyst
• Sourcing analyst
• Replenishment analyst
• S&OP
• Sales and operations planning
• Integrated business planning (IBP)
• Forecast accuracy
• MAPE
• WMAPE
• Forecast bias
• Forecast value add (FVA)
• Safety stock
• Reorder point
• Days of supply
• Inventory turns
• Excess and obsolete (E&O)
• ABC analysis
• Cycle counting
• Inventory record accuracy
• Fill rate
• OTIF (on-time in-full)
• Purchase price variance (PPV)
• Spend analysis
• Supplier scorecard
• Cost to serve
• Landed cost
• Scenario analysis
• Dual sourcing
• MRP (material requirements planning)
• Master production schedule (MPS)
• DRP (distribution requirements planning)
• Bill of materials (BOM)
• Capacity planning
• Lead time variability
• Network optimization
• SAP ECC
• SAP S/4HANA
• SAP IBP
• SAP MM and PP
• Oracle
• NetSuite
• Microsoft Dynamics 365 Supply Chain
• Kinaxis RapidResponse (Maestro)
• Blue Yonder
• o9 Solutions
• Anaplan
• Manhattan Associates
• WMS
• TMS
• Oracle Transportation Management (OTM)
• project44
• FourKites
• Coupa
• SAP Ariba
• Excel
• Pivot tables
• Power Query
• Power Pivot
• SQL
• Power BI
• Tableau
• Python
• pandas
• APICS
• ASCM
• CPIM
• CSCP
• CLTD
• CPSM
• SCPro
• Lean Six Sigma
• 3PL

Mistakes that cost people this job

Questions people ask