(I bombed it because my C skills were Rust-y :shrug:)
Do not look for the super-core stuff like user32.dll and ntdll.dll. There is already a lot of folks working there and it's hard to make an improvement if that's your first contribution. But there are a plethora of random forgotten libraries in dlls/ which usually nobody cares about until some application depends on those, and they are quite likely to have a good amount of low hanging fruits. Look for the todos in the tests, for example.
Disclosure: I work for CodeWeavers, but I am not involved in the hiring process.
Just:
"The senior reviewed your work and it's a 'no'. However you may want to consider submitting patches to either Wine or Proton. Developers that get patches into either of these projects tend to be sought out and offered developer jobs."
I found it gross, and thought that it was actually an ad to contribute to both Wine and Proton first, and not hire someone.
I know I am not the best C programmer in the world, but I think that if you spend two hours of your time doing a test to have a chance for an interview, you might have a feedback of what was wrong instead of a "nope dude".
The test was composed of two things: 1. reviewing a bad C code and make comments, 2. you have an is an unimplemented string sorting API and you have to provide the implementation, the unit tests, etc.
First time and last time I applied to CodeWeavers.
They really should give proper feedback.
Otherwise, the test and first response you received was identical to mine.
FWIW I've never received feedback directly from a rejection email. I've always had to reply back and ask.
If that's not a waste of time, I really don't know what else to call it...
The main issue in the room is that the feedback *should* be present with the rejection email, especially if they spent 5 minutes for a review and 3 minutes for the rejection email...