Just replying here so you can see it, but I would caution against continuing to share this story as it's written. If I was a hiring manager and I saw this, I wouldn't hire you, regardless of how well you did during interviews.

These are my options, some shared by others in the threads here, some opposite.

> It would lock the low-level features that allowed you to make calls, use Wifi, or even post pictures on Instagram/Facebook (the horror!) until you paid up.
...
> Except for the poor sod in Peru who couldn't make phone calls or post duck-face pictures to Instagram, but no one asked him.

Both of these quotes seems like you don't quite understand the impact on your end users, or just don't care. Neither are good options as you grow your career.

> Our own internal tool worked well (I would like to say it was all due to me, which would be an arrogant thing to say, but also 100% true, so I will say it: It was all or mostly due to me).

Your internal tool, which you are taking complete credit for, is what didn't have protections in place that ended up harming users. Also, it comes across as bragging or something. People that are too obsessed about credit usually are not ones I'd like to work with. Team efforts are hard to define and split up and people that over index on that usually are just bad team members.

> But one mobile phone manufacturer (that I will call the K-Pop Phone Manufacturing Company), based in Korea (yes, that one)

Say it or don't. These games where you can act all cheeky about how you didn't 'actually' say it is just juvenile IMHO.

> Because of time pressures, there was no time (or political will) to check the script was well written. As soon as I banged it out, it was live. And I mean literally, 10 seconds after I pressed save, the script was running on live production servers.

This is beyond just the org's failure. As engineers, we're responsible for what happens on our watch. We hold the line and try to enforce engineering practices, not shrug and yolo and then blame the org.

> I could have tested it better, but that would have meant working late into the night. No thanks. I had already worked a few late nights/weekends and I was done.

This comes across as again, you don't actually care at all. Not a hiring quality IMHO

> My colleague was helping me, so we got it all done in about an hour. By 18:30, we had unlocked all phones.

Oh no! You worked an entire hour between 5:30 pm and 6:30 pm! The horror! Most people work much much longer hours, later into the evening or night when things fail. The difference is they don't complain about it and care.

> A project manager confirmed it, and I took a breath of relief and quickly logged off before more fuckups could be found.

Great! You fixed it, but rather then trying to verify you fixed everything, you logged off at 6:30 and screw anyone else effected. Not a great look.

> The Lessons we learnt (or more likely, didn't learn)

If you didn't learn the lessons, why are you writing about it? Just as a war story? Or do you think this comes across as a positive for your career?

> The lesson here is: Do some f'king checks before you lock someone's phone, but I don't know if that lesson applied to us or K-pop (most likely, both of us).

You know. You're in control of what you can do, so you do what you can to prevent issues from happening under your watch.

> This is not just good QA, but good security as well. But bah! None of that silliness for us, thanks.

Again, you come across as uncaring. Why are you working in this industry?

> We assumed that because our own software checked for this sort of thing, that the K-pop phone's software would do as well.

Great. Your software failed. Don't blame downstream if you can't even get your first layer correct.

> Everyone pretended it was an honest mistake.

It was an honest mistake. The difference is if you learn and grow, or if you just shrug and make the mistakes over and over again.

Honestly, this is just my two cents. Take it all with grains of salt, and ignore as you wish. I don't intend to be personally attacking you or any of the sort. Just expressing where my mind is reading it.

If I was you, I'd take this down and seriously consider if engineering is the right career path for you. It doesn't seem like you actually enjoy it or care about it and just working for the easy money doesn't lead to a fulfilled life at the end. And living a fulfilled, happy life, is the most important thing after all.

Best of luck in the future.