Rescheduling regular DMB meeting day/time

Rafael David Tinoco rafaeldtinoco at
Tue Nov 9 17:03:27 UTC 2021

> On 9 Nov 2021, at 1:59 PM, Dan Streetman <ddstreet at> wrote:
>> I'm +1 on defaulting to async and letting the applicant to choose if
>> he would like the process to be sync. Only one thing we have to consider:
>> async "tests" are easy to "pass" as you can seek for information on a
>> question done by e-mail for example (while the sync interviewing process
>> does not give that option to the candidate).
> In some of the applications we've had, I have suspected that
> applicants who have 'teams' supporting them (i.e. not candidates from
> the community) might have more experienced people privately 'helping'
> them with the answers to our questions.

I felt the same way.

> Now, I don't actually think
> that is a *bad* thing; we aren't trying to administer a closed-book
> school test here, and no actual engineer would ever make an important
> decision they were unsure of without consulting peers. However, I feel
> it's unfair to community candidates who may be 'on their own' going
> through this process. And I have no direct knowledge or proof, so
> maybe it's only my suspicion and not actually happening.

Its okay to think that way. We're not seeking guilty people, just
understanding the process based on our previous experience. I felt
the same of what you just said more than twice.

>> Nevertheless, I'm not a
>> huge fan of the interview process we currently have as it always seem
>> to me we're trying to trick candidates to answer something wrong. I
>> prefer to analyze the previous work of the candidate and base my
>> vote from this "async" root of information anyway.
> And I think this is the real core of the issue - I'm in total
> agreement that we should be reviewing candidates on their actual work,
> not on answers to realtime questions. If all their work looks very
> good, I don't need to ask them anything.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Devel-permissions mailing list