Home
/
Blog
/
Developer Insights
/
Exclusive SQL Tutorial on Data Analysis in R

Exclusive SQL Tutorial on Data Analysis in R

Author
Manish Saraswat
Calendar Icon
December 28, 2016
Timer Icon
3 min read
Share

Explore this post with:

Introduction

Many people are pursuing data science as a career (to become a data scientist) choice these days. With the recent data deluge, companies are voraciously headhunting people who can handle, understand, analyze, and model data.

Be it college graduates or experienced professionals, everyone is busy searching for the best courses or training material to become a data scientist. Some of them even manage to learn Python or R, but still can't land their first analytics job!

What most people fail to understand is that the data science/analytics industry isn't just limited to using Python or R. There are several other coding languages which companies use to run their businesses.

Among all, the most important and widely used language is SQL (Structured Query Language). You must learn it.

I've realized that, as a newbie, learning SQL is somewhat difficult at home. After all, setting up a server enabled database engine isn't everybody's cup of tea. Isn't it? Don't you worry.

In this article, we'll learn all about SQL and how to write its queries.

Note: This article is meant to help R users who wants to learn SQL from scratch. Even if you are new to R, you can still check out this tutorial as the ultimate motive is to learn SQL here.

Table of Contents

  1. Why learn SQL ?
  2. What is SQL?
  3. Getting Started with SQL
    • Data Selection
    • Data Manipulation
    • Strings & Dates
  4. Practising SQL in R
Machine learning challenge, ML challenge

Why learn SQL ?

Good question! When I started learning SQL, I asked this question too. Though, I had no one to answer me. So, I decided to find it out myself.

SQL is the de facto standard programming language used to handle relational databases.

Let's look at the dominance / popularity of SQL in worldwide analytics / data science industry. According to an online survey conducted by Oreilly Media in 2016, it was found that among all the programming languages, SQL was used by 70% of the respondents followed by R and Python. It was also discovered that people who know Excel (Spreadsheet) tend to get significant salary boost once they learn SQL.

Also, according to a survey done by datasciencecentral, it was inferred that R users tend to get a nice salary boost once they learn SQL. In a way, SQL as a language is meant to complement your current set of skills.

Since 1970, SQL has remained an integral part of popular databases such as Oracle, IBM DB2, Microsoft SQL Server, MySQL, etc. Not only learning SQL with R will increase your employability, but SQL itself can make way for you in database management roles.

What is SQL ?

SQL (Structured Query Language) is a special purpose programming language used to manage, extract, and aggregate data stored in large relational database management systems.

In simple words, think of a large machine (rectangular shape) consisting of many, many boxes (again rectangles). Each box comprises a table (dataset). This is a database. A database is an organized collection of data. Now, this database understands only one language, i.e, SQL. No English, Japanese, or Spanish. Just SQL. Therefore, SQL is a language which interacts with the databases to retrieve data.

Following are some important features of SQL:

  1. It allows us to create, update, retrieve, and delete data from the database.
  2. It works with popular database programs such as Oracle, DB2, SQL Server, etc.
  3. As the databases store humongous amounts of data, SQL is widely known for it speed and efficiency.
  4. It is very simple and easy to learn.
  5. It is enabled with inbuilt string and date functions to execute data-time conversions.

Currently, businesses worldwide use both open source and proprietary relational database management systems (RDBMS) built around SQL.

Getting Started with SQL

Let's try to understand SQL commands now. Most of these commands are extremely easy to pick up as they are simple "English words." But make sure you get a proper understanding of their meanings and usage in SQL context. For your ease of understanding, I've categorized the SQL commands in three sections:

  1. Data Selection - These are SQL's indigenous commands used to retrieve tables from databases supported by logical statements.
  2. Data Manipulation - These commands would allow you to join and generate insights from data.
  3. Strings and Dates - These special commands would allow you to work diligently with dates and string variables.

Before we start, you must know that SQL functions recognize majorly four data types. These are:

  1. Integers - This datatype is assigned to variables storing whole numbers, no decimals. For example, 123,324,90,10,1, etc.
  2. Boolean - This datatype is assigned to variables storing TRUE or FALSE data.
  3. Numeric - This datatype is assigned to variables storing decimal numbers. Internally, it is stored as a double precision. It can store up to 15 -17 significant digits.
  4. Date/Time - This datatype is assigned to variables storing data-time information. Internally, it is stored as a time stamp.

That's all! If SQL finds a variable whose type is anything other than these four, it will throw read errors. For example, if a variable has numbers with a comma (like 432,), you'll get errors. SQL as a language is very particular about the sequence of commands given. If the sequence is not followed, it starts to throw errors. Don't worry I've defined the sequence below. Let's learn the commands. In the following section, we'll learn to use them with a data set.

Data Selection

  1. SELECT - It tells you which columns to select.
  2. FROM - It tells you columns to be selected should be from which table (dataset).
  3. LIMIT - By default, a command is executed on all rows in a table. This command limits the number of rows. Limiting the rows leads to faster execution of commands.
  4. WHERE - This command specifies a filter condition; i.e., the data retrieval has to be done based on some variable filtering.
  5. Comparison Operators - Everyone knows these operators as (=, !=, <, >, <=, >=). They are used in conjunction with the WHERE command.
  6. Logical Operators - The famous logical operators (AND, OR, NOT) are also used to specify multiple filtering conditions. Other operators include:
    • LIKE - It is used to extract similar values and not exact values.
    • IN - It is used to specify the list of values to extract or leave out from a variable.
    • BETWEEN - It activates a condition based on variable(s) in the table.
    • IS NULL - It allows you to extract data without missing values from the specified column.
  7. ORDER BY - It is used to order a variable in descending or ascending order.

Data Manipulation

  1. Aggregate Functions - These functions are helpful in generating quick insights from data sets.
    • COUNT - It counts the number of observations.
    • SUM - It calculates the sum of observations.
    • MIN/MAX - It calculates the min/max and the range of a numerical distribution.
    • AVG - It calculates the average (mean).
  2. GROUP BY - For categorical variables, it calculates the above stats based on their unique levels.
  3. HAVING - Mostly used for strings to specify a particular string or combination while retrieving data.
  4. DISTINCT - It returns the unique number of observations.
  5. CASE - It is used to create rules using if/else conditions.
  6. JOINS - Used to merge individual tables. It can implement:
    • INNER JOIN - Returns the common rows from A and B based on joining criteria.
    • OUTER JOIN - Returns the rows not common to A and B.
    • LEFT JOIN - Returns the rows in A but not in B.
    • RIGHT JOIN - Returns the rows in B but not in A.
    • FULL OUTER JOIN - Returns all rows from both tables, often with NULLs.
  7. ON - Used to specify a column for filtering while joining tables.
  8. UNION - Similar to rbind() in R. Combines two tables with identical variable names.

You can write complex join commands using comparison operators, WHERE, or ON to specify conditions.

sql joins data analysis data science

Strings and Dates

  1. NOW - Returns current time.
  2. LEFT - Returns a specified number of characters from the left in a string.
  3. RIGHT - Returns a specified number of characters from the right in a string.
  4. LENGTH - Returns the length of the string.
  5. TRIM - Removes characters from the beginning and end of the string.
  6. SUBSTR - Extracts part of a string with specified start and end positions.
  7. CONCAT - Combines strings.
  8. UPPER - Converts a string to uppercase.
  9. LOWER - Converts a string to lowercase.
  10. EXTRACT - Extracts date components such as day, month, year, etc.
  11. DATE_TRUNC - Rounds dates to the nearest unit of measurement.
  12. COALESCE - Imputes missing values.

These commands are not case sensitive, but consistency is important. SQL commands follow this standard sequence:

  1. SELECT
  2. FROM
  3. WHERE
  4. GROUP BY
  5. HAVING
  6. ORDER BY
  7. LIMIT

Practising SQL in R

For writing SQL queries, we'll use the sqldf package. It activates SQL in R using SQLite (default) and can be faster than base R for some manipulations. It also supports H2 Java database, PostgreSQL, and MySQL.

You can easily connect database servers using this package and query data. For more details, check the GitHub repo by its author.

When using SQL in R, think of R as the database machine. Load datasets using read.csv or read.csv.sql and start querying. Ready? Let’s begin! Code every line as you scroll. Practice builds confidence.

We'll use the babynames dataset. Install and load it with:

> install.packages("babynames")
> library(babynames)
> str(babynames)

This dataset contains 1.8 million observations and 5 variables. The prop variable is the proportion of a name given in a year. Now, load the sqldf package:

> install.packages("sqldf")
> library(sqldf)

Let’s check the number of rows in this data.

> sqldf("select count(*) from mydata")
#1825433

Ignore the warnings here. Next, let's look at the data — the first 10 rows:

> sqldf("select * from mydata limit 10")

* selects all columns. To select specific variables:

> sqldf("select year, sex, name from mydata limit 10")

To rename a column in the output using AS:

> sqldf("select year, sex as 'Gender' from mydata limit 10")

Filtering data with WHERE and logical conditions:

> sqldf("select year, name, sex as 'Gender' from mydata where sex == 'F' limit 20")
> sqldf("select * from mydata where prop > 0.05 limit 20")
> sqldf("select * from mydata where sex != 'F'")
> sqldf("select year, name, 4 * prop as 'final_prop' from mydata where prop <= 0.40 limit 10")

Ordering data:

> sqldf("select * from mydata order by year desc limit 20")
> sqldf("select * from mydata order by year desc, n desc limit 20")
> sqldf("select * from mydata order by name limit 20")

Filtering with string patterns:

> sqldf("select * from mydata where name like 'Ben%'")
> sqldf("select * from mydata where name like '%man' limit 30")
> sqldf("select * from mydata where name like '%man%'")
> sqldf("select * from mydata where name in ('Coleman','Benjamin','Bennie')")
> sqldf("select * from mydata where year between 2000 and 2014")

Multiple filters with logical operators:

> sqldf("select * from mydata where year >= 1980 and prop < 0.5")
> sqldf("select * from mydata where year >= 1980 and prop < 0.5 order by prop desc")
> sqldf("select * from mydata where name != '%man%' or year > 2000")
> sqldf("select * from mydata where prop > 0.07 and year not between 2000 and 2014")
> sqldf("select * from mydata where n > 10000 order by name desc")

Basic aggregation:

> sqldf("select sum(n) as 'Total_Count' from mydata")
> sqldf("select min(n), max(n) from mydata")
> sqldf("select year, avg(n) as 'Average' from mydata group by year order by Average desc")
> sqldf("select year, count(*) as count from mydata group by year limit 100")
> sqldf("select year, n, count(*) as 'my_count' from mydata where n > 10000 group by year order by my_count desc limit 100")

Using HAVING instead of WHERE for aggregations:

> sqldf("select year, name, sum(n) as 'my_sum' from mydata group by year having my_sum > 10000 order by my_sum desc limit 100")

Counting distinct names:

> sqldf("select count(distinct name) as 'count_names' from mydata")

Creating new columns using CASE (if/else logic):

> sqldf("select year, n, case when year = '2014' then 'Young' else 'Old' end as 'young_or_old' from mydata limit 10")
> sqldf("select *, case when name != '%man%' then 'Not_a_man' when name = 'Ban%' then 'Born_with_Ban' else 'Un_Ban_Man' end as 'Name_Fun' from mydata")

Joining data sets using a key:

> crash <- read.csv.sql("crashes.csv", sql = "select * from file")
> roads <- read.csv.sql("roads.csv", sql = "select * from file")
> sqldf("select * from crash join roads on crash.Road = roads.Road")
> sqldf("select crash.Year, crash.Volume, roads.* from crash left join roads on crash.Road = roads.Road")

Joining with aggregation and multiple keys:

> sqldf("select crash.Year, crash.Volume, roads.* from crash left join roads on crash.Road = roads.Road order by 1")
> sqldf("select crash.Year, crash.Volume, roads.* from crash left join roads on crash.Road = roads.Road where roads.Road != 'US-36' order by 1")
> sqldf("select Road, avg(roads.Length) as 'Avg_Length', avg(N_Crashes) as 'Avg_Crash' from roads join crash using (Road) group by Road")
> roads$Year <- crash$Year[1:5]
> sqldf("select crash.Year, crash.Volume, roads.* from crash left join roads on crash.Road = roads.Road and crash.Year = roads.Year order by 1")

String operations in sqldf with RSQLite extension:

> library(RSQLite)
> help("initExtension")

> sqldf("select name, leftstr(name, 3) as 'First_3' from mydata order by First_3 desc limit 100")
> sqldf("select name, reverse(name) as 'Rev_Name' from mydata limit 100")
> sqldf("select name, rightstr(name, 3) as 'Back_3' from mydata order by First_3 desc limit 100")

Summary

The aim of this article was to help you get started writing queries in SQL using a blend of practical and theoretical explanations. Beyond these queries, SQL also allows you to write subqueries aka nested queries to execute multiple commands in one go. We shall learn about those in future tutorials.

As I said above, learning SQL will not only give you a fatter paycheck but also allow you to seek job profiles other than that of a data scientist. As I always say, SQL is easy to learn but difficult to master. Do practice enough.

In this article, we learned the basics of SQL. We learned about data selection, aggregation, and string manipulation commands in SQL. In addition, we also looked at the industry trend of SQL language to infer if that's the programming language you will promise to learn in your new year resolution. So, will you?

If you get stuck with any query written above, do drop in your suggestions, questions, and feedback in comments below!

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
Manish Saraswat
Calendar Icon
December 28, 2016
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.

What AI Is Forcing HR to Rethink About Hiring

What AI is forcing HR to rethink

For recruiters and talent leaders, AI has made one thing clear: resumes can no longer be trusted as the primary signal of candidate capability. What AI is forcing HR to rethink is the entire screening stack — from how reqs are written, to how the ATS filters applicants, to how quality of hire (QoH) is measured against time-to-fill. According to LinkedIn's Future of Recruiting 2024 report, 73% of recruiters say skills-based hiring is a priority, yet most pipelines still screen on degree and employer brand at the ATS layer. That gap is where the rethink begins.

Why traditional resumes no longer predict strong hires

Resumes measure presentation more reliably than capability. Recruiters have long used job titles, company names, degrees, and years of experience as proxies for performance, but generative AI tools — ChatGPT, Teal, Rezi, and Kickresume among them — have collapsed the cost of producing a polished application. The World Economic Forum's Future of Jobs Report 2023 found that 44% of workers' core skills are expected to change by 2027, which means a resume snapshot ages faster than the role it describes.

For recruiters, the operational impact is direct: pipelines fill, screen rates rise, and yet QoH stays flat. As AI becomes more deeply embedded in hiring, HR leaders are being forced to rethink a single question:

What if resumes are no longer the best predictor of performance?

That question is reshaping recruitment faster than many organizations expected — though, as discussed later, the shift away from resumes carries its own trade-offs.

Share of Workers' Core Skills Expected to Change by 2027
Source: World Economic Forum Future of Jobs Report 2023

The resume was built for a different era

Modern work no longer fits the resume's static format. Skills evolve in months rather than years, roles overlap across functions, and professionals build expertise through online communities, freelance projects, bootcamps, and self-directed learning. According to SHRM's 2024 Talent Trends research, nearly half of HR leaders report that candidates from non-traditional backgrounds are increasingly competitive on assessments.

Resumes still reduce people to standardized timelines, and many capable candidates are filtered out by ATS rules simply because they lack the "right" employer logos. At the same time, candidates skilled in resume optimization can outperform genuinely capable professionals at the screen stage — a pattern that pre-dates AI but has been amplified by it.

It has become far easier for candidates to generate polished resumes, cover letters, and interview responses in minutes. For recruiters, the takeaway is practical: formatting and phrasing are no longer reliable proxies for capability.

AI did not break hiring — it exposed existing problems

AI did not create the resume problem; it surfaced one already present in most hiring funnels. Surveys of recruiters, including Gartner's 2024 HR research, have consistently shown three pre-AI pressures: recruiters overwhelmed by application volume, candidates optimizing resumes to pass ATS filters, and hiring managers reporting weak outcomes despite reviewing seemingly strong resumes.

AI accelerated these problems to a point where they can no longer be ignored. Many candidates can now generate a highly optimized application in seconds, and recruiters increasingly struggle to distinguish between candidates skilled at self-presentation and those who can actually do the work.

The operational shift is moving from:

"What does your resume say?"

Toward:

"Can you actually do the job?"

The rise of skills-based hiring

Skills-based hiring outperforms resume screening because it measures demonstrated capability rather than credential proximity. A growing number of organizations — including IBM, Accenture, and Delta, profiled in LinkedIn's Skills Path program — are moving toward skills-first models that prioritize practical assessments, simulations, project work, and role-specific problem-solving over employer brand or degree.

This trend is most visible in technology hiring, where coding assessments and real-world technical evaluations generally provide stronger signals than resumes alone, particularly when compared against resume-only screens for time-to-productivity. HackerEarth has run over 100 million developer assessments across enterprise hiring programs, and the consistent pattern in that dataset is that demonstrated coding performance correlates more closely with on-the-job output than degree or prior employer.

Beyond tech, a growing number of organizations are extending the model: marketing teams using campaign-brief exercises, sales teams using recorded customer-handling scenarios, and operations teams using situational judgment tests. For a deeper view of how this maps to specific roles, see our skills-based hiring guide and developer assessment platform.

Where skills-based hiring breaks down

Skills-based hiring is not without trade-offs, and recruiters evaluating it should plan for known failure modes:

  • Assessment bias. Poorly designed assessments can disadvantage career returners, caregivers, and candidates with limited test-taking time as severely as resume screens disadvantage non-traditional backgrounds.
  • Gaming of take-home tests. Unproctored coding or case exercises are increasingly solvable with generative AI, which means assessment design has to evolve in step with candidate tooling.
  • Candidate experience at scale. Long assessment batteries lower completion rates and damage employer brand, particularly for senior candidates who have multiple offers in play.
  • Legal exposure. In jurisdictions including New York City (Local Law 144) and under the EU AI Act, automated employment decision tools are subject to bias audits and disclosure requirements. Recruiters should confirm vendor compliance before deploying AI-driven scoring.

The honest read: most organizations announcing a "shift" to skills-based hiring still filter by degree at the ATS layer. The shift is real, but it is uneven.

Skills-Based Hiring Priority vs. ATS Screening Reality
Source: LinkedIn Future of Recruiting 2024; ATS screening figure illustrative based on article claims

Why HR leaders are rethinking potential

Potential is becoming more measurable in ways resumes never allowed. Traditional hiring often prioritized pedigree — familiar universities, recognizable employers, conventional career paths — but AI-powered assessment platforms (HackerEarth, HireVue, Pymetrics, Codility, and Workday Skills Cloud among them) score candidates on demonstrated performance against role-specific tasks, calibrated to a benchmark population.

These tools typically combine task-based evaluations, behavioral simulations, and structured scoring rubrics. Their limits matter too: they score what they are trained to score, they can encode bias from the training population, and they do not measure long-arc traits like cultural contribution or leadership trajectory. Recruiters should treat them as one signal in a structured interview loop, not a single decision point.

Research suggests that candidates without elite degrees frequently match or outperform credentialed peers on standardized technical assessments. In many cases, career switchers and self-taught professionals demonstrate strong adaptability and practical skill. Organizations that shift toward capability-based evaluation may gain access to broader and more diverse talent pools — though, as noted above, only if assessment design itself is audited for fairness.

The recruiter's role is changing

AI is not replacing recruiters; it is shifting where recruiters spend their time. Traditional recruitment rewarded screening volume and speed. Modern hiring increasingly rewards judgment, stakeholder alignment, and structured decision-making.

As automation handles sourcing, scheduling, resume parsing, and initial outreach, recruiters are spending more time on work AI cannot do well:

  • Probing candidate motivation through structured behavioral interviews
  • Evaluating adaptability against specific role demands using scorecards
  • Building hiring-manager alignment on the req and intake brief
  • Designing candidate-experience touchpoints that protect offer-accept rates
  • Calibrating assessment results against on-the-job performance data

The recruiter who succeeds in an AI-heavy pipeline is the one who can interpret signal, not the one who can scan resumes faster.

Candidates are changing faster than hiring systems

Modern career paths now move faster than most ATS configurations. Today's workforce values flexibility, creativity, continuous learning, and project-based growth, and many professionals build experience through freelance work, startups, creator platforms, and side projects. Their resumes often look unconventional, but unconventional no longer equates to unqualified.

Organizations that shift toward capability-based evaluation may access talent pools that rigid resume filters would otherwise miss. For practical guidance on adjusting screening criteria, see our guide to evaluating an ATS for skills-based hiring.

The future of hiring will feel more human

There is an irony in the AI shift: as resumes become easier to automate, organizations are being pushed to evaluate creativity, adaptability, collaboration, and real-world problem-solving more directly. The likely structure of mature AI-enabled hiring is AI handling repetitive tasks — sourcing, scheduling, parsing, initial scoring — while recruiters and hiring managers focus on nuance, context, and long-term fit.

FAQ

Is skills-based hiring more effective than resume screening? Skills-based hiring tends to predict on-the-job performance more reliably than resume screening for roles where the work can be assessed directly, such as engineering, data, sales, and marketing execution. According to LinkedIn's Future of Recruiting report, 73% of recruiters now prioritize skills-based approaches. Effectiveness depends heavily on assessment design and on whether downstream ATS filters still gate candidates by degree.

What HR processes is AI changing first? AI is changing sourcing, resume parsing, candidate matching, and initial assessment scoring first, because these are high-volume, rules-based tasks. Structured interviewing, offer negotiation, and onboarding remain primarily human-led, though AI-assisted note-taking and scorecard analysis are growing.

Will AI replace recruiters? AI is unlikely to replace recruiters, but it is changing the skill profile. Recruiters who can interpret assessment data, align hiring managers, and design candidate experience will be more valuable; recruiters whose role is primarily resume scanning are most exposed.

How do I evaluate an AI hiring tool for bias? Ask the vendor for a bias audit report (required under NYC Local Law 144 for automated employment decision tools), the demographic composition of the training data, the validation methodology against job performance, and the appeal process for candidates. Avoid tools that cannot answer all four.

Is resume-based hiring going away? Resume-based hiring is under pressure but not disappearing. Most organizations are moving toward hybrid models where resumes provide context and assessments provide the capability signal. A full move away from resumes is unlikely in the next hiring cycle for most enterprises.

What is the biggest risk of switching to skills-based hiring? The biggest risk is poorly designed assessments that introduce new forms of bias or damage candidate experience. A skills-based process built on a long, unproctored, untested assessment battery will perform worse than a structured resume screen.

Next steps: See it in action

If you are a recruiter or talent leader evaluating how to move from resume-led to skills-led screening, book a demo of HackerEarth Assessments to see how role-specific evaluations, proctoring, and benchmarked scoring fit into an existing ATS pipeline. For background reading, see our developer assessment platform overview and the HackerEarth recruiter blog.

Recruiters who pair structured assessment data with strong human judgment build better pipelines than either resumes or AI alone can produce.

Must-Know Recruitment Questions for HR and Talent Acquisition Teams (2026)

Recruitment questions every HR professional should know in 2025

Estimated read time: 7 minutes

Most "tell me about yourself" answers are now written by ChatGPT the night before the interview. That single shift — candidates arriving with rehearsed, AI-polished narratives — has broken the standard interview script and forced recruiters to redesign their question sets from the ground up. This guide outlines the categories of recruitment questions every HR professional should know in 2025, why each matters, and example questions you can adapt to your hiring rubric or scorecard today.

LinkedIn's 2024 Global Talent Trends report notes that skills-based hiring and behavioral assessment have moved from optional to expected in most talent acquisition workflows. Yet many hiring conversations still rely on outdated prompts that produce polished answers and unclear signals. The recruiter persona — the one running req intake, pipeline reviews, and screen calls — needs a tighter toolkit.

Who this is for: This article is written for recruiters and talent acquisition partners running structured interviews. Hiring managers building a scorecard alongside the recruiter will also find the question categories useful.

Adoption of Structured Hiring Practices Among HR Teams (2020–2025)
Source: LinkedIn Global Talent Trends claims cited in article

Why modern recruitment questions fail when they stay outdated

Industry observers at SHRM have noted that candidates are better prepared, interviews are more structured, and expectations on both sides have risen (SHRM research). With generative AI tools widely available, many candidates now enter screens with refined, rehearsed narratives.

The result is predictable — polished answers, unclear signals, and decisions made on incomplete understanding. The quality of the recruitment questions you bring into the room directly defines the quality of the signal you capture on the scorecard.

A contestable position worth stating plainly: behavioral interview frameworks like STAR are now overused to the point where candidates have memorized the structure, which reduces signal quality unless interviewers probe past the rehearsed answer with follow-ups.

What this article won't claim

Structured behavioral interviewing is not a silver bullet. Over-indexing on adaptability can screen out deep specialists whose value is stability and depth. Ownership-mindset framing, if applied rigidly, can disadvantage neurodivergent candidates or those from cultures where collective credit is the norm. Use the questions below as part of a balanced rubric — not as a single filter.

From "tell me about yourself" to understanding real intent

Traditional opening questions rarely reveal a candidate's intent or direction. A stronger opening probes why a candidate is moving at this specific point and what kind of work keeps them engaged beyond compensation.

Evidence from Gallup's 2023 State of the Global Workplace report suggests today's workforce is increasingly motivated by alignment, learning, and perceived growth — not stability alone. If this layer is missed early in the interview, the rest of the evaluation becomes less reliable.

Example intent and motivation questions

  • "Walk me through the last time you decided to leave a role. What specifically triggered the decision?"
  • "What kind of work has made you lose track of time in the last 12 months?"
  • "If this role didn't exist, what would your second-choice next move be — and why?"
  • "What would need to be true 18 months from now for you to consider this move a success?"

What to listen for

  • Specific triggers and trade-offs, not generic phrases like "growth" or "new challenges."
  • Consistency between the stated motivation and the candidate's actual career pattern.

Red flags

  • Answers that match the job description back to you almost verbatim.
  • Vague language about "culture" or "growth" with no concrete example.

Behavioral and competency-based recruitment questions: getting past scripted answers

One of the biggest challenges recruiters face today is not lack of talent, but over-prepared talent. Hiring practitioners increasingly find that well-structured, confident answers do not always reflect real capability, especially when responses are influenced by preparation tools or rehearsed narratives.

This is why competency-based questions — which explore decision-making logic, trade-offs, and real-time reasoning — produce higher signal than story-based prompts alone. For technical roles, pairing these with a practical assessment helps confirm what the interview surfaces. HackerEarth's skill assessments use role-specific question libraries and rubric-based scoring so the recruiter can compare candidate outputs against a defined standard, rather than relying on the candidate's own narrative of their capability.

Example behavioral and competency-based questions

  1. "Tell me about a decision you made in the last six months that you would make differently today. What changed your thinking?"
  2. "Describe a time you disagreed with your manager on a priority. How did you handle it?"
  3. "Walk me through a project where the scope changed mid-execution. What did you cut, and why?"
  4. "Give me an example of feedback you initially rejected but later acted on."

How to probe past the rehearsed answer

If a candidate delivers a clean STAR-format response, follow up with: "What's one detail you usually leave out of that story?" or "Who would tell that story differently?" These prompts disrupt the rehearsed structure and surface the actual reasoning.

Situational judgment and adaptability questions

Workplaces are shaped by continuous change — shifting priorities, evolving tools, and hybrid collaboration. Many hiring teams now treat adaptability as a core hiring parameter rather than a soft skill, particularly for roles where ambiguity is the default state.

Situational judgment questions present a realistic scenario and ask the candidate how they would navigate it. They are harder to rehearse than story-based prompts because the scenario is novel.

Example situational judgment questions

  • "You join the team and discover the project you were hired to lead has already slipped two months. What are your first three actions in week one?"
  • "Two stakeholders give you conflicting priorities on the same Friday. Both are senior to you. How do you handle it?"
  • "A teammate is consistently delivering work that is technically correct but late. You are not their manager. What do you do?"
  • "You realize halfway through a quarter that the metric you committed to is no longer the right one. How do you raise it?"
  • "Your top-performing team member tells you in a 1:1 they're considering leaving. They haven't told their manager. What do you do in the next 24 hours?"
  • "A vendor misses a critical deadline that puts your launch at risk. Walk me through how you decide whether to escalate, switch vendors, or absorb the delay."

What to listen for

  • Sequencing — do they ask clarifying questions before acting?
  • Trade-off awareness — do they acknowledge what they would not do?
  • Stakeholder reasoning — who do they involve, and when?

Culture and values-alignment questions

Cultural fit is often misunderstood as shared interests or personality alignment. A more useful frame is behavioral consistency with the team's working norms.

A second contestable position: generic "culture fit" questions should be retired in favor of values-alignment scenarios that name a specific behavior the company expects. "Culture fit" as a phrase invites bias; a scenario tied to a stated company value forces a more concrete answer.

Example values-alignment questions

  • "Our team gives feedback in writing before live discussion. Describe the last time you gave hard feedback. What did you write down first?"
  • "We prioritize shipping over perfection. Tell me about a time you shipped something you weren't fully proud of. What happened next?"
  • "Describe the last time you changed your mind because of data, not opinion."

For a deeper look at how culture signals show up in technical interviews, see our guide on how to design a structured technical interview.

Identifying ownership mindset over task execution

Task completion alone is no longer a strong hiring indicator for most knowledge roles. What recruiters and hiring managers increasingly screen for is the ownership mindset — how a candidate behaves when outcomes are unclear, accountability is shared, or success metrics evolve mid-execution.

A concrete scenario

Consider a Series B SaaS company hiring its first sales operations manager. The pipeline is messy, the CRM is half-implemented, and the founder is the de-facto rev-ops owner. Standard task-execution questions ("walk me through how you'd clean a pipeline") produce textbook answers. Ownership-mindset questions — "What would you stop doing in your first 30 days, and how would you tell the founder?" — surface whether the candidate can hold the seat. A strong answer names a specific thing they'd stop (e.g., "weekly pipeline reviews in their current form"), the trade-off they're willing to accept, and how they'd frame the conversation with the founder. A weak answer lists everything they'd add — new dashboards, new processes, new tooling — without naming a single thing they'd remove or a single conversation they'd own.

Example ownership questions

  • "Tell me about something you fixed that wasn't your job to fix."
  • "Describe a time the goalposts moved on you. What did you do in the first 48 hours?"
  • "What's a process you killed, and what replaced it?"

Red flags

  • Answers that always credit "the team" with no individual decision named.
  • Stories where the candidate is consistently the rescuer or always the victim.

Questions to avoid: legal and compliance boundaries

A structured question set is only as strong as its weakest prompt. In most jurisdictions, certain questions are either illegal or carry significant legal risk because they touch protected characteristics or regulated information.

Common categories to avoid in initial screens:

  • Age, date of birth, or graduation year as a proxy for age.
  • Marital status, family planning, or childcare arrangements ("Do you plan to have kids?" "Who watches your children?").
  • Citizenship or national origin beyond the legally permitted "Are you authorized to work in [country]?"
  • Religion, religious holidays, or observance schedules.
  • Disability or medical history, including questions about prior workers' compensation claims.
  • Salary history — now restricted or banned in many US states and several other jurisdictions. Ask about salary expectations instead.

For a deeper treatment of pre-employment screening practices and compliance, see our overview of pre-employment assessment design. Always confirm specifics with your legal or HR compliance partner — local law varies.

Rethinking what "good answers" actually mean

In traditional interviews, clarity and confidence were often equated with strong performance. Modern hiring increasingly challenges this assumption.

The signal you want is depth, consistency, and reasoning quality — even when responses are less polished. A candidate who says "I don't know, but here's how I'd find out" is often a stronger hire than one who delivers a fluent answer with no underlying logic.

To codify this on the scorecard, score reasoning and presentation as separate rubric lines. A candidate can score 4/5 on reasoning and 2/5 on presentation and still be a strong hire — but you will only see that if the rubric separates them.

FAQ: structured hiring questions

Which recruitment question category is most often skipped — and why does it matter?

In practice, ownership-mindset questions are the category recruiters most often skip, because they're the hardest to score consistently and the answers don't fit neatly into STAR. The cost of skipping them is high: ownership signal is what separates strong individual contributors from people who execute well only when the path is clear. If you only have time to add one new category to your interview guide, this is the one with the largest marginal lift.

What is the STAR method, and is it still useful?

STAR stands for Situation, Task, Action, Result. It is a candidate-response framework that helps structure answers to behavioral questions. It remains useful as a default structure, but because most candidates now prepare STAR-formatted stories, interviewers should probe past the rehearsed answer with follow-up questions about trade-offs, omitted details, and alternative perspectives.

How many interview question frameworks should a structured interview include?

Practitioners commonly recommend 5–8 core questions per 45-minute round, with planned follow-up probes. This is a rule of thumb rather than a sourced standard. Fewer questions with deeper probes typically produce more signal than many surface-level questions.

What is the difference between behavioral and situational judgment questions?

Behavioral questions ask about past actions ("Tell me about a time you…"). Situational judgment questions ask about hypothetical scenarios ("What would you do if…"). Behavioral questions test verified history; situational questions test reasoning on novel problems. Strong interview loops use both.

How do you reduce bias in recruitment questions?

Use a structured interview where every candidate is asked the same core questions, score answers on a defined rubric, and have at least two interviewers calibrate independently before discussing. Avoid "culture fit" as a freeform judgment; replace it with values-alignment scenarios tied to documented company behaviors.

Can skill assessments replace interview questions?

No. Assessments and interview questions answer different things. Assessments produce structured skill evaluation against a defined rubric; interview questions surface reasoning, motivation, and judgment. The strongest hiring loops pair both — skill assessments for verified capability, structured behavioral interviews for everything assessments can't measure.

Final thoughts and next steps

The recruitment questions every HR professional should know in 2025 are not a fixed list — they are a working toolkit you adapt to the role, the level, and the rubric. The categories above (intent, behavioral, situational, values-alignment, ownership) give you a structure; the example questions give you a starting point.

Next steps

  • Audit your current interview guide. Map every question to one of the five categories above. If a category is empty, add two questions.
  • Separate reasoning from presentation on your scorecard. Score them as distinct rubric lines.
  • Pair interviews with skill verification. Schedule a demo of HackerEarth Assessments to see how rubric-based skill scores integrate with your interview scorecard, so your hiring decision isn't relying on candidate self-report alone.

Sources referenced: LinkedIn Global Talent Trends, SHRM Research, Gallup State of the Global Workplace.

Why Empathy Could Be Your Biggest Hiring Advantage

Why Empathy Could Be Your Biggest Hiring Advantage

Why Human-Centered Hiring Matters More Than Ever

Hiring has never been more optimized than it is today.

From AI-powered recruitment tools to automated screening systems and structured interview workflows, HR and talent acquisition teams now have more ways than ever to improve hiring speed, consistency, and scalability.

But in the middle of this efficiency-driven approach, one critical element is slowly disappearing: employee empathy.

Empathy in hiring is not about slowing down recruitment or making decisions less objective. It is about ensuring candidates are treated like people navigating important career decisions, not just profiles moving through a hiring pipeline.

As recruitment becomes increasingly system-driven, preserving the human side of hiring is becoming both more difficult and more important.

For HR leaders and talent acquisition professionals, this is no longer just a workplace culture discussion. It directly impacts candidate experience, employer branding, hiring quality, and long-term employee retention.

When Hiring Feels Like a Process Instead of an Experience

Most modern recruitment systems are designed around efficiency.

Applications are filtered automatically, interviews are scheduled faster, and candidates move through hiring stages with minimal manual effort. Operationally, this creates speed and structure.

But from a candidate’s perspective, the experience can often feel distant and impersonal.

Many candidates go through multiple interview rounds without clear communication, feedback, or transparency about timelines and expectations. Even when the hiring process is fair, it may still feel mechanical.

This creates a growing challenge for HR and TA teams:

How do you maintain hiring efficiency without removing the human connection from recruitment?

That is where empathy becomes essential.

The Hidden Cost of Low-Empathy Hiring

The impact of low-empathy hiring is not always immediate, but it compounds over time.

Candidates remember how organizations made them feel during the recruitment process, especially during rejection or delayed communication. Those experiences shape employer perception long before someone becomes an employee.

Over time, this directly affects employer brand and candidate trust.

There is also another hidden cost.

When hiring becomes too rigid or overly process-driven, recruiters may overlook candidates with strong long-term potential simply because they do not perfectly match predefined criteria.

Without empathy, context disappears.

And when context disappears, opportunities are often missed.

For HR leaders, empathy is no longer just a soft skill. It is becoming a competitive hiring advantage.

Why Empathy Is Becoming a Competitive Hiring Skill

Today’s workforce is far more dynamic than it was a decade ago.

Professionals switch industries, build careers through unconventional paths, and learn skills outside traditional education systems. As a result, resumes and structured evaluations only tell part of the story.

Empathy helps recruiters understand what exists beyond the surface.

It allows hiring teams to better understand:

  • Career transitions
  • Employment gaps
  • Nontraditional experience
  • Personal growth journeys

This shift changes the entire hiring mindset.

Instead of asking:

“Does this candidate perfectly match the role?”

Recruiters are increasingly asking:

“What could this candidate become in the right environment?”

That perspective creates stronger and more future-focused hiring decisions.

Where Empathy Fits in Modern Recruitment

Empathy does not replace structured hiring systems.

In fact, it becomes most effective when built into them.

Simple improvements in communication can significantly improve candidate experience. Clear updates, transparent timelines, respectful rejection emails, and honest feedback all contribute to a more human-centered recruitment process.

These small changes often have a lasting impact on how candidates perceive an organization.

For HR teams, the goal is not to remove structure from hiring.

The goal is to ensure structure does not remove humanity.

Better Hiring Decisions Start With Better Human Understanding

Empathy also improves the quality of hiring decisions themselves.

When recruiters take time to understand a candidate’s context, they often uncover strengths that are not immediately visible on resumes or scorecards.

A candidate who appears average on paper may demonstrate exceptional adaptability, resilience, or problem-solving ability in real-world situations.

Without empathy, those signals are easy to miss.

For talent acquisition leaders, this means recognizing that hiring is not just about selecting the strongest profile.

It is about identifying the strongest long-term fit within a real human context.

Final Thoughts

As recruitment continues evolving through automation, AI hiring tools, and structured decision-making, the biggest risk is not losing efficiency.

It is losing humanity.

Employee empathy ensures hiring remains people-focused, even as processes become more technology-driven.

It does not slow recruitment down. Instead, it helps organizations create better candidate experiences, stronger employer brands, and more thoughtful hiring decisions.

Because candidates may forget interview questions or assessment scores.

But they will always remember how they were treated during the hiring process.

And in today’s competitive talent market, that experience often determines whether top talent chooses to join or walk away.

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