I can't post the exact tests but these aren't difficult tests, they are smoke tests and representative of the type of work we do every day (I'm not asking anyone to invert a b-tree or <insert any other stupid "look how smart we are"-type test>).
Our interview process is 4 steps:
1. Get to know you interview, talk about your resume a little, go through a set of questions we ask all applicants - 1hr
2. Very basic test where you need to fetch data from an endpoint, and render content based on what your retrieved. It's very straightforward and simple (HTML/JS), after this we run you through a real issue we ran into giving you all the background information and ask you to talk through how you would solve it (and you can ask any/all questions). We guide you as you go and it's not a "gotcha" question at all. You don't need to guess exactly how we solved it to "pass". - 2hr
3. Simple debugging test, existing HTML/JS + PHP code with a few bugs scattered through it. We are talking raw PHP here and a TLOC of <300. None of these bugs are "gotchas" either. You can find them all by looking at the logs and/or the server response (basic debugging skills for this kind of job). After this you meet some more of the team - 1.5hr
Consolidate step 2 and 3 into one and cut it down from 4 hours to 1 or you’ll have a lot of people “fail” because they don’t want their time wasted (usually companies pay for extensive tests with programming). You can still kick people out during their trial period even in countries with strict labor laws too.
joshstrange|1 year ago
Our interview process is 4 steps:
1. Get to know you interview, talk about your resume a little, go through a set of questions we ask all applicants - 1hr
2. Very basic test where you need to fetch data from an endpoint, and render content based on what your retrieved. It's very straightforward and simple (HTML/JS), after this we run you through a real issue we ran into giving you all the background information and ask you to talk through how you would solve it (and you can ask any/all questions). We guide you as you go and it's not a "gotcha" question at all. You don't need to guess exactly how we solved it to "pass". - 2hr
3. Simple debugging test, existing HTML/JS + PHP code with a few bugs scattered through it. We are talking raw PHP here and a TLOC of <300. None of these bugs are "gotchas" either. You can find them all by looking at the logs and/or the server response (basic debugging skills for this kind of job). After this you meet some more of the team - 1.5hr
4. Meet the owners, talk compensation, etc - 1hr
eska|1 year ago