Skip to content

Baylex/Pewlett_Hackard_Analysis

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 

Repository files navigation

Pewlett_Hackard_Analysis

Employee Database with SQL

Purpose:

  1. Design an ERD that will apply to the data.
  2. Create and use a SQL database.
  3. Import and export large CSV datasets into pgAdmin.
  4. Practice using different joins to create new tables in pgAdmin.
  5. Write basic- to intermediate-level SQL statements.

Overview:

After reviewing the employee files for Pewlett Hackard, an entity relationship diagram was created using quick database diagrams to gather and organize the key elements from various data tables. The data was imported using postgres and the pgAdmin interface. SQL queries were written to create data tables by joining primary keys from different data sets together and establishing foreign keys. The leadership is concerned about a "silver tsunami," where there is a mass exodus of retiring employees creating a massive amount of job vacancies. SQL queries were created to generate a list of retiring employees by title and a list of employees eligible for mentorship.

Employee database relationship diagram for Pewlett Hackard: Pic 1

Results:

  1. With the first review of creating a list of potential "silver tsunamis," the query resulted in many duplicates due having multiple positions. Pic 2

  2. Using the 'distinct on' SQL script, the duplicates were removed leaving the most recent job title to create a unique list of retiring employees.

Pic 3

  1. Retiring Counts by Title for a total of 90,398 potential retirees.
    Pic 4

  2. Mentor Eligibility List of 1549 employees born in 1965. Pic 5

Summary:

1. How many roles will need to be filled as the "silver tsunami" begins to make an impact?

The "silver tsunami" will have a significant impact of leaving 90,398 vacancies.

2. Are there enough qualified, retirement-ready employees in the departments to mentor the next generation of Pewlett Hackard employees?

Using the criteria of those born in 1965, the potential mentee list is 1,549 employees. The gap between approximately 90,000 mentors and 1,500 mentees is significant.

Future Area of Focus:

Creating a new query to further investigate the gap, the two charts below compare the counts by titles of the retiring and mentor eligible employees. There is a reasonable ratio of titles between the two tables implying that matching mentor to mentee is scalable under the right criteria. However, it is concerning that no managers met the mentor eligibility requirement. Further discussion is need to fill the manager gap.
Pic 6 Pic 7

To move forward with the approximately 1,500 potential mentee list as a pilot mentoring program, the list of more than 90,000 retiring employees was narrowed to close the gap of matching mentor to mentee. The potential mentor list was narrowed by setting the criteria for being around age 35 when they started their current job title resulting in 5,521 employees that could be matched with the 1,549 mentees, which significantly narrows the mentor-mentee gap.

Pic 7 Pic 8

Lessons from creating a mentoring pilot program with the 1,549 mentees can be studied and then expanded to more potential mentees when a new list is generated by expanding the date criteria.

About

Employee Database with SQL

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages