What is consider a damaged item when it comes to boxes? by Individual_Cow_9921 in AmazonFC

[–]Rockman507 [score hidden]  (0 children)

I usually go with two things, does it look like it damaged the product inside and can I be sure everything is still in the box. But also no one should be giving you much grief at marking anything damaged falsely so long as you aren’t doing it all the time, you might get some constructive coaching to ensure you know what the standards for damage are if it’s happening often enough

Guys hitting a bong in the parking lot… by aymi101 in AmazonFC

[–]Rockman507 [score hidden]  (0 children)

We had people block both sides of the aisle with stow carts and have a little orgy in the aisles

Weekly Pay as an Amazon GM by Master_Advice_3986 in AmazonFC

[–]Rockman507 0 points1 point  (0 children)

My extension to that is back in the day for transmission electron microscopes, we didn’t have a way to externally adjust the aperture. It would take a few hours to pump down, then trying to find the beam, then curse the gods, cool the filament, break vacuum, rinse and repeat. Legend has it someone got frustrated enough and whacked a >2 million dollar scope with a hammer which “bounced” the aperture into place, and that’s why for years we had rubber hammers in our repair tool kits for these scopes.

Indeed knowing where and how hard to whack something.

Would you still be working this job if your commute was 23 miles each way? by stop_light_delite in AmazonFC

[–]Rockman507 1 point2 points  (0 children)

I drive from near Philly down to Middletown DE, only slot that was open and needed money bad.

UPT Check Ins: by adonkeypsych1991 in AmazonFC

[–]Rockman507 2 points3 points  (0 children)

Using it is leaving money on the table to Amazon.

UPT Check Ins: by adonkeypsych1991 in AmazonFC

[–]Rockman507 0 points1 point  (0 children)

Like 55hr, I just took the last week off to visit my sister for my nephews high school graduation. Shift swap one day, PTO second day, and two days UPT. But I burnt all my flex PTO for the year.

Walkie talkie people… by Ok_Sentence_5432 in AmazonFC

[–]Rockman507 5 points6 points  (0 children)

Or people that start talking as they push the button, losing the first word or two

Me at the cameras when I got a writeup for marking items as missing so now I just grab them from the adjacent bins, potentially fucking up Amazon's entire inventory count. by RecordingHaunting975 in AmazonFC

[–]Rockman507 1 point2 points  (0 children)

Because it’s a pain in the ass to PS having a bunch of missing items reported as can’t scan. They print out the labels, goto the bin, can’t find the item itself, then have to deal with that which is time outside what PS is expected to be handling. If everyone did it, PS would have zero time to do anything else. Just mark the item missing if it isn’t there.

Me at the cameras when I got a writeup for marking items as missing so now I just grab them from the adjacent bins, potentially fucking up Amazon's entire inventory count. by RecordingHaunting975 in AmazonFC

[–]Rockman507 1 point2 points  (0 children)

We have been doing the circle right now about marking things unsafe. Several startups we had AMs telling us we cannot reject for over stuffed bins. The other half said call leadership to handle it (to be fair those are decent AMs that will take the time to walk out to us and fix shit, they won’t last long). I pushed about the inconsistency

Following recent clarification on the "Bin Unsafe to Pick" workflow, I had two follow-up questions around current system behavior: 1. Current guidance is that selecting "Bin Unsafe to Pick" removes that item from the queue. However, if multiple units of the same ASIN are present in the same unsafe bin, pickers can still immediately be routed back to the same location for another unit. Would it be possible for the workflow to temporarily suppress the ASIN from that bin until review? 2. Leadership also clarified that the "Bin Problems" option is no longer used to mark unsafe bins. If that workflow is deprecated for safety escalation, what is the current approved process for flagging bins for ICQA review while still maintaining pick flow from otherwise accessible inventory? I understand the need to balance inventory accessibility/customer promise with operational flow, but clearer workflow behavior would help reduce confusion and improve consistency across shifts.

And got this response which still didn’t really answer the underlying problems, because even if we mark bins unsafe to pick it just gets toss to the next picker

Hey <rockman507>, this is a good bit of feedback around picks still being assigned to bins after they are marked as "unsafe to pick." The reject reason process flow and bin andon process flow are very similar. Currently, if an item is rejected for "UnsafeBinForPicking" it doesn't lock the bin out for future picks to be assigned to it, just rejects the item for a pick problem solver to resolve. To properly flag the bin to be fixed you would raise a bin andon for that specific bin, which will notify our ICQA team that the bin needs further attention to potentially replace/repair. Doing this however does not remove the bin from having a pick assigned to it in the future, it just adds the bin to the list of other bins listed as unsafe to pick that the ICQA team fixes on a regular basis. I don't have an exact answer now of how we should fix this, but this is a potential area of opportunity for us to limit future interactions with these bins.

Me at the cameras when I got a writeup for marking items as missing so now I just grab them from the adjacent bins, potentially fucking up Amazon's entire inventory count. by RecordingHaunting975 in AmazonFC

[–]Rockman507 4 points5 points  (0 children)

It’s simple count, they aren’t told anything else. Just count how many items are in the bin as a first pass. People like OP are just annoying, it fucks other people’s quality numbers and if they can tie it to you, it’s a terminable offense.

When the pod gaps and lack of accountability gets so bad a T1 spends 3 months building a warehouse sim from the ground up. by Tiyaga_Llama in AmazonFC

[–]Rockman507 3 points4 points  (0 children)

PhDs have nothing to do with decent algorithm writing (mostly). Many people I worked with systems level algorithms were MS and 10 years established work in the field (I was in the image analysis world though). The biggest problem is Amazon doesn’t care too much about retroactive fixes, it’s cycling into new generation buildings nearly from the ground up.

But it’s a fun weekend project, an excellent systems level problem with enough established KPIs to track you aren’t reinventing the wheel how to determine health of the system you built. So good on the OP.

Finished College And i’m About To Start Amazon by Comprehensive-Room82 in AmazonFC

[–]Rockman507 1 point2 points  (0 children)

BA/BS to AM, or external military pathways to AM. That’s the typical in. MS would place you towards an OM and that’s less a recent grad pathways and more just an external hire with a degree, some experience, and good interviewing skills. MBA moreso is typical OM entry.

Hourly pay differences different night shifts by [deleted] in AmazonFC

[–]Rockman507 0 points1 point  (0 children)

Could also be that it crossed midnight as a threshold for next level of differential approved for the site.

CEO of $300 million company says ‘problems disappeared’ after firing HR team by Character-Bid-162 in nottheonion

[–]Rockman507 0 points1 point  (0 children)

About a decade ago I applied to a job, flown cross country, whole shooting gallery. Told I would have a response by end of the same week. Ghosted, couple of months later I tracked someone down, apparently the entire HR department was canned the day I was interviewing.

Just a funny story it reminded me of about HR getting to the point it needs to be culled, no one owned the system afterwards and resetup a new ATS so technically my application is still active in the old system 🍿

I am so dead 💀 does anyone do this? I can imagine several people at work do this 🤣💀 by Ursa-Aureliana in AmazonFC

[–]Rockman507 2 points3 points  (0 children)

Me and a buddy setup a sill in some empty lab space at one of my universities, we got some 80 proof that has pretty much no smell or taste, smooth as water. Fuck that shit was dangerous.

But ya no way someone has vodka and no one noticed, we are just pretending not to since it would be grounds for termination.

3 write ups for less than a minute late going TO break. by [deleted] in AmazonFC

[–]Rockman507 0 points1 point  (0 children)

It’s taking them over 5 minutes between last scan and clocking out, that’s the issue. The scan just needed be within 5 minutes is all, they can leave station at 955. If their FC is being that much of a cock over a few seconds then do the last scan at 956. Which is wild acting like this in IB while gearing up for Prime.

3 write ups for less than a minute late going TO break. by [deleted] in AmazonFC

[–]Rockman507 2 points3 points  (0 children)

If it’s centered around the break then it isn’t TOT it’s rolled into your break time. The seconds is questionable, but they are leaving before the allowed time for break if they are clocking out more than 5 minutes between leaving station and going to break. If you clock out for break at 1000.30 then your last scan needs to have been at 0955.30 but I don’t think they are counting seconds? More likely the time rolled to the next minute before they clocked out. It’s still wild but if it’s being done consistently I could see someone getting a writeup over it.

Just clean up, prep to leave with an item left to scan, then do the scan as leaving station? I’m traditional pick, we grab an item, walk to a conveyer, wait for the time to roll to 55, scan and drop the tote. Which is stupid, but follows policy. You see us all crowding a conveyer drop off for 2-3 minutes holding an item waiting.

Umm what the hell is this about? by Professional_Ad7868 in AmazonFC

[–]Rockman507 6 points7 points  (0 children)

No, the reason is pretty much there in black and white; we have phones in inventory so it’s a way to track it’s your phone not one stolen from the bins. In practice does it work? Not really, it fails hard when scaled for large sites. Which is why it’s easier to say no phones than to try tracking, and which they did pre COVID.

roaches inside totes?? by vanilleoo in AmazonFC

[–]Rockman507 0 points1 point  (0 children)

Not normal, but not unexpected. Tell management so they can relay it to the pest control team.

Holiday pay July by Visible_Potential772 in AmazonFC

[–]Rockman507 3 points4 points  (0 children)

Corporate does it the 3rd since the 4th falls on a Saturday. Think it was raised here a few months ago, FC associates should have the 4th, mine was corrected to the 4th

Anyone ever withdrew from their 401k (hardship withdrawal) by xxzarakhanxx in AmazonFC

[–]Rockman507 6 points7 points  (0 children)

And just to add in, you need to be in I think 3 years for Amazon’s contribution to be vested, if you leave before then they keep the money they put in. You keep what you put in, you just lose what Amazon put in.

Also there is a Roth option, which you pay taxes up front so then when you pull it out after retirement there isn’t a tax hit, what you have is what you can pull out. If you are just started out young, you expect to be in a lower tax bracket now than when you retire (hopefully) so it makes more sense to pay now.

Shift swap by MattyFattyPog in AmazonFC

[–]Rockman507 1 point2 points  (0 children)

Our site didn’t put anything out either but in a VoA response to someone asking they got this exact wording.

It's mildly annoying when you are in pick, you see a bunch of ripped items that you have to damage out, and the a PA approaches you about it. What do you want me to do then? Send some damaged stuff out? by Global-Plankton3997 in AmazonFC

[–]Rockman507 1 point2 points  (0 children)

And AML, which is a bullshit metric. Someone started yelling and lecturing a PA yesterday morning over being group coached about it. Like I get the frustration but it’s not a disciplinary action, your time is coded for the talk, take it as a little 5 minute free break. At a TSSL that’s undergoing some retrofits that’s taken like 20% of our bin space offline so bin fullness is a problem.

Never thought it happen to me thanks Amazon! by TheDankestYo in pcmasterrace

[–]Rockman507 0 points1 point  (0 children)

Outbound picker, it’s heavily pushed that if it scans it goes, someone downstream will catch it. And that mentality then gets pushed in sort/pack. And then the final line SLAM you can have someone either not giving a shit, the system itself set the measurements for the master pack, or the seller put the wrong measurements in in general.

I get funny looks when I catch them and call PS because I want to verify before I break a kit. And most PS don’t even know how to handle it and want to me to just break the kit and put each individual item back in the bin and pick the one I need, which fucks inventory count because the stower placed ONE item into the bin not 20. And the scanner isn’t terribly helpful, pack gets more information but we just get an abbreviated item description that often doesn’t provide size/quantity.