Jobs · Consulting · Washington

Software Development Engineer , DynamoDB Index, Search and Storage

Amazon Web Services (AWS) · Seattle, WA · 3 wk ago
ConsultingFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description (About the role?), responsibilities (Key job responsibilities), Basic Qualifications, Preferred Qualifications, Benefits, Pay (salary range). No schedule. Also maybe "About The Team" could be part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content. We have: - Description: includes overview of DynamoDB Search and Indexing, what they're building, etc. That could be "About the role". - Key job responsibilities: list bullet points. - Basic Qualifications and Preferred Qualifications: could be under "Requirements" and "Qualifications"? The instruction says sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically "Requirements" could be basic qualifications, "Qualifications" could be preferred qualifications, "Skills" maybe specific skills? But we have no explicit skills list besides languages etc. Could combine. We must not repeat job title as heading. No Job ID. We must preserve all substantive information, not invent. We must remove boilerplate: EEO, accommodations, etc. Also remove "Why AWS?" etc? That's maybe not substantive? It's about company culture; could be considered part of About the role? But we might keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why AWS?" section is not boilerplate but maybe considered generic marketing; but it's substantive? It's about AWS culture. Might be okay to keep but not required. However we need to preserve ALL substantive information; we should keep it unless it's considered boilerplate. It's not EEO etc. It's about AWS values. Could be considered part of About the role or maybe separate but we don't have a heading for culture. Could include under About the role. We also have "About The Team" which includes diversity encouragement. That's also substantive. We need to decide sections. Let's propose:

About the role

... (description + Why AWS? + About The Team maybe)

Responsibilities

  • ... each responsibility

Requirements

  • Basic Qualifications items

Qualifications

  • Preferred Qualifications items
  • maybe.

    Skills

    maybe list specific skills: C#, C++, Java, Perl, OOD, distributed systems, etc. But we already have those in qualifications. Could combine. But instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Requirements" section? But they gave separate headings possible. We need to decide. We have basic qualifications (must have) and preferred qualifications (nice to have). Could put both under "Requirements" with subheadings? But we cannot add extra headings beyond the allowed list? We could still use

    or

      inside. Better: Use "Requirements" for basic qualifications, "Qualifications" for preferred qualifications. That seems fine. Skills: we could omit if not distinct. Benefits: we have benefits description: health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention sign-on payments and RSUs. That's substantive. Pay: we have salary range: $143,700 - $194,400 USD annually. Schedule: not present, so omit. Now we need to preserve all substantive information: include sign-on payments and RSUs mention, benefits link, etc. We must not include duplicated lines. Let's extract text. Description paragraph: "Software Development Engineer, DynamoDB Search and Indexing Amazon DynamoDB is a serverless, distributed NoSQL database that delivers single-digit millisecond performance at virtually any scale. The DynamoDB Search and Indexing organization is building native search capabilities that allow customers to perform vector similarity search, full-text search, and hybrid search across their operational data. We are looking for a Senior Software Development Engineer to help design and build the distributed indexing, retrieval, and ranking infrastructure behind these capabilities. You will work on problems at the intersection of databases, distributed systems, information retrieval, and machine-learning infrastructure. The role includes designing vector and text-indexing architectures that operate across partitioned datasets; integrating approximate nearest-neighbor algorithms and inverted indexes with DynamoDB’s storage and query systems; and building hybrid retrieval that combines semantic similarity, lexical relevance, and structured filtering. You will help determine how search indexes are created, maintained, rebuilt, rebalanced, and recovered while the underlying DynamoDB data continues to change. You will also shape query planning, distributed execution, relevance ranking, and result aggregation while delivering predictable performance across latency, throughput, recall, freshness, availability, and cost. This is an opportunity to shape new DynamoDB capabilities from foundational architecture through customer launch and operation at DynamoDB scale." Then "Key job responsibilities" list: - Design and implement distributed vector, full-text, and hybrid-search capabilities for DynamoDB. - Build vector-indexing and approximate nearest-neighbor retrieval mechanisms for high-dimensional embeddings. - Develop full-text indexing and retrieval capabilities, including tokenization, text analysis, inverted indexes, relevance scoring, and phrase or term-based search. - Build hybrid retrieval and ranking that combines vector similarity, lexical relevance, and structured attribute filters. - Evaluate ranking and result-fusion techniques for combining semantic and lexical results, including score normalization, rank fusion, and reranking. - Design distributed query execution, including partition selection, query fan-out, local retrieval, top-k result merging, filtering, and aggregation. - Build index lifecycle mechanisms covering creation, backfill, incremental updates, compaction, schema or configuration changes, rebalancing, recovery, and deletion. - Ensure that indexes remain sufficiently synchronized with changes to the underlying DynamoDB data and define clear search-freshness and consistency semantics. - Integrate search indexes with DynamoDB’s distributed storage, partitioning, replication, and query-processing systems. - Optimize tradeoffs among search quality, recall, relevance, query latency, ingestion throughput, index freshness, memory usage, storage amplif (cut off). The text ends abruptly: "storage amplif". Probably "storage amplification". We'll keep as is? We should preserve exactly as given? It says "storage amplif". Might be a truncation. We'll keep as given. Then "About The Team" paragraph: "AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying." Then "Why AWS?" paragraph: "Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses." Then "Inclusive Team Culture" etc. That's more boilerplate? Might be considered generic but still substantive. However we might keep as part of About the role. But we need to avoid duplication. The "About The Team" and "Why AWS?" and subsequent sections are all about AWS culture. Could combine into About the role. Then "Basic Qualifications" list: - 3+ years of non-internship professional software development experience - 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience - 1+ years of software development engineer or related occupational experience - 1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience - 1+ years of Object Oriented Design experience - Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field - Experience programming with at least one software programming language "Preferred Qualifications": - 3+ 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 Then benefits paragraph: "Amazon is an equal opportunity employer ..." that's EEO boilerplate, remove. Then: "Our inclusive culture empowers Amazonians to deliver the best results for our customers. If you have a disability and need a workplace accommodation or adjustment during the application and hiring process, including support for the interview or onboarding process, please visit https://amazon.jobs/content/en/how-we-hire/accommodations for more information. If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's accommodation boilerplate, remove. Then: "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. 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." Then location: "USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually Company - Amazon Development Center U.S., Inc. Job ID: A10561388" We need to include salary range and mention sign-on payments and RSUs, benefits list. We must not include Job ID. Now craft HTML. We'll have:

      About the role

      Software Development Engineer, DynamoDB Search and Indexing Amazon DynamoDB is a serverless, distributed NoSQL database that delivers single-digit millisecond performance at virtually any scale. The DynamoDB Search and Indexing organization is building native search capabilities that allow customers to perform vector similarity search, full-text search, and hybrid search across their operational data. We are looking for a Senior Software Development Engineer to help design and build the distributed indexing, retrieval, and ranking infrastructure behind these capabilities. You will work on problems at the intersection of databases, distributed systems, information retrieval, and machine-learning infrastructure. The role includes designing vector and text-indexing architectures that operate across partitioned datasets; integrating approximate nearest-neighbor algorithms and inverted indexes with DynamoDB’s storage and query systems; and building hybrid retrieval that combines semantic similarity, lexical relevance, and structured filtering. You will help determine how search indexes are created, maintained, rebuilt, rebalanced, and recovered while the underlying DynamoDB data continues to change. You will also shape query planning, distributed execution, relevance ranking, and result aggregation while delivering predictable performance across latency, throughput, recall, freshness, availability, and cost. This is an opportunity to shape new DynamoDB capabilities from foundational architecture through customer launch and operation at DynamoDB scale.

      Maybe also include About The Team and Why AWS? Could add another paragraph. Add:

      AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying.

      Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and

Similar jobs