Python AWS AI Engineer
Infosys · Hartford, CT · 1 mo ago
EngineeringFull-time
We need to produce HTML fragment with headings for sections present: About the role? The posting includes Overview, Your Contribution To The Team, Required Skill And Experience, Preferred Skill And Experience, Additional Required Qualifications, Benefits, About Us. Also maybe "Overview" is like About the role. We should not repeat job title. Use
for sections present: About the role? The posting includes Overview, Your Contribution To The Team, Required Skill And Experience, Preferred Skill And Experience, Additional Required Qualifications, Benefits, About Us. Also maybe "Overview" is like About the role. We should not repeat job title. Use for each section heading. Use - for lists. Use
for prose. Remove boilerplate: EEO, etc. Also remove navigation/legal etc. Also remove duplicated lines. Must preserve all substantive info. Must not invent or summarize away detail. Must not create sections with placeholder text. Must only include sections where posting has real specific content.
We need to decide which sections to include.
Let's parse content:
Overview: paragraph about Infosys Financial Services unit, role description. That's substantive.
Your Contribution To The Team: bullet-like sentences (list of qualities). Could be a list.
Required Skill And Experience: list of required skills (many lines). Could be a list.
Preferred Skill And Experience: list.
Additional Required Qualifications: paragraph about Bachelor's degree etc.
Benefits: list of benefits.
About Us: paragraph about Infosys.
We should not include "EEO". Also not include "About Us"? It's substantive, keep.
We should not include "Overview" maybe rename to "About the role". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly.
We have Overview -> About the role.
Your Contribution To The Team -> maybe Responsibilities? Actually it's about contribution/qualities. Could be "Responsibilities" or "Skills". But we have separate Required Skill and Preferred Skill sections. The "Your Contribution To The Team" seems like desired attributes/qualities. Could be "Skills". But we already have Skills sections. However we could treat it as "Responsibilities"? It lists things like collaborative spirit, communication skills, ability to handle end-to-end SDLC, etc. Those are more like qualifications/skills. Might be better as "Skills". But we already have Required Skill and Preferred Skill sections. Could combine? But instruction: prefer a few substantive sections over many thin ones. Could merge "Your Contribution To The Team" into Required Skill? But it's not exactly skill, it's attributes. Might be okay to have a section "Skills" that includes both required and preferred? But we have separate required and preferred. Might be okay to keep them separate.
We need to avoid creating sections with placeholder text. All sections have content.
Thus sections:
- About the role (Overview)
- Responsibilities? Actually we have no explicit responsibilities list besides the bullet list under "In the assigned Job Role of Technology Consultant 2, your Area Of Responsibility will be as below:" followed by a list of duties. That is a list of responsibilities. So we should have a Responsibilities section with that list.
- Skills? Could split into Required Skills and Preferred Skills. Or combine into Skills with subheadings? But instruction says use for section headings. Could have Required Skills
and Preferred Skills
. That's fine.
- Qualifications (Additional Required Qualifications)
- Benefits
- About Us (maybe "About the company").
We should not include Pay or Schedule as not present.
Now we need to extract the content precisely.
Let's copy relevant parts.
Overview paragraph:
"The Infosys Financial Services unit is a global leader in driving digital transformation for financial institutions. We specialize in leveraging advanced technologies such as AI, cloud, and data-led innovation to help our clients accelerate growth and unlock business value. Our AI-driven solutions empower financial institutions to make smarter decisions, enhance customer experiences, and achieve operational excellence. Join us to be part of a pioneering team that is at the forefront of financial services transformation. You'll have the opportunity to work with cutting-edge AI technologies, collaborate with industry experts, and contribute to transformative projects across banking, wealth management, and insurance sectors. If you're passionate about AI and eager to make a significant impact, the Infosys Financial Services unit is the perfect place for you to grow and excel."
That's the overview.
Next: "In the assigned Job Role of Technology Consultant 2, your Area Of Responsibility will be as below:" then list:
- Contribute to the requirements elicitation process by documenting assigned parts of business requirements, in line with guidance provided
- Facilitate software application design discussions, and document design decisions to guide the technical team towards building software solutions
- Participate in coding and integrate new features or updates into existing applications, with a focus on maintaining system stability
- Conduct code reviews, do changes to the codebase and maintain code repositories
- Implement test strategies, analyse results, and coordinate bug fixes to uphold the software quality standards
- Develop user training programs, documentation, and support frameworks to ensure a smooth transition to new software applications
- Actively participate in resolving production issues and recommend preventive strategies to enhance system reliability
- Maintain detailed records of code, testing techniques, and support activities to enrich the knowledge base and assist other similar projects
That's responsibilities.
Next: "Your Contribution To The Team" then sentences:
- A collaborative spirit and excellent communication skills.
- The ability to handle end to end SDLC phases from requirement gathering to implementation.
- A knack for translating complex requirements into actionable development tasks.
- A passion for design and hands-on coding experience
- A proactive approach to testing, troubleshooting, and refining our applications.
- The ability to work with cross-functional teams and do software integration.
We could treat as a list under maybe "Team Contribution" or "Skills". But we have Required Skill and Preferred Skill sections. This seems like desired attributes/qualities. Could be a separate section "Key Attributes". But instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Your Contribution To The Team" could be considered "Skills". However we already have Required Skill and Preferred Skill sections. Might be okay to make a section "Skills" and include these bullet points plus required/preferred? But that would mix. Better to keep separate: maybe "Key Attributes". But not in the given examples. However we can still use any heading as long as it's . The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. So we can create a heading like "Key Attributes". That's fine.
But to follow the spirit, maybe we can treat it as "Skills". Then we would have Required Skills, Preferred Skills, and also Skills (duplicate). Could be confusing. Better to rename to "Key Attributes". It's still a heading.
Now Required Skill And Experience: list lines each starting with "Experience in ..." or "Experience with ..." etc. We'll capture each line as a list item.
Let's extract them:
- Experience in Python and ML libraries (e.g., TensorFlow, PyTorch, scikit-learn).
- Experience in Design, develop, and fine-tune machine learning models, particularly those involving LLMs and generative AI.
- Experience with AWS services, especially Bedrock, S3, EC2, and Lambda
- Familiarity with ML Ops practices and tools for model deployment and monitoring.
- Experience with AWS SageMaker for model development and model deployment.
- Experience with developing and deploying AI Agents for business problems.
- Experience in optimizing and adapt prompt engineering strategies to improve model performance and relevance.
- Experience with LLMs (e.g., OpenAI, Anthropic, Cohere) and prompt engineering.
- Experience in understanding quantitative/ statistical/ML/AI modeling methodologies.
- Experience in ML engineering, including hands-on experience with Generative AI/LLMs.
Note: some lines have minor grammar issues but we keep as is.
Preferred Skill And Experience:
- Experience in building and maintaining scalable data pipelines and APIs to support ML workflows.
- Knowledge of data privacy and security best practices in cloud environments.
- Familiarity with containerization (Docker) and container orchestration is a plus.
Additional Required Qualifications:
- Bachelor’s degree or foreign equivalent required from an accredited institution.
- Will also consider three years of progressive experience in the specialty in lieu of every year of education.
- This position may require relocation and/or travel to work/project location.
- Candidates authorized to work for any employer in the United States without employer-based visa sponsorship are welcome to apply.
- Infosys is unable to provide immigration sponsorship for this role now or in the future.
Benefits:
- Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:
Then list:
- Medical/Dental/Vision/Life Insurance
- Long-term/Short-term Disability
- Health and Dependent Care Reimbursement Accounts
- Insurance (Accident, Critical Illness , Hospital Indemnity, Legal)
- 401(k) plan and contributions dependent on salary level
- Paid holidays plus Paid Time Off
We need to keep the introductory sentence maybe as a
then list.
About Us:
Paragraph: "Infosys is a global leader in next-generation digital services and consulting. We enable clients in more than 50 countries to navigate their digital transformation. With over four decades of experience in managing the systems and workings of global enterprises, we expertly steer our clients through their digital journey. We do it by enabling the enterprise with an AI-powered core that helps prioritize the execution of change. We also empower the business with agile digital at scale to deliver unprecedented levels of performance and customer delight. Our always-on learning agenda drives their continuous improvement through building and transferring digital skills, expertise, and ideas from our innovation ecosystem."
We should exclude EEO.
Now produce HTML.
Structure:
About the role
Overview paragraph
Responsibilities
- ...
...
Key Attributes
- ...
...
Required Skills
- ...
...
Preferred Skills
- ...
...
Qualifications
- ...
...
Benefits
Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:
- ...
...
About Us
About Us paragraph
Check that we didn't miss any content: The overview includes also "Join us to be part of a pioneering team..." etc. All included.
Check that we didn't include any boilerplate like EEO, navigation, legal, etc. Good.
Check that we didn't include any placeholder like "commensurate with experience". Not present.
Check that we didn't repeat job title. Not.
Check that we didn't include Job ID/requisition numbers. Not present.
Now ensure we preserve all substantive information. Let's verify each piece.
Overview: captured all sentences.
Responsibilities: captured all 8 bullet points.
Key Attributes: captured 6 bullet points.
Required Skills: captured 10 bullet points.
Preferred Skills: captured 3 bullet points.
Qualifications: captured 5 bullet points.
Benefits: captured intro sentence and 6 bullet points.
About Us: captured paragraph.
Now ensure we didn't miss any nuance: In Responsibilities bullet "Conduct code reviews, do changes to the codebase and maintain code repositories" we keep as is.
In Required Skills bullet "Experience in Design, develop, and fine-tune machine learning models, particularly those involving LLMs and generative AI." Keep.
In Required Skills bullet "Experience with AWS services, especially Bedrock, S3, EC2, and Lambda" keep.
In Required Skills bullet "Familiarity with ML Ops practices and tools for model deployment and monitoring." keep.
In Required Skills bullet "Experience with AWS SageMaker for model development
- for lists. Use
for prose. Remove boilerplate: EEO, etc. Also remove navigation/legal etc. Also remove duplicated lines. Must preserve all substantive info. Must not invent or summarize away detail. Must not create sections with placeholder text. Must only include sections where posting has real specific content. We need to decide which sections to include. Let's parse content: Overview: paragraph about Infosys Financial Services unit, role description. That's substantive. Your Contribution To The Team: bullet-like sentences (list of qualities). Could be a list. Required Skill And Experience: list of required skills (many lines). Could be a list. Preferred Skill And Experience: list. Additional Required Qualifications: paragraph about Bachelor's degree etc. Benefits: list of benefits. About Us: paragraph about Infosys. We should not include "EEO". Also not include "About Us"? It's substantive, keep. We should not include "Overview" maybe rename to "About the role". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. We have Overview -> About the role. Your Contribution To The Team -> maybe Responsibilities? Actually it's about contribution/qualities. Could be "Responsibilities" or "Skills". But we have separate Required Skill and Preferred Skill sections. The "Your Contribution To The Team" seems like desired attributes/qualities. Could be "Skills". But we already have Skills sections. However we could treat it as "Responsibilities"? It lists things like collaborative spirit, communication skills, ability to handle end-to-end SDLC, etc. Those are more like qualifications/skills. Might be better as "Skills". But we already have Required Skill and Preferred Skill sections. Could combine? But instruction: prefer a few substantive sections over many thin ones. Could merge "Your Contribution To The Team" into Required Skill? But it's not exactly skill, it's attributes. Might be okay to have a section "Skills" that includes both required and preferred? But we have separate required and preferred. Might be okay to keep them separate. We need to avoid creating sections with placeholder text. All sections have content. Thus sections: - About the role (Overview) - Responsibilities? Actually we have no explicit responsibilities list besides the bullet list under "In the assigned Job Role of Technology Consultant 2, your Area Of Responsibility will be as below:" followed by a list of duties. That is a list of responsibilities. So we should have a Responsibilities section with that list. - Skills? Could split into Required Skills and Preferred Skills. Or combine into Skills with subheadings? But instruction says use
for section headings. Could have
Required Skills
andPreferred Skills
. That's fine. - Qualifications (Additional Required Qualifications) - Benefits - About Us (maybe "About the company"). We should not include Pay or Schedule as not present. Now we need to extract the content precisely. Let's copy relevant parts. Overview paragraph: "The Infosys Financial Services unit is a global leader in driving digital transformation for financial institutions. We specialize in leveraging advanced technologies such as AI, cloud, and data-led innovation to help our clients accelerate growth and unlock business value. Our AI-driven solutions empower financial institutions to make smarter decisions, enhance customer experiences, and achieve operational excellence. Join us to be part of a pioneering team that is at the forefront of financial services transformation. You'll have the opportunity to work with cutting-edge AI technologies, collaborate with industry experts, and contribute to transformative projects across banking, wealth management, and insurance sectors. If you're passionate about AI and eager to make a significant impact, the Infosys Financial Services unit is the perfect place for you to grow and excel." That's the overview. Next: "In the assigned Job Role of Technology Consultant 2, your Area Of Responsibility will be as below:" then list: - Contribute to the requirements elicitation process by documenting assigned parts of business requirements, in line with guidance provided - Facilitate software application design discussions, and document design decisions to guide the technical team towards building software solutions - Participate in coding and integrate new features or updates into existing applications, with a focus on maintaining system stability - Conduct code reviews, do changes to the codebase and maintain code repositories - Implement test strategies, analyse results, and coordinate bug fixes to uphold the software quality standards - Develop user training programs, documentation, and support frameworks to ensure a smooth transition to new software applications - Actively participate in resolving production issues and recommend preventive strategies to enhance system reliability - Maintain detailed records of code, testing techniques, and support activities to enrich the knowledge base and assist other similar projects That's responsibilities. Next: "Your Contribution To The Team" then sentences: - A collaborative spirit and excellent communication skills. - The ability to handle end to end SDLC phases from requirement gathering to implementation. - A knack for translating complex requirements into actionable development tasks. - A passion for design and hands-on coding experience - A proactive approach to testing, troubleshooting, and refining our applications. - The ability to work with cross-functional teams and do software integration. We could treat as a list under maybe "Team Contribution" or "Skills". But we have Required Skill and Preferred Skill sections. This seems like desired attributes/qualities. Could be a separate section "Key Attributes". But instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Your Contribution To The Team" could be considered "Skills". However we already have Required Skill and Preferred Skill sections. Might be okay to make a section "Skills" and include these bullet points plus required/preferred? But that would mix. Better to keep separate: maybe "Key Attributes". But not in the given examples. However we can still use any heading as long as it's. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. So we can create a heading like "Key Attributes". That's fine. But to follow the spirit, maybe we can treat it as "Skills". Then we would have Required Skills, Preferred Skills, and also Skills (duplicate). Could be confusing. Better to rename to "Key Attributes". It's still a heading. Now Required Skill And Experience: list lines each starting with "Experience in ..." or "Experience with ..." etc. We'll capture each line as a list item. Let's extract them: - Experience in Python and ML libraries (e.g., TensorFlow, PyTorch, scikit-learn). - Experience in Design, develop, and fine-tune machine learning models, particularly those involving LLMs and generative AI. - Experience with AWS services, especially Bedrock, S3, EC2, and Lambda - Familiarity with ML Ops practices and tools for model deployment and monitoring. - Experience with AWS SageMaker for model development and model deployment. - Experience with developing and deploying AI Agents for business problems. - Experience in optimizing and adapt prompt engineering strategies to improve model performance and relevance. - Experience with LLMs (e.g., OpenAI, Anthropic, Cohere) and prompt engineering. - Experience in understanding quantitative/ statistical/ML/AI modeling methodologies. - Experience in ML engineering, including hands-on experience with Generative AI/LLMs. Note: some lines have minor grammar issues but we keep as is. Preferred Skill And Experience: - Experience in building and maintaining scalable data pipelines and APIs to support ML workflows. - Knowledge of data privacy and security best practices in cloud environments. - Familiarity with containerization (Docker) and container orchestration is a plus. Additional Required Qualifications: - Bachelor’s degree or foreign equivalent required from an accredited institution. - Will also consider three years of progressive experience in the specialty in lieu of every year of education. - This position may require relocation and/or travel to work/project location. - Candidates authorized to work for any employer in the United States without employer-based visa sponsorship are welcome to apply. - Infosys is unable to provide immigration sponsorship for this role now or in the future. Benefits: - Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits: Then list: - Medical/Dental/Vision/Life Insurance - Long-term/Short-term Disability - Health and Dependent Care Reimbursement Accounts - Insurance (Accident, Critical Illness , Hospital Indemnity, Legal) - 401(k) plan and contributions dependent on salary level - Paid holidays plus Paid Time Off We need to keep the introductory sentence maybe as a
then list. About Us: Paragraph: "Infosys is a global leader in next-generation digital services and consulting. We enable clients in more than 50 countries to navigate their digital transformation. With over four decades of experience in managing the systems and workings of global enterprises, we expertly steer our clients through their digital journey. We do it by enabling the enterprise with an AI-powered core that helps prioritize the execution of change. We also empower the business with agile digital at scale to deliver unprecedented levels of performance and customer delight. Our always-on learning agenda drives their continuous improvement through building and transferring digital skills, expertise, and ideas from our innovation ecosystem." We should exclude EEO. Now produce HTML. Structure:
About the role
Overview paragraph
Responsibilities
- ... ...
Key Attributes
- ... ...
Required Skills
- ... ...
Preferred Skills
- ... ...
Qualifications
- ... ...
Benefits
Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:
- ... ...
About Us
About Us paragraph
Check that we didn't miss any content: The overview includes also "Join us to be part of a pioneering team..." etc. All included. Check that we didn't include any boilerplate like EEO, navigation, legal, etc. Good. Check that we didn't include any placeholder like "commensurate with experience". Not present. Check that we didn't repeat job title. Not. Check that we didn't include Job ID/requisition numbers. Not present. Now ensure we preserve all substantive information. Let's verify each piece. Overview: captured all sentences. Responsibilities: captured all 8 bullet points. Key Attributes: captured 6 bullet points. Required Skills: captured 10 bullet points. Preferred Skills: captured 3 bullet points. Qualifications: captured 5 bullet points. Benefits: captured intro sentence and 6 bullet points. About Us: captured paragraph. Now ensure we didn't miss any nuance: In Responsibilities bullet "Conduct code reviews, do changes to the codebase and maintain code repositories" we keep as is. In Required Skills bullet "Experience in Design, develop, and fine-tune machine learning models, particularly those involving LLMs and generative AI." Keep. In Required Skills bullet "Experience with AWS services, especially Bedrock, S3, EC2, and Lambda" keep. In Required Skills bullet "Familiarity with ML Ops practices and tools for model deployment and monitoring." keep. In Required Skills bullet "Experience with AWS SageMaker for model development