Rapidly scaling start-ups can sometimes be (mis)guided by following the mentality of hiring like the big tech giants – think Facebook, Google, Amazon. Their convoluted, seemingly cunning and lengthy interview process can be a real inhibitor to scaling and growing a company.
The only way technology start-ups can scale teams ahead of the competition is by creating their own unicorns and learning from the experience of failing to do so. Obsessive interview processes around an impossible to fill requirement will either kill most technology start-ups dead or at least ensure they fail to compete for talent.
Make your Technical test an enabler to show off a developer’s talent, not an inhibitor! A growing number of companies are using technical coding tests as a key part of interviewing new developers. However, in our experience the number of developers that fail these tests greatly outweigh the number who pass them... but does this make them bad developers?
When you first start to program, the question plagues you. The problem, as you see it, is quite simple: learning to program is a series of building blocks, and you want to know which is the lowest to get your knee up onto first. It seems like a straight-forward question - why can no-one give you a straight-forward answer?
Having worked at Talent Point for over a decade I believe that the gap between customer and recruitment agency has never been wider. Empathy is critical to the success of the job seeker, the agency and the appointing business, yet the three-way relationship rarely creates it naturally – effort and trust are required from all three parties to achieve mutually beneficial outcomes.
Why establish a Java Engineering function outside London? What are the issues faced with tech hiring in Berkshire, Surrey and Somerset? How do you market non-London roles more effectively? How do you attract top talent to companies outside of London? Tech hiring outside of Lodnon is whole different ball game. Learn form our experience how to navigate this terrain.
"Do one thing at a time. Create slack in your system. Stop to reflect. Have clear priorities. Be responsive to change. Learn from failures. Things that sound kind of obvious, but are sometimes hard to apply in practice." Is it Agile in the same context as software development? No. But is it an agile way of working? Definitely.