Technical Competency Model
"Senior" is a word that means nothing until an institution defines it. This page states how technical capability is described here, how it is assessed, how it advances, and how the gap between what a program needs and what the team holds is found before it becomes a performance problem.
Discipline Ladders
Competency is defined per discipline rather than as a single generic engineering scale, because what makes a propulsion analyst senior is not what makes a mission assurance engineer senior. Each ladder names the knowledge, the tools, the standards, and the demonstrated work products expected at each level.
- Propulsion and thermal-fluid systems — cycle analysis, combustion and nozzle performance, thermal management, test data reduction
- Systems engineering — requirements development and flow-down, interface control, verification and validation, trade studies, technical reviews
- Structures, materials, and mechanisms — loads and stress analysis, fracture control, materials selection, environmental qualification
- Nuclear and high-energy systems — reactor and power conversion fundamentals, shielding and radiation transport, safety analysis, handling controls
- Avionics, software, and autonomy — architecture, flight software assurance, verification, model-based design, cybersecurity for embedded systems
- Mission assurance and quality — reliability, FMEA, fault tree, hazard analysis, problem reporting and corrective action, independent review
- Program and business disciplines — planning and scheduling, cost engineering, subcontract management, capture and proposal practice
Proficiency Levels
Four levels apply to every discipline. They describe demonstrated capability, not years served. A person can hold different levels in different disciplines, and that combination is what makes a small technical organization able to cover a broad program.
- Level 1 — Practitioner: Performs defined technical tasks under review. Applies established methods correctly and recognizes when a problem exceeds the method.
- Level 2 — Independent Engineer: Owns a technical element end to end. Selects methods, defends assumptions, and produces work products that survive peer review without rework.
- Level 3 — Discipline Lead: Sets technical approach for a discipline across a program. Reviews the work of others, resolves cross-discipline conflicts, and carries technical accountability for outcomes.
- Level 4 — Technical Authority: Recognized judgment in a domain. Makes and defends decisions where analysis is incomplete, and is trusted by a customer's own technical staff to be right about hard problems.
How Proficiency Is Assessed
Assessment relies on evidence a reviewer could examine. Self-assessment starts the conversation; work product and peer judgment settle it. The intent is a competency record an institution could defend to a customer, not a self-reported skills inventory.
- Self-assessment against the published discipline ladder before the review discussion
- Supervisor and discipline-lead assessment based on delivered work products, analyses, and reviews
- Peer and independent review input where the person's work has been formally reviewed
- Evidence anchored to artifacts: analysis packages, design documentation, test reports, review board dispositions
- Assessment recorded, revisited on a defined cadence, and used as the basis for the individual development plan
- Disagreement escalation path that does not run only through the person's own supervisor
Dual Career Tracks
The technical ladder and the management ladder are separate and comparable. An engineer who wants to go deeper rather than wider is not required to take a supervisory role to reach senior standing, compensation range, or institutional influence.
- Technical track advancement judged on depth of judgment, technical leadership, and external recognition in the discipline
- Management track advancement judged on program outcomes, team development, and stewardship of cost and schedule
- Movement between tracks is permitted and does not reset standing
- Senior technical contributors participate in review boards, technical authority decisions, and proposal technical volumes
- Neither track is treated as the default destination for a strong performer
Competency Gap Analysis
The model exists to be compared against work. Program staffing needs are expressed in the same competency vocabulary, which makes the gap between the capability a contract requires and the capability on hand visible early enough to close it.
- Program staffing requirements expressed as discipline and level, not just headcount
- Gap analysis performed at capture and again at contract start, before performance depends on the answer
- Gaps closed by targeted development, assignment change, hiring, or teaming — decided explicitly rather than by default
- Single-point technical dependencies identified as a risk and treated with deliberate cross-training
- Results feed the staffing plan and the make-or-buy analysis rather than sitting in a personnel file
Competency Evidence in Proposals
Source selection evaluates key personnel and staffing approach on demonstrable grounds. A defined competency model turns statements about a team's capability into something a technical evaluator can trace.
- Key personnel qualifications mapped to the labor category and competency level a solicitation requires
- Staffing approach describing how the level required is verified before assignment, not asserted after award
- Substitution procedures stating that a replacement meets the same competency criteria
- Development plans supporting long periods of performance where capability must grow with the program
- Individual records furnished under the terms of the acquisition rather than published
Where This Connects
Competency levels drive the labor category discipline described in workforce and resource cost decisions and the scale-up sequencing in the contract surge model. Advancement expectations are described for candidates in the career corridor and talent philosophy.
Alignment Disclosure
Monarch Space Systems describes its workforce development practices as aligned with publicly documented NASA and prime contractor learning practice, including agency knowledge services, handbook-based technical curricula, and lessons-learned discipline. Alignment is a statement of design, not an endorsement, affiliation, or accreditation. The institution does not claim sponsorship by or partnership with NASA, enrollment in agency training systems, an accredited degree program, a certifying authority, or any specific training vendor relationship. Workforce size, training hours, credential counts, and individual development records are not published.
Curriculum outlines, competency definitions, and training records applicable to a specific acquisition are furnished to a contracting officer or prime contractor through the confidential engagement pathway or by request through institutional contact.