Navigating the world of HR analytics can feel like stepping into a maze without a map. Sifting through mountains of raw employee data, trying to see patterns, predict turnovers, or even just understand how long your employees stick around. Not just daunting. But overwhelming at times.
The sheer weight makes you question if HR analytics is even worth the effort. But it can be different. An organized, systematic approach to HR analytics where employee tenure analysis becomes a breeze. That's right. With just a touch of Python magic, you can turn the tide.
Dive into this guide, and I'll walk you through the transformative world of HR analytics, one step at a time. By the end, you'll have the tools and knowledge to confidently tackle any HR analytics challenge that comes your way. βFollow along using my Google Colab notebook (free)β βStruggling with something else? Let me know!β Step 1: Install Required Libraries and Preview the DatasetFirst, we load the dataset from a URL using pandas and display the first few rows
Step 2: Data Cleansing: Remove Specific RecordsNext, filter out rows from the dataset where the department is labeled as 'Human Resources'. This is just an example to show how filtering works with Pandas.
Step 3: Date Parsing with Timezone ConversionConverting 'hire_date' and 'termdate' columns into datetime format with UTC timezone and handling potential invalid dates. This is an important skill to learn because often times dates and time stamps are poorly formatted when working with data.
Step 4: Combine Location Data and Remove RedundanciesHere, we create a unified 'location' column by merging 'location_city' and 'location_state' columns and then drop the originals to streamline the dataframe. This can be useful when combining any columns. For example, combining first name and last name into a full name field. Or combining business unit and sub-business unit. Very handy!
Step 5: Calculate Employee Tenure in DaysNext, let's calculate the tenure of employees in terms of days. If an employee has a termination date (termdate), the tenure is the difference between the hire_date and termdate. Otherwise, it's the difference between the hire_date and the current date.
Step 6: Categorize Employee TenureThis code segments employees based on their tenure, classifying them as 'New', 'Mid-level', or 'Experienced'. Notice how we use a Python function here. First, we create the categorize_tenure function with one parameter (the number of days that each employee has been employed). Then we call that function while creating a new field in the data frame.
Step 7: Visualization of Employee Tenure DistributionFor the final step, let's take a look at everything we've done to turn raw data into a useful analysis. This code visualizes the distribution of employees across the 'New', 'Mid-level', and 'Experienced' tenure categories using a histogram.
And here's the final result: Great job! The idea for this newsletter came directly from a reader β just like you! βTake 3 minutes to let me know what you want help with next.β Until next time, keep exploring and happy analyzing! Brian Whenever you're ready, here's how I can help you:
|
You are receiving this because you signed up for Starting with Data, purchased one of my data analytics products, or enrolled in one of my data analytics courses. Unsubscribe at any time using the link below. 600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246 |
Learn to build analytics projects with SQL, Tableau, Excel, and Python. For data analysts looking to level up their career and complete beginners looking to get started. No fluff. No theory. Just step-by-step tutorials anyone can follow.
Hello Reader, Here's a scenario that happens more often than anyone admits: You build a report. Your director uses it in a board presentation. A week later, someone notices the customer count includes 58 records with obviously fake email addresses like evan.clarke743@noemail. The report wasn't wrong. The data underneath it was dirty. And now your credibility takes a hit. Bummer. Not because of your SQL skills, but because you didn't check the final product before sending it off. Data quality...
Hey Reader, Last month, we covered LEFT JOIN to find customers who never booked. That's one type of absence β people who never showed up. But there's another kind that's even more expensive: people who showed up, committed, and then left. The dreaded cancellation. Customers who said "yes", then said "actually, never mind". In the Summit Adventures database (the fake adventure tourism company I created to help people learn business analytics), nearly 47% of all bookings end in cancellation....
Hello Reader, This week's newsletter is a bit different. There's SQL in here, but the real topic is career strategy. Because one of the most common questions I get from readers is some version of: "I've been learning SQL for a few months. How do I prove I can actually do this job?" The honest answer: a portfolio of 2-3 projects that demonstrate business thinking, not just technical syntax. The problem is most portfolios I've reviewed look the same. A Kaggle competition. A tutorial from...