Skillbridge: Heat Transfer and Thermodynamic Systems Intern

We need to output HTML fragment with sections only if real content. Must include headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Do not invent or summarize away detail. Include a section only when posting has real, specific content for it—never emit 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 posting actually states them. We need to parse the posting. Key sections: - About the role: maybe the introductory paragraph about Raytheon, SkillBridge, mission, etc. The posting includes: "At Raytheon, we know and value the strategic and tactical talents that only veterans can offer... We are seeking ambitious military talent... Raytheon is a provider of SkillBridge/HOH Fellowship opportunities...". That's about the role. Could be "About the role". We'll put that as prose. - Responsibilities: The "What You Will Do" section lists key responsibilities. That's a list. So we can have

  Responsibilities

  then
  • each bullet. - Requirements: The posting includes "U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required..." Also "Security Clearance Type: None/Not Required". Also "Must be eligible to participate in Fellowship per DoD Instruction 1322.29..." etc. Those are eligibility requirements for SkillBridge. Also "Minimum a Master’s degree..." etc are qualifications. The distinction between Requirements and Qualifications can be fuzzy. We'll treat "Requirements" as citizenship, security clearance, SkillBridge eligibility requirements. "Qualifications" as education/experience requirements and preferred qualifications. - Skills: maybe we can include "Skills" section for preferred skills like analytical modeling, programming, FEA/CFD, etc. But we need to ensure we only create if there is real specific content. There is a list of "Qualifications We Prefer" which includes skills. Could put under Skills. - Benefits: The posting says "What We Offer" includes values, relocation non-eligible, etc. Also mentions that as SkillBridge participant, you will not receive compensation or benefits. So there is no actual benefits offered to the fellow. The posting says "Relocation Non-Eligible – Relocation assistance not available". Also mentions that as SkillBridge participant, you will not receive any form of compensation and will not receive benefits. So there is no benefit section to include (since they say no benefits). We should not create a Benefits section if it's just stating no benefits. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that there is no compensation/benefits for SkillBridge participants. That is stating them (i.e., stating that there is no compensation/benefits). Should we include a Benefits section with that info? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state that there is no compensation/benefits. So we could include a Benefits section with that statement. However, the instruction also says "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Saying "no compensation/benefits" is not filler; it's specific. So we could include a Benefits section with a

    stating that as a SkillBridge fellow, you will not receive compensation or benefits, and relocation assistance not available. - Pay: The posting says "SkillBridge fellows will not be eligible for any compensation during their fellowship, as they will continue to receive all military pay and benefits." So there is no pay from RTX. That is stating pay: none. Should we include Pay section? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state that there is no compensation. So we could include Pay section with that info. However, we might combine Pay and Benefits? Better to follow instruction: include Pay if stated. So we will include Pay section with statement that no compensation from RTX; fellows continue to receive military pay. - Schedule: The posting does not mention schedule (e.g., full-time, part-time, hours). It mentions Onsite role type. No schedule details. So we should not create Schedule section. - Also we have "Location" and "Date Posted" etc. Those are metadata; we can fold into a short

    or drop. 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

    with date posted and location maybe. - Also there is a line: "Position Role Type: Onsite". That's role type. Could be part of About the role or metadata. - Also there is a line: "We are RTX #SkillBridge". That's maybe a tagline. - Also there is a line: "As part of our commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of the interview process in-person at one of our office locations, regardless of whether the role is designated as on-site, hybrid or remote." That's maybe boilerplate but it's about interview process; could be considered application instructions? It's not exactly application instructions but could be considered part of process. The instruction says remove application instructions. This is about interview process; maybe we should remove as it's not substantive about the role? It's somewhat generic. I'd consider removing. - Also there is a line: "IAW DoDI 1322.29, as a SkillBridge participant, you will not be an RTX employee and will remain under the administrative control of your military chain of command. Therefore, you will not receive any form of compensation for your work. Additionally, any type of benefits that the company offers its regular employees such as, but not limited to, health benefits, holiday pay, vacation pay, sick leave, and retirement benefits, will not be available to SkillBridge participants." That's already covered. - Also there is a line: "RTX anticipates the application window closing approximately 40 days from the date the notice was posted. However, factors such as candidate flow and business necessity may require RTX to shorten or extend the application window." That's about application window; could be considered application instructions; maybe remove. - Also there is EEO statement: remove. - Also there is "Privacy Policy and Terms: Click on this link to read the Policy and Terms" - remove. Thus we will produce sections: - About the role (prose summarizing the introductory paragraphs about Raytheon, SkillBridge, mission, veteran talent, etc.) - Responsibilities (list of key responsibilities from "What You Will Do"). - Requirements (citizenship, security clearance, SkillBridge eligibility requirements). Could be a list. - Qualifications (education/experience minimum requirements). Could be a list. - Skills (preferred qualifications/skills). Could be a list. - Pay (statement about no compensation from RTX, fellows receive military pay). - Benefits (statement about no benefits, relocation not eligible). We need to ensure we don't create sections with filler. All have specific content. We must not repeat job title as heading. No job title given explicitly; but we can ignore. We must output only HTML fragment, no /, no markdown. Let's craft. First, maybe a short metadata paragraph: "Date Posted: 2026-09-17 | Location: East Hartford, CT (US-CT-EAST HARTFORD-RTRC K ~ 411 Silver Ln)". Could be a

    . Then sections. We'll need to preserve all substantive information. Let's extract details. About the role: The posting includes: "At Raytheon, we know and value the strategic and tactical talents that only veterans can offer. Our military veterans work across all disciplines, lead our businesses, engineer our products, and lead our supply chain. As a US military veteran, you are uniquely qualified to work at Raytheon. We are seeking ambitious military talent who will bring the skills and experience gained while wearing the uniform to help us create trusted, creative solutions for a safer, more connected world, join us. Your next MISSION starts with Raytheon. Raytheon is a provider of SkillBridge/HOH Fellowship opportunities for transitioning service members to gain an in-depth understanding of the aerospace and defense business from some of the most respected leaders and engineers in the industry. SkillBridge fellows will not be eligible for any compensation during their fellowship, as they will continue to receive all military pay and benefits. Upon successful completion of this fellowship, you will be well prepared and encouraged to apply for open positions listed on our careers page." Also "We are RTX #SkillBridge". Might include. We'll combine into a few paragraphs. Responsibilities: list from "Key responsibilities include:" then bullet points. Let's copy them exactly: - Perform high‑fidelity and reduced‑order computational modeling of single‑ and two‑phase flows, including interfacial physics, phase change, and transient behavior - Develop and integrate multi‑physics simulations coupling thermal, fluid, structural, and thermomechanical responses - Create advanced computational cooling strategies for high‑heat‑flux electronics using microchannels, jet impingement, passive spreaders, heterogeneous integration, and phase‑change materials - Conduct design‑space exploration using machine learning, AI‑assisted modeling, uncertainty quantification, and other advanced optimization techniques - Perform parametric and topology optimization of thermal components such as heat sinks, cold plates, heat exchangers, and integrated flow channels - Model novel systems for next‑generation engines, space propulsion, undersea propulsion, waste‑heat recovery, power generation, and cryogenic cooling - Predict device reliability using thermomechanical modeling - Support (as a secondary responsibility) experimental efforts such as thermal testing, two‑phase flow loops, additively manufactured coupon evaluation, interface characterization, and system demonstrations We'll put each as

  • . Requirements: includes: - U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract. - Security Clearance Type: None/Not Required - Security Clearance Status: Not Required - Must be eligible to participate in Fellowship per DoD Instruction 1322.29. - Must be projected to receive an honorable discharge from the military. - Must have all TAP and transition requirements completed prior to the start date. - Must receive approval from Unit Commander or O4+ in the chain of command. - Must be located within a commutable distance or willing/approved to relocate to the job location. We could combine some. Also note "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" but we already have citizenship required. We'll make a list. Qualifications (minimum): - Minimum a Master’s degree in Mechanical, Aerospace, Chemical, or Nuclear Engineering and minimum 3 years experience - OR Ph.D. in Mechanical, Aerospace, Chemical, or Nuclear Engineering and no formal experience - Minimum 1 year research experience in Heat Transfer or Thermodynamics We'll list as items. Skills (preferred): list from "Qualifications We Prefer": - Strong analytical modeling and programming skills - General understanding of FEA and CFD methods - Demonstrated experience publishing or presenting technical research - Exceptional computational modeling capability in multi‑physics, multi‑phase, and interfacial phenomena - Demonstrated ability to model complex geometry and highly coupled physical systems - Ability to manage uncertainty, formulate problems from ill-defined needs, and identify when additional SME expertise is required - Excellent communication skills and ability to foster strong technical collaborations - Experience developing or supporting externally funded research programs