4 ms·
As a follow up to the IP point, you could always say "I have an integrated AI in my IDE for code completion, so I need to be certain regarding the IP" :D
by SillyUsername 2y ago
As a follow up to the IP point, you could always say "I have an integrated AI in my IDE for code completion, so I need to be certain regarding the IP" :D
- fsndz 2y agoI would be inclined to participate if the process involved a test, followed by a manager's review, and then a go/no-go decision. However, the actual process is much more convoluted: the test is estimated at three hours, but from my experience with something similar, it definitely takes more like six to eight hours. After putting in that effort, you go through HR, which then gives a go/no-go decision before the manager even considers your candidacy. Only then can you present the code you wrote for the test, after which they finally make a decision. This sequence just doesn't make sense to me. I can complete the test, which mirrors real tasks at the job, share it with them, and then possibly get rejected because HR didn't like something about how I expressed myself. So, what’s the point of the test before the HR review? It sends bad vibes even before starting at the company, so I'm inclined to just not engage with it. They would rather have me spend three to eight hours on a test instead of having HR do a 30-minute pre-screening. This approach says a lot about the company's culture.