Project Engineer

Project Engineer

Company:

The Boeing Company

We are Boeing Global Services (BGS) Engineering team creating and implementing innovative technologies that make the impossible possible and enabling the future of aerospace.  We provide engineering design and support, including aftermarket modifications, and are innovating to make product and services safety even stronger. Join us and put your passion, determination, and skill to work building the future! #TheFutureIsBuiltHere #ChangeTheWorld

The Boeing Translation Engine translates raw binary data from the Quick Access Recorder (QAR), Digital Aircraft Condition Monitoring System (ACMS) Recorder (DAR) [Aeronautical Radio Incorporated (ARINC) 717], Continuous Parameter Logging (CPL), Enhanced Airborne Flight Recorder (EAFR)(CPL) [ARINC 767], ARINC 429, ARINC 629, ARINC 664 (plus any other future data) binary files into standardized binary files and engineering units. Additionally, the BTE imports pre-translated data from operators or other external systems in a standardized way to support downstream applications.  

We are seeking a Project Engineer in Seattle, Washington who can bridge engineering and business, translating complex, ambiguous customer needs into clear, actionable plans. This role thrives in ambiguity and organizational complexity, proactively drives clarity without waiting for perfect requirements, shields engineers from unnecessary churn, and ensures our infrequent releases land with high quality and measurable customer impact. 

What you’ll do 

• Facilitate, elicit and refine requirements, partner with customer-facing leads, software engineering, and SMEs to determine the path forward, validate assumptions, and ask the hard questions. 

• Translate customer problems into developer-ready work: craft epics, features, and stories with clear acceptance criteria; build and maintain a robust, prioritized backlog. 

• Help build and maintain a performance engineering backlog tailored to aviation needs; anticipate algorithmic, data, and performance implications across scenarios and edge cases. 

• Drive cross-functional collaboration with engineering, design/UX, performance engineers, QA, program management, support, marketing, and sales to align on outcomes and delivery plans. 

• Develop and own PI and sprints backlog, that is based on release plans and product road map, balancing infrequent release cadences with incremental value delivery and readiness. 

• Proactively facilitate dependencies across teams; identify critical path, risks, and mitigation strategies; ensure stakeholders know what’s needed and when. 

• Provide crisp, timely status updates and executive-ready communications; ensure the right level of information reaches the right audience at the right time so teams never feel lost. 

• Use data and feedback loops (analytics, customer inputs, support tickets, ops metrics) to prioritize, measure impact, and continuously propose changes to improve product performance and quality  

• Engage directly with customers and end users (often through customer-facing team members) to understand real-world use cases and constraints. 

• Lead with healthy assertiveness: facilitate alignment among decision-makers, resolve blockers directly when possible, and know when to escalate; drive clarity in complex, ambiguous, or politically sensitive situations. 

• Respect developer focus time and preferences: minimize unnecessary meetings, handle design/planning/story mapping overhead, and bring only well-structured questions and decisions to engineering. 

• Prepare thorough scenario thinking: analyze downstream implications of product and technical decisions across safety, reliability, usability, and operational workflows. 

How you’ll operate in the BTE program context 

• Partner with customer-facing leads and decision-makers to translate customer needs into developer-ready work; proactively schedule and drive alignment sessions. 

• Manage dependencies across engineering groups that prefer minimal process involvement. 

• Maintain engineering backlog; anticipate edge cases and operational impacts before they become issues. 

• Drive clarity in a rarely-ship environment by emphasizing readiness, reliability, and quality gates; ensure stakeholders know what will ship, when, and why. 

• Provide predictable, no-surprises communications: crisp status, risks, and decisions; ensure support, customers, and leadership have what they need. 

Success in this role looks like 

• Clear, prioritized backlogs aligned with business roadmap