30 karma · joined May 16, 2020
- It is not entirely clear how the datasets split is done. Do you make sure that the model is evaluated on unseen data ? More generally how does one knows whether a dataset was part of the training or not ?
- You mention some serious limitations (10k rows, 500 cols.). It seems a bit weird to have fixed numbers. Can these numbers be roughly balanced ? (eg. 1M rows, 5 columns ... ). Does these numbers scale with memory ? (what memory was used for the 10k rows / 500 cols figure ?)
- Update your resume / cover letter to make it more appetizing. Don't hesitate to use ChatGPT. Change the title to match the job. You usually have to cater for HR first, not technical people. Also remove the stuff that you don't want to work with. This will remove the tech you don't want to work with anymore.
- Emphasize anything that could stand out (side projects, anything to do with hot topics / techs). Again you have to catter to HR first.
- Don't get afraid of the numbers (out of the 500 applications you mention a good 450 will be thrown into the garbage immediatly). But try to get early.
- Often the first steps of the process require some customs texts (mails, achievements, why I want to works with you). LLMs can save you time and make your answers more appealing.
- Specialized Recruiting firms can be you friend. Sometimes you need to be blunt with them. Discuss expectation early. ("I am currently making X with Y days remote. Would you be able to find something that match my skill and offer X+20% and at least Y+1 days remote ?")
Now I am just concerned about the privacy of what I share (can it be worse than google ?) and the optimality of the code ? (code usually works, but could it work faster ? what happen when new libraries get out ?)
Might be the problem ...
> the work being a higher percentage non-code is what's causing us trouble
Might be another problem... are you recruiting a PM or a Software Eng ?
> - Take-home technical assignment (~4h) or similar at candidate's choosing
I've personnaly stopped doing those. Either they are very far off the job either too revealing. And generally taking way too much time.
Last question was followed by the longest silence I ever heard in a meeting... I wasn't invited the next meetings. I heard it took them more than 5 other meetings to reconsider my solution. An intern has finally been sent to buy the hard drive last week.
"Equality of Opportunity in Supervised Learning" (https://arxiv.org/abs/1610.02413)
It explain the basic concept about fairness in ML. Very practical exemple in my domain knowledge that show the trade-off between fairness of an algo and overall performance (money). Really make you see what may go wrong with bias in ML. It shows, in my opinion, why we will have to regulate ML as corporation aren't really incentivized to deal with fairness. It also shows that there is different notions of fairness. So there will always be something that feel unfair and also doing something can always be interpreted as positive discrimination.
Edit: ok nevermind the GME DD exemple. I tried to find it to link it here, but it is now deleted. People are claiming the author was a Microsoft Insider. Disclosing that info was highly illegal. I don't know what would be the legal ramifications of trading on illegal info when you don't know that said info is illegal. But I knwo that being investigated by a 3 letters agency is something you want to avoid.