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: https://christianlydemann.com/case-study/.

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

Related Posts and Comments

How I migrated my Course Platform to Analog (step by step)

Analog is a full-stack framework for Angular ala NextJS that offers server-side rendering, static site generation, and API routes. Analog empowers Angular with server rendering tools making it optimal for public websites. Otherwise, Angular has often been neglected in favor of NextJS/NuxtJS for these purposes (due to the subpar SSR/SSG experience). I recently migrated my

Read More »

The Future of Angular and the Latest Features in Angular

In this video, I’ll be discussing the future of Angular and the latest features in Angular 17, including standalone components, signals, new control flow, the deferred operator, and server-side rendering improvements. I’ll also touch on the use of Tailwind CSS for styling and the benefits it offers. Join me to learn more about the exciting

Read More »

How to Invest as a Software Developer

In this video, I share my personal investment strategy as a software developer, focusing on putting money to work and owning assets that generate cash flow and appreciation. I discuss the snowball effect of building an investment portfolio over time and the importance of compounding. I also touch on the allocation of investments in stocks,

Read More »

Angular 17: What’s new?

Angular has since the latest major version started what the Angular team calls a renaissance, which means a radical renewal of the framework. The main goals of the latest updates have been to improve the developer experience and performance so it aligns more with the other leading front-end frameworks in the space by introducing new

Read More »

How to Set up a CI pipeline with Azure Pipelines and Nx

It goes without saying that having a CI pipeline for your Angular apps is a must. Setting one up for regular Angular apps is fairly straightforward but when you have an Nx monorepo there are certain other challenges that you have to overcome to successfully orchestrate a “build once, deploy many” pipeline. This post will

Read More »

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 »