Barbara Wierzbicka
Senior Project Engineer · Programs & Delivery
Gdansk, Poland
Senior Project Engineer with a background in systems engineering and program delivery. Bridges the gap between technical teams and program office — translates engineering constraints into schedule impacts and customer commitments into actionable work packages.
Expertise
- statement of work (SOW) preparation
- requirements decomposition and allocation
- milestone tracking and reporting
- customer interface management
- technical baseline management
- work package definition
Technologies
Work History
2024-01
Managed delivery of 14 engineering documents for a quarterly contract review — ICD updates, test reports, design drawings. Coordinated across documentation, quality, and engineering teams.
Challenge: Three documents were blocked by unresolved technical issues. Escalated to sub-system leads, defined minimum acceptable content for interim submission, and flagged remainder for next delivery cycle.
Learned: Partial delivery with explicit open items is better than a missed delivery. Customers can plan around known gaps; they cannot plan around silence.
2023-05
Led preparation of Critical Design Review (CDR) package: 280 slides across 8 sub-systems, coordinated review comments from 4 customer engineers, tracked 178 action items to closure.
Challenge: Two sub-systems submitted CDR slides 48 hours before the review with significant open items. Negotiated a partial CDR with those two teams presenting as 'CDR minus' and completing within 30 days.
Learned: CDR readiness criteria must be defined and checked 3 weeks before the event, not the week before. Build in a dry-run with engineering leads.
2022-11
Decomposed top-level system requirements from DOORS into sub-system work packages for 6 engineering teams. Created traceability matrix linking customer requirements to internal engineering deliverables.
Challenge: Customer requirements contained 23 'TBD' entries that blocked engineering planning. Negotiated interim assumptions with the customer and flagged each as a program risk until formally resolved.
Learned: TBD requirements are schedule risks dressed up as technical unknowns. Tracking them explicitly in the risk register creates visible pressure for resolution.