Garbage in, garbage out and why companies find it hard to screen and recruit good tech talent

Share on facebook
Share on google
Share on twitter
Share on linkedin

It is common to hear companies complain that it is hard to find good talent. A lot of the reason for that is that the companies don’t have an efficient way to screen candidates fast. They waste weeks interviewing the wrong candidates because they don’t really know what makes a good engineer. Is it their impressive results that they claim? Is it their fantastic superhuman brain that just got them to be naturally born rockstar developers? The reason companies are wasting their time is because they screen based on output (resumé and claimed experiences) and raw intelligence and neglect the most important thing. What is that? Inputs.

In software development, there is a common phrase “garbage in, garbage out”. What that means is that no matter how smart your overly buzz-worded AI-machine-learning-blockchain system is, it will only produce good outputs if you give it good inputs. The same applies to humans. No degree of the super brain will produce excellent outputs without also being given excellent inputs, and a guy with average raw intelligent but with awesome inputs will beat the guy with excellent raw intelligence but bad inputs.

What does this rambling have to do with recruiting?

In your screening, have awareness of what is good input and screen the candidate for taking in good input. Start asking your candidates these questions:

  • Who are your idols/main influences in software engineering?
  • Which books/blogs/courses have thought you the most about software engineering?

You can’t lie about these questions. When you are sure that the candidates are taking in good input, you can start to trust that the outputs they claim are actually true. If the candidate says they can’t recall any of their influences or they don’t have any, you can politely thank them for their time and move on. Good output needs good input.

Standing on the shoulders of giants are the core ingredients of all geniuses in history, so start screening for that instead of being overly fixated with raw intelligence and their past experiences.

If you are looking for better talent in your team, you should either improve the inputs by doing a workshop for the team or recruit new talent using these kinds of input focused questions. If you are working with Angular development, then I recommend taking a look at this case study:

Do you want to become an Angular architect? Check out Angular Architect Accelerator.

Related Posts and Comments

How to Handle Errors in a Reactive Angular App

In this post, we will cover how to handle errors in a reactive Angular app. To provide a good user experience you should always let your users know what state your application is in. That includes showing a loading spinner when it’s loading and showing error messages if there are any errors. It is a

Read More »

How to Set Up Git Hooks in an Nx Repo

Git hooks can be used to automate tasks in your development workflow. The earlier a bug is discovered, the cheaper it is to fix (and the less impact it has). Therefore it can be helpful to run tasks such as linting, formatting, and tests when you are e.g. committing and pushing your code, so any

Read More »

The Stages of an Angular Architecture with Nx

Long gone are the times when the frontend was just a dumb static website. Frontend apps have gotten increasingly complex since the rise of single-page application frameworks like Angular. It comes with the price of increased complexity and the ever-changing frontend landscape requires you to have an architecture that allows you to scale and adapt

Read More »

The Best Way to Use Signals in Angular Apps

Since Angular 16, Angular now has experimental support for signals and there is a lot of confusion in the community about whether this is going to replace RxJS or how it should be used in an app in combination with RxJS. This blog post sheds some light on what I think is the best way

Read More »

High ROI Testing with Cypress Component Testing

Testing is one of the most struggled topics in Angular development and many developers are either giving up testing altogether or applying inefficient testing practices consuming all their precious time while giving few results in return. This blog post will change all this as we will cover how I overcame these struggles the hard way

Read More »