[LucidLynx]

I applied early last year, and got rejected by a Senior from CodeWeavers but without any insight...

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.

[inahga]

Sorry I should have been clearer--the initial rejection email did not contain feedback. I replied to the rejection back asking for feedback, and the CEO replied back with the senior engineer's precise 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.

[LucidLynx]

Let me be honest here: I spent time to get a 'hey, nope.', and I should write an email to ask why?

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...

[stuaxo]

That's not great - not unusual, but I expect better respect of people's time from a company involved in FOSS.

They really should give proper feedback.