4 ms·

If I got something like this at a job interview, I'd let them know my hourly contact rate and ask them to sign a contract for completion of this work. They can

If I got something like this at a job interview, I'd let them know my hourly contact rate and ask them to sign a contract for completion of this work. They can put a little skin in the game to see if you're the right hire and paying for a few hours of dev work at 150-300/hr is peanuts to the cost of picking the wrong person. To many jobs available right now. Companies only get away with this people choose to play. Job market is just too good for this nonsense. Seriously respond with a contract to sign that includes your hourly rate. Maybe open with the letter that says, "I'm sorry your last girlfriend hurt you, but..." Then extol your virtues and how you get paid for work.

bryanrasmussen 4y ago
I agree I am not willing to do this test, it's too much. Have things to do. But if you were given a jira ticket with this in it and asked to specify how long, how long would you say? 2.5 days is what I'd say. Maybe I'd get lucky and finish in even 1, but that would depend on me not finding weird edge cases, which I'm pretty good at finding those. So fixing edge cases another day. Half day buffer.
- brudgers 4y ago
  Edge cases are relevant for some definitions of "production ready" but not for all. I mean it's not like someone dies if the search just mostly works. To put it another way, an engineering constraint is a three hour budget and part of the test is can the candidate accept the cost-benefit implications of such a constraint?
  - bryanrasmussen 4y ago
    yeah, but production ready is what is checked against, since you have 6 days and 23 hours to compete the code test that should take approximately 3 maybe 4 hours I assume the actual time is 6 days and 23 hours if that's what it takes to make it 'production ready'. >Edge cases are relevant for some definitions of "production ready" but not for all. yes sure, if all your platform looks like shit on mobile then when your new component looks like shit on mobile it is production ready, however when all you have is that one component and nothing else pretty sure people will resize etc. and say hey it is not production ready! Also production ready also refers to code quality of course, did you turn everything that should be module into a module even though doing so of course adds a little more time. >To put it another way, an engineering constraint is a three hour budget this is not what they say they want however, I would be willing to deliver as much as I can in 3 hours and say how's that? But then I wouldn't get the job so in the same time I know, well it's not worth doing. I mean it's not worth doing since I am just as far along with 3 other companies, one which gave me a 1 hour test which took 1 hour and probably will pay better and have better benefits. So obviously there is just no scenario in which I would do this test, but what I'm wondering is how close is my estimation to how much other people think it would take.
    - brudgers 4y ago
      As I said elsewhere, I might be able to do it in a month —I’d have to StackOverflow enough React — but can imagine someone who can knock it out in an hour. That’s a perfect candidate vs the don’t call us we’ll call you I would be. If you can’t deliver what they expect in the time window, then the simplest explanation is you are not able to provide what they are looking for. This makes it a useful and relevant assignment for both parties. A test that most candidates can pass is a waste of everyone’s time. —— Crappy on mobile may be good enough because production is a business process not an engineering theory. Low initial cost may be preferable to lowering operational cost. The bottom line and cash flow are legitimate measures of code quality.

bryanrasmussen 4y ago

I agree I am not willing to do this test, it's too much. Have things to do. But if you were given a jira ticket with this in it and asked to specify how long, how long would you say? 2.5 days is what I'd say. Maybe I'd get lucky and finish in even 1, but that would depend on me not finding weird edge cases, which I'm pretty good at finding those. So fixing edge cases another day. Half day buffer.

brudgers 4y ago
Edge cases are relevant for some definitions of "production ready" but not for all. I mean it's not like someone dies if the search just mostly works. To put it another way, an engineering constraint is a three hour budget and part of the test is can the candidate accept the cost-benefit implications of such a constraint?
- bryanrasmussen 4y ago
  yeah, but production ready is what is checked against, since you have 6 days and 23 hours to compete the code test that should take approximately 3 maybe 4 hours I assume the actual time is 6 days and 23 hours if that's what it takes to make it 'production ready'. >Edge cases are relevant for some definitions of "production ready" but not for all. yes sure, if all your platform looks like shit on mobile then when your new component looks like shit on mobile it is production ready, however when all you have is that one component and nothing else pretty sure people will resize etc. and say hey it is not production ready! Also production ready also refers to code quality of course, did you turn everything that should be module into a module even though doing so of course adds a little more time. >To put it another way, an engineering constraint is a three hour budget this is not what they say they want however, I would be willing to deliver as much as I can in 3 hours and say how's that? But then I wouldn't get the job so in the same time I know, well it's not worth doing. I mean it's not worth doing since I am just as far along with 3 other companies, one which gave me a 1 hour test which took 1 hour and probably will pay better and have better benefits. So obviously there is just no scenario in which I would do this test, but what I'm wondering is how close is my estimation to how much other people think it would take.
  - brudgers 4y ago
    As I said elsewhere, I might be able to do it in a month —I’d have to StackOverflow enough React — but can imagine someone who can knock it out in an hour. That’s a perfect candidate vs the don’t call us we’ll call you I would be. If you can’t deliver what they expect in the time window, then the simplest explanation is you are not able to provide what they are looking for. This makes it a useful and relevant assignment for both parties. A test that most candidates can pass is a waste of everyone’s time. —— Crappy on mobile may be good enough because production is a business process not an engineering theory. Low initial cost may be preferable to lowering operational cost. The bottom line and cash flow are legitimate measures of code quality.