Senior Specialist - Architecture
LTM · Minneapolis, MN · 4 wk ago
On-siteArt & CreativeFull-time
We need to output HTML fragment only, with sections for headings where there is real content. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
From posting:
- Role Description / Job Summary: "Seeking a Senior AWS Cloud Generative AI Engineer Consultant with 7 to 11 years of experience to design develop and manage scalable secure cloud native solutions and AI powered applications on AWS". That's about the role. So we can have
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
From posting:
- Role Description / Job Summary: "Seeking a Senior AWS Cloud Generative AI Engineer Consultant with 7 to 11 years of experience to design develop and manage scalable secure cloud native solutions and AI powered applications on AWS". That's about the role. So we can have About the role
with a paragraph.
- Job Description: list of duties: "Design deploy and manage cloud native solutions using a broad range of AWS services including EC2 S3 VPC Lambda ECSEKS RDS CloudWatch EMR and Glue Develop and optimize infrastructure leveraging AWS Compute Storage Networking IAM and Security services Build and integrate Generative AI applications using LLMs RAG architectures prompt engineering and AI orchestration frameworks Implement CICD pipelines and Infrastructure as Code using Terraform and CloudFormation Use containerization and orchestration tools such as Docker and Kubernetes Collaborate with data engineering and analytics teams to build AIready cloud platforms Ensure cloud governance security scalability and cost optimization best practices Stay current with AIML and cloud security governance frameworks to drive innovation and compliance Provide technical leadership bridging cloud engineering and AI innovation to deliver next generation enterprise solutions". That's responsibilities. So we can have Responsibilities
with a - each bullet.
- Roles And Responsibilities: seems similar but more bullet-like: "Architect scalable secure and resilient cloud solutions on AWS tailored to enterprise needs Develop and maintain AI powered applications leveraging Generative AI technologies and frameworks such as Lang Chain and Llama Index Lead the implementation of DevOps best practices including CICD Infrastructure as Code and automated cloud deployments Manage AWS services including EC2 EMR Glue S3 and others to support data processing and AI workloads Collaborate with stakeholders to identify and prioritize AI driven business transformation opportunities Mentor and guide junior engineers on cloud and AI initiatives Optimize cloud infrastructure for performance security and cost efficiency Ensure compliance with cloud security standards and AI governance policies". This is also responsibilities; we can combine with previous or separate? Might duplicate. We should preserve all substantive info but avoid duplication. We can merge into one responsibilities list, ensuring we include all points.
- Other Details: includes compensation statement: "Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity." Also benefits list. Also note about range displayed etc. Also disclaimer about EEO etc (should be removed). So we have Benefits section: list of benefits. Also Pay section? There's mention of compensation range but not actual numbers. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits (list). It does mention compensation but not specific numbers; it says "Actual compensation within the range will be dependent upon ...". It also says "The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations." This is generic but still mentions compensation range. However we should not create a Pay section if only generic statements like "commensurate with experience" etc. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here they do state that compensation is dependent on skills etc, but not actual numbers. Is that considered filler? It's not a specific number, but it's still some info about compensation. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation (range dependent). I'd argue we can include a Pay section with a paragraph describing that compensation is based on skills/experience etc. However we must avoid filler like "commensurate with experience". The text says "Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity." That's not exactly filler; it's a statement. Also they mention "The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations." That's also generic but still info. I'd include Pay section with a paragraph summarizing that.
- Benefits: we have list: Comprehensive Medical Plan Covering Medical, Dental, Vision; Short Term and Long-Term Disability Coverage; 401(k) Plan with Company match; Life Insurance; Vacation Time, Sick Leave, Paid Holidays; Paid Paternity and Maternity Leave. We'll put those as
- .
- Schedule: not mentioned. So omit.
- Requirements/Qualifications/Skills: The posting mentions "Seeking a Senior AWS Cloud Generative AI Engineer Consultant with 7 to 11 years of experience". That's a requirement (years of experience). Also maybe skills: AWS services, Generative AI, LLMs, RAG, prompt engineering, AI orchestration frameworks, Terraform, CloudFormation, Docker, Kubernetes, DevOps, etc. But we already covered many in responsibilities. Could create a Skills section summarizing technical skills. However we must not invent or summarize away detail; we can extract from responsibilities. But we need to decide if we need separate sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills into one section maybe "Requirements". But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include.
We have:
- About the role: yes.
- Responsibilities: yes (combined).
- Requirements: we have experience requirement (7-11 years). Could also include "Senior" level. We'll put that.
- Qualifications: maybe not separate; could be same as Requirements. But we could skip Qualifications if not distinct.
- Skills: we could list technical skills: AWS services (EC2, S3, VPC, Lambda, ECS/EKS, RDS, CloudWatch, EMR, Glue), Compute, Storage, Networking, IAM, Security, Generative AI, LLMs, RAG, prompt engineering, AI orchestration frameworks, Lang Chain, Llama Index, Terraform, CloudFormation, Docker, Kubernetes, DevOps, CI/CD, Infrastructure as Code, containerization, orchestration, data engineering, analytics, cloud governance, security, scalability, cost optimization, AI/ML, cloud security governance frameworks. That's a lot but we can extract from responsibilities. However we must not invent; we can list them as bullet list under Skills.
But we must avoid duplication with Responsibilities. It's okay to have some overlap as long as we preserve all info. However we might be repeating same content in two sections, which is allowed but maybe not ideal. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication. But we should aim for few substantive sections. Could combine Requirements and Skills into one "Requirements" section that includes experience and skills. But we have separate headings allowed; we could just use Requirements and Skills both.
Let's think: The posting includes a "Job Summary" (About the role). Then "Job Description" (list of duties). Then "Roles And Responsibilities" (more duties). Then "Other Details" (compensation, benefits, disclaimer). So we can map:
- About the role: from Job Summary.
- Responsibilities: combine Job Description and Roles And Responsibilities.
- Requirements: experience (7-11 years) maybe also senior level.
- Skills: maybe not explicitly listed as a separate section; but we could derive from responsibilities. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we just have About the role, Responsibilities, Requirements (experience), Benefits, Pay. That's five sections. Skills could be omitted because it's covered in Responsibilities. But we might lose explicit skill enumeration. However the responsibilities already mention many skills; we can keep them there.
Thus final sections:
About the role
Seeking a Senior AWS Cloud Generative AI Engineer Consultant with 7 to 11 years of experience to design develop and manage scalable secure cloud native solutions and AI powered applications on AWS.
Responsibilities
- Design, deploy and manage cloud native solutions using a broad range of AWS services including EC2, S3, VPC, Lambda, ECS/EKS, RDS, CloudWatch, EMR and Glue.
- Develop and optimize infrastructure leveraging AWS Compute, Storage, Networking, IAM and Security services.
- Build and integrate Generative AI applications using LLMs, RAG architectures, prompt engineering and AI orchestration frameworks.
- Implement CI/CD pipelines and Infrastructure as Code using Terraform and CloudFormation.
- Use containerization and orchestration tools such as Docker and Kubernetes.
- Collaborate with data engineering and analytics teams to build AI‑ready cloud platforms.
- Ensure cloud governance, security, scalability and cost optimization best practices.
- Stay current with AI/ML and cloud security governance frameworks to drive innovation and compliance.
- Provide technical leadership bridging cloud engineering and AI innovation to deliver next‑generation enterprise solutions.
- Architect scalable, secure and resilient cloud solutions on AWS tailored to enterprise needs.
- Develop and maintain AI‑powered applications leveraging Generative AI technologies and frameworks such as Lang Chain and Llama Index.
- Lead the implementation of DevOps best practices including CI/CD, Infrastructure as Code and automated cloud deployments.
- Manage AWS services including EC2, EMR, Glue, S3 and others to support data processing and AI workloads.
- Collaborate with stakeholders to identify and prioritize AI‑driven business transformation opportunities.
- Mentor and guide junior engineers on cloud and AI initiatives.
- Optimize cloud infrastructure for performance, security and cost efficiency.
- Ensure compliance with cloud security standards and AI governance policies.
Requirements
7 to 11 years of experience in AWS cloud engineering and Generative AI; senior‑level expertise.
Benefits
- Comprehensive Medical Plan covering Medical, Dental, Vision
- Short Term and Long-Term Disability Coverage
- 401(k) Plan with Company match
- Life Insurance
- Vacation Time, Sick Leave, Paid Holidays
- Paid Paternity and Maternity Leave
Pay
Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity. The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations; individual pay is determined by work location, job level and additional factors including job‑related skills, experience and relevant education or training. Other forms of compensation (e.g., annual performance‑based bonus, sales incentive pay) may be provided as part of overall compensation.
We must exclude boilerplate like EEO disclaimer, navigation, cookie, legal, duplicated lines, application instructions. We have removed those.
Check for any filler: In Pay section we have descriptive text, not filler like "commensurate with experience". It's okay.
Check for any missing info: The posting also mentioned "Depending on the position offered, other forms of compensation may be provided as part of overall compensation like an annual performance-based bonus, sales incentive pay and other forms of bonus or variable compensation." We included that.
We also included "Disclaimer: The compensation and benefits information provided herein is accurate as of the date of this posting." That's boilerplate; we should remove. We didn't include.
We also removed "LTIMindtree is an equal opportunity
- .
- Schedule: not mentioned. So omit.
- Requirements/Qualifications/Skills: The posting mentions "Seeking a Senior AWS Cloud Generative AI Engineer Consultant with 7 to 11 years of experience". That's a requirement (years of experience). Also maybe skills: AWS services, Generative AI, LLMs, RAG, prompt engineering, AI orchestration frameworks, Terraform, CloudFormation, Docker, Kubernetes, DevOps, etc. But we already covered many in responsibilities. Could create a Skills section summarizing technical skills. However we must not invent or summarize away detail; we can extract from responsibilities. But we need to decide if we need separate sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills into one section maybe "Requirements". But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include.
We have:
- About the role: yes.
- Responsibilities: yes (combined).
- Requirements: we have experience requirement (7-11 years). Could also include "Senior" level. We'll put that.
- Qualifications: maybe not separate; could be same as Requirements. But we could skip Qualifications if not distinct.
- Skills: we could list technical skills: AWS services (EC2, S3, VPC, Lambda, ECS/EKS, RDS, CloudWatch, EMR, Glue), Compute, Storage, Networking, IAM, Security, Generative AI, LLMs, RAG, prompt engineering, AI orchestration frameworks, Lang Chain, Llama Index, Terraform, CloudFormation, Docker, Kubernetes, DevOps, CI/CD, Infrastructure as Code, containerization, orchestration, data engineering, analytics, cloud governance, security, scalability, cost optimization, AI/ML, cloud security governance frameworks. That's a lot but we can extract from responsibilities. However we must not invent; we can list them as bullet list under Skills.
But we must avoid duplication with Responsibilities. It's okay to have some overlap as long as we preserve all info. However we might be repeating same content in two sections, which is allowed but maybe not ideal. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication. But we should aim for few substantive sections. Could combine Requirements and Skills into one "Requirements" section that includes experience and skills. But we have separate headings allowed; we could just use Requirements and Skills both.
Let's think: The posting includes a "Job Summary" (About the role). Then "Job Description" (list of duties). Then "Roles And Responsibilities" (more duties). Then "Other Details" (compensation, benefits, disclaimer). So we can map:
- About the role: from Job Summary.
- Responsibilities: combine Job Description and Roles And Responsibilities.
- Requirements: experience (7-11 years) maybe also senior level.
- Skills: maybe not explicitly listed as a separate section; but we could derive from responsibilities. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we just have About the role, Responsibilities, Requirements (experience), Benefits, Pay. That's five sections. Skills could be omitted because it's covered in Responsibilities. But we might lose explicit skill enumeration. However the responsibilities already mention many skills; we can keep them there.
Thus final sections:
About the role
Seeking a Senior AWS Cloud Generative AI Engineer Consultant with 7 to 11 years of experience to design develop and manage scalable secure cloud native solutions and AI powered applications on AWS.
Responsibilities
- Design, deploy and manage cloud native solutions using a broad range of AWS services including EC2, S3, VPC, Lambda, ECS/EKS, RDS, CloudWatch, EMR and Glue.
- Develop and optimize infrastructure leveraging AWS Compute, Storage, Networking, IAM and Security services.
- Build and integrate Generative AI applications using LLMs, RAG architectures, prompt engineering and AI orchestration frameworks.
- Implement CI/CD pipelines and Infrastructure as Code using Terraform and CloudFormation.
- Use containerization and orchestration tools such as Docker and Kubernetes.
- Collaborate with data engineering and analytics teams to build AI‑ready cloud platforms.
- Ensure cloud governance, security, scalability and cost optimization best practices.
- Stay current with AI/ML and cloud security governance frameworks to drive innovation and compliance.
- Provide technical leadership bridging cloud engineering and AI innovation to deliver next‑generation enterprise solutions.
- Architect scalable, secure and resilient cloud solutions on AWS tailored to enterprise needs.
- Develop and maintain AI‑powered applications leveraging Generative AI technologies and frameworks such as Lang Chain and Llama Index.
- Lead the implementation of DevOps best practices including CI/CD, Infrastructure as Code and automated cloud deployments.
- Manage AWS services including EC2, EMR, Glue, S3 and others to support data processing and AI workloads.
- Collaborate with stakeholders to identify and prioritize AI‑driven business transformation opportunities.
- Mentor and guide junior engineers on cloud and AI initiatives.
- Optimize cloud infrastructure for performance, security and cost efficiency.
- Ensure compliance with cloud security standards and AI governance policies.
Requirements
7 to 11 years of experience in AWS cloud engineering and Generative AI; senior‑level expertise.
Benefits
- Comprehensive Medical Plan covering Medical, Dental, Vision
- Short Term and Long-Term Disability Coverage
- 401(k) Plan with Company match
- Life Insurance
- Vacation Time, Sick Leave, Paid Holidays
- Paid Paternity and Maternity Leave
Pay
Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity. The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations; individual pay is determined by work location, job level and additional factors including job‑related skills, experience and relevant education or training. Other forms of compensation (e.g., annual performance‑based bonus, sales incentive pay) may be provided as part of overall compensation.
We must exclude boilerplate like EEO disclaimer, navigation, cookie, legal, duplicated lines, application instructions. We have removed those. Check for any filler: In Pay section we have descriptive text, not filler like "commensurate with experience". It's okay. Check for any missing info: The posting also mentioned "Depending on the position offered, other forms of compensation may be provided as part of overall compensation like an annual performance-based bonus, sales incentive pay and other forms of bonus or variable compensation." We included that. We also included "Disclaimer: The compensation and benefits information provided herein is accurate as of the date of this posting." That's boilerplate; we should remove. We didn't include. We also removed "LTIMindtree is an equal opportunity