AboutRock god of code
SkillsJava, JS, FE, BE
Joined devRant on 9/27/2019
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Anyone heard of a an interview process where you apply through a job site and the first interaction back from the company is a coding project?
I've had it a few times where I'm told there will be a coding project or there has been later in the process, but I've never had it as the immediate first step.
Why would an unknown small startup think that someone would spend a couple of hours effectively working for them without having the slightest idea about the company and culture. An application is usually classed as an expression of interest and a discussion into the wider detail is then usually had with some HR or recruiter representative (or at least that's my experience in the UK)6
When the idea of a bonus is ignored again by corporate, and the idea of pay rises has been long forgotten3
Know the basics of the tech, don't just dive in with some off the shelf blackbox buzzword then find yourself crippled when you need to debug it going wrong1
For the challenge:
The challenge of living within your means when you start out then realising that no company gives the payrises and/or bonuses stipulated as possible in the contract or 'a sure thing' by the recruiter, such that what was comfortably your living within your means becomes living well outside your means thanks to inflation, and no pay review to make things match.
Because I like to do work that either never gets used, or gets rewritten and fucked by the apprentice before anyone attempts to use it.2
Why do people like hiring managers at companies seem to think that because you are paid to code you spend your spare time coding?
You don't expect a surgeon to operate all day then go home and randomly start cutting people up, so don't expect a code surgeon to spend all day coding to go clock off the start hacking away at shit either!10
Guy advertises job. Decent pay, decent benefits, all in all decent package.
Guy replies to request for further information with some shit about being able to get you 50 calls from people who will hire you but would you want to work for them... well that's why i didn't apply to 50 jobs you applied to the 1, because it sounded like you would want to work for them.
Then guy says they are paying a lot less than avertised, and the advert is basically bullshit to get him people to give his 50 opportunities shit to.2
I know lets create a method that does nothing like this other method, but call it the same thing with 'get' in front. Won't confuse anyone at all that3
Just had my reasoning for not doing technical projects for interviews proven.
Pass the first 2 stages of interview (including showing some personal portfolio projects) then after a week of hearing nothing get sent a technical project to complete.
Spend every spare moment for a week polishing this thing, decent front end, quick and efficient back end, low traffic between fe, be, persistence etc.
Submit the code at midday ready for the interview the following day, only for the company to phone at 5pm and say all is fine and the code is great for the final interview (walkthrough) the next day, then phone 5:10pm phone and pull the position.
That company has just had free work done which should have cost 1 weeks worth of fees, using the premise of a job at the end of it, only to take the code that they are super happy with and run with no payout.10