4 ms·
But Chrome extensions are easy to deconstruct. Just open the CRX file using 7Zip and read through the source code. Your interview might have made them acutely
by UnoriginalGuy 11y ago
But Chrome extensions are easy to deconstruct. Just open the CRX file using 7Zip and read through the source code.
Your interview might have made them acutely aware that your extension exists and they may have either got a copy and looked their site's products to find issues or at least take care of the "low hanging fruit" examples you used.
So what occurred might have been as you say. And I suspect you didn't move forward on the interview process BECAUSE of your extension (i.e. they didn't want to muddy the waters in case Amazon's legal department wants to send you a C&D letter) but I don't think they needed to interview you to get intelligence on your extension (since any engineer worth their salt at Amazon could have told them the same thing, just by downloading a copy and reading).
It sucks that Amazon didn't see the value of your innovations and exploit them to make their site better. But their loss I guess...
- DasIch 11y agoThey don't need to make an interview to learn more about the extension but even so it's convenient to be able to talk to the author directly.
- osstard_s 11y agoThat's nothing - I had an interview with them in their early days, and showed them my idea for a one click button. Never heard back from them - wonder if they used it?
- Guillaume86 11y agoThey couldn't if he put the logic on a server and just make the extension a client (which seems better to cache things across clients, I don't know if it's the case here).
- lmg643 11y agoI tried out this extension and found that it slowed down chrome and even crashed within a few minutes of using it. so perhaps amazon didn't get as much useful information as you think.