Technical Product Manager (Acrovyn Door Solutions)

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Skills, Benefits, Pay, Schedule. Only include sections if there is real specific content. The posting includes: Scope of Position (maybe "About the role"?), Responsibilities (Essential Duties and Responsibilities), Requirements (list of duties? Actually they have "Requirements" heading then a paragraph about performing duties, then list of duties again? The content after "Requirements" includes a paragraph then a list of duties (Guides the product strategy ...). That seems like responsibilities again. Then "Qualifications" heading with knowledge/skills/experience/education. Then "About Us" (company description). There's no explicit Benefits, Pay, Schedule. So we should not include those sections. We need to use

for section headings. For each section, we need to put content: either

for prose,

• for lists. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement: "Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, disability, veteran status, or any other characteristic protected by applicable federal, state or local law." That's boilerplate EEO, should be removed. Also "About Us" section is substantive; we can treat as maybe "About the role"? Actually "About Us" is company description. Could be placed under a heading like "About the role"? But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings if appropriate. The "Scope of Position" is like About the role. So we can put that under

  About the role

  . Then Responsibilities under

  Responsibilities

  . Then Requirements? The posting has a "Requirements" heading but then it's basically a paragraph about performing duties then a list of duties again. That seems like responsibilities again; but we already have Responsibilities. However we must preserve all substantive info; we could treat the "Requirements" section as part of Responsibilities? But we need to follow headings: we can still include a

  Requirements

  if there is real specific content. The content after "Requirements" includes: "To perform this job successfully, an individual must be able to perform each essential duty satisfactorily. The requirements listed below are representative of the knowledge, skill, and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions, including but not necessarily limited to the following:" Then a list of duties (Guides the product strategy ...). That is essentially a list of responsibilities. So we could treat that as Responsibilities again, but we already have a Responsibilities section from earlier "Responsibilities ESSENTIAL DUTIES AND RESPONSIBILITIES:" which likely had no list? Actually after "Responsibilities ESSENTIAL DUTIES AND RESPONSIBILITIES:" there is no list directly; then immediately "Requirements". So the responsibilities are listed under the Requirements heading. So we should combine them: The responsibilities are the list after Requirements. So we should have a Responsibilities section with that list. The earlier "Responsibilities ESSENTIAL DUTIES AND RESPONSIBILITIES:" is just a heading with no content; we can ignore it as it's just a heading placeholder. So we will output

  Responsibilities

  with a
  • list of the duties. Then we have Qualifications section with knowledge/skills/experience/education. That's a heading. We'll output

    Qualifications

    with content: maybe a

    for the paragraph describing minimum education etc., then a

    • for the list of qualifications (proficiency in Microsoft..., proficiency with technical product files..., strong data analysis..., proven ability..., communication..., self-motivated..., experience leading projects..., ability to lead..., willingness to travel..., Preferred Experience..., Preferred Education...). We need to preserve all substantive info; we should not drop any. We also have "About Us" description. There's no specific heading for that in the allowed list, but we could put it under

      About the role

      ? Actually About the role is more about the role itself, not company. But we have no other heading for company description. The instruction says use those headings for section headings; but we can also include other headings? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but we should likely stick to those. However we have company description that is substantive; we could put it under

      About the role

      as a brief description of the company? But that might be misleading. Alternatively we could omit it? But we must preserve ALL substantive information; we cannot drop the About Us description. So we need to include it somewhere. Perhaps we can treat it as a section with heading

      About the company

      but that's not in the list. 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 (e.g. ...). It might be okay to use other headings as long as they are

      . However to be safe, we could incorporate the About Us content into the About the role section, maybe as a paragraph describing the company context. The About the role section could include both scope of position and company description. That would preserve all info. Thus:

      About the role

      Scope of Position: The Acrovyn Door Systems (ADS) Technical Product Manager’s primary role is to lead product line cost reductions, improvement projects, and line extensions for Acrovyn Door Systems products within the Interior Product Solutions product line. Technical expertise is needed to dive deep into product optimization efforts, to determine impact, priority and opportunities for projects, all while coordinating with cross-functional teams to maintain a best-in-class product line. The Technical Product Manager partners with the Interior Product Solutions (IPS) Product Manager and IPS Technical Product Manager to continuously collect customer feedback and custom inquiries on products to guide the strategy for new and existing products. These recommendations stem from representing the customer and business interests throughout the product lifecycle (ideation, development, delivery, and discontinuation).

      About Us: CONSTRUCTION SPECIALTIES, INC. Founded in 1948, Construction Specialties (CS) is a specialty building products manufacturer. CS provides solutions to building challenges that architects, designers, building owners, facility managers, and contractors face every day. Since inventing the first extruded louver, CS has become a global leader in all our product categories. Our products are a part of some of the most iconic buildings around the world– from the world’s tallest tower, Burj Khalifa in Dubai, to the Oculus at the World Trade Center Transit Hub in Manhattan. If you want to work in an inspiring atmosphere and collaborate with customers and colleagues to solve challenges, we're the right place for you. CS: People. Buildings. Better.

      Then Responsibilities: list. Then Qualifications: paragraph + list. We must not include Benefits, Pay, Schedule sections. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO statement at end. Check for duplicated lines: The responsibilities list includes many items; we need to ensure we capture all. Let's extract the responsibilities list from the text after "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions, including but not necessarily limited to the following:" Then list: - Guides the product strategy - Supports and guides the product vision, strategy, and roadmap - Uses technical aptitude to dive into product issues and information, identify solutions, and explain technical concepts in non-technical terms to stakeholders - Identifies market opportunities and competitive differentiation - Monitors competitors product lines and business activities such as product cost, market share, manufacturing capabilities, etc. - Stays on top of applicable marketplace trends in technology, value delivery, codes, new materials, aesthetics, life safety, sustainability, resiliency, etc. - Defines product requirements and specification documents - Optimizes the business strategy - Leads the development of the business case for new products, improvements to products, and cost reduction projects to senior management through business plans and project proposals - Manages all aspects of a product (product design, placement, pricing and positioning) by working with product development teams, sales and manufacturing - Works closely with cross-functional teams (engineering, sales, marketing, operations, etc.) to ensure business and customer satisfaction goals are met. - Facilitates sales and operations forecasts for new products, standard products, and samples - Proposes project prioritization of product management activities - Acts as a project manager on various NPD projects - Champions NPD projects to ensure customer and business needs are attained throughout the course of the project - Maintains technical product documents and monitors technical advancements in this arena - Tracks progress of KPI’s from product launches/business plans and facilitates plans for continuous improvements - Serves as the product expert - Acts as the central point of contact for technical questions - Acts as the liaison with operations to identify product line cost reductions - Analyzes product metrics on an ongoing basis to optimize the product offering - Collaborates with finance, accounting and business unit management to assemble and evaluate market potential and financial forecasts for the product line - Ensures each stage-gate of the new product delivery process is properly followed and makes recommendations on ways to improve the processes and tools - Represents the customer - Gathers, manages and prioritizes market/customer requirements - Acts as the customer advocate by articulating their requirements and translating it to product design requirements - Immerses themselves in the needs and design trends of the market by attending trade shows, reading research reports, meeting with customers on sales calls, industry associations, etc. - Represents CS in trade associations and code committees - Performs other duties assigned by management That's a long list. We'll output as
      • each. Now Qualifications: The text after "Qualifications KNOWLEDGE/ SKILLS/ EXPERIENCE/ EDUCATION: (Minimum Education and/or Experience required)" includes: "Associates or Bachelor’s degree in engineering, business administration, industrial design or another technical degree with three to five years related experience and/or training. Balanced understanding of business (strategy, marketing, operations, finance, etc.) is critical.Proficiency in Microsoft Word, Excel, PowerPoint, Teams, and OutlookProficiency with technical product files such as AutoCad and Inventor (preferred)Strong data analysis & interpretation capabilities. Experience with tools such as Excel, PowerBI, Construct Connect, Dodge, etc.Proven ability to analyze, prioritize and integrate large amounts of complex information into clear, concise plansCommunication – ability to simplify and effectively communicate complex concepts in written and verbal formats. Strong presentation and public speaking skills.Self-motivated, self-starter who is eager to learnExperience with leading projects and working in teamsAbility to lead and influence othersWillingness to travel an average 10% of the time to connect with third parties Preferred Experience Building products, specifically door industry.Background in product development, engineering or manufacturingProject management Preferred Education PDMA certificationPMP certification" We need to parse into sensible items. There's no punctuation separating some items; we need to split logically. We can create a

        for the first sentence about