> the site can now pretty easily handle 12 requests per second.
Right prod architecture (nginx -> gunicorn -> django, with nginx serving static assets), decent PRAGMAs for sqlite3 and caching for generic content should improve the RPS one or two orders of magnitude.
My prejudice is that there are only a few countries in the world (US, Canada, Australia, Mexico, possibly others I don't have experience with) where coming as an immigrant they take you in and you can be considered from that country.
you still need filter phone/remote interviews to select which candidates to have for on-site interviews, and this article centers on this initial interview being broken
Instead of trying to get the actual SOC 2 attestation, do a version of the homework that would get you there; basically writing documentation. The output would be documents describing different procedures or existing infra (disaster recovery, network diagrams etc) and a master spreadsheet with the "soc 2" questions (that you pick) and answers, a "security questionnaire" and this is what you send to companies when they insist.
Note in security-speak the keyword is "mitigation" (you don't have x but you mitigate that by y)
I agree that estimation questions (not "brain teasers" as coming up with the clever solution) are good. Developers should be able to think in orders of magnitude.
The new SEO fad is CEOs and CTOs writing articles trying to look like a regular guy.
Also the "C" in CTO means Chief, as in main manager (of managers); if you have no direct report you are not a manager, let alone a "chief" one; call yourself Founder/Distinguished Engineer
> The wall was actually as likely to end five months from when they visited it, as it was to end 500 years from then.
I don't think this is correct; as in something that has been there for say hundreds of years had more probability to be there in a hundred years than something that has been there for a month.