Software Development Engineer (New Grad / Entry Level)
Qumulo · Seattle, WA · 3 wk ago
Hybrid$110k–$140k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading. Use
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate like EEO, legal, etc. Preserve all substantive info.
We need to parse the posting.
Key sections:
- About the Role: paragraph describing role.
- Why join Qumulo: maybe part of About? Could be part of About the role? But we can treat as part of About the role or separate? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
About the Role: (the paragraph after "About the Role:").
Then "Why join Qumulo:" maybe part of Benefits? Actually it's about culture, could be part of About the role or maybe we can treat as part of About the role as well. But we have separate Benefits & Perks later.
Then "As a Software Engineer at Qumulo, you will:" list of responsibilities.
Then "What we're looking for:" list of requirements/qualifications.
Then "Must be authorized to work in the United States..." etc.
Then "This role is hybrid, based at our downtown Seattle HQ, targeting 3 days a week in-office." That's schedule.
Then "The salary range for this role is USD $110,000 - $140,000 annual base salary plus pre-IPO stock options and benefits." That's pay.
Then "Benefits & Perks:" list.
Also there is "About Qumulo:" description of company; maybe we can include as part of About the role? But we have About the role already. Could treat as separate "About Qumulo" but not in allowed headings. Probably we can incorporate into About the role or ignore? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About Qumulo description somewhere. Could be part of About the role? But that heading is for role description. However we could add a section "About Qumulo" but not allowed headings. The allowed headings list is not exhaustive? It says: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but maybe we can also use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we should stick to those. So we need to fit all content into those sections.
Thus we can put company description under About the role (maybe as a paragraph). Or we could put under Responsibilities? No.
Better: About the role includes both role description and company overview.
Responsibilities: list from "As a Software Engineer at Qumulo, you will:".
Requirements: maybe "What we're looking for:" includes education, ability to write code, grasp of algorithms, proficiency in languages, willingness to work collaboratively, ability to work hybrid schedule, must be authorized to work in US. Some of those are requirements.
Qualifications: maybe overlapping; but we can separate: Qualifications could be education and experience; Skills could be technical skills (C, C++, Rust, Java, Go). But we need to avoid duplication.
We have to preserve all substantive info; we can split as needed.
Let's extract:
About the Role paragraph:
"Joining us, 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."
Why join Qumulo paragraph:
"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 of smart, capable engineers who will serve as your 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 - and we’re small enough that the work you do will actually show up in the product."
As a Software Engineer at Qumulo, you will: list:
- Collaborate with team members on design, code reviews, and pair programming to deliver high-quality software.
- Collaborate with team members and area leads on architecture and design of new/updated features.
- Contribute to full-lifecycle feature development and testing using C, Rust, and Python.
- Take ownership of defining and implementing customer-facing features and internal system improvements.
- Help debug, troubleshoot, and fix test failures and complex product or service issues in production environments.
What we're looking for:
- Recently graduated (or graduating within the next 9 months) with a degree in Computer Science, a related field, or equivalent experience.
- Ability to write well-factored, maintainable, and well-tested code.
- Strong grasp of algorithms and data structures, with solid academic or project experience in distributed systems, database concepts, concurrent programming, or operating systems concepts.
- Proficiency in C, C++, Rust, Java, or Go demonstrated through classes, internships, or personal projects
- Willingness to work collaboratively with a team to solve complex problems and learn quickly on the job.
- Ability to work a hybrid schedule from our downtown Seattle HQ
- Must be authorized to work in the United States. We are unable to provide visa sponsorship or transfer.
- This role is hybrid, based at our downtown Seattle HQ, targeting 3 days a week in-office.
Salary range: "The salary range for this role is USD $110,000 - $140,000 annual base salary plus pre-IPO stock options and benefits. Individual compensation depends on factors such as role level, relevant experience, and skill set."
Benefits & Perks list:
- Pre-IPO stock options
- Flexible time-off policy
- HSA and PPO health insurance options
- Dental and Vision insurance
- 401(k) plan
- Choice of an ORCA card or parking subsidy
About Qumulo paragraph (company description) we need to embed somewhere; maybe under About the role as additional paragraph.
Also "Our Values:" etc is boilerplate? It's values; could be considered part of About the role or maybe we can include under About the role as well. But it's not boilerplate; it's substantive. However we might consider it as part of About the role.
Equal Opportunity Employer etc is boilerplate to remove.
Applicant Privacy Policy link also boilerplate.
Thus we need to produce HTML with sections:
About the role
... (including role description, why join, company overview, values maybe)
Responsibilities
- ... each responsibility
Requirements
- ... list of requirements (education, ability to write code, grasp of algorithms, proficiency, willingness to collaborate, ability to work hybrid, work authorization)
Qualifications
Maybe we can treat qualifications as education and experience? But we already used education in requirements. Could split: Requirements = technical skills and abilities; Qualifications = education/experience. But we need to avoid duplication. Let's think: The posting has "What we're looking for:" which includes education, ability to write code, grasp of algorithms, proficiency, willingness, hybrid schedule, work auth. That's basically qualifications. So we could put all under Requirements. Then Qualifications could be empty? But we must not emit empty sections. So we need to decide which sections to include based on content.
We have distinct content for:
- Responsibilities (list)
- Requirements/Qualifications (list)
- Skills (maybe list of languages)
- Benefits (list)
- Pay (salary range)
- Schedule (hybrid schedule)
We could treat Skills as proficiency in languages list.
Thus:
About the role
Combine role description, why join, company overview, values.
Responsibilities
...
Skills
- Proficiency in C, C++, Rust, Java, or Go
maybe also mention Python? Actually responsibilities mention using C, Rust, Python. But skills could be languages.
But we also have "Ability to write well-factored, maintainable, and well-tested code." That's more ability than skill.
We could put that under Requirements.
Let's define:
Requirements: education, ability to write code, grasp of algorithms, willingness to collaborate, work auth.
Skills: proficiency in languages (C, C++, Rust, Java, Go) and maybe Python? But Python is used in responsibilities; we could include.
But we need to avoid duplication: proficiency list appears in "What we're looking for:" as "Proficiency in C, C++, Rust, Java, or Go demonstrated through classes, internships, or personal projects". That's a skill.
Thus Skills section can list those languages.
Requirements can list education, ability to write code, grasp of algorithms, willingness to collaborate, work auth.
Schedule: hybrid schedule 3 days a week in-office.
Pay: salary range USD $110,000 - $140,000 annual base salary plus pre-IPO stock options and benefits. Note benefits also listed separately; but pay section should include salary and maybe mention stock options? However benefits also list pre-IPO stock options. To avoid duplication, we could mention salary only in Pay, and benefits list includes stock options etc. But the posting says salary plus pre-IPO stock options and benefits. So stock options are part of compensation but also listed under Benefits & Perks. We could include stock options in Benefits section and mention salary range in Pay. That's fine.
Thus Pay: "The salary range for this role is USD $110,000 - $140,000 annual base salary.
"
Benefits: list as given.
Schedule: "This role is hybrid, based at our downtown Seattle HQ, targeting 3 days a week in-office.
"
Now About the role: need to include role description, why join, company overview, values.
Let's craft a paragraph that includes all that info without repeating.
We'll combine:
"Joining us, 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
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate like EEO, legal, etc. Preserve all substantive info. We need to parse the posting. Key sections: - About the Role: paragraph describing role. - Why join Qumulo: maybe part of About? Could be part of About the role? But we can treat as part of About the role or separate? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: About the Role: (the paragraph after "About the Role:"). Then "Why join Qumulo:" maybe part of Benefits? Actually it's about culture, could be part of About the role or maybe we can treat as part of About the role as well. But we have separate Benefits & Perks later. Then "As a Software Engineer at Qumulo, you will:" list of responsibilities. Then "What we're looking for:" list of requirements/qualifications. Then "Must be authorized to work in the United States..." etc. Then "This role is hybrid, based at our downtown Seattle HQ, targeting 3 days a week in-office." That's schedule. Then "The salary range for this role is USD $110,000 - $140,000 annual base salary plus pre-IPO stock options and benefits." That's pay. Then "Benefits & Perks:" list. Also there is "About Qumulo:" description of company; maybe we can include as part of About the role? But we have About the role already. Could treat as separate "About Qumulo" but not in allowed headings. Probably we can incorporate into About the role or ignore? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About Qumulo description somewhere. Could be part of About the role? But that heading is for role description. However we could add a section "About Qumulo" but not allowed headings. The allowed headings list is not exhaustive? It says: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but maybe we can also use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we should stick to those. So we need to fit all content into those sections.
Thus we can put company description under About the role (maybe as a paragraph). Or we could put under Responsibilities? No.
Better: About the role includes both role description and company overview.
Responsibilities: list from "As a Software Engineer at Qumulo, you will:".
Requirements: maybe "What we're looking for:" includes education, ability to write code, grasp of algorithms, proficiency in languages, willingness to work collaboratively, ability to work hybrid schedule, must be authorized to work in US. Some of those are requirements.
Qualifications: maybe overlapping; but we can separate: Qualifications could be education and experience; Skills could be technical skills (C, C++, Rust, Java, Go). But we need to avoid duplication.
We have to preserve all substantive info; we can split as needed.
Let's extract:
About the Role paragraph:
"Joining us, 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."
Why join Qumulo paragraph:
"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 of smart, capable engineers who will serve as your 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 - and we’re small enough that the work you do will actually show up in the product."
As a Software Engineer at Qumulo, you will: list:
- Collaborate with team members on design, code reviews, and pair programming to deliver high-quality software.
- Collaborate with team members and area leads on architecture and design of new/updated features.
- Contribute to full-lifecycle feature development and testing using C, Rust, and Python.
- Take ownership of defining and implementing customer-facing features and internal system improvements.
- Help debug, troubleshoot, and fix test failures and complex product or service issues in production environments.
What we're looking for:
- Recently graduated (or graduating within the next 9 months) with a degree in Computer Science, a related field, or equivalent experience.
- Ability to write well-factored, maintainable, and well-tested code.
- Strong grasp of algorithms and data structures, with solid academic or project experience in distributed systems, database concepts, concurrent programming, or operating systems concepts.
- Proficiency in C, C++, Rust, Java, or Go demonstrated through classes, internships, or personal projects
- Willingness to work collaboratively with a team to solve complex problems and learn quickly on the job.
- Ability to work a hybrid schedule from our downtown Seattle HQ
- Must be authorized to work in the United States. We are unable to provide visa sponsorship or transfer.
- This role is hybrid, based at our downtown Seattle HQ, targeting 3 days a week in-office.
Salary range: "The salary range for this role is USD $110,000 - $140,000 annual base salary plus pre-IPO stock options and benefits. Individual compensation depends on factors such as role level, relevant experience, and skill set."
Benefits & Perks list:
- Pre-IPO stock options
- Flexible time-off policy
- HSA and PPO health insurance options
- Dental and Vision insurance
- 401(k) plan
- Choice of an ORCA card or parking subsidy
About Qumulo paragraph (company description) we need to embed somewhere; maybe under About the role as additional paragraph.
Also "Our Values:" etc is boilerplate? It's values; could be considered part of About the role or maybe we can include under About the role as well. But it's not boilerplate; it's substantive. However we might consider it as part of About the role.
Equal Opportunity Employer etc is boilerplate to remove.
Applicant Privacy Policy link also boilerplate.
Thus we need to produce HTML with sections:
About the role
About the role
... (including role description, why join, company overview, values maybe)
Responsibilities
- ... each responsibility
Requirements
- ... list of requirements (education, ability to write code, grasp of algorithms, proficiency, willingness to collaborate, ability to work hybrid, work authorization)
Qualifications
Maybe we can treat qualifications as education and experience? But we already used education in requirements. Could split: Requirements = technical skills and abilities; Qualifications = education/experience. But we need to avoid duplication. Let's think: The posting has "What we're looking for:" which includes education, ability to write code, grasp of algorithms, proficiency, willingness, hybrid schedule, work auth. That's basically qualifications. So we could put all under Requirements. Then Qualifications could be empty? But we must not emit empty sections. So we need to decide which sections to include based on content. We have distinct content for: - Responsibilities (list) - Requirements/Qualifications (list) - Skills (maybe list of languages) - Benefits (list) - Pay (salary range) - Schedule (hybrid schedule) We could treat Skills as proficiency in languages list. Thus:About the role
Combine role description, why join, company overview, values.
Responsibilities
- ...
Skills
- Proficiency in C, C++, Rust, Java, or Go
The salary range for this role is USD $110,000 - $140,000 annual base salary.
" Benefits: list as given. Schedule: "This role is hybrid, based at our downtown Seattle HQ, targeting 3 days a week in-office.
" Now About the role: need to include role description, why join, company overview, values. Let's craft a paragraph that includes all that info without repeating. We'll combine: "Joining us, 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