Summer 2027 Internship - DevOps Engineer (Hybrid) - 30229
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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 based on content.
We have:
- About the role: maybe a short paragraph about the role: "Enlighten is seeking a DevOps Engineer Intern. The ideal candidate will enter their senior year or final semester of college after the summer 2027 internship. Will work in a fast-paced, small business environment, maintaining and updating big data systems automation and cloud management tooling. Will work a hybrid schedule with some on-site work with the team." That's substantive.
- Responsibilities: list of duties: "Assist with the maintenance and upkeep of distributed computing systems and configuration management automation. Scripting in languages such as Python and Bash for automation and development of product features. Troubleshooting customer reported issues in applications and providing support. Engage in quality assurance testing. Other duties as assigned."
- Requirements: Minimum Qualifications: includes clearance requirement, US citizenship, high school diploma, working towards Bachelor's degree with at least 60% credits, degree in Computer Science or related field, Python software development, Bash scripting, familiarity with Git or other version control software, familiarity with AWS or other cloud platforms, familiarity with Kubernetes or other containerization technologies, comfortable working on Linux command line, self-motivated, ability to multi-task, problem solving skills, must be able to work in hybrid environment, spending average 1-2 days per week at Grapevine, TX office, flexibility essential.
- Preferred Requirements: "A current Secret level clearance is desired. Prior technical internship experience is a big plus. A Security+ certification is a plus, but not required."
- Benefits: "We have many more additional great benefits/perks that you can find on our website at www.eitccorp.com [eitccorp.com]." That's vague but mentions benefits exist; we could include a Benefits section with a link? The rule: include a section ONLY when posting has real, specific content for it. This is somewhat generic but still mentions benefits/perks and a website. Might be considered real content? It says "many more additional great benefits/perks that you can find on our website". Not specific. Might be considered filler? The rule says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". This is not exactly those but still vague. However, we could include a Benefits section with a
that says "See website for benefits and perks." That might be acceptable. But we need to decide.
- Pay: "Anticipated Hourly Range: $22.00 - $30.00." plus explanation about good faith estimate etc. That's specific pay info. So we should include Pay section.
- Schedule: "Will work a hybrid schedule with some on-site work with the team." Also "Must be able to work in a hybrid environment, spending an average of 1-2 days per week at our Grapevine, TX office. Flexibility is essential to adapt to schedule changes as needed." That's schedule info. So we can include Schedule section.
We need to avoid duplication. Also we need to not repeat job title as heading.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
...
Responsibilities
- ...
...
Minimum Qualifications
maybe we combine Requirements and Qualifications? The rules list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Qualifications for minimum qualifications, and maybe Skills for preferred? But we have both minimum qualifications and preferred requirements. Could use Requirements for minimum qualifications, and Skills for preferred? Or we could have Requirements (minimum) and Preferred (maybe as part of Requirements?). The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory list. We can choose appropriate headings.
We need to preserve all substantive info. So we need to include both minimum qualifications and preferred requirements. Could put them under Requirements (minimum) and then a separate subsection for Preferred? But we cannot create subheadings besides h3? We could use for Requirements and then within that have
for minimum and
for preferred. Or we could have two sections: Requirements (minimum) and Preferred Qualifications (maybe under Skills). But we need to avoid too many thin sections. Perhaps combine them into one Requirements section with both minimum and preferred, labeling inside paragraphs.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe we have About the role, Responsibilities, Requirements (including both minimum and preferred), Pay, Schedule, Benefits. That's 6 sections.
Let's craft:
About the role: paragraph summarizing role and hybrid work.
Responsibilities: list.
Requirements: we need to include minimum qualifications and preferred requirements. We'll write a paragraph for minimum qualifications (list as
) and then a paragraph for preferred (maybe also ). But we need to use - for any list of duties/requirements/benefits. So we can have two lists: one for Minimum Qualifications, one for Preferred Requirements. That's okay.
Pay: paragraph with hourly range and note.
Schedule: paragraph describing hybrid schedule, average 1-2 days onsite, flexibility.
Benefits: paragraph referencing website for benefits/perks.
We must not include boilerplate like "We recognize that the most effective environment..." etc. That's part of About the role? Actually that is generic company description; we might include it in About the role? The About the role section should be about the role, not company. But we could include a brief company overview if it's substantive. However, the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The company description may be considered minor metadata? It's not about the role. But we might keep it in About the role? The role description includes "Enlighten is seeking a DevOps Engineer Intern..." plus hybrid work. The earlier paragraph about Enlighten being a Top Workplace etc is company overview; could be considered boilerplate? It's not navigation/legal/EEO, but it's generic marketing. Might be okay to include as part of About the role? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that company overview if it's substantive. It's not duplicated lines. It's about the company. Could be considered part of About the role? Might be okay.
But we need to avoid duplication: The posting includes "Enlighten, honored as a Top Workplace from USA Today, is a leader in big data solution development and deployment, with expertise in cloud-based services, software and systems engineering, cyber capabilities, and data science. Enlighten provides continued innovation and proactivity in meeting our customers’ greatest challenges. We recognize that the most effective environment for your projects doesn’t always look the same. Our hybrid work approach ensures that you can make lasting relationships with your team and collaborate in-person to get the job done—while having the flexibility to work from home when needed to achieve focused results." That's generic company info plus hybrid work approach. We could incorporate hybrid work approach into About the role or Schedule. The hybrid work approach is relevant to schedule. So we could put that in Schedule section.
Thus About the role could be just: "Enlighten is seeking a DevOps Engineer Intern. The ideal candidate will enter their senior year or final semester of college after the summer 2027 internship. Will work in a fast-paced, small business environment, maintaining and updating big data systems automation and cloud management tooling." That's from the job description.
We'll keep the company overview maybe as a brief intro before sections? But we need to output only HTML fragment; we could include a
at top with that company overview. However, the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having a leading paragraph without heading. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid a leading paragraph. But to be safe, we could wrap company overview in a
before any headings. That's acceptable.
Let's decide to include a leading
with company overview (Top Workplace etc). Then sections.
Now craft content.
Company overview paragraph:
"Enlighten, honored as a Top Workplace from USA Today, is a leader in big data solution development and deployment, with expertise in cloud-based services, software and systems engineering, cyber capabilities, and data science. Enlighten provides continued innovation and proactivity in meeting our customers’ greatest challenges."
We could also include hybrid work approach there, but we might move to Schedule.
Now About the role paragraph:
"Enlighten is seeking a DevOps Engineer Intern. The ideal candidate will enter their senior year or final semester of college after the summer 2027 internship. Will work in a fast-paced, small business environment, maintaining and updating big data systems automation and cloud management tooling."
Now Responsibilities list:
- Assist with the maintenance and upkeep of distributed computing systems and configuration management automation.
- Scripting in languages such as Python and Bash for automation and development of product features.
- Troubleshooting customer reported issues in applications and providing support.
- Engage in quality assurance testing.
- Other duties as assigned.
Now Requirements (minimum) list:
We need to include: Clearance Requirement: Must obtain and maintain a U.S. Government Security Clearance, but not required on day one; U.S. Citizenship required. High School Diploma or equivalent and must be working towards a Bachelor's degree with at least 60% of the required credits completed. Degree must be in Computer Science or related field. Python software development. Bash scripting. Familiarity with Git or other version control software. Familiarity with AWS or other cloud platforms. Familiarity with Kubernetes or other containerization technologies. Comfortable working on a Linux command line. Self-motivated – a strong desire to find and address gaps in execution or capability without explicit direction. Ability to multi-task and prioritize open issues/ tickets accordingly. Problem solving skills and ability to review information and compile data appropriately as needed. Must be able to work in a hybrid environment, spending an average of 1-2 days per week at our Grapevine, TX office. Flexibility is essential to adapt to schedule changes as needed.
We could split some into list items.
Now Preferred
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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 based on content. We have: - About the role: maybe a short paragraph about the role: "Enlighten is seeking a DevOps Engineer Intern. The ideal candidate will enter their senior year or final semester of college after the summer 2027 internship. Will work in a fast-paced, small business environment, maintaining and updating big data systems automation and cloud management tooling. Will work a hybrid schedule with some on-site work with the team." That's substantive. - Responsibilities: list of duties: "Assist with the maintenance and upkeep of distributed computing systems and configuration management automation. Scripting in languages such as Python and Bash for automation and development of product features. Troubleshooting customer reported issues in applications and providing support. Engage in quality assurance testing. Other duties as assigned." - Requirements: Minimum Qualifications: includes clearance requirement, US citizenship, high school diploma, working towards Bachelor's degree with at least 60% credits, degree in Computer Science or related field, Python software development, Bash scripting, familiarity with Git or other version control software, familiarity with AWS or other cloud platforms, familiarity with Kubernetes or other containerization technologies, comfortable working on Linux command line, self-motivated, ability to multi-task, problem solving skills, must be able to work in hybrid environment, spending average 1-2 days per week at Grapevine, TX office, flexibility essential. - Preferred Requirements: "A current Secret level clearance is desired. Prior technical internship experience is a big plus. A Security+ certification is a plus, but not required." - Benefits: "We have many more additional great benefits/perks that you can find on our website at www.eitccorp.com [eitccorp.com]." That's vague but mentions benefits exist; we could include a Benefits section with a link? The rule: include a section ONLY when posting has real, specific content for it. This is somewhat generic but still mentions benefits/perks and a website. Might be considered real content? It says "many more additional great benefits/perks that you can find on our website". Not specific. Might be considered filler? The rule says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". This is not exactly those but still vague. However, we could include a Benefits section with a
that says "See website for benefits and perks." That might be acceptable. But we need to decide. - Pay: "Anticipated Hourly Range: $22.00 - $30.00." plus explanation about good faith estimate etc. That's specific pay info. So we should include Pay section. - Schedule: "Will work a hybrid schedule with some on-site work with the team." Also "Must be able to work in a hybrid environment, spending an average of 1-2 days per week at our Grapevine, TX office. Flexibility is essential to adapt to schedule changes as needed." That's schedule info. So we can include Schedule section. We need to avoid duplication. Also we need to not repeat job title as heading. We need to output only HTML fragment, no /, no markdown fences. We'll structure:
About the role
...
Responsibilities
- ... ...
Minimum Qualifications
maybe we combine Requirements and Qualifications? The rules list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Qualifications for minimum qualifications, and maybe Skills for preferred? But we have both minimum qualifications and preferred requirements. Could use Requirements for minimum qualifications, and Skills for preferred? Or we could have Requirements (minimum) and Preferred (maybe as part of Requirements?). The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory list. We can choose appropriate headings.
We need to preserve all substantive info. So we need to include both minimum qualifications and preferred requirements. Could put them under Requirements (minimum) and then a separate subsection for Preferred? But we cannot create subheadings besides h3? We could use for Requirements and then within that have
for minimum and
for preferred. Or we could have two sections: Requirements (minimum) and Preferred Qualifications (maybe under Skills). But we need to avoid too many thin sections. Perhaps combine them into one Requirements section with both minimum and preferred, labeling inside paragraphs. But the rule: "Prefer a few substantive sections over many thin ones." So maybe we have About the role, Responsibilities, Requirements (including both minimum and preferred), Pay, Schedule, Benefits. That's 6 sections. Let's craft: About the role: paragraph summarizing role and hybrid work. Responsibilities: list. Requirements: we need to include minimum qualifications and preferred requirements. We'll write a paragraph for minimum qualifications (list as
- ) and then a paragraph for preferred (maybe also
- for any list of duties/requirements/benefits. So we can have two lists: one for Minimum Qualifications, one for Preferred Requirements. That's okay.
Pay: paragraph with hourly range and note.
Schedule: paragraph describing hybrid schedule, average 1-2 days onsite, flexibility.
Benefits: paragraph referencing website for benefits/perks.
We must not include boilerplate like "We recognize that the most effective environment..." etc. That's part of About the role? Actually that is generic company description; we might include it in About the role? The About the role section should be about the role, not company. But we could include a brief company overview if it's substantive. However, the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The company description may be considered minor metadata? It's not about the role. But we might keep it in About the role? The role description includes "Enlighten is seeking a DevOps Engineer Intern..." plus hybrid work. The earlier paragraph about Enlighten being a Top Workplace etc is company overview; could be considered boilerplate? It's not navigation/legal/EEO, but it's generic marketing. Might be okay to include as part of About the role? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that company overview if it's substantive. It's not duplicated lines. It's about the company. Could be considered part of About the role? Might be okay. But we need to avoid duplication: The posting includes "Enlighten, honored as a Top Workplace from USA Today, is a leader in big data solution development and deployment, with expertise in cloud-based services, software and systems engineering, cyber capabilities, and data science. Enlighten provides continued innovation and proactivity in meeting our customers’ greatest challenges. We recognize that the most effective environment for your projects doesn’t always look the same. Our hybrid work approach ensures that you can make lasting relationships with your team and collaborate in-person to get the job done—while having the flexibility to work from home when needed to achieve focused results." That's generic company info plus hybrid work approach. We could incorporate hybrid work approach into About the role or Schedule. The hybrid work approach is relevant to schedule. So we could put that in Schedule section. Thus About the role could be just: "Enlighten is seeking a DevOps Engineer Intern. The ideal candidate will enter their senior year or final semester of college after the summer 2027 internship. Will work in a fast-paced, small business environment, maintaining and updating big data systems automation and cloud management tooling." That's from the job description. We'll keep the company overview maybe as a brief intro before sections? But we need to output only HTML fragment; we could include a
at top with that company overview. However, the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having a leading paragraph without heading. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid a leading paragraph. But to be safe, we could wrap company overview in a
before any headings. That's acceptable. Let's decide to include a leading
with company overview (Top Workplace etc). Then sections. Now craft content. Company overview paragraph: "Enlighten, honored as a Top Workplace from USA Today, is a leader in big data solution development and deployment, with expertise in cloud-based services, software and systems engineering, cyber capabilities, and data science. Enlighten provides continued innovation and proactivity in meeting our customers’ greatest challenges." We could also include hybrid work approach there, but we might move to Schedule. Now About the role paragraph: "Enlighten is seeking a DevOps Engineer Intern. The ideal candidate will enter their senior year or final semester of college after the summer 2027 internship. Will work in a fast-paced, small business environment, maintaining and updating big data systems automation and cloud management tooling." Now Responsibilities list: - Assist with the maintenance and upkeep of distributed computing systems and configuration management automation. - Scripting in languages such as Python and Bash for automation and development of product features. - Troubleshooting customer reported issues in applications and providing support. - Engage in quality assurance testing. - Other duties as assigned. Now Requirements (minimum) list: We need to include: Clearance Requirement: Must obtain and maintain a U.S. Government Security Clearance, but not required on day one; U.S. Citizenship required. High School Diploma or equivalent and must be working towards a Bachelor's degree with at least 60% of the required credits completed. Degree must be in Computer Science or related field. Python software development. Bash scripting. Familiarity with Git or other version control software. Familiarity with AWS or other cloud platforms. Familiarity with Kubernetes or other containerization technologies. Comfortable working on a Linux command line. Self-motivated – a strong desire to find and address gaps in execution or capability without explicit direction. Ability to multi-task and prioritize open issues/ tickets accordingly. Problem solving skills and ability to review information and compile data appropriately as needed. Must be able to work in a hybrid environment, spending an average of 1-2 days per week at our Grapevine, TX office. Flexibility is essential to adapt to schedule changes as needed. We could split some into list items. Now Preferred
- ). But we need to use