Software Development Engineer, Early Career

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to parse the description. Let's extract sections: - About This Role: description about role: "As a Software Development Engineer, it’s up to you to define, design and refine the tech that keeps us one step ahead of listeners. Anticipate. Innovate. Bring challenging ideas and we’ll support you with the latest tech, tools, and systems that you need to succeed. We pride ourselves on our ability to imagine and invent solutions to problems of the future. You’ll be essential in this forward-thinking approach to development. Together with the team, you’ll build and maintain our platform to bring thousands of stories to millions of listeners and unleash the power of the human voice." - About You: description about candidate: "If you’re a dedicated problem solver, this is the role for you. Identifying and overcoming challenges is at the heart of everything you do; whether it’s looking ahead to our listeners problems, or analyzing every inefficiency, you thrive when you strive for perfection. We look for people who take responsibility, who feel the pride in a job well done and see every failure as an opportunity to learn. With a knowledgeable team around you, and opportunities to challenge yourself, it’s a perfect environment to develop and apply your new skills." - As a Software Development Engineer, you will... list of duties: bullet points: Develop, test, and maintain software components and applications for the world's largest audiobook creator and provider Identify and resolve software defects through code review, log analysis, metrics examination, debugging, and other troubleshooting methods Write maintainable and scalable code for software components as part of an agile engineering team Collaborate with stakeholders to envision, design, develop, test, and launch customer-centric software that inspires and impacts users Apply computer science, engineering, and analysis principles to solve moderate-scale problems Continuously enhance testability, operational excellence (OE), and documentation for owned software components Handle data classification, storage, and management in accordance with company policies Participate in the interview process and provide mentorship to fellow engineers - About Audible: description of company: "Audible is the leading producer and provider of audio storytelling. We spark listeners’ imaginations, offering immersive, cinematic experiences full of inspiration and insight to enrich our customers daily lives. We are a global company with an entrepreneurial spirit. We are dreamers and inventors who are passionate about the positive impact Audible can make for our customers and our neighbors. This spirit courses throughout Audible, supporting a culture of creativity and inclusion built on our People Principles and our mission to build more equitable communities in the cities we call home." - Basic Qualifications: list: Are 18 years of age or older Experience with at least one modern language such as Java, Python, C++, or C# including object-oriented design Experience with at least one general-purpose programming language such as Java, Python, C++, C#, Go, Rust, or TypeScript Experience with data structure implementation, basic algorithm development, and/or object-oriented design principles Currently enrolled in a Bachelor's degree or above in Computer Science, Computer Engineering, Data Science, Information Systems, or related STEM fields OR completed a Bachelor's or Graduate degree in specified fields Experience with data structure implementation, basic algorithm development, and/or object-oriented design principles (duplicate) Must be 18 years of age or older (duplicate) We need to preserve all substantive info but remove duplicates? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicates are not substantive new info; but they are repeated lines. Should we keep them? It says remove duplicated lines. So we should deduplicate. Thus Basic Qualifications unique items: - Are 18 years of age or older (or Must be 18 years of age or older) -> one line. - Experience with at least one modern language such as Java, Python, C++, or C# including object-oriented design - Experience with at least one general-purpose programming language such as Java, Python, C++, C#, Go, Rust, or TypeScript - Experience with data structure implementation, basic algorithm development, and/or object-oriented design principles - Currently enrolled in a Bachelor's degree or above in Computer Science, Computer Engineering, Data Science, Information Systems, or related STEM fields OR completed a Bachelor's or Graduate degree in specified fields We could combine the two experience lines? They are distinct: modern language vs general-purpose programming language. Keep both. - Preferred Qualifications: list: Experience from a technical internship Experience in optimization mathematics such as linear programming and nonlinear optimization Experience with distributed, multi-tiered systems, algorithms, and relational databases Work 40 hours/week, and overtime as required Experience from previous technical internship(s) or demonstrated project experience Experience with Cloud platforms (preferably AWS), database systems (SQL and NoSQL), AI tools for development productivity, contributing to open-source projects, and/or version control systems Bachelor's degree in engineering or equivalent, or experience with Cloud platforms (preferably AWS), database systems (SQL and NoSQL), AI tools for development productivity, contributing to open-source projects, and/or version control systems Demonstrated ability to learn and adapt to new technologies quickly Basic understanding of software development lifecycle (SDLC) Strong problem-solving and analytical skills Excellent written and verbal communication skills We need to deduplicate: "Experience from a technical internship" and "Experience from previous technical internship(s) or demonstrated project experience" are similar but not identical; keep both? The latter includes demonstrated project experience. Keep both. Also "Experience with Cloud platforms (preferably AWS), database systems (SQL and NoSQL), AI tools for development productivity, contributing to open-source projects, and/or version control systems" appears twice (once in Preferred Qualifications list and again in the Bachelor's degree line). Actually the line: "Bachelor's degree in engineering or equivalent, or experience with Cloud platforms (preferably AWS), database systems (SQL and NoSQL), AI tools for development productivity, contributing to open-source projects, and/or version control systems" is a combined statement. We'll keep it as is. We also have "Work 40 hours/week, and overtime as required" - that is schedule info. So we can put that under Schedule section. Pay: "The starting pay for this position is listed below. Starting Day 1 of employment, Amazon offers EAP, Mental Health Support, Medical Advice Line, 401(k) matching. Learn more about our benefits at https://hiring.amazon.com/why-amazon/benefits. Cambridge, MA, USA - 129,000.00 USD Annually" Thus Pay: 129,000.00 USD Annually (maybe also location). Benefits: EAP, Mental Health Support, Medical Advice Line, 401(k) matching. Also maybe other benefits? The link to benefits but we shouldn't invent. So we list those. Schedule: Work 40 hours/week, and overtime as required. Now sections: About the role (maybe combine About This Role and About You? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. - About the role: could include About This Role and About You? Or maybe About the role is generic description of role. We'll put About This Role content under About the role. About You could be part of Requirements? Actually About You describes candidate traits; could be under Requirements or Skills. But we have separate headings: Requirements, Qualifications, Skills. We need to decide. We have Basic Qualifications (mandatory) and Preferred Qualifications (preferred). Those map to Requirements and Qualifications? Usually Requirements = basic qualifications, Qualifications = preferred? Or we could treat Requirements as Basic Qualifications, Qualifications as Preferred Qualifications. Skills could be derived from responsibilities? But we have a list of duties under "As a Software Development Engineer, you will..." which are responsibilities. So Responsibilities section will contain those bullet points. Skills could be derived from Preferred Qualifications that are skill-based: e.g., experience with Cloud platforms, optimization mathematics, distributed systems, etc. But we already have Preferred Qualifications. Might be better to put Preferred Qualifications under Qualifications. Skills could be a subset like "Strong problem-solving and analytical skills, Excellent written and verbal communication skills, Basic understanding of SDLC, Demonstrated ability to learn and adapt to new technologies quickly". However the instruction: "Prefer a few substantive sections over many thin ones." So we might combine. We need to include sections only when posting has real specific content. We have content for: - About the role (About This Role) - Responsibilities (the bullet list) - Requirements (Basic Qualifications) - Qualifications (Preferred Qualifications) - Benefits (EAP, Mental Health Support, Medical Advice Line, 401(k) matching) - Pay (salary) - Schedule (Work 40 hours/week, overtime as required) Skills maybe not needed separately if we incorporate into Qualifications. But we have a heading Skills in the list of allowed headings; we could omit if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it". So we can omit Skills if we don't have distinct skill content not already covered. However we have some skill-like items in Preferred Qualifications; but we could treat those as Qualifications. So we can omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to format:

About the role

... (prose)

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Pay

...

Schedule

...

We must not include markdown fences. Just raw HTML. Now we need to ensure we preserve all substantive info. Let's extract exact phrasing. About This Role paragraph: "As a Software Development Engineer, it’s up to you to define, design and refine the tech that keeps us one step ahead of listeners. Anticipate. Innovate. Bring challenging ideas and we’ll support you with the latest tech, tools, and systems that you need to succeed. We pride ourselves on our ability to imagine and invent solutions to problems of the future. You’ll be essential in this forward-thinking approach to development. Together with the team, you’ll build and maintain our platform to bring thousands of stories to millions of listeners and unleash the power of the human voice." We could keep as is. About You paragraph: maybe we could incorporate into About the role? But we already used About the role for About This Role. Could we add About You also under About the role? Might be redundant but we could combine both paragraphs under About the role heading. The instruction: "Prefer a few substantive sections over many thin ones." So we could merge About This Role and About You into About the role section. That would be okay. Thus About the role content: combine both paragraphs. Let's craft:

As a Software Development Engineer, it’s up to you to define, design and refine the tech that keeps us one step ahead of listeners. Anticipate. Innovate. Bring challenging ideas and we’ll support you with the latest tech, tools, and systems that you need to succeed. We pride ourselves on our ability to imagine and invent solutions to problems of the future. You’ll be essential in