Senior Staff Project Engineer
Twenty-Six Defense · Merrimack, NH · 1 mo ago
EngineeringFull-time
We need to produce HTML fragment with sections: About the role? The posting includes "Company Information", "Job Summary", "Responsibilities And Tasks" broken into subcategories: Project Execution, Cost and Schedule Management, Bids and Proposals, Project Planning, Resource Management, Process, People/Relationships, Expected Leadership Characteristics, Knowledge (Education/License/Certification, Prior Experience), Skills And Abilities, Benefits.
We need headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections that have real content. The posting includes "Company Information" which could be "About the role"? Actually "Company Information" is about the company, not role. The instruction says use
. The responsibilities are grouped under headings: Project Execution, Cost and Schedule Management, Bids and Proposals, Project Planning, Resource Management, Process, People/Relationships, Expected Leadership Characteristics. We should keep them as list items, maybe preserve the subheadings? But we cannot add extra headings besides text. That's okay.
We need to extract each bullet. Let's parse responsibilities:
Project Execution:
- Primary technical POC with the customer, lead engineering team in the development of the technical review packages and lead customer technical reviews
- Mediate and Adjudicate conflicts that arise within the engineering team and between engineering and the program manager
- Support the business unit in identification, mitigation, and management of risks, issues, and opportunities, specifically focused on the technical and engineering aspects
- Lead engineering project execution to include the cost, schedule and technical baselines for all engineering activities
- Partner with PM’s, Engineering Functional Managers, and Functional CAMs to ensure the project is being staffed and executed to plan
- Manage project scope ensuring budget/schedule changes are made with corresponding scope changes
Cost and Schedule Management:
- Utilize EVMS (scaled as appropriate) to monitor and control engineering cost and schedule performance
- Ensure IMS is kept up to date with support from appropriate PP&C personnel or schedulers
- Work with team to develop both technical and process improvement work arounds to mitigate potential cost and schedule variances
- Coordinate/document variance reporting with the CAMs, or leads, as appropriate
- Update WBS as required
- Conduct project reviews as required, reporting program status to senior management
- Continuously work with the team to identify ways to improve efficiency of the technical team’s performance
- Mentor/coach project team members to help achieve efficient and effective project execution.
Bids and Proposals:
- Develop/coordinate engineering program bid and execution baselines (technical, scope, cost, schedule, risk, opportunities…) IAW defined scope and objectives
- Partner with Systems Engineers and Director(s) to provide innovative technical solutions to fit within budget and schedule constraints
- Develop/Lead the development of bids and BOE’s IAW company policy, using historical data wherever possible
- Develop engineering WBS, IAW company standards tailored as appropriate to meet specific project requirements
- Develop/support the development of the IMS, developing work packages and staffing requirements
- Coordinate and document process tailoring activities for specific project requirements
- Document risks and opportunities associated with the Engineering Bid
- Develop bid package and obtain approval from relevant stakeholders
Project Planning:
- Develop/refine engineering WBS, IAW company standards tailored as appropriate to meet specific project requirements
- Clearly define and document project scope and deliverables
- Coordinate and integrate the different functional inputs into a coherent executable project plan.
- Establish, negotiate and allocate budgets to the CAMs
- Coordinate the development of the engineering portion of the resource loaded IMS
- Coordinate the development of the initial risk and opportunity register
- Communicate staffing requirements to functional management in support of the engineering resource planning process
Resource Management:
- Develop and maintain staffing requirements (by skill and time phased) – ideally through a resource loaded schedule.
- Negotiate staffing requirements with Engineering Functional leadership
- Enter and maintain staffing requirements into workforce planning tool.
- Support functional staffing analysis for future work
- Partner with functional management in employee performance assessment, development, and corrective action
- Identify and report variances between staffing levels vs plan
Process:
- Execute role IAW project management process and other relevant procedures
- Support company level process initiatives and audits
- Continually seek ways to improve efficiency and performance
- Partner with functional management to establish process tailoring. Identify risks associated with tailored tasks.
People/Relationships:
- Establish and maintain business unit partnerships
- Establish and maintain key Elbit, customer, and engineering functional management relationships
- Establish and maintain relationships with Applications Engineering
Expected Leadership Characteristics:
- Encourages and builds mutual trust, respect, and cooperation among team members
- Fosters an environment where employees are valued and cost effectiveness and efficiency is rewarded
- Clearly explains project assignments, expectations, priorities, and follows up to ensure they are met
- Practices the philosophy of communicate, negotiate, elevate when dealing with others
- Delegates tasks as appropriate
- Agile and open to change, embracing it to deal with unpredictable or unexpected events
- Strong written and verbal communication skills
- Assumes responsibility for their project’s performance
- Practices self-improvement
- Looks for outside opinions and advice
- Exemplifies the company core values (Ethics, Customer Focus, Respect, and Excellence)
- Coaches/develops others and is open to coaching and feedback
Now Knowledge (Education/License/Certification, Prior Experience):
- Bachelor’s degree in Electrical Engineering, Mechanical Engineering, Computer Science, Physics or relevant technical discipline with advanced technical degree(s) preferred.
- 20 years relevant product development experience (Military products preferred)
- CAM experience preferred
- PMP certification preferred
- Earned Value Management experience strongly preferred
Skills And Abilities:
- Demonstrated leadership skills
- Strong written and verbal communication skills
Benefits:
- Most locations offer a 9/80 schedule, providing every other Friday off
- Competitive compensation & 401(k) program to plan for your future
- Robust medical, dental, vision, & disability coverage with qualified wellness discounts
- Basic Life Insurance and Additional Life & AD&D Insurances are available
- Flexible Vacation & PTO
- Paid Parental Leave
- Generous Employee Referral Program
- Voluntary Benefits Available: Longer Term Care, Legal, Identity Theft, Pet Insurance, and more
- Voluntary Tricare Supplement available for military retirees
Schedule: we could extract the 9/80 schedule detail. But it's already in Benefits. However we could still create a Schedule section with that detail. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info, so we can create Schedule section. But we must not duplicate content. If we put schedule info in both Benefits and Schedule, that's duplication. Better to put schedule info only in Schedule section, and maybe keep other benefits in Benefits. However the benefit list includes that line; we could remove it from Benefits and put under Schedule. But we must preserve ALL substantive information; we can move it. So Benefits section will exclude the schedule line. Schedule section will contain that line.
Thus:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections that have real content. The posting includes "Company Information" which could be "About the role"? Actually "Company Information" is about the company, not role. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. Likely we should have sections: About the role (maybe from Job Summary), Responsibilities (list of duties), Requirements (knowledge/experience), Qualifications (maybe education/license?), Skills (Skills And Abilities), Benefits (benefits list). Pay and Schedule only if present. The posting mentions schedule: "Most locations offer a 9/80 schedule, providing every other Friday off" under Benefits. So schedule is part of benefits; but we could still create a Schedule section if we have explicit schedule info. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info (9/80). So we could create a Schedule section with that detail. Pay: there is no explicit pay range; there is a note about Virginia salary range but that's conditional and not actual pay. It says "For Virginia-based positions only* In accordance with Virginia DOL requirements, the listed salary range reflects the anticipated base pay range for this role." However there is no actual salary range listed; it's just a note. So we should not create Pay section because no actual pay range given. Benefits: we have benefits list. So include Benefits.
Thus sections: About the role (Job Summary), Responsibilities (all responsibilities and tasks), Requirements (Knowledge (Education/License/Certification, Prior Experience) maybe also include PMP etc), Qualifications? Could combine with Requirements? But we need to follow instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Requirements and Qualifications separately if content distinct. Knowledge section includes education, experience, certifications. That's both requirements and qualifications. Could split: Requirements = experience, certifications; Qualifications = education? But better to follow typical: Requirements = experience, certifications; Qualifications = education. However the posting lumps them together: "Bachelor’s degree ... with advanced technical degree(s) preferred. 20 years relevant product development experience (Military products preferred) CAM experience preferred PMP certification preferred Earned Value Management experience strongly preferred". So we could put education under Qualifications, experience/certifications under Requirements. Skills section: Skills And Abilities.
Thus produce:
About the role
About the role
Job Summary paragraph...
Responsibilities
- ... each responsibility item ...
for sections; we could include the subheadings as part of the
Schedule
Most locations offer a 9/80 schedule, providing every other Friday off
Benefits section will have the rest. Now About the role: Use Job Summary paragraph: "We are currently recruiting for a Senior Staff Project Engineer-- but we are looking for more than an impressive skill set. We are looking for the type of person who respects others for their knowledge, skills, and experience as individuals and as team members. We want someone who is highly ethical, honest, fair…because that’s who we are. If you are the type of person who has high integrity and would thrive in an inclusive environment of camaraderie with your fellow teammates, we’re pretty confident you’ll love it here." We need to preserve that exactly. Now we need to output only HTML fragment, no /, no markdown. We'll produce:About the role
We are currently recruiting for a Senior Staff Project Engineer-- but we are looking for more than an impressive skill set. We are looking for the type of person who respects others for their knowledge, skills, and experience as individuals and as team members. We want someone who is highly ethical, honest, fair…because that’s who we are. If you are the type of person who has high integrity and would thrive in an inclusive environment of camaraderie with your fellow teammates, we’re pretty confident you’ll love it here.
Responsibilities
- Primary technical POC with the customer, lead engineering team in the development of the technical review packages and lead customer technical reviews
- Mediate and Adjudicate conflicts that arise within the engineering team and between engineering and the program manager
- Support the business unit in identification, mitigation, and management of risks, issues, and opportunities, specifically focused on the technical and engineering aspects
- Lead engineering project execution to include the cost, schedule and technical baselines for all engineering activities
- Partner with PM’s, Engineering Functional Managers, and Functional CAMs to ensure the project is being staffed and executed to plan
- Manage project