Sr. Software Development Engineer, AWS DynamoDB

We need to output HTML fragment with headings

for 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. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the description. Sections present: - Description (intro) maybe "About the role"? The intro paragraphs about role: "Are you passionate about performance measurement and optimization? DynamoDB Observability and Performance team is looking for a senior engineer..." That's about the role. Could be "About the role". We'll put that in

About the role

with

content. - Key job responsibilities: list bullet points. We'll make

Responsibilities

with

• ... each bullet. - "A day in the life": could be part of responsibilities? Might be separate but we can include under Responsibilities or maybe separate section "Day in the Life". But we only have allowed headings list; we can put under Responsibilities or maybe "About the role". Since we must prefer few substantive sections, we can merge day in the life into Responsibilities. - "About The Team": could be "About the team" but not in allowed list; maybe we can put under "About the role" or omit? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings. "About The Team" could go under About the role or maybe we can omit if not fitting. But we have substantive info about team culture, diverse experiences, etc. Could be placed under About the role as additional description. - "About AWS": could be omitted or placed under About the role as well. - "Inclusive Team Culture", "Work/Life Balance", "Mentorship & Career Growth": these are benefits/culture. Could go under Benefits? Benefits section is for benefits like health insurance etc. But we could include them under Benefits if we want. However we have actual benefits listed later: health insurance, 401(k) matching, paid time off, parental leave, etc. So we can make Benefits section with those specifics. The culture statements could be omitted or placed under About the role. Since we prefer few sections, we can put culture statements under About the role. - "Basic Qualifications": that's Requirements/Qualifications. We'll put under Requirements (or Qualifications). The allowed headings include Requirements and Qualifications separate. We need to decide. Basic Qualifications list: 5+ years of non-internship professional software development experience, 5+ years of programming with at least one software programming language experience, 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience, Experience as a mentor, tech lead or leading an engineering team. That's qualifications. Could be Requirements. We'll put under Requirements. - "Preferred Qualifications": list: 5+ years of full software development life cycle..., Bachelor's degree in computer science or equivalent, Experience creating reports..., Knowledge of big data businesses..., etc. That's also qualifications. Could be Qualifications section. - Skills: not explicitly listed but we could infer from responsibilities: innovation, data, search, analytics, distributed systems, etc. Could make Skills section with those. - Pay: we have salary range: USA, WA, Seattle - 168,100.00 - 227,400.00 USD annually. Also mention sign-on payments and RSUs. So we can make Pay section with that. - Benefits: we have comprehensive benefits list: health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, parental leave. Also link to benefits page. We'll put that. - Schedule: not mentioned. So we omit Schedule. - Also we have "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location." That's pay. We must not include boilerplate like EEO, accommodation link, etc. Remove those. We must not repeat job title. No Job ID. We must preserve all substantive information. So we need to include all bullet points from responsibilities, day in the life, team description, AWS description, inclusive culture, work/life balance, mentorship, basic qualifications, preferred qualifications, skills (maybe from responsibilities), pay, benefits. We must not invent or summarize away detail. So we need to keep the exact bullet points? We can keep them as is but maybe rephrase slightly? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the content verbatim where possible, but we can format as list items. We must not include filler like "commensurate with experience". Not present. Now produce HTML fragment. Structure:

  About the role

  Are you passionate about performance measurement and optimization? DynamoDB Observability and Performance team is looking for a senior engineer to improve efficiency of the overall DynamoDB stack. You'll champion software that measures performance under simulated and production workloads, ties it back to customer outcomes and identifies opportunities for improvement. You'll push the industry boundaries to create innovative ways to identify performance bottlenecks. Our mission is to give teams deep insights into where performance bottlenecks occur and empower them to drive improvements within their areas of ownership. In this role, you'll work with partner teams to align on requirements and expectations, delivering solutions that empower service teams to analyze performance / latency / utilization. You'll design and build data products that explain customer experience and show opportunities. The team operates at the intersection of data analysis, system performance, and developer productivity. We're building the next generation of performance analysis tools that will help DynamoDB maintain its position as a leading database service. Join us in creating solutions that directly impact the performance and reliability of systems serving millions of customers worldwide.

  Maybe also include team description and AWS description etc. Could add after that paragraph: "About The Team Our team delivers together..." etc. But we might be duplicating. However we need to preserve all substantive info. So we should include that content somewhere. Could add another

  under About the role covering team and AWS description. Or we could create a separate section but not allowed. So we will embed. Thus About the role paragraph will be long, containing all that descriptive text. Next Responsibilities: list bullet points from "Key job responsibilities" and "A day in the life". We'll combine. Bullet points from Key job responsibilities: - Solve challenging technical problems, often ones not solved before, at every layer of the stack. - Research implementations that deliver the best possible experiences for customers. - Design, implement, test, deploy and maintain innovative software solutions to measure, describe and improve service performance. - Build high-quality, highly available, always-on products. From "A day in the life": - As you design and code solutions to help our team drive efficiencies in software architecture, you’ll create measurement products, integrate them into SDCL, implement automation and other improvements, and resolve the root cause of software defects. - propose team priorities. - Identify, design and write code for critical path. - Mentor and grow junior engineers. - Work cross-functionally to help drive business decisions with your technical input. - Work in a startup-like development environment, where you’re always working on the most important stuff. We need to keep the exact phrasing. Note some bullets start with lowercase? We'll keep as is. We'll wrap each in

• . Next Requirements: Basic Qualifications bullet points. - 5+ years of non-internship professional software development experience - 5+ years of programming with at least one software programming language experience - 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience - Experience as a mentor, tech lead or leading an engineering team Next Qualifications: Preferred Qualifications bullet points. - 5+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience - Bachelor's degree in computer science or equivalent - Experience creating reports, interpreting metrics and driving overall insights or analysis - Knowledge of big data businesses and technical concepts Next Skills: we could extract from responsibilities: passion for innovation, data, search, analytics, distributed systems. Also from description: performance measurement, optimization, software that measures performance, data products, etc. We'll create a list. But we must not invent. We can derive from text: "You’ll bring a passion for innovation, data, search, analytics, and distributed systems." That's a sentence. We'll put that as a bullet or as part of Skills. We'll make Skills section with bullet points: - Innovation - Data - Search - Analytics - Distributed systems - Performance measurement and optimization - Data product design - Customer outcome analysis But some of these may be inferred. However the instruction says do NOT invent or summarize away detail. If we create a list that is not directly in the posting, that could be considered inventing. Better to keep the exact sentence as a paragraph under Skills? But Skills section expects list. We could put a single

  with that sentence. However the instruction says use

  • for any list of duties/requirements/benefits, and

    for prose. Skills is not explicitly a list but could be considered a list. Safer to put as

    describing skills. Thus Skills section:

    Skills

    You’ll bring a passion for innovation, data, search, analytics, and distributed systems.

    Next Pay:

    Pay

    The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. USA, WA, Seattle - 168,100.00 - 227,400.00 USD annually

    We could also mention sign-on payments and RSUs already. Next Benefits:

    Benefits

    Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits.

    We must not include the link? It's substantive info; we can keep. We should not include the accommodation link, EEO, etc. Now ensure we didn't miss any substantive info: The description about "Our team delivers together..." etc we included in About the role paragraph? We haven't yet. Let's incorporate that. We need to include "About The Team Our team delivers together. We make bets as a team, deliver them and learn from the experience. All our mechanisms are team-centric. Together, we create culture where you can learn and teach." Also "Diverse Experiences AWS values diverse experiences..." etc. Also "About AWS Amazon Web Services (AWS) is the world’s most comprehensive..." etc. Also "Inclusive Team Culture Here at AWS, it’s in our nature to learn and be curious..." etc. Also "Work/Life Balance We value work-life harmony..." etc. Also "Mentorship & Career Growth We’re continuously raising our performance bar..." etc. All that is substantive. We need to include it somewhere. Since we already have About the role section, we can append those paragraphs there. Thus About the role will be a series of