Originally posted by northernladuk
View Post
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
- You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
- You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
- If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Programming Contracting Jobs: What is the interview/hiring process like?"
Collapse
-
Originally posted by FIERCE TANK BATTLE View PostThis is a common thing for people to say in these circumstances, and for most cases I would agree, but as a contractor I will do literally anything they want for my day rate and putting up with dire companies and incompetent managers etc. is par for the course. Also I would say the interview quality doesn't always line up with the job, I've had amazing interviews and terrible jobs, and vica versa. Total crapshoot!
Tech tests can be pretty good, if they're like 15-20 minutes and are straightforward.
Honestly I prefer just talking to someone who asks questions or shows a bit of code and says what's wrong with it etc. because software engineering is about coming up with solutions and explaining how you'd solve a problem takes 30 seconds and shows more skill than remembering the exact syntax of a bunch of commands that you'd normally just grab off stackoverflow.
Leave a comment:
-
Originally posted by hungrybear View Postif they give you such treatment during the interview, its actually good you didn't get the job
Tech tests can be pretty good, if they're like 15-20 minutes and are straightforward.
Honestly I prefer just talking to someone who asks questions or shows a bit of code and says what's wrong with it etc. because software engineering is about coming up with solutions and explaining how you'd solve a problem takes 30 seconds and shows more skill than remembering the exact syntax of a bunch of commands that you'd normally just grab off stackoverflow.
Leave a comment:
-
Originally posted by FIERCE TANK BATTLE View PostHave learned my lesson now, I won't do any stupid coding tests that take several hours. I did that and turned it in and they said 'we couldn't get it to run, so we gave it to a dev and he said it sucked'.
I literally did about 2 weeks of work in 2 hours, to write an entire website with all kinds of fancy functionality.
Leave a comment:
-
I'm on the fence about coding tests.
Been burnt by one "in your own time" test I spent a bit of time on that was entirely fabricated for the interview (eg not a real world freebie consultancy thing), but was so ivory tower it was ridiculous. I did not get that role.
Another was a 1hr 30min in person, with first 45 mins as a coding test.
That couldn't have been more perfectly set up.
It was a 3/4 finished website (a set of a few data driven pages really) with a service layer, and database.
There were 3 built in errors I had to resolve, which were common issues in the framework, and 2 or 3 small features to complete.
It was short, concise, and plenty enough to practically prove that I knew the technology, and I got the role.
Leave a comment:
-
Originally posted by FIERCE TANK BATTLE View PostTotal crapshoot.
Have learned my lesson now, I won't do any stupid coding tests that take several hours. I did that and turned it in and they said 'we couldn't get it to run, so we gave it to a dev and he said it sucked'.
I literally did about 2 weeks of work in 2 hours, to write an entire website with all kinds of fancy functionality. It was very stressful trying to work so fast but the result worked perfectly as I put it onto my own webserver to test it. The recruiter obviously removed me as a potential candidate the second he didn't get his payday and wouldn't give me any feedback.
Figures, I often end up working for companies that have the worst devs, assuming they haven't walked out already.
Next day, had another call, an interview 2 days later, and were so keen they apologised for not playing it cool and going through the recruiter but offered me the job on the spot. Just a quick grilling on all things technical in the interview which was a total breeze for someone with 15+ years relevant experience.
Was super miffed (still am) though at the time I sunk into that first one just for them to hurt my pride like that. Yeah, my CV of 15+ companies of job history is bollocks and I can't write a website that runs
Leave a comment:
-
Originally posted by FIERCE TANK BATTLE View PostTotal crapshoot.
Have learned my lesson now, I won't do any stupid coding tests that take several hours. I did that and turned it in and they said 'we couldn't get it to run, so we gave it to a dev and he said it sucked'.
I literally did about 2 weeks of work in 2 hours, to write an entire website with all kinds of fancy functionality. It was very stressful trying to work so fast but the result worked perfectly as I put it onto my own webserver to test it. The recruiter obviously removed me as a potential candidate the second he didn't get his payday and wouldn't give me any feedback.
Figures, I often end up working for companies that have the worst devs, assuming they haven't walked out already.
Next day, had another call, an interview 2 days later, and were so keen they apologised for not playing it cool and going through the recruiter but offered me the job on the spot. Just a quick grilling on all things technical in the interview which was a total breeze for someone with 15+ years relevant experience.
Was super miffed (still am) though at the time I sunk into that first one just for them to hurt my pride like that. Yeah, my CV of 15+ companies of job history is bollocks and I can't write a website that runs
At the other end you get "do Fizzbuzz". Why? It's a test that's so well documented it's impossible to not do a good job - plus it's noddy and unrepresentative.
I tend to find companies doing those tests are those lacking "Interviewer" skills. Best one I ever had was a company showing a very small part of their existing system, some Java classes. Interviewer asked me just to explain what I thought they'd done well, done badly and how it could be improved. A much better way of doing things - you're not blindly and expediently cranking possibly crap code out, you're explaining your thought processes behind decision making.
Leave a comment:
-
Total crapshoot.
Have learned my lesson now, I won't do any stupid coding tests that take several hours. I did that and turned it in and they said 'we couldn't get it to run, so we gave it to a dev and he said it sucked'.
I literally did about 2 weeks of work in 2 hours, to write an entire website with all kinds of fancy functionality. It was very stressful trying to work so fast but the result worked perfectly as I put it onto my own webserver to test it. The recruiter obviously removed me as a potential candidate the second he didn't get his payday and wouldn't give me any feedback.
Figures, I often end up working for companies that have the worst devs, assuming they haven't walked out already.
Next day, had another call, an interview 2 days later, and were so keen they apologised for not playing it cool and going through the recruiter but offered me the job on the spot. Just a quick grilling on all things technical in the interview which was a total breeze for someone with 15+ years relevant experience.
Was super miffed (still am) though at the time I sunk into that first one just for them to hurt my pride like that. Yeah, my CV of 15+ companies of job history is bollocks and I can't write a website that runs
Leave a comment:
-
Originally posted by ukcontr View PostHi,
I've been freelancing for years (mostly php, but other related languages/technologies too), and am thinking of moving to London to get some contracting jobs.
One thing that I can't find much info on is what is the hiring/interview process like?
I can find lots about 'normal' interviews. All I've really found is that when they hire you for a contract job the interview process is much quicker.
Can you post some examples of what you've been through.
Also, what is the market like in London? If you know your stuff, how hard is to to land a contracting job even if you don't have many references? I've read that they like to hire people who have a few years of many contracting jobs (each 3-6 months)
they are more to the point, usually ~1 hour technical conversation / code review and team culture fit conversation with managers. most clients have specific work they want to be done and specific frameworks they are using. so if you are technically sound at these (do some research during the initial phone call) & can work in a team you should be good.
in my experience, the market is currently quite good for devs.
Leave a comment:
-
Originally posted by oliverson View PostIt really can vary. I'm a contract dev, mostly in London finance. Typically you'll have a telephone interview where they'll ask technical questions, tell you about the role, etc. If all goes well you'll be called in for a face-to-face where anything might happen. It may be a discussion of the projects you've worked on, might be some white-boarding, they may give you a technical test and call back in a set period of time or my least favourite, they'll sit there watching you code in order to 'analyse your thought process'. If you get through that you may well receive an offer or for some of the banks, typically the American ones, there'll be further rounds. I think Morgan Stanley used to favour about 5 or 6 rounds! I've also done coding 'assignments' for some roles which I prefer to the pair-programming stuff. You then get to talk about your code in the next stage, which is far less pressure. The issue with the pair programming type thing is the guy you're sat with knows the spec. like the back of his hand having done it a number of times, whereas you are expected to immediately understand it and start coding away. The tendency there is to get stuck in without really understanding the problem you are trying to solve. Each second that passes before your start coding seems like a minute. Horrible. I just don't do those interviews anymore.
Leave a comment:
-
Originally posted by Unix View PostIf your good, it will be a 10 min interview were they ask when you can start. If not it will be like a permie interview.
Leave a comment:
-
If your good, it will be a 10 min interview were they ask when you can start. If not it will be like a permie interview.
Leave a comment:
-
Originally posted by ukcontr View PostHi,
I've been freelancing for years (mostly php, but other related languages/technologies too), and am thinking of moving to London to get some contracting jobs.
One thing that I can't find much info on is what is the hiring/interview process like?
I can find lots about 'normal' interviews. All I've really found is that when they hire you for a contract job the interview process is much quicker.
Can you post some examples of what you've been through.
Also, what is the market like in London? If you know your stuff, how hard is to to land a contracting job even if you don't have many references? I've read that they like to hire people who have a few years of many contracting jobs (each 3-6 months)
Leave a comment:
-
Originally posted by Contractor101101 View PostI've also seen a contractor ostracised until they were let go because everyone hated the guy (he was obnoxious, I did a little dance when he was walked out).
Be a normal human, not a gaping arseh0le, get along with people.
Leave a comment:
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers
Contractor Services
CUK News
- Streamline Your Retirement with iSIPP: A Solution for Contractor Pensions Sep 1 09:13
- Making the most of pension lump sums: overview for contractors Sep 1 08:36
- Umbrella company tribunal cases are opening up; are your wages subject to unlawful deductions, too? Aug 31 08:38
- Contractors, relabelling 'labour' as 'services' to appear 'fully contracted out' won't dupe IR35 inspectors Aug 31 08:30
- How often does HMRC check tax returns? Aug 30 08:27
- Work-life balance as an IT contractor: 5 top tips from a tech recruiter Aug 30 08:20
- Autumn Statement 2023 tipped to prioritise mental health, in a boost for UK workplaces Aug 29 08:33
- Final reminder for contractors to respond to the umbrella consultation (closing today) Aug 29 08:09
- Top 5 most in demand cyber security contract roles Aug 25 08:38
- Changes to the right to request flexible working are incoming, but how will contractors be affected? Aug 24 08:25
Leave a comment: