Wafer Care FTS
MSR FSR · Santa Clara, CA
Start free. No credit card.
About the Job
This position is responsible for transporting semiconductor wafers between buildings within a campus environment, ensuring the safe, timely, and accurate movement of materials in support of production operations.
Delivery Process
- 1. Scans label
- 2. Transport
- 3. Delivers
- 4. Comments on requests
- 5. 30 mins -1 Hour lead time
Investigation Process
Creating manual LTS
» BU Writes on paper to ship
» PC is down due to lock out
Printing FTS label
» BU writes FTS# on paper
» BU prints out on standard paper
» Printer down
Moving F/F to correct cage to ship
» If a request is placed in wrong cage by the BU
Investigation
» Looking through open requests, physically & systematically
− Clearing the database of all void requests, when user submits request but does not drop it off for delivery. Retrieving clear confirmation from user before canceling.
− LTS: Checking the site for miss scans
− Emails: searching for the FTS request to ensure no communication is missed
GIS
» when PC or printer goes down, (weekly) work with deskside GIS to resolve.
Daily Escalation Process
- - Sweeps requests after 48 hours
- - Stores Violations
- - Retrieves when requested
- - Replaces zebra printer ink & labels
- - Check all buildings for misplaced requests
- FOUP Management
Engineering Corridor
- 1. A move request comes in via FM/
- 2. FM/ sends email to Team + also available to view on FM/ Engineering corridor as an open request
- 3. Team delivers F/F from or picks up F/F from pass through window
- 4. Team will close out delivery once in pass through or record EC cage location and close out after pickup.
Violation
- 1. Team places a yellow violation tag on the F/F and records the violation on FM/
- 2. After 24 hours the team walks back through space and collects F/F still in a violation location
- 3. FOUPS taken to OSH (Observation Hallway) in B85, M101 81, B74 unknown, B3 there is a storage room. FOSBs are taken to Reciprocator room in B85, wafer transfer rooms in B81, B3 storage room.
- 4. After two weeks, FOSBs are palletized and sent to B21 for external reclaim
- 5. FOUPs stay in storage locations
Metrology Violation
- 1. Metrology tags with yellow violation tags at 12am on Sunday night
- 2. Nothing is recorded on FM/
- 3. Team will sweep as many as they can fit in the EC
- 4. Team creates Metrology violations on FM/ and the FOUP owner is notified.
Engineering corridor to Building 21
- 1. Team clicks FOSBs over 30 days and selects FOSBs (check boxes)
- 2. Team clicks Transfer to Building 21
- 3. Team prints out labels for the protocol team
- 4. Team goes to WCT to pick up labels
- 5. Team gathers FOSBs from EC and puts them on the green rolling cart
- 6. Team delivers to WCT who palletizes and ships B21.
- 7. Team clicks moved to B21 and cleared 36 requests.
Building 74
- 1. A move request comes in via FM/
- 2. FM/ sends email to team l+ also available to view on FM/ Engineering corridor as an open request
- 3. Team delivers F/F from or picks up F/F from pass through window
- 4. Team will close out delivery once in pass through or record EC cage location and close out after pickup.
Requirements
- - Valid Driver’s license
- - Automobile
- - Open bandwidth: Possible building to building floater to back fill
- - Comfortable with cross training, between FTS & FM.
- - Able to lift to 35 lbs.
- - Other duties as assigned by AMAT management
Key Inventory Management Requirements
- - Accurate Tracking & Monitoring: Real-time visibility of inventory levels, movements, and stock locations (e.g., using barcode scanning).
- - Demand Forecasting: Using historical data to predict future inventory needs and reduce dead stock.
- - Warehouse Organization & Control: Standardizing storage locations, organizing, and implementing efficient receiving, picking, packing, and shipping processes.
- - Auditing & Security: Regular, frequent cycle counts and audits to maintain accuracy and prevent shrinkage.
- - Software & Technology: Using emails and AMAT software (FM/FTS/PP/Excel) for automation, reporting, and integration.
Posted: July 28, 2026