How do those subvert rate limiting / blacklisting?
By using Redis and MySQL, I minimized the number of calls the app has to make directly to the Robinhood API. For things like the next earnings date, which changes typically once per 90 days or so, I have Redis store the result of that endpoint from Robinhood for some number of days, probably not 90, but not 1. For things like the current price of a stock, Redis might store that for a minute or two, so that my app can "spam" for the latest prices (maybe I have a refresh button in the app) without triggering a 401 or 403 from the Robinhood API.
TLDR: Since rate limiting prevents my app from pulling all the data it needs at one time - it has to throttle requests - I don't want to have to wait a couple of minutes each time the app is started because it needs to download data from Robinhood, much of which probably hasn't changed since the last time I started the app.
I hate to break it to you, but tickers and CUSIPs do change.
The world of 'corporate actions' turns out to be a catchbasin requiring human intervention.
This was probably against their TOS and even if not, trying to bypass security measures, no matter how weak, is unethical behavior, and possibly illegal.
That would be a red flag in an hiring scenario since you were essentially bragging about breaking the law.
Unless Robinhood had a bug bounty/responsible disclosure kind of program and you were fully acting within its limit, but your comment did not sound like it.
Otherwise, breaking ToS is akin to jaywalking and anybody who sees a side project like this, and their takeaway is "wow they broke ToS" doesn't deserve to be hiring software engineers, and certainly doesn't deserve to be putting them through the ringer such that the first bar to pass is literally Triplebyte (RIP Triplebyte).
Otherwise it sounds more like a case of "Here's how to get around the rate limiting of Company Foo's API and abuse those limits anyway".
Without the explanation, that'd get you an immediate No at lots of places just from the implied legal exposure/liability. Though probably not all. ;)
You could distribute the requests amongst multiple IP addresses via say a proxy, but that isn’t necessarily going to work, like if the rate limiting is done by bearer token or API key rather than IP address (they should be doing it by the token rather than the IP address), but I made no mention of that so I don’t think anybody would think that’s what I was doing.
If you went with something like "using caching to avoid hitting API limits" it sounds legit.
Whereas if you went with something like "getting around Company Foo's API rate limits" it sounds like you're exploiting a bug in their system.
If you did present the system as spoofing requests to subvert a rate limit / blacklist, as per:
#4, my presentation was about how I reverse engineered the Robinhood API, spoofed
requests to get around their “security”, and used two levels of caching (Redis and a
typical relational DB) to subvert rate limiting/IP blacklisting
... then that doesn't sound like the legit use case scenario. ;)Your further follow up discussion makes it sound like you were just using a self-developed caching system though, and presented it terribly for the target audience.
All sorts of possibilities spring to mind for that. :)
Here's a hypothetical example. Lets say you discovered a logic bug in the API limit code along these lines: "So, it turns out if you have an `X-Forwarded-For` header in the request, then the request is processed properly except it isn't counted towards the limit. Effectively a bypass."
Exploiting this one would of course be trivial, as you'd just need to set that header for all your requests.
I once interviewed with a startup whose process was:
1. Pass TripleByte (already puts you in top whatever percentage of SWEs)
2. Meet with 4 members of the company for an hour each, and if they all like you:
3. Create a 15 minute presentation on some code you worked on. It can be code from a current or past job, but that will probably reflect poorly on you, so go build something so you can create a 15 minute presentation on it.
4. Deliver the presentation during lunch to anyone at the company who joins the meeting. Also, join the meeting via some pseudo video game in the browser that you’ve never heard of and probably won’t exist in 2 years (about 8 people joined the meeting, most of which I never met).
5. Meet with the cofounder for an hour, and if they like you enough:
6. You have the privilege of working for them for a week “trial” to make sure it’s really a good fit. You can still be rejected at this point, though if I made it this far only to be rejected, I’d have killed myself, so the fact that I’m writing this now should tell you I did not make it past #4.
For those curious, #4, my presentation was about how I reverse engineered the Robinhood API, spoofed requests to get around their “security”, and used two levels of caching (Redis and a typical relational DB) to subvert rate limiting/IP blacklisting. I don’t know anybody who has done something as remarkable, especially in their spare time, for fun. BUT, I apparently said or did something they didn’t like so all that is moot.
If carpenters had to go through what we go through… Jesus Christ himself could come back to Earth, apply at the Google of construction firms, and be rejected because of the gap on his resume. Ooo, sorry, that gap is a huge red flag. What’s that, you were murdered by Romans and it’s not your fault? Ehhh…. I don’t want to risk making a bad hire. Thank you so much for your interest though, we will surely keep you in mind for future opportunities.