I applied online as I was interested in remote job and seemed very interesting , first step was to send an app I made before , It was really great that they didn't make it a must to implement a specific coding solution , after the recruiter missed my solution , I pinged him and then he came back to me with a rejection, it is ok to be rejected for coding solution , though the explanation is super weird and even contradicting , he mentioned that they rejected the solution cause of : - UserDefaults for storage -> this is weird , since I really needed to persist a very small metadata and it is very advisable to use this common approach , actually it will be really over engineering approach to implement a sqlite based solution via coredata or use Realm for example, archiving might be a good option as well, but still why would user defaults be bad for simple non-senstive data storage, where no migration in the future is needed or something!!!? - second reason was about that the get request is designed to parse array responses only , well for my demo app I didn't need anything else beside that , so according to the YAGNI principle why would I handle an object response for example !? this would be a waste of my time, as I would write more tests and code for something that I won't need !!! Would have loved to discuss this with an engineer, however the biggest turnoff and why I won't recommend applying is that the recruiter wrote -> "Not up to the level for a senior engineer within our team" !! This is rude