By readability I mean: "Candidate did not produce 100 lines of code in a single block".

Depending on how you trust interviewers to do right thing these rubrics might be more specific (e.g.: "Code is indented", "variables are descriptive"). . .

I dunno. I'm happy I don't have to design recruitment process now :)


Well it is hard. Depending on how your read them. I try to interpret them graciously.

Like if somebody starts doing variables: "lengthOfTheArray" but they come from Java enviornment this is understandable. If somebody uses int* array in C++ but they did embedded then this is also understandable.


3) Take home tests are nice, but then you have a 2h take-home test, for which candidate spends 8h as they are incentivized to overdo it, which is as bad as 1.;
4) Maybe asking FizzBuzz questions are enough? I'd be wary about the signal to noise ration;
5) Some people evaluate github profiles, which is fine and dandy, until you notice that sometimes you evaluate candidate code that was written 5 years ago. . .


Re: What to ask.

This is a hard question.

1) I think that hard algo challenges are actually biased against underprivileged people (you won't pass them without time to prepare);
2) Testing "real world" knowledge is hard as you need either force interviewee to use your frameworks (which is as bad as 1.) or you should evaluate their code as given and deal with unfamiliarity (which is hard to do).

Such rubric makes it hard to grade somebody lower due to, I dunno, gender.

Obviously if this only helps with unconscious biases.

When interviewing such rubric helps me to check artifact produced by interviewee against "objective" metric.


RE: Evaluation:

I'd assume being fair implies being unbiased.

For fairness you should have some rubric that is shared by all interviewers, and this rubric should be hinted to interviewees, like: "Oh we care about code correnctness a lot, also we want the code to be idiomatic".

Ideally rubric has both axes, eg. "code clarity" and descrpitions for ratings: "Code was idiomatic for a given language, readable, yadda da".

Polish Refugee Crisis // Reasons for hope 

I wish I could do more than donate money and things to the cause.

But sometimes staying back is better than moving to the front-lines.

Show thread

Polish Refugee Crisis // Reasons for hope 

There is a little hope in this situation.

Right now there is a group of volunteers that try to fish out refugees from forests, feed them, give them warm clothes, and take their asylum requests, and take them into client-lawyer relation with (volunteer) lawyers.

They are funded by some NGO's and by people donations.

So in Polish forests there are two groups Border Guard that tries to push refugees back, and volunteers trying to find them and help them.

Show thread

Polish Refugee Crisis (CW in first message) 

This is a weird emergency, the post works, it was even proposed to allow hunting (including international hunters who pay fat money). Yes they wanted to allow random people with guns into a forests where refugees hide. Polish hunters are very known for mistaking dogs, people and other hunters with animals they hunt. The line of defense is: "I mistook my colleague for a boar your honor", and it worked for a time.

Show thread

Polish Refugee Crisis (CW in first message) 

Ruling party also started State of Emergency in the border towns, which mainly does block access to the site to volunteers, doctors and media.

Apparently they want refugees to die in silence.

Show thread

Polish Refugee Crisis (CW in first message) 

Ruling party tried to legalize push-backs (pushing people to the other side of the border). They even passed some law (with support of the liberal "opposition").

However they still break the law by not taking asylum requests.

Show thread

Polish Refugee Crisis (CW in first message) 

Border guard needs to take asylum request, and needs to take asylum seeker to safe place, where they wait for the asylum being granted (or not).

They don't do that, and in fact weren't doing that for quite some time. I read reports from border crossings from year ago describing not taking asylum requests.

Show thread

Polish Refugee Crisis (CW in first message) 

It is winter now and most of the people that try to cross the border are unprepared.

Already, at least 10 people died (this is the number of bodies found, though I would assume that there is way more bodies in the forest).

Just to reiterate this fact: people die from cold and hunger in Polish Forests hiding from Border Guard in 2021 year, in a modern society in a EU member state.

Show thread

Polish Refugee Crisis (CW in first message) 

So we have refugee crisis in Belarusian Border.

EU sanctioned Belarus, and Belarus decided that in turn they will open their borders to people from middle east (e.g. people that spent last 6 years in a refugee camps).

When they arrive they are transferred to the border and are forced to pass the border illegally.

Polish Border Guard does not allow them to apply for asylum, and instead illegaly-ish pushes them back to Belarus border.

Show thread

Polish Refugee Crisis 

Below I will write things about polish refugee crisis on the Belarus Border.

If you need more info AMA, I'll try to answer.

Content warnings:

- Physical harm and trauma;
- Death;
- Border guard harming people;

(Rest in the thread)

@lm Having to specific requirements will make sourcing hard.

Google has very fair interview process, which ticks most of the basics boxes: you get to know what is expected, the process is fair, their sourcing is biases. But the outcome they are less diverse that the industry...

My guess at the reason is that their Interview is hard. And to learn algorithms for a month before the process you need some kind of privilege (free time, child support, good mental health...).

@lm Maybe about interviews.

Basics are that Interviews test skills needed for the job, candidates know what will happen.

I'm also against checking specific skills but rather general knowledge. This is why corps test algorithm, assuming that I'd you know algo you will learn specific framework when you are inside. This is obviously expensive approach. But the baseline would be not testing specific framework you use, but maybe test any framework in language od your choice.

@lm About retaining I have probably least input.

Hire good managers, pay above market rate, spend some money on team building.

To retain diverse employees probably you need good employee code of conduct, and HR that enforces it. E g. the company won't retain woman if sexism (even in jokes, etc.) is acceptable. It will be hard to retain trans folks if dead naming is ok, or if dead name is in any online register (in practice all systems should show preferred name).

@lm If I were to reach out to diverse folks in Poland I'd probably know a Facebook group or two.

Having fair interview process also helps. Moreover it would be good if the process involved multiple people. So no single person can shoot down an applicant.

As other mentioned interview process should be more about skills not about past achievements.

@lm while interviewing process should be probably the same, independently of candidate background, but sourcing can be biased towards minorities. I.e. while you can expect cis males to reach out to you, the company should actively reach out to people from minority background.

I have no idea what support you have. In big corp I would assume that most you head is quota for recruitment team. If you need source yourself then probably you need to be creative.

Show older
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!