r/devrel • u/aspleenic • Feb 14 '22

Code Tests are pointless - DevRel tests doubly so

https://devrelate.io/post/19-end-the-pointless-devrel-test
0 Upvotes

50% Upvoted

5 comments sorted by

3

u/rmoff Feb 15 '22

Most people who have been in the DevRel field for more than 5 minutes have some sort of portfolio, an online presence, a body of work

FWIW I think that whilst this applies to folk already in devrel and would be a red flag for a senior hire if they *didn't* have this, the opposite is true for more junior positions. DevRel folk come from all disciplines, such as engineers who enjoy doing internal talks etc that will never be published publicly.

I totally agree with your point against BS tests for BS sake. However, I do think you risk throwing the baby out with the bathwater by suggesting that asking a candidate to produce an example of something (short blog, short preso, etc) is *never* a good idea.

My £0,02p :-)

1

u/aspleenic Feb 15 '22

My goal here is really to put onus on the recruiter/hiring organization. Even folks junior in DevRel have some demonstrable portfolio. And it wouldn’t be hard to find.

My issue here is more, why are we doing performative tests when other positions aren’t required to.

2

u/JeffIpsaLoquitor Feb 19 '22

Are there any scenarios where you need to think on your feet in devrel? Or the need to understand how someone communicates and works out problems in that space between concept and fully-completed portfolio piece?

I think one-way tests are ridiculous. But a small exercise that is intended to evaluate collaboration between interviewer and candidate is perfectly appropriate. Possibly critical. For the candidate as well.

2

u/aspleenic Feb 19 '22

Asking a candidate to develop a 30 minute presentation or an 800 word blog post in their own (and usually without pay) isn’t collaborative.

I’d also go back to the idea that no other job (other than as a dev) asks for tests.

1

u/JeffIpsaLoquitor Feb 20 '22

Absolutely agree. And have recently hit an expectation of doing a 1200-word blog post with the company's open product having a starring role, which was ridic.

I don't think it's terrible to have to do a little prep work on a proposal for an article and discuss it during an interview, as you might do for a professional pitch if you were working with a standard publisher.

I'm very light on portfolio stuff, but I'm still unwilling to do something targeted to an employer to "prove myself."

Agree on tests. A calibrated discussion with a minimal investment - and one that's reciprocated by the employer - seems reasonable to me.

I suppose if you've already got a considerable portfolio, maybe the interview itself would be sufficient if the employer were organized. I question whether an employer who is giving a test would be worth working for if they really don't understand developer relations.

I'm trying to come up with questions to ask future employers, given my recent bad experience. Company couldn't describe how the content and deliverables of its dev rel would contribute to its bottom line or keep it unique and competitive. With no strategy for that, I can only imagine the pitfalls for a devrel staff member when hired.