The Misguided Emphasis on Competitive Programming in Interviews

As a job candidate for the Amazon ML Summer School program, I witnessed a rather peculiar and troubling evaluation process. Despite having in-depth knowledge in Machine Learning (ML), my application was rejected due to lower competitive programming (CP) scores in the coding round. Conversely, another candidate with minimal ML knowledge but high CP scores in the coding round was accepted. This evaluation method, primarily based on parameters not directly related to the job role, fails to confirm a candidate's ability in the required field.

A Misaligned Evaluation Approach

When hiring, it is pivotal to measure candidates based on relevant skills. According to LinkedIn's 2019 Workforce Learning Report, 93% of employees would stay at a company longer if it invested in their careers. If companies like Amazon continue to value irrelevant skills over the necessary ones, they risk losing highly experienced and suitable candidates who, given the opportunity, could significantly contribute to the company.

The over-reliance on CP in the hiring process is a glaring example of this misalignment. While CP is undoubtedly a useful skill, it is not the be-all and end-all of computer engineering or software development. In the real world, engineers need to solve complex, domain-specific problems, collaborate with teams, understand user requirements, and maintain code quality over time—skills that CP does not adequately assess.

The Broader Impact on the Industry

This issue is not confined to Amazon alone. Major MNCs like the MAANG (Meta, Apple, Amazon, Netflix, Google) companies often use CP as a significant part of their interview process. While these companies are leaders in the tech industry, their reliance on CP as a primary evaluation tool has far-reaching negative consequences for the entire computer engineering field.

1. Narrowing the Talent Pool: By prioritizing CP skills, companies inadvertently narrow their talent pool. Many highly skilled developers, who excel in practical problem-solving and have extensive experience in software development, may not perform well in CP challenges. As a result, they are overlooked despite their potential to add significant value to the company.

2. Discouraging Diversity: The emphasis on CP can also discourage diversity. Competitive programming tends to attract a specific demographic, often those who have had the time and resources to train in these specific skills. This can lead to a homogenous workforce, lacking in varied perspectives and innovative ideas that come from a diverse team.

3. Misalignment with Job Roles: Many roles in software engineering, especially those involving ML, data science, or backend development, require a deep understanding of the respective domains rather than CP skills. The current evaluation approach often fails to assess candidates' domain knowledge and practical experience, leading to a mismatch between the skills tested and those actually needed for the job.

A Call for Change

In light of the above, we request HR departments to reconsider their evaluation systems, such as the use of CP in non-related roles, to ensure they not only align with the job description but also allow candidates to demonstrate their true potential. A more holistic approach, incorporating real-world problem-solving, project-based assessments, and domain-specific knowledge, would be far more effective in identifying the best candidates.

Companies must recognize that the true measure of an engineer's capability lies not in their ability to solve abstract algorithmic problems under time pressure, but in their overall skill set, experience, and ability to contribute to the team's success. Sign this petition today so that organizations can create a hiring process that respects and values a candidate's specific knowledge and expertise for the role they apply for. This will not only improve the hiring process but also lead to a more competent and diverse workforce, ultimately benefiting the entire industry.