Product Security Intern
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. Let's parse. Compensation: $28 per hour => Pay section. Location: Omaha, NE => maybe part of Schedule? Actually location not a heading; we can embed in a short
maybe under About the role? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location can be a short
maybe after heading? Could be part of About the role? Probably we can include a
with location and compensation? But compensation is separate Pay section. We need sections: About the role (intro paragraph). Responsibilities (list of duties). Requirements (maybe "Who You Are And What You Need" includes qualifications). Qualifications maybe overlapping. Skills maybe list of skills. Benefits (list of perks). Pay (compensation). Schedule (maybe mention work hours: Monday-Friday 8am-5pm, no weekend hours). Also mention full-time onsite for summer. We must not create sections with filler like "commensurate with experience". We have actual content. Let's extract. About the role: The paragraph after "The Job": "As a Product Security Intern, you'll spend the summer helping protect a platform construction professionals rely on every day. You'll work alongside experienced security engineers, learn how security gets built into the software development lifecycle, and get hands-on with the same tools and workflows our Product Security team uses to keep Buildertrend's customers safe. By the end of the internship, you'll have sharpened your security skills, gained real-world experience with application and cloud security, and contributed to work that protects the way the world builds." That's good. Responsibilities: bullet list under "What You Will Do". Many items separated by periods but we can treat each sentence as a list item. We'll need to split. List items: - Assist in running and triaging results from SAST (Static Application Security Testing) and DAST (Dynamic Application Security Testing) scanning tools under the guidance of senior security engineers. - Help investigate and validate security findings, distinguishing true positives from false positives and documenting confirmed vulnerabilities. - Support the review of authentication and authorization implementations, including OAuth 2.0 flows, token handling and role-based access controls. - Assist with cloud security posture reviews in GCP and Azure, including IAM policy analysis, storage access controls and network configuration checks. - Contribute to maintaining and improving security scanning pipelines integrated into CI/CD workflows. - Participate in secure code reviews alongside security engineers, learning to identify common vulnerability patterns (injection, XSS, insecure deserialization, broken access control). - Help maintain and update internal security documentation, runbooks and vulnerability tracking records. - Support dependency and software composition analysis (SCA) scanning to identify known vulnerabilities in third-party libraries. - Assist in basic penetration testing activities and security assessments as directed. - Participate in team meetings, incident reviews and security-focused sprint activities. - Work on an assigned security project with regular check-ins and progress updates to mentors. - Use AI-assisted development tools, including Claude, to accelerate security analysis, research and problem-solving while still being responsible and accountable for the quality and accuracy of your work. That's responsibilities. Requirements: maybe "Who You Are And What You Need" includes qualifications and skills. We can split into Requirements (education, availability) and Skills (technical). But we can also combine. The instruction: prefer few substantive sections over many thin ones. We could have Requirements covering education, availability, interest, experience with AI tools, foundational understanding, etc. Skills could list specific technical skills: programming languages, auth concepts, cloud platforms, Linux, networking, security tools, etc. Benefits: list of perks. Let's extract Requirements: - Currently pursuing a bachelor’s or master’s degree in computer science, cybersecurity, information security, mathematics, physics, engineering or a related field. - Available to work full-time onsite at the Buildertrend HQ in Omaha, NE, for the full summer. - Strong interest in product security and a desire to grow your skills. - Experience using AI tools (such as Claude, GitHub Copilot or similar) in coursework or personal projects, or a strong interest in learning how to use them effectively. - Foundational understanding of web application security concepts (OWASP Top 10) and at least one programming or scripting language (e.g., Python, C#, JavaScript, Bash). - Basic understanding of authentication and authorization concepts (OAuth, SAML, JWTs, session management), plus exposure to or interest in cloud platforms (GCP) and their security models. - Familiarity with Linux/Unix command-line environments and networking fundamentals (TCP/IP, DNS, HTTP). - Interest in learning security tools and techniques, including vulnerability scanners, proxy tools (e.g., Burp Suite) and CI/CD security integrations. - Participation in CTF competitions, security-related clubs, or relevant coursework (computer networking, application security, operating systems or cryptography) is a plus, any level helps. - Strong analytical and problem-solving skills, clear written and verbal communication, and comfortable working both independently and as part of a team. - Eager to learn, ask questions and apply feedback constructively. That's many items; could be Requirements. Skills: maybe we can extract specific technical skills: programming languages, auth concepts, cloud platforms, Linux, networking, vulnerability scanners, proxy tools, CI/CD, AI tools. But many overlap with Requirements. To avoid thin sections, maybe we combine Requirements and Skills into one "Requirements" section that includes both education and skills. But we have separate headings allowed; we could still have Requirements and Skills but ensure each has substantive content. Let's try: Requirements: education, availability, interest, AI tools experience, foundational understanding, basic auth understanding, Linux familiarity, interest in learning tools, participation in CTF etc., analytical skills, communication, eager to learn. Skills: programming languages (Python, C#, JavaScript, Bash), auth concepts (OAuth, SAML, JWTs, session management), cloud platforms (GCP, Azure), security tools (SAST, DAST, SCA, Burp Suite, vulnerability scanners, CI/CD integrations), AI-assisted tools (Claude), networking fundamentals (TCP/IP, DNS, HTTP). That seems substantive. Benefits: list from "We Are Giving You": Office environment with all the perks of a high-energy tech company. Free daily lunches at the office. Summer housing at a local university. Onsite fitness center. No weekend hours – just work hard Monday-Friday between 8 a.m. and 5 p.m. Monthly events to connect other interns and Buildertrend employees. Also maybe mention "We Are Giving You" includes those. Pay: $28 per hour. Schedule: maybe we can note "full-time onsite ... for the full summer" and "No weekend hours – just work hard Monday-Friday between 8 a.m. and 5 p.m." That's schedule info. Could be separate Schedule section. But we already used availability in Requirements. However schedule details about hours can go to Schedule. Let's craft. We must not repeat job title as heading. We'll not. We'll output HTML fragment with headings
and content.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
$28 per hour
Schedule
Full‑time onsite at Buildertrend HQ in Omaha, NE for the summer; Monday‑Friday, 8 a.m.–5 p.m., no weekend hours.
Make sure we preserve all substantive information. Let's verify we didn't lose any. From About the role we captured the paragraph. Responsibilities list includes all items. Requirements list: need to include all items from "Who You Are And What You Need". Let's list them: - Currently pursuing a bachelor’s or master’s degree in computer science, cybersecurity, information security, mathematics, physics, engineering or a related field. - Available to work full-time onsite at the Buildertrend HQ in Omaha, NE, for the full summer. - Strong interest in product security and a desire to grow your skills. - Experience using AI tools (such as Claude, GitHub Copilot or similar) in coursework or personal projects, or a strong interest in learning how to use them effectively. - Foundational understanding of web application security concepts (OWASP Top 10) and at least one programming or scripting language (e.g., Python, C#, JavaScript, Bash). - Basic understanding of authentication and authorization concepts (OAuth, SAML, JWTs, session management), plus exposure to or interest in cloud platforms (GCP) and their security models. - Familiarity with Linux/Unix command-line environments and networking fundamentals (TCP/IP, DNS, HTTP). - Interest in learning security tools and techniques, including vulnerability scanners, proxy tools (e.g., Burp Suite) and CI/CD security integrations. - Participation in CTF competitions, security-related clubs, or relevant coursework (computer networking, application security, operating systems or cryptography) is a plus, any level helps. - Strong analytical and problem-solving skills, clear written and verbal communication, and comfortable working both independently and as part of a team. - Eager to learn, ask questions and apply feedback constructively. We'll put each as