Home
/
Blog
/
AI Recruiting
/
How to Create Better Workplaces: Tips for Recruiters

How to Create Better Workplaces: Tips for Recruiters

Author
Swetha Harikrishnan
Calendar Icon
December 9, 2020
Timer Icon
3 min read
Share

How does one define a word that has been around for ages, and yet has no distinct meaning? Having just come out of an interview, where someone said “I want to be a part of HackerEarth because of your culture”, I found myself thinking, how oft-used (to the point of becoming banal) yet indecipherable the word culture really is. Contradictory, don’t you think?

Peter Drucker said that culture eats strategy for breakfast. I totally believe that it eats strategy for lunch and dinner too (someone said that as well I think).

The reason why culture is so hard to pin down, in my opinion, is because it’s not a specific set of processes that everyone agrees upon. Wall Street swears by its black-tie culture. Startups think it’s cool that you can use four-letter words in a conversation with your CEO and not get flak for it. Perhaps it’s not as much as what we do as what we don’t, which is the real measure of an organization’s culture.

When writing your culture handbook, the must-nots are probably more important than the must-haves. As HR professionals, it is our job to help define what the must-nots really are.

At HackerEarth, our work culture revolves around a central DON’T.

Don’t Be An Asshole.

When I first walked into HackerEarth, I was awestruck by a poster screaming “Don’t Be An Asshole”. Which, if you look closely, should be the basic tenet of every company’s culture handbook. The poster was a big part of the reason I signed up for the job.

The tenet is self-explanatory, but if asked to explain I would say it translates to don’t be that manager, that colleague, that employee, and that person who makes life hell for others at work. Period. Everything at HackerEarth stems from this basic idea of respect – for self, and for others.

Keeping respect as the central sun of HackerEarth’s galaxy helps us do a few things well:

  • It helps us keep our employees at the forefront of our organization.
  • It helps us underline what is NOT OKAY – behaviors, patterns, conflicts get called out much more easily and resolved faster.
  • It helps us trust our teammates and give them the freedom they need.
  • It helps us understand differences and find common ground.
  • It helps us put the team above individual egos.

Let me elaborate.

1. Keeping employees at the forefront of the organization.

Our approach is ‘inside-out’ when it comes to our people. For anything and everything we do, we start the conversation by asking what it means for our people and then move outward to answer what it means for the company. Yes, it does mean there’s a lot of care and mutual trust for our people. No, it does not mean that we don’t make difficult decisions. We make those decisions too; only we do so with care.

For my peers in HR, you need to move away from the crutches of policies, processes, and practice, and start placing that lens more on individuals. Your policies are just a guidebook. They aren’t written in stone. If you must break the rules to do the right thing, then just do it.

Employee-first culture

2. Underlining what is NOT OKAY.

We like to keep it straightforward and simple. If someone is disrespectful in their tone, or their action, we boldly call it out and tell them it’s NOT OK. In some of these conversations people stay; in others we politely, but firmly, take corrective action.

As an HR professional, you need to be proactive in constantly calling out what’s NOT OK. And that’s how the company learns to do it, too. You also need to ensure that what’s NOT OK does not change for a company’s CEO, the top leaders, your boss, your employees, or yourself.

3. Trusting our people and giving them complete freedom.

Before HackerEarth, I had never worked in a company that trusts so unconditionally. It’s commendable how we do it. We do not hide any information. We always give our people an understanding of the why behind a decision. Even if it is the decision about a pandemic-induced pay-cut or about letting someone go. If we have made a mistake, we own it. We provide every opportunity for our people to ask difficult questions. In fact, we get worried when they don’t. We are never afraid to be vulnerable in front or to show emotions, and that takes a lot of trust.

We want our people to feel as confident to say ‘NO’, as they would feel saying a ‘YES’. We’re not afraid to make mistakes. We’re famously anal about learning from those mistakes. This is part of trusting them.

Dear HR peeps, please don’t kill the human side of the job. Rather, deal with the ‘people’ side of things to make your job, and the company, better. You have plenty of time to go back to those 2 Ps (Policies, Processes) later. This also means that you need to openly show your human side, too. It’s unfortunate that the strong conditioning of the HR industry has always asked us to portray a ‘rock-solid HR’ figure. Spend time thinking about how comfortable you feel about owning your emotions, and creating a safe space for others to do so, too.

4. Understanding differences. Finding common grounds.

We let our people bring their whole selves to work. We don’t expect anyone to be under any pressure to outperform the other person. We understand that each one of us is different. Yes, we expect them to be the best version of themselves, and give their best, while respecting their innate differences.

As a startup, velocity is extremely important for us. So is listening to everyone at the table and finding what works best for an individual, the team, and the company at large. In that order. You cannot dream of the best ideas without critique. Everyone loves doers. We love and respect naysayers as well, and trust them to be our conscience keepers.

A word of caution here. Differences and diversity are beautiful, only when practiced with intent. Dear HR people, please don’t overuse the word diversity and inclusion at the drop of your hat. ‘Inclusion’ is really not for everyone. You need to be bold to allow for it. Be honest if you want similar people. That’s OK too. Be honest if you want people to say ‘yes’ all the time. But if you really want your people to say ‘NO’, then bloody well coach yourself and your leaders to listen to the ‘NO’, embrace the diverse thoughts, encourage it. I’m not championing ‘Inclusion’ for the sake of it. I’m fiercely advocating it for the merit of it – for any business and its people.

Diversity and Inclusion

5. Putting the team above individual egos.

At HackerEarth, we pride ourselves on being the stone that cuts brilliant individuals, but it cannot stop there. They need to contribute to creating brilliant teams. We do not tolerate cut-throat behavior between individuals, ever.

Putting the team above individual egos also means allowing for and respecting divergence. Our people challenge us, all the time. And we absolutely adore the fact! We strongly believe in Team > Me and do not compromise on it, at any cost.

Dear HR people, creating a brilliant or high-performing team does not mean individuals need to be in constant competition. It means supporting them in becoming the best version of themselves. Don’t create stress in the guise of gunning for performance.

Coach your leaders to intuitively understand strengths and weaknesses. Not everyone performs at the same level.

Some parting advice from Anti-AssholeVille.

I have always believed that the role of an HR professional is to be the sole custodian of a company’s culture. In the span of my career, I have seen the conversation around work culture morph from ‘what time does an employee punch in’ to ‘what can we do to make our employees happier?’. Topics of diversity, equality, and the creation of a fair and hospitable workplace are our water-cooler gossip now.

To me, it all stems from respecting the Other. In literature and philosophy, the ‘Other’ is anyone who is not you or doesn’t follow the norms laid down by you. ‘Otherization’ is an actual verb, and something I see happening in many HR teams. We are trained to believe a good employee is one who is always hungry, acing their projects; a rabbit on a constant dopamine hunt.

For instance, when someone says “what do I need to do if I need to stay in the same job role and level for the next 3 years?”, our first instinct is to brand them as ‘unambitious’. That’s Otherization. And that’s being an Asshole.

In situations like this, I remind myself to approach with respect. The person in front of me may not have the same life goals as I do, or as I was taught that all employees should have, but it is a goal they believe in personally and I do not have the right to judge. Instead of stereotyping, I remind myself that their statement only means that this is what they want NOW. My role: to facilitate this NOW, so that I can retain a hard-working teammate for the future.

It’s NOT OK to judge, or draw people into boxes, or pitch them against each other. Or otherize them in any manner. This is where we as HR professionals need to be aware of our unconscious biases, and the assholes we can be if we let age-old dictums govern the way we create our workplaces.

So, take charge. Be open to learn and unlearn. Lead with respect so that you can create a more fair, equitable, honest, and pleasant workplace.

And never, ever, be an Asshole.

Subscribe to The HackerEarth Blog

Get expert tips, hacks, and how-tos from the world of tech recruiting to stay on top of your hiring!

Author
Swetha Harikrishnan
Calendar Icon
December 9, 2020
Timer Icon
3 min read
Share

Hire top tech talent with our recruitment platform

Access Free Demo
Related reads

Discover more articles

Gain insights to optimize your developer recruitment process.

The Mobile Dev Hiring Landscape Just Changed

Revolutionizing Mobile Talent Hiring: The HackerEarth Advantage

The demand for mobile applications is exploding, but finding and verifying developers with proven, real-world skills is more difficult than ever. Traditional assessment methods often fall short, failing to replicate the complexities of modern mobile development.

Introducing a New Era in Mobile Assessment

At HackerEarth, we're closing this critical gap with two groundbreaking features, seamlessly integrated into our Full Stack IDE:

Article content

Now, assess mobile developers in their true native environment. Our enhanced Full Stack questions now offer full support for both Java and Kotlin, the core languages powering the Android ecosystem. This allows you to evaluate candidates on authentic, real-world app development skills, moving beyond theoretical knowledge to practical application.

Article content

Say goodbye to setup drama and tool-switching. Candidates can now build, test, and debug Android and React Native applications directly within the browser-based IDE. This seamless, in-browser experience provides a true-to-life evaluation, saving valuable time for both candidates and your hiring team.

Assess the Skills That Truly Matter

With native Android support, your assessments can now delve into a candidate's ability to write clean, efficient, and functional code in the languages professional developers use daily. Kotlin's rapid adoption makes proficiency in it a key indicator of a forward-thinking candidate ready for modern mobile development.

Breakup of Mobile development skills ~95% of mobile app dev happens through Java and Kotlin
This chart illustrates the importance of assessing proficiency in both modern (Kotlin) and established (Java) codebases.

Streamlining Your Assessment Workflow

The integrated mobile emulator fundamentally transforms the assessment process. By eliminating the friction of fragmented toolchains and complex local setups, we enable a faster, more effective evaluation and a superior candidate experience.

Old Fragmented Way vs. The New, Integrated Way
Visualize the stark difference: Our streamlined workflow removes technical hurdles, allowing candidates to focus purely on demonstrating their coding and problem-solving abilities.

Quantifiable Impact on Hiring Success

A seamless and authentic assessment environment isn't just a convenience, it's a powerful catalyst for efficiency and better hiring outcomes. By removing technical barriers, candidates can focus entirely on demonstrating their skills, leading to faster submissions and higher-quality signals for your recruiters and hiring managers.

A Better Experience for Everyone

Our new features are meticulously designed to benefit the entire hiring ecosystem:

For Recruiters & Hiring Managers:

  • Accurately assess real-world development skills.
  • Gain deeper insights into candidate proficiency.
  • Hire with greater confidence and speed.
  • Reduce candidate drop-off from technical friction.

For Candidates:

  • Enjoy a seamless, efficient assessment experience.
  • No need to switch between different tools or manage complex setups.
  • Focus purely on showcasing skills, not environment configurations.
  • Work in a powerful, professional-grade IDE.

Unlock a New Era of Mobile Talent Assessment

Stop guessing and start hiring the best mobile developers with confidence. Explore how HackerEarth can transform your tech recruiting.

Vibe Coding: Shaping the Future of Software

A New Era of Code

Vibe coding is a new method of using natural language prompts and AI tools to generate code. I have seen firsthand that this change makes software more accessible to everyone. In the past, being able to produce functional code was a strong advantage for developers. Today, when code is produced quickly through AI, the true value lies in designing, refining, and optimizing systems. Our role now goes beyond writing code; we must also ensure that our systems remain efficient and reliable.

From Machine Language to Natural Language

I recall the early days when every line of code was written manually. We progressed from machine language to high-level programming, and now we are beginning to interact with our tools using natural language. This development does not only increase speed but also changes how we approach problem solving. Product managers can now create working demos in hours instead of weeks, and founders have a clearer way of pitching their ideas with functional prototypes. It is important for us to rethink our role as developers and focus on architecture and system design rather than simply on typing c

The Promise and the Pitfalls

I have experienced both sides of vibe coding. In cases where the goal was to build a quick prototype or a simple internal tool, AI-generated code provided impressive results. Teams have been able to test new ideas and validate concepts much faster. However, when it comes to more complex systems that require careful planning and attention to detail, the output from AI can be problematic. I have seen situations where AI produces large volumes of code that become difficult to manage without significant human intervention.

AI-powered coding tools like GitHub Copilot and AWS’s Q Developer have demonstrated significant productivity gains. For instance, at the National Australia Bank, it’s reported that half of the production code is generated by Q Developer, allowing developers to focus on higher-level problem-solving . Similarly, platforms like Lovable enable non-coders to build viable tech businesses using natural language prompts, contributing to a shift where AI-generated code reduces the need for large engineering teams. However, there are challenges. AI-generated code can sometimes be verbose or lack the architectural discipline required for complex systems. While AI can rapidly produce prototypes or simple utilities, building large-scale systems still necessitates experienced engineers to refine and optimize the code.​

The Economic Impact

The democratization of code generation is altering the economic landscape of software development. As AI tools become more prevalent, the value of average coding skills may diminish, potentially affecting salaries for entry-level positions. Conversely, developers who excel in system design, architecture, and optimization are likely to see increased demand and compensation.​
Seizing the Opportunity

Vibe coding is most beneficial in areas such as rapid prototyping and building simple applications or internal tools. It frees up valuable time that we can then invest in higher-level tasks such as system architecture, security, and user experience. When used in the right context, AI becomes a helpful partner that accelerates the development process without replacing the need for skilled engineers.

This is revolutionizing our craft, much like the shift from machine language to assembly to high-level languages did in the past. AI can churn out code at lightning speed, but remember, “Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” Use AI for rapid prototyping, but it’s your expertise that transforms raw output into robust, scalable software. By honing our skills in design and architecture, we ensure our work remains impactful and enduring. Let’s continue to learn, adapt, and build software that stands the test of time.​

Ready to streamline your recruitment process? Get a free demo to explore cutting-edge solutions and resources for your hiring needs.

Guide to Conducting Successful System Design Interviews in 2025

What is Systems Design?

Systems Design is an all encompassing term which encapsulates both frontend and backend components harmonized to define the overall architecture of a product.

Designing robust and scalable systems requires a deep understanding of application, architecture and their underlying components like networks, data, interfaces and modules.

Systems Design, in its essence, is a blueprint of how software and applications should work to meet specific goals. The multi-dimensional nature of this discipline makes it open-ended – as there is no single one-size-fits-all solution to a system design problem.

What is a System Design Interview?

Conducting a System Design interview requires recruiters to take an unconventional approach and look beyond right or wrong answers. Recruiters should aim for evaluating a candidate’s ‘systemic thinking’ skills across three key aspects:

How they navigate technical complexity and navigate uncertainty
How they meet expectations of scale, security and speed
How they focus on the bigger picture without losing sight of details

This assessment of the end-to-end thought process and a holistic approach to problem-solving is what the interview should focus on.

What are some common topics for a System Design Interview

System design interview questions are free-form and exploratory in nature where there is no right or best answer to a specific problem statement. Here are some common questions:

How would you approach the design of a social media app or video app?

What are some ways to design a search engine or a ticketing system?

How would you design an API for a payment gateway?

What are some trade-offs and constraints you will consider while designing systems?

What is your rationale for taking a particular approach to problem solving?

Usually, interviewers base the questions depending on the organization, its goals, key competitors and a candidate’s experience level.

For senior roles, the questions tend to focus on assessing the computational thinking, decision making and reasoning ability of a candidate. For entry level job interviews, the questions are designed to test the hard skills required for building a system architecture.

The Difference between a System Design Interview and a Coding Interview

If a coding interview is like a map that takes you from point A to Z – a systems design interview is like a compass which gives you a sense of the right direction.

Here are three key difference between the two:

Coding challenges follow a linear interviewing experience i.e. candidates are given a problem and interaction with recruiters is limited. System design interviews are more lateral and conversational, requiring active participation from interviewers.

Coding interviews or challenges focus on evaluating the technical acumen of a candidate whereas systems design interviews are oriented to assess problem solving and interpersonal skills.

Coding interviews are based on a right/wrong approach with ideal answers to problem statements while a systems design interview focuses on assessing the thought process and the ability to reason from first principles.

How to Conduct an Effective System Design Interview

One common mistake recruiters make is that they approach a system design interview with the expectations and preparation of a typical coding interview.
Here is a four step framework technical recruiters can follow to ensure a seamless and productive interview experience:

Step 1: Understand the subject at hand

  • Develop an understanding of basics of system design and architecture
  • Familiarize yourself with commonly asked systems design interview questions
  • Read about system design case studies for popular applications
  • Structure the questions and problems by increasing magnitude of difficulty

Step 2: Prepare for the interview

  • Plan the extent of the topics and scope of discussion in advance
  • Clearly define the evaluation criteria and communicate expectations
  • Quantify constraints, inputs, boundaries and assumptions
  • Establish the broader context and a detailed scope of the exercise

Step 3: Stay actively involved

  • Ask follow-up questions to challenge a solution
  • Probe candidates to gauge real-time logical reasoning skills
  • Make it a conversation and take notes of important pointers and outcomes
  • Guide candidates with hints and suggestions to steer them in the right direction

Step 4: Be a collaborator

  • Encourage candidates to explore and consider alternative solutions
  • Work with the candidate to drill the problem into smaller tasks
  • Provide context and supporting details to help candidates stay on track
  • Ask follow-up questions to learn about the candidate’s experience

Technical recruiters and hiring managers should aim for providing an environment of positive reinforcement, actionable feedback and encouragement to candidates.

Evaluation Rubric for Candidates

Facilitate Successful System Design Interview Experiences with FaceCode

FaceCode, HackerEarth’s intuitive and secure platform, empowers recruiters to conduct system design interviews in a live coding environment with HD video chat.

FaceCode comes with an interactive diagram board which makes it easier for interviewers to assess the design thinking skills and conduct communication assessments using a built-in library of diagram based questions.

With FaceCode, you can combine your feedback points with AI-powered insights to generate accurate, data-driven assessment reports in a breeze. Plus, you can access interview recordings and transcripts anytime to recall and trace back the interview experience.

Learn how FaceCode can help you conduct system design interviews and boost your hiring efficiency.

Top Products

Explore HackerEarth’s top products for Hiring & Innovation

Discover powerful tools designed to streamline hiring, assess talent efficiently, and run seamless hackathons. Explore HackerEarth’s top products that help businesses innovate and grow.
Frame
Hackathons
Engage global developers through innovation
Arrow
Frame 2
Assessments
AI-driven advanced coding assessments
Arrow
Frame 3
FaceCode
Real-time code editor for effective coding interviews
Arrow
Frame 4
L & D
Tailored learning paths for continuous assessments
Arrow
Get A Free Demo