Jobs · OTHR

Senior Director, Growth APG

Parry Labs · Maryland, United States · 3 wk ago
RemoteRemoteOTHRFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "Who Are We?" and "About The Job". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include: About the role (maybe "About The Job" content), Responsibilities (Key Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Skills? Not explicit. Benefits: there is "Why Join Parry Labs?" which mentions benefits like workplace flexibility, health and well-being, education assistance, unlimited paid time off. That's benefits. Pay: not mentioned. Schedule: not mentioned. So we should not create Pay or Schedule sections. We need to include sections only if there is real specific content. So we can have:

About the role

(content from "About The Job" paragraph(s) describing the role). Could also include "Who Are We?" maybe as part of about the role? But "Who Are We?" is company overview, not role. Might be considered part of about the role? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. Thus: - About the role: description of the Senior Director role, focusing on Army C2 seam and tactical edge campaign, etc. - Responsibilities: list from "Key Responsibilities" bullet points. - Requirements: from "Required Qualifications". - Qualifications: from "Preferred Qualifications". - Benefits: from "Why Join Parry Labs?" (benefits description). Also maybe "No One Has Time for Long Job Applications!" is application instructions, we should drop. Also "Accessibility/Accommodation" is legal boilerplate, drop. We must not repeat job title as heading. Not include Job ID. We must use
  • for any list of duties/requirements/benefits, and

    for prose. Thus for each section we need to decide if content is list or prose. For About the role: it's prose (multiple sentences). We'll wrap in

    . For Responsibilities: list of duties; we should output

    • each duty. For Requirements: list of qualifications; we can output
      • . For Qualifications (Preferred): also list. For Benefits: list of benefits (workplace flexibility, health and well-being, education assistance, unlimited paid time off). Could be list. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from each section. Let's extract content precisely. First, "Who Are We?" paragraph: At Parry Labs we believe the modern combat advantage relies on the speed and scale of open systems. We’re redefining the edge of the increasingly ever-changing battlespace by delivering game changing capabilities to our warfighters through digital engineering, software, and hardware solutions that are essential to our core of being a Digital Systems Integrator. Born digital and agile, Parry Labs is building a winning team to be the premier provider for Next Generation Mission Systems Integration across air, land, sea, space and cyber. Are you ready to be an instrumental part of experts in the industry? Join us in the innovation of integration at Parry and apply to help develop the technologies of tomorrow while reaching new heights in your career today. This is company overview; maybe we can incorporate into About the role? But the instruction says About the role heading for section about the role. Could we include company overview as part of About the role? Might be okay but maybe better to include as part of About the role? The role description starts after "About The Job". The "Who Are We?" is separate. The instruction says preserve ALL substantive information; we should not drop it. So we need to include it somewhere. Since we don't have a heading for company overview, we could include it as a paragraph before the About the role heading? But the instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

        for section headings (list). It might be okay to have other headings? It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; we could also have other headings but they'd deviate. Safer to stick to those headings only. So we need to fit company overview into one of those sections. Probably About the role can include both company overview and role description. That would be substantive. Thus About the role section will contain the "Who Are We?" paragraph plus the "About The Job" description. Now extract "About The Job" paragraph: "This Senior Director owns Parry Labs' growth and capture for the Army C2 seam and tactical edge campaign. The focus is the Portfolio Acquisition Executive for C2 and Counter C2 (PAE C2/CC2) at Aberdeen Proving Ground (APG), including the Army's Next Generation Command and Control (NGC2) effort as it scales from divisions to corps, and the programs that carry C2 applications and data to soldiers, vehicles, and uncrewed systems at the edge. You will own a slate of pursuits from the first customer conversation through contract award: qualify the opportunity, shape the requirement and the acquisition approach, build the team, structure the deal, and close it. You will carry a qualified pipeline target in your first year and a bookings target after that. You will lead the campaign end to end: the plan, the customer contact plan and events calendar, the pursuit slate, and the monthly campaign review. You will position Parry Labs' edge compute hardware, the STRATIA software infrastructure, the VIW virtual integration workspace, and FUSION as the open, modular layer between the Army's enterprise C2 data baseline and the tactical edge, conformant with the Army's own interfaces. This is a senior field role for someone who has closed Army deals, is known across the Army C2 community." We'll keep that as prose. Now Responsibilities: list under "Key Responsibilities". Let's extract each bullet: - Lead the campaign. Own the Army C2 seam and tactical edge campaign plan: the customer map across PAE C2/CC2 and the tactical edge programs, the funding lines, the pursuit slate, the contact plan, the key events calendar, and the monthly campaign review with the CRO. Bring Parry Labs' product, engineering, and proposal leads together behind one plan and hold it to its dates. - Own the number and the pipeline for Army C2 and the tactical edge. Build and carry a qualified pipeline target, then a bookings target. - Identify, qualify, and prioritize pursuits across PAE C2/CC2 (including CPE C2IN and the NGC2 program, and CPE ISW), the C5ISR Center, the soldier and mounted C2 programs (including Nett Warrior and the Tactical Assault Kit), and the Army units and innovation offices that generate demand. - Shape opportunities early by engaging program offices, operational units, and the ASA(ALT) Pathway for Innovation and Technology (including Army FUZE and xTech ). Influence requirements, funding, and acquisition strategy before solicitations are written. - Win a position at the seam. Secure Parry Labs' place in the NGC2 integration pipeline and application storefront and pass the Army's C2 software development kit integration events. Build and maintain relationships across Army program offices and units, NGC2 prime integrators and ecosystem partners, and the broader Army C2 community. - Lead captures from qualification through award. Own the win strategy, customer call plans, teaming, and price to win, and present each pursuit at gate reviews. - Structure and close deals. Match each opportunity to the right vehicle and funding source (OTA prototypes and their production awards, CSOs, SBIR Phase III, enterprise and license agreements, and subcontracts under primes), then negotiate terms with customers and partners. - Grow the tactical edge programs. Own follow on and expansion opportunities for Parry Labs' edge compute hardware and mission software on current tactical edge programs, working with the program managers who run them today. Connect customer needs to Parry Labs capabilities across edge compute hardware, STRATIA, VIW, and FUSION, working with Product and Engineering to turn them into priced, repeatable offers. - Drive proposal content with the solution narrative, win themes, discriminators, and customer intelligence. - Represent Parry Labs at customer engagements, demonstrations, Army experimentation events, and industry events. - Maintain CRM discipline and deliver an accurate monthly forecast of bookings, award timing, and probability of win to the CRO. - Other duties as assigned. We need to keep each as separate
      • . Ensure we preserve all details. Now Required Qualifications: - Bachelor's degree or equivalent experience. - 10+ years of defense business development, capture, program management, or acquisition experience focused on Army C2, tactical networks, or mission command, including at least 5 years carrying a bookings target or leading captures. - A record of closed Army deals you can walk through in detail. - Working relationships across the Army C2 community at APG, including PAE C2/CC2, CPE C2IN and the NGC2 program, CPE ISW, the C5ISR Center, and Army Contracting Command, plus the integrators and partners on NGC2 teams. - Experience selling, architecting, or managing edge compute, tactical networks, or mission command systems for the Army, and working knowledge of the NGC2 application, data, infrastructure, and transport layers and of the Tactical Assault Kit ecosystem. - Practical Army acquisition experience with OTAs, CSOs, and the Software Acquisition Pathway, and a record of shaping requirements and transitioning prototypes into programs of record, including how budget lines, continuing resolutions, and the Army's portfolio acquisition structure shape award timing. - Experience leading a multi year campaign or account plan across several program offices and units, with a cross functional team behind it. - Clear, concise briefing skills: able to present a pursuit, its value, and its risks to senior Army leaders and Parry Labs executives in a few minutes. - Willingness to travel about 50%. - Active Secret security clearance (U.S. citizenship required) and the ability to obtain TS/SCI. Now Preferred Qualifications: - Prior Army service or Army civilian experience in acquisition, signal, or mission command roles. - Experience at a defense technology company that sells commercial products. - Familiarity with modular open systems approaches (MOSA, SOSA, and CMOSS) and with government owned interface standards. - Established teaming relationships with primes and integrators. - Active TS/SCI clearance. - Experience with Army FUZE, xTech , SBIR, or Army experimentation events such as Project Convergence. Now Benefits/Why Join Parry Labs: Paragraph: "At Parry Labs, we foster a culture of curiosity and collaboration. Employees are given the autonomy to leverage their skills in creating state-of-the-art tech solutions that aid in the protection of the American Warfighter. We encourage new and bold ideas that push the status quo. It is this entrepreneurial spirit that drives us. Parry Labs will support you with workplace flexibility, a commitment to the health and well-being of you

Similar jobs

Senior Director, Growth

Sauce LabsSan Francisco, CA· 1 mo ago
RemoteOTHR$230k–$270k/yrapply on job-boards.greenhouse.io