Q : My current job isn't great. There's no code review, no testing, no version control, no organisation of software architecture, no concept of 'test vs production servers' and no code commenting.
Needless to say, I want out. But when I'm interviewing, I'm often asked about my processes and how I go about testing or validation. I'm worried that if I mention the bad practice stuff, it will throw up a red flag. What can I do?
A : Don't despair - you're in a much stronger position than you realise.
Demonstrating best practice through your personal projects is an easy place to start. You can set up the src control correctly, test the code, comment on it and find a way to make it scalable and reusable.
The fact you realise why these things are important leaves you in good stead. Turn the negatives of your current job into positive examples where you explain how you would do things differently.
A final thing to bear in mind is that when you apply for a job through Client Server, you will undergo a technical test that will give you an opportunity to flex your knowledge. These tests are written in conjunction with our clients and reflect what the market is looking for. We will never put you forward for a role that doesn't suit your profile and skillset.
With more than 300 live roles on our website
, it's worth having a conversation about.