Site icon Adron's Composite Code

The Reality of “Code Challenge” Culture Outcomes Among Large & Small Organizations

Adron

Young caucasian female programmer in glasses writes program code on a laptop computer. home office

Key definitions for this article:

“Code Challenge” Culture: This culture is more of a “do as we say, we’ll grow you as we see fit, and you may then continue with us if you perform accordingly” type of environment. It starts with a more defined, strict adherence to an academic achievement type environment that enforces one do things a certain way and follow a certain path, and to ensure you too will do those things a code challenge is used to gate keep a particular job role. There are obviously good and bad results to this culture, and this article is going to get deep into those cultures.

Wholistic Culture: This culture is more open to getting a larger picture idea of a candidate in the interview pipeline. With more of an intent around having the individual develop the organization and for the individual to learn. The possibility of bringing knowledge that can help one improve the organization is readily accepted as is an individual that might not pass a rigorous academic code challenge to shift arrays, or move bits, or trickle values around a binary tree! There are however, good and bad outcomes to this type of culture.

Caveats: In both cultures there are numerous additional criteria that changes them. In this article I’ll write about them in a general sense, and then when detailing something specific, I’ll state that caveat with a call out.

The Big Organizations & Smaller Niche Organizations

I’m going to use three big companies and three small companies here that have varying degrees of “Code Challenge” Culture. In that, I’ll dive deeper into the problems that arise from a strict “Code Challenge” Culture vs. a Wholistic Culture.

The Big Organizations

Smaller Niche Organizations

With all those companies described, it is time to get deep into their current outcomes and state of affairs when it comes to “Code Challenge” Culture vs. Wholistic Culture. For each of these I’ll give a % of each culture and discuss their current situational report (SITREP) and what their outcomes have been.

The Big Orgs Culture and Outcomes

No Zama – This company, now that it’s a bit older and has moved into multiple geographical markets continues to hire based on a strict academic “Code Challenge” type of model along with other strict criteria, without emphasizing for wholistic fit and uninterested in improving its own culture to ensure longevity of candidates once employees. For this type of culture this outcome – numerous hires with a goal of keeping the top performers and removing the theoretical lower performing – is the point. However, it perpetuates that top performers end up being missed and often leave from the toxicity of it and the lower performing are often positioned to fail because of the inflexibility of the culture.

In the end the outcome looks like this; a pipeline that has nowhere near the top talent, but instead gets a rough middle demographic of candidates, that are often there for the sole purpose of collecting lucrative salaries and bonuses. Then after a few years leaving to something with a better, healthier, more humane culture.

The outcome, is not particularly ideal. So much so, that the leadership often opines that their pipeline is limited in the markets they have a large footprint, seemingly clueless to having shot themselves in the foot.

JoonBugle – This company, unlike the first tends to have a moderately healthier culture and more humane work life balance for its employees, but still adheres to a strict academic “Code Challenge” type of culture which leads to an interesting gap of folks who regularly – and this is seen even in products as their released – are short sighted on what the overall market looks like or how a product would fit into it.

Because of an increased work balance their retention is marketably higher, while finding work for lower performers to be productive at and keeping high performers retained through bonuses and more choice work. This seems to work, and overall the “Code Challenge” combined with some wholistic hiring practices seems to have done this company well, however without also being massive and having lucrative salaries and bonuses, the probability of having a very limited pipeline of hires would be a significant issue.

Even as it stands, the SITREP for this company remains that the pipelines are slow, costly, and have a mixed outcome result. Lots of candidates, often very competent candidates, go into pipeline and few are hired and fewer tend to remain past six months to a year.

LargeStone – Over the years this company has backed away from the heavy handedness of academically strict “Code Challenge” Culture and focsed more and more on wholistic cultural fit with the additional flexbility of teams organizing more, and having more options to organize as they need, around their respective team and individuals. The result of this is some of the best retention in the industry and – over time as this shift has occurred – a growing retention.

The Smaller Niche Orgs Culture and Outcomes

Developer Consulting of Igor Gatekeeper – Developer Consulting of Igor Gatekeeper embodies a deeply entrenched “Code Challenge” Culture. With a few hundred employees, the organization focuses on consultants who produce at a consistent, high pace, maintaining a rigid, academic, and performance-based hiring process. Candidates are expected to excel in code challenges that emphasize specific technical skills and problem-solving abilities, often rooted in academic principles. This strict approach aims to ensure that new hires can immediately contribute at a high level. While this culture can result in a team of highly skilled technical experts, it also risks alienating potentially valuable employees who might not perform well in high-pressure testing environments but could excel in a more supportive, collaborative atmosphere.

The work however also matches this assembly line style “Do X, only X, and be done” type of work. It’s very much command and control dictate vs. dynamic thinking, something that if lots of Xs need completed as quickly as possible works real well, but for a company working on hard problems that aren’t well defined the need to innovate, invent, or otherwise create solutions and sometimes even find the problems themselves – this is a horrible way to hire and work. The simple reason is, X task often doesn’t exist outside of very well defined problems.

Atty Comms – Atty Comms, a communications organization with a diverse range of products and services, does not heavily focus on software development. This company leans more towards a wholistic culture, seeking candidates who bring a broad set of skills and experiences. Their interview process is designed to understand the candidate’s overall potential and fit within the company rather than just their ability to solve specific technical challenges. This approach allows Atty Comms to hire individuals who contribute to the company’s growth through innovative ideas and diverse perspectives. The flexibility of this culture can attract a wide range of talent, fostering an environment where employees feel valued for their unique contributions, leading to potentially higher retention and job satisfaction.

This is a type of company that can, under the right circumstances, have absolutely stellar high performing development teams. However, in this particular company the leadership is extremely scatterbrained and rarely utilizes or sets up their development teams for success. Often shifting their goals and projects in a way that seems random and haphazard. A prime example of how wholistic hiring is great, and can build great teams, but if leadership doesn’t back it up or doesn’t provide – ya know, leadership – things sort of fall apart anyway. Opportunities not seized!

Starzy – This is software company with around 50 developers, thrives on a wholistic culture and has minimal reliance on formal academic code challenges. This company values community involvement and open-source contributions, seeking candidates who are passionate about their work and can bring fresh insights to the team. Their hiring process is flexible and open-minded, aiming to identify individuals who are not only technically competent but also align with the company’s values and collaborative spirit. This inclusive approach helps Starzy build a diverse team with varied strengths, promoting innovation and a strong sense of community within the organization. As a result, employees at Starzy often feel more engaged and committed to their work, leading to better overall performance and job satisfaction.

In an exception to the norm, Starzy also retaining their employees for dramatically longer than most companies in the industry, even so much as some have worked for and retired – i.e. actually retired, not just having *left* – from the company.

Company Culture Outcome Ratings

No Zama

JoonBugle

LargeStone

Developer Consulting of Igor Gatekeeper

Atty Comms

Starzy

Cultural Scenarios Summarized

Through examining these organizations, it’s evident that the culture and leadership within a company significantly impact hiring effectiveness and employee retention. While a “Code Challenge” Culture may ensure technical proficiency, it can lead to high turnover and dissatisfaction. Conversely, a wholistic approach fosters a more inclusive and supportive environment, though it requires strong leadership to maintain consistency and direction. Ultimately, the key to a high-performing team often lies in removing barriers and empowering employees through thoughtful leadership. More detailed insights and recommendations will be shared in the upcoming articles. Stay tuned, and let’s continue the conversation!

More on that, more on all these topics in the near future. I’m always interested in your thoughts dear reader, so comment, subscribe, and let’s get a conversation going!

Exit mobile version