Solutions Architect

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID/requisition numbers as headings; can fold minor metadata into short p or drop it. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract content: - Intro: "The company built on breakthroughs. Join us. Corning is one of the world’s leading innovators in glass, ceramic, and materials science. From the depths of the ocean to the farthest reaches of space, our technologies push the boundaries of what’s possible. How do we do this? With our people. They break through limitations and expectations – not once in a career, but every day. They help move our company, and the world, forward. At Corning, there are endless possibilities for making an impact. You can help connect the unconnected, drive the future of automobiles, transform at-home entertainment, and ensure the delivery of lifesaving medicines. And so much more. Come break through with us. Our Optical Communications segment has recently evolved from being a manufacturer of optical fiber and cable, hardware and equipment to being a comprehensive provider of industry-leading optical solutions across the broader communications industry. This segment is classified into two main product groupings – carrier network and enterprise network. The carrier network product group consists primarily of products and solutions for optical-based communications infrastructure for services such as video, data and voice communications. The enterprise network product group consists primarily of optical-based communication networks sold to businesses, governments and individuals for their own use." That's about company and segment; could be "About the role"? Actually "About the role" is more about the job description. But we can treat this as "About the role" or maybe "About the company". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" heading and put the description of role purpose and maybe company overview. But we need to preserve all substantive info. Let's identify sections: Role Purpose: "Serve as an Engineering Services (ES) resource collaborating with COC to support the innovation and commercialization of new solutions for strategic hyperscale data center (HSDC) customers. This role contributes to new product design activities including gathering customer requirements, supporting concept development with AIR and Market Development teams, coordinating prototype efforts with Corning Technology, and creating supporting documentation. The position requires understanding customer priorities, market needs, and competitive activity to help inform solution development and reduce risk to Corning." Key Responsibilities: list bullet points. Education/Skills - Required: list. Skills - Desired: list. Other info: "This position does not support immigration sponsorship. The range for this position is $82,974.00 - $114,090.00 assuming full time status. Starting pay for the successful applicant is dependent on a variety of job-related factors, including but not limited to geographic location, market demands, experience, training, and education." Benefits: "A job that shapes a life. Corning offers you the total package. Your well-being is our priority. Our compensation and benefits package supports your health and wellness, financial aspirations, and career from day one. Company-wide bonuses and long-term incentives align with key business results and ensure you are rewarded when the company performs well. When Corning wins, we all win. As part of our commitment to your financial well-being, we provide a 100% company-paid pension benefit with fixed contributions that grow throughout your career. Combined with matching contributions to your 401(k) savings plan, Corning’s total contributions to your retirement accounts can reach between 7% and 12% of your pay, depending on your age and years of service. Our health and well-being benefits include medical, dental, vision, paid parental leave, family building support, fitness, company-paid life insurance, disability, disease management programs, paid time off, and an Employee Assistance Program (EAP) to support you and your family. Getting paid for our work is important, but feeling appreciated and recognized for those contributions motivates us much more. That’s why Corning offers a recognition program to celebrate successes and reward colleagues who make exceptional contributions." EEO etc: we must remove boilerplate: "We prohibit discrimination on the basis of race, color, gender, age, religion, national origin, sexual orientation, gender identity or expression, disability, veteran status or any other legally protected status. Corning is committed to providing equal employment opportunities and considers requests for reasonable accommodations in accordance with applicable laws. Individuals with disabilities or sincerely held religious beliefs may request reasonable accommodations to participate in the application or interview process, perform essential job functions, or access other benefits and privileges of employment. To submit a request for reasonable accommodation related to disability or religion, please contact us at accommodations@corning.com ." We must remove that. Also remove "Requisition Number: 78196" maybe as minor metadata in a short p. We must not include application instructions. Now decide sections: - About the role: could include company overview and role purpose? Or we could have "About the role" with role purpose description. The company overview maybe not needed but it's substantive. Could include under About the role. - Responsibilities: list of key responsibilities. - Requirements: Education/Skills - Required. - Qualifications: maybe combine with Requirements? But we have both Education/Skills - Required and Skills - Desired. Could treat Required as Requirements, Desired as Skills (or Qualifications). The instruction list includes Qualifications as a possible heading. We could put Education/Skills - Required under Qualifications, and Skills - Desired under Skills. Or we could have Requirements for required, and Skills for desired. Let's follow typical: Requirements = required qualifications; Skills = desired skills. We'll also maybe have a Qualifications section? Might be redundant. Better to stick to a few substantive sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. No Schedule (not mentioned). No Qualifications separate. We must not create sections with filler like "not specified". So we include only those with content. Now we need to format lists: Use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive info; not invent or summarize away detail. So we must keep each bullet point as is. Let's extract bullet points from Key Responsibilities: The text after "Key Responsibilities" appears as a paragraph with sentences separated by periods but not bullet list. However we need to treat as list? The instruction: Use

  • for any list of duties/requirements/benefits. The posting didn't explicitly use bullet characters but it's a series of statements separated by periods. We could still convert each sentence into a list item? Might be considered a list. However we must preserve all substantive info; we can keep as prose

    if not explicitly a list. The instruction says use

    • for any list of duties/requirements/benefits. If the original didn't have list formatting, we could still treat as list? Safer to keep as

      with sentences separated by periods. But we could also split into

      • each sentence. The instruction says "for any list of duties/requirements/benefits". If it's not presented as a list, maybe we keep as prose. I'd keep as prose to avoid altering structure. Similarly for Education/Skills - Required: it's a list of items separated by line breaks? The text: "BS in Engineering Related Studies (Mechanical, Electrical, Chemical, Optics) 1+ years of telecommunications, data center, or related industry experience Project management/project coordination experience preferred Telecom manufacturing experience preferred Ability to translate complex technical information into clear customer-facing and internal communications Effective communicator able to deliver messages through various methods Strong knowledge of fiber optic products, structured cabling systems, and installation practices Fluent English language skills, both spoken and written Ability to manage tasks effectively in a changing environment Results-oriented with a strong commitment to task completion Willingness to work outside normal business hours when necessary Strong problem-solving and decision-making skills Dedicated to meeting internal and external customer expectations Detail-oriented and conscientious Willing to remain in the position for a minimum of two years Able to pass a background check, drug screening, and driving record check Must not be color blind; distinct color acuity is required Valid driver's license required Travel up to 25%" That's a long sentence with items separated by spaces. Could treat as list but not explicit. Safer to keep as

        . Skills - Desired: similar. Benefits: paragraph. Pay: we have salary range. Thus we will have sections: - About the role: include company overview and role purpose? Might be two paragraphs. - Responsibilities: paragraph. - Requirements: paragraph (required education/skills). - Skills: paragraph (desired skills). - Benefits: paragraph. - Pay: paragraph (salary range). We must not include Schedule. Now we need to remove boilerplate like "A job that shapes a life." Actually that's part of benefits description; we keep it. Now we need to ensure we don't repeat job title as heading. Not include. We need to include minor metadata like Requisition Number maybe as a short p at top? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So we can include a short p with the requisition number. But maybe better to drop it? It says fold minor metadata into a short

        or drop it. We can include a short p:

        Requisition Number: 78196

        . That's minor metadata. Now output only HTML fragment. Let's craft:

        Requisition Number: 78196

        About the role

        [company overview + role purpose]

        We need to combine company overview and role purpose into one paragraph? Could be two paragraphs but still under same heading. We'll put as

        ...

        maybe multiple

        under heading? The instruction: Use

        for prose. So we can have multiple

        elements under heading. Thus:

        About the role

        Corning is one of the world’s leading innovators in glass, ceramic, and materials science. From the depths of the ocean to the farthest reaches of space, our technologies push the boundaries of what’s possible. How do we do this? With our people. They break through limitations and expectations – not once in a career, but every day. They help move our company, and the world, forward. At Corning, there are endless possibilities for making an impact. You can help connect the unconnected, drive the future of automobiles, transform at-home entertainment, and ensure the delivery of lifesaving medicines. And so much more. Come break through with us. Our Optical Communications segment has recently evolved from being a manufacturer of optical fiber and cable, hardware and equipment to being a comprehensive provider of industry-leading optical solutions across the broader communications industry. This segment is classified into two main product groupings – carrier network and enterprise network. The carrier network product group consists primarily of products and solutions for optical-based communications infrastructure for services such as video, data and voice communications. The enterprise network product group consists primarily of optical-based communication networks sold to businesses, governments and individuals for their own use.

        Serve as an Engineering Services (ES) resource collaborating with COC to support the innovation and commercialization of new solutions for strategic hyperscale data center (HSDC) customers. This role contributes to new product design activities including gathering customer requirements, supporting concept development with AIR and Market Development teams, coordinating prototype efforts with Corning Technology, and creating supporting documentation. The position requires understanding customer priorities, market needs, and competitive activity to help inform solution development and reduce risk to Corning.