Software Development Engineer (Seattle) - Internship 2027
About the role
thenwith that content. - Why intern at Qumulo: maybe could be part of About the role? But we have separate sections: maybe "About Qumulo" later. The posting includes "Why intern at Qumulo:" which is like benefits/culture. Could map to Benefits? But Benefits section should be only if posting actually states them. It mentions: "Qumulo blends the flexibility of a startup with the security of a mature and profitable organization. Here you’ll work closely with a small team...". That's more about culture/benefits. Could be placed under Benefits? But we also have explicit "What we're looking for:" which is requirements/qualifications/skills. - "As a Software Engineering Intern at Qumulo, you will:" list of duties. That's Responsibilities. - "What we're looking for:" list of requirements: ability to write well-factored code, strong grasp of algorithms..., at least one class..., willingness to work collaboratively..., ability to reside in Seattle..., pursuing BS/BA..., must be authorized to work in US. That's Requirements/Qualifications/Skills. - "The base pay for this intern role is USD $100,000 annual base salary (prorated to $1,900 per week for the duration of your internship), plus relocation, travel, and local transit support as applicable." That's Pay and maybe Benefits (relocation, travel, local transit). Also schedule: "This role is hybrid, based at our downtown Seattle HQ, targeting 3 days a week in-office." That's Schedule. - "About Qumulo:" paragraph about company. Could be About the role? Actually we already have About the role. Could treat as About Qumulo but not required heading. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (already), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. We must not repeat job title as heading. No Job ID. We must not include boilerplate like EEO, privacy, etc. We must not create sections with filler like "commensurate with experience". We have actual content for Pay, Schedule, Benefits (relocation, travel, local transit). Also maybe Benefits could include "relocation, travel, and local transit support". That's specific. Qualifications: maybe education requirement: pursuing BS/BA in CS or CE or equivalent experience, available for full-time internship during Winter, Spring, or Summer 2027. Must be authorized to work in US. That's qualifications. Skills: maybe ability to write well-factored code, strong grasp of algorithms and data structures, experience in distributed systems, database concepts, concurrent programming, or OS concepts, at least one class/internship/personal project using C, C++, Rust, Java, or Go, willingness to work collaboratively, ability to reside in Seattle. Those could be skills. Requirements: maybe overlapping. But we can split: Requirements: ability to reside in Seattle, must be authorized to work in US, pursuing BS/BA, available full-time internship. Qualifications: education etc. Skills: technical skills. We need to avoid duplication. Let's extract distinct bullet points. From "What we're looking for:" bullet list: - Ability to write well-factored and well-tested code - Strong grasp of algorithms and data structures, with some experience in distributed systems, database concepts, concurrent programming, or operating systems concepts - At least one class, internship or personal project using C, C++, Rust, Java, or Go - Willingness to work collaboratively with a team to solve complex problems - Ability to reside in Seattle for the duration of your internship - Pursuing a BS or BA in Computer Science or Computer Engineering or equivalent experience, available for a full-time internship during Winter, Spring, or Summer 2027 - Must be authorized to work in the United States. We are unable to provide visa sponsorship or transfer. That's 7 bullets. Now "As a Software Engineering Intern at Qumulo, you will:" list: - Collaborate with team members on design, code reviews, and pair programming - Collaborate with team members and area leads on architecture and design of new/updated features - Work directly with a team on core product features; not on a siloed intern project - Contribute to feature development and testing using C, Rust and Python - Define and implement customer-facing features and internal improvements - Help debug and fix test failures and product or service issues That's responsibilities. Now "Why intern at Qumulo:" paragraph: talk about flexibility, small team, mentors, opinions expected, disagreement normal, hands-on experience, value quality, correctness, performance, architecture public, work will show up in product. That's more like Benefits/culture. Could be Benefits. Also "About Qumulo:" paragraph about company description, customers, etc. Could be omitted or maybe part of About the role? But we already have About the role. Could treat as About Qumulo but not required heading. Probably we can omit because not needed. Now Pay: base pay $100k annual, prorated $1,900 per week, plus relocation, travel, local transit support as applicable. Schedule: hybrid, based at downtown Seattle HQ, targeting 3 days a week in-office. Now Benefits: we could include relocation, travel, local transit support as benefits. Also maybe the "flexibility of a startup with security of mature organization" etc. But we should only include if posting actually states them. It does state those benefits in "Why intern at Qumulo:" and also the relocation etc. So we can create Benefits section with those points. We need to avoid filler like "commensurate with experience". Not present. Now we need to output HTML fragment only. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
We must ensure we don't create empty sections. All have content. Now we need to decide what goes into each. Let's assign: About the role: paragraph from "About the Role:" (first paragraph after that heading). That is: "Joining us for our Summer 2027 internship program, you'd learn and work across our distributed storage engine and the services that help customers store, manage, and protect their data, under the guidance of experienced senior engineers. This includes a fault-tolerant block layer that erasure-codes and distributes data beneath the file system, a transactional file system where aggregates roll up as they change so a query across billions of files answers in real time instead of walking a tree, and that same machinery drives quotas, capacity trends, snapshot policy, multiple access protocols, plus replication and backup - all running in userspace. All of which makes Qumulo a distributed operating system problem: scheduling, memory hierarchy, protection, and concurrency. We're AI-forward and specific about what that means. You will learn to use agents to help write code while developing your engineering judgment to ensure every design decision is correct, because nothing ships that isn't right." We'll put that in. Responsibilities: the list under "As a Software Engineering Intern at Qumulo, you will:" (six items). Use
- . Requirements: maybe the items about authorization, residency, availability, pursuing degree. Let's pick: "Ability to reside in Seattle for the duration of your internship", "Must be authorized to work in the United States. We are unable to provide visa sponsorship or transfer.", "Pursuing a BS or BA in Computer Science or Computer Engineering or equivalent experience, available for a full-time internship during Winter, Spring, or Summer 2027". That's three. Qualifications: maybe education requirement? But we already used that. Could treat Qualifications as "Pursuing a BS or BA in Computer Science or Computer Engineering or equivalent experience". But we already used that. Maybe we can shift: Requirements: technical baseline? Hmm. Better: Use Requirements for the mandatory eligibility items (residency, work authorization, availability). Qualifications for education/degree. Skills for technical abilities. Thus: Requirements: - Ability to reside in Seattle for the duration of your internship - Must be authorized to work in the United States. We are unable to provide visa sponsorship or transfer. - Available for a full-time internship during Winter, Spring, or Summer 2027 Qualifications: - Pursuing a BS or BA in Computer Science or Computer Engineering or equivalent experience Skills: - Ability to write well-factored and well-tested code - Strong grasp of algorithms and data structures, with some experience in distributed systems, database concepts, concurrent programming, or operating systems concepts - At least one class, internship or personal project using C, C++, Rust, Java, or Go - Willingness to work collaboratively with a team to solve complex problems Benefits: - Qumulo blends the flexibility of a startup with the security of a mature and profitable organization - Work closely with a small team of smart, capable engineers who will serve as mentors - Opinions are expected, disagreement is normal, and you'll get hands-on experience taking projects from ideation to release - We value quality, correctness, and performance - Our architecture, protocols, and patents are public, so you can read how most of this works before you talk to us - The work you do during your internship will actually show up in the product - Relocation, travel, and local transit support as applicable Pay: - Base pay: USD $100,000 annual base salary (prorated to $1,900 per week for the duration of your internship), plus relocation, travel, and local transit support as applicable. But we already included relocation etc in Benefits; we might duplicate. Better to keep Pay just salary, and Benefits include relocation etc. So Pay: "Base pay: USD $100,000 annual base salary (prorated to $1,900 per week for the duration of your internship)." Benefits: list includes relocation, travel, local transit support, plus the cultural points. Schedule: - This role is hybrid, based at our downtown Seattle HQ, targeting 3 days a week in-office. Now ensure we didn't miss any substantive info: The "Why intern at Qumulo:" paragraph also mentions "Here you’ll work closely with a small team of smart, capable engineers who will serve as your mentors." included. "Opinions are expected, disagreement is normal, and you'll get hands-on experience taking projects from ideation to release." included. "We value quality, correctness, and performance." included. "Our architecture, protocols, and patents are public, so you can read how most of this works before you talk to us - and we’re small enough that the work you do during your internship will actually show up in the product." included. Also "As part of our culture we believe diversity drives innovation." That's a statement but maybe could be included in Benefits. It's a substantive line. Let's add: "As part of our culture we believe diversity drives innovation." Also "Equal Opportunity Employer" boilerplate we