Pay: $59 - $65/hr DOE
Location: Bothell, WA
Submit to Rebecca Hicks (contact info on the email below)
Candidates will start with phone interview with Rebecca then a second round with the PM Manager.
Duration: 1 year
Here is some additional info that Rebecca provided. This is for internal use only:
Regarding the problem statements, I was thinking you could ask questions like this:
My expected answer is that the person would say they would study the SOW for a day or two, discuss with the program team high level milestones and objectives, start outlining the program schedule with the PE, Cert Manager, SCM and Production.
In this case it will be important for me that they say they the sequence of design, engineering, planning, procurement, testing / qualification, production, and installation. It will also be important that they say they would be working with engineering or project engineering, certification, and rest of the team to determine the schedule and would lead the discussions. I also expect them to say that they’d be setting up the program administratively ensuring each department understand their deliverables, their budget and schedule.
My expected answer is that they would describe how they assess if something is in or out of scope. In this case I am looking for them to determine on a technical basis why something is out of scope and how they can justify it to the customer.
Following the determination, they need to work with relevant teams to collect the hours impact, schedule impact, impact to weights or aircraft, etc. then negotiate the change with the customer explaining and defending why the change is out of scope.
My expected answer here, and what usually a person will say, is that they like to communicate with the team, establish relationships, create trust within the team, etc.
I am also looking for them to say that they are a leader, are a mentor to others, humble about the feedback they receive, work as a team, use lessons learned and look for continuous improvement. Let them give you a detailed example of any of these items and see what they choose.
Some other questions to ask are:
My expected answer is that the person lists an action item register, risk register, program schedule, and change log at the minimum.
My expected answer is that the person would work with other departments to forecast potential risks in engineering, certification, and it’s important that they mention the test phase of the program here too (flam, structural, qual testing risks, etc.)
Location: Bothell, WA
Submit to Rebecca Hicks (contact info on the email below)
Candidates will start with phone interview with Rebecca then a second round with the PM Manager.
Duration: 1 year
- They are open to candidates converting, but it’s not required
- Rebecca said they won a huge 7 yr contract which will bring a lot of work (and is not public knowledge yet) so they will be needing more PMs in the near future.
- Rebecca will provide quick feedback and is good with us running resumes by her before we even contact them. She doesn’t want us to waste time.
- Want candidates with aviation Interior PM experience
- Companies to look for would be Zodiac Aerospace and Jamco Aerospace
Here is some additional info that Rebecca provided. This is for internal use only:
Regarding the problem statements, I was thinking you could ask questions like this:
- The expectation of a Sr. PM and Program Director is that they can run the program independently. Tell us what you expect you will do when you first join GTI and we hand you a Statement of work for a new program.
My expected answer is that the person would say they would study the SOW for a day or two, discuss with the program team high level milestones and objectives, start outlining the program schedule with the PE, Cert Manager, SCM and Production.
In this case it will be important for me that they say they the sequence of design, engineering, planning, procurement, testing / qualification, production, and installation. It will also be important that they say they would be working with engineering or project engineering, certification, and rest of the team to determine the schedule and would lead the discussions. I also expect them to say that they’d be setting up the program administratively ensuring each department understand their deliverables, their budget and schedule.
- Can you describe the approach you follow when a customer makes a request that may or may not be in the statement of work.
My expected answer is that they would describe how they assess if something is in or out of scope. In this case I am looking for them to determine on a technical basis why something is out of scope and how they can justify it to the customer.
Following the determination, they need to work with relevant teams to collect the hours impact, schedule impact, impact to weights or aircraft, etc. then negotiate the change with the customer explaining and defending why the change is out of scope.
- Ask the person about their leadership skills at the program level and individuals.
My expected answer here, and what usually a person will say, is that they like to communicate with the team, establish relationships, create trust within the team, etc.
I am also looking for them to say that they are a leader, are a mentor to others, humble about the feedback they receive, work as a team, use lessons learned and look for continuous improvement. Let them give you a detailed example of any of these items and see what they choose.
Some other questions to ask are:
- As a Sr. PM or Program Director at GTI, tell me what type of daily Program Management tools you intend to use to manage the program.
My expected answer is that the person lists an action item register, risk register, program schedule, and change log at the minimum.
- Ask the person about the risk register – how do they determine risks to their program?
My expected answer is that the person would work with other departments to forecast potential risks in engineering, certification, and it’s important that they mention the test phase of the program here too (flam, structural, qual testing risks, etc.)