Giter Site home page Giter Site logo

a-memme / pewlett-hackard-analysis Goto Github PK

View Code? Open in Web Editor NEW
0.0 1.0 0.0 19.19 MB

Leveraging postgreSQL to organize data and determine which employees from a large company's database are up for, or close to, retirement based on their age and tenure.

sql postgresql relational-databases querying

pewlett-hackard-analysis's Introduction

Pewlett-Hackard-Analysis

Purpose

Using PostgreSQL to determine the number of employees in Pewlett Hackard who are either up for, or close to, retirement. These tools were then used to determine how many senior employees there are in the company who are eligible to participate in an employee mentorship program to help train future employees. Insights are provided as to whether there are sufficient candidates for this program to help support the upcoming "silver tsnuami" retirement wave.

Results

Results revealed that:

  • There are a total of 90,398 employees ready to retire at Pewlett Hackard (see first image below)
  • 44,397 or ~50% of those employees, as of most recently, are in engineering positions - 29,414 as senior engineers, 14,222 as regular engineers, and 1,761 as assistant engineers. (see second image below or reference Data folder/retiring_titles.csv)
  • An extremely small portion of employees ready for retire are in management positions - a total of 2 employees (see below).
  • There are 1,549 employees eligible to participate in the mentorship program to help train upcoming employees following a large retirement wave (see last image below).

total_retiring

retiring_titles

mentorship

Reference Employee_Database_challenge.sql in the Queries folder for all code used to provide the above analysis/tables

Summary

Roles to Fill

Given the above information, there will be a total of 90,398 roles to fill in the given years ahead, assuming that all employees ready to retire will, indeed, retire.

Further analysis, however, could provide more in-depth insight as to how many roles and which roles by department will need to be filled at different given times. In the table below, employees ready to retire were categorized by the year they were born. Not all employees will retire at the same exact time, and knowing how many employees at what ages are ready, can provide one with greater information on how many individuals will be retiring through each wave, given an assumption that those who are older may be more likely to retire sooner (see image below or reference the extras folder/birthdate_counts.csv).

groupby_birthyear

Reference extra_queries.sql in Extras folder for all code used to create tables regarding further analysis

The table above shows that employees ready to retire are distributed fairly equally across the four ages. As each year roughly contains 20,000 or so employees ready to retire, one can use this number as a baseline to try and predict how large these retirement waves will be. Although there is definitely no guarantee that employees will retire in chronological order according to their age, this information provides one with some form of insight for future preparation, rooted in solidifed data.

To further the depth of this analysis, four seperate tables were created for each birth year, and sorted by specific department/title of each employee. (See tables below or reference extras folder/fiftytwo.csv, fiftythree.csv, fiftyfour.csv, and fiftyfive.csv)

fiftytwo

fiftythree

fiftyfour

fiftyfive

From these tables one can see that:

  • Engineers of all types (predictably) make up roughly 50% of each group (quite similarily to the overall numbers)
    • 10,670 or ~50% ready to retire in the 1952 group
    • 11,353 or ~49% ready to retire in the 1953 group
    • 11,641 or ~50% ready to retire in the 1954 group
    • 11,733 or ~51% ready to retire in the 1955 group
  • General staff positions (staff/senior staff) make up the second largest portion of each group and are generally equally proportioned across ages
    • 9,475 or ~45% ready to retire in the 1952 group
    • 10,331 or ~45% ready to retire in the 1953 group
    • 10,430 or ~45% ready to retire in the 1954 group
    • 10,260 or ~44% ready to retire in the 1955 group

The generally even distribution of department types across age groups, once again, makes future preparation somewhat easier here when looking to determine what roles will need to be filled and when.

Support from Mentorship

From the above information, one can make the assumption to prepare for retirement waves occuring in chunks of 20,000 or so employees. Based on the extended analysis, somewhere around 50% of each retirement wave will consist of engineering positions to fill, followed by general staff positions.

Given that there are 1,549 employees eligible to participate in the program, the company is looking at one mentorship trainer for every 12-13 or so new employees. This is given the assumption that the participation rate from employees eligible for the mentorship program is 100%, and that cycling through groups of new employees as the senior employees retire can happen somewhat seamlessly without much overlap. If one considers a 50% participation rate, there is roughly 1 mentorship trainer for every 25-26 or so new employees. The acceptable ratio of mentor to new employee will be influenced by a number of factors (i.e department, trainer, etc) however, unless the mentorship is mandatory, it may be advisable to look at increasing the number of eligible employees for the program given the unknown nature of participation.

In addtion, further analysis regarding the mentorship program was also conducted here, grouping individuals eligible for the program into departments/titles once again to compare to that of the ready-to-retire groups (See table below or reference extras folder/mentorship_titles.csv)

mentorship_titles

The data here reveals that the proprotions of mentorship employees in specific departments matches that of the ready-to-retire age groups, as well as the overall numbers of employees ready to retire in different positions. This consistent nature provides confidence that there will be sufficient employees in each department to participate in the mentorship program once the silver tsunami begins to take its toll, given the current total numbers.

pewlett-hackard-analysis's People

Contributors

a-memme avatar

Watchers

 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.