Got a 3-day take home project. Ignore the misspellings. Ignore that this project was a pure backend project for an, acknowledged, frontend role. Ignore that, for the code to work, I would have had to reveal my Github security credentials. Ignore that, to work, using the referenced v3 of the Github heavily rate-limited public API, I would have had to saturate my account's allocated bandwidth - heaven forbid I actually used it for something besides applying to Splunk. Ignore that I already knew, from past experience, that the Github API has, shall we say, quirks in how it wants the caller to handle throttling API calls. My approach was to write the code, but let them supply the credentials and register the app with Github if they wanted to run it against the live Github API. To test, I created a mock API, with optional enforced rate-limiting, that returned the data as if from Github itself. This fed a cache, so that the fictional client of this project could get, potentially stale (lazily updated), data without waiting the 6 or so minutes for the Github API to fetch all the data. After about 5 hours coding, I documented how this could be scaled by using a distributed keyvalue store and a serverless function instead of the in-line classes created for the take-home project. Crickets - then a week-later a no-reply, no explanation reject. Going by the interview process, I highly doubt whether Splunk is a good place to work. Seriously, do I, as a frontend engineer, really want my team to be judged and chosen on how well they can implement the backend interface to a rather idiosyncratic API (v.4 is much better)?

As a candidate, I spent 2 hours for technical screening rounds and 5 hours/1 day to interview onsite. Recruiters are available any time before the interview, after the interview, they don't have the courtesy to call and tell the results. If they don't give feedback, that's acceptable. But not letting you know the results for few days and getting to know from automated emails indicates company culture.