SW Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to parse content.
The posting:
- About Us: description of Visa. Could be "About the role"? Actually "About Us" is company description. Could map 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 use those headings if content exists.
We have:
- Job Description: description of SW Engineer responsibilities. That's responsibilities.
- "What You'll Do": list of duties.
- "This is a Hybrid position...": schedule/hybrid info.
- Qualifications: Basic Qualifications and Preferred Qualifications.
- Skills: maybe we can extract from qualifications: programming languages, AI/ML frameworks, etc.
- Benefits: "Visa has a comprehensive benefits package ... includes Medical, Dental, Vision, 401(k), FSA/HSA, Life Insurance, Paid Time Off, and Wellness Program."
- Pay: "For roles located in the US, the estimated salary range for this position is $95.500,00 to $ 148.300,00 USD per year, which may include potential sales incentive payments (if applicable). Salary may vary depending on job-related factors which may include knowledge, skills, experience, and location. In addition, this position may be eligible for bonus and equity."
- Schedule: "This is a Hybrid position. Visa requires at least 3 days in office, expectations of these days will be confirmed by your Hiring Manager." Also "Work Hours Varies upon the needs of the department." Travel Requirements 5-10% maybe schedule? But schedule section is for work hours/hybrid. We'll include schedule info.
- Also "Information for US Applicants" includes salary and benefits.
- "Travel Requirements" maybe not needed as separate section; could be part of Schedule? But schedule is about work hours/hybrid. Travel could be separate but not in allowed headings. Could incorporate into Schedule or maybe omit if not fitting. The instruction: include a section ONLY when posting has real, specific content for it. We have content for Pay, Benefits, Schedule (hybrid). Also Responsibilities, Qualifications, Skills.
We need to avoid boilerplate like EEO, etc.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove duplicated lines.
Let's extract content.
About Us: "Visa is a world leader in payments technology, facilitating transactions between consumers, merchants, financial institutions and government entities across more than 200 countries and territories, dedicated to uplifting everyone, everywhere by being the best way to pay and be paid. At Visa, you'll have the opportunity to create impact at scale — tackling meaningful challenges, growing your skills and seeing your contributions impact lives around the world. Join Visa and do work that matters – to you, to your community, and to the world. Progress starts with you."
We could put that under "About the role"? Actually About the role maybe company overview. We'll use About the role heading.
Responsibilities: from Job Description and What You'll Do.
Job Description paragraph: "The SW Engineer is responsible for conducting, planning, or overseeing one or more aspects of the analysis, design, programming, debugging, and modification of computer programs for commercial or end user applications. This role involves writing code, completing programming tasks, and performing testing and debugging of applications. The SW Engineer also completes documentation and procedures for installation and maintenance, and may interface with users to define system requirements and/or necessary modifications or develop cost estimates, budgets, and schedules. All roles require digital fluency, including the ability to work with emerging technologies such as Generative AI tools (e.g. ChatGPT, Microsoft Copilot) to support everyday work."
What You'll Do list:
- Conduct analysis, design, programming, debugging, and modification of computer programs for commercial or end user applications.
- Write code, complete programming tasks, and perform testing and debugging of applications.
- Complete documentation and procedures for installation and maintenance.
- Interface with users to define system requirements and/or necessary modifications.
- Develop cost estimates, budgets, and schedules as needed.
We need to avoid duplication: The Job Description paragraph already covers many of these; but we should preserve all substantive information, not remove duplication? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to combine and avoid repeating same content.
Thus we can produce a concise responsibilities section that captures unique points.
Let's list unique responsibilities:
- Conduct analysis, design, programming, debugging, and modification of computer programs for commercial or end user applications.
- Write code, complete programming tasks, perform testing and debugging of applications.
- Complete documentation and procedures for installation and maintenance.
- Interface with users to define system requirements and/or necessary modifications.
- Develop cost estimates, budgets, and schedules as needed.
- Work with emerging technologies such as Generative AI tools (e.g., ChatGPT, Microsoft Copilot) to support everyday work.
That covers.
Now Qualifications: Basic Qualifications and Preferred Qualifications.
Basic Qualifications:
- Be based in Austin, TX or the Greater Austin metropolitan area
- Bachelor's degree, OR 3+ years of relevant work experience
- Programming Languages: Strong proficiency in Java / Python including async/await patterns, type hints (Pydantic v2), and high-performance serialization (orjson).
- AI/ML Frameworks: Hands-on experience with LangChain, RAG architectures, LLM API integration, prompt engineering, and agentic AI patterns.
- Familiarity with intent classification and NLP pipelines.
Preferred Qualifications:
- Experience with FastAPI for building production APIs.
- Experience in analysis, design, and programming of computer applications.
- Experience in debugging and modifying software programs.
- Experience in writing and maintaining technical documentation.
- Experience in performing software testing and troubleshooting.
- Experience in collaborating with users or stakeholders to gather requirements.
- Experience in developing or supporting installation and maintenance procedures.
- Protocols & Integration: Experience with Model Context Protocol (MCP) JSON-RPC 2.0, REST APIs, Server-Sent Events (SSE), and mTLS. Understanding of agent-to-agent communication patterns.
- API Development: Ability to design and implement robust APIs using FastAPI, including request validation (Pydantic), authentication (OAuth2, API Key, mTLS), and streaming responses.
- Cloud Computing: Experience developing and deploying cloud-native containerized applications.
- GenAI: Practical utilization of Generative AI models for code development and familiarity with LLM API integration patterns (ChatOpenAI, token management, streaming).
We can combine into Requirements and Skills sections. The instruction allows sections: Requirements, Qualifications, Skills. We need to decide what to put where.
We could put Basic Qualifications under Requirements (or Qualifications). Preferred Qualifications under Skills. Or we could have Requirements = Basic Qualifications, Skills = Preferred Qualifications (technical skills). Let's follow typical: Requirements = Basic Qualifications (must-haves). Skills = Preferred Qualifications (nice-to-haves). Also we could have a Qualifications section maybe combine both? But we have three possible headings: Requirements, Qualifications, Skills. We need to avoid thin sections. Let's use:
- Requirements: Basic Qualifications (must-haves)
- Skills: Preferred Qualifications (nice-to-haves)
- Qualifications: maybe we could omit if redundant. But we have both Requirements and Skills; maybe we don't need Qualifications separate. However we could put Qualifications as a combined section? But we already have Requirements and Skills; maybe we can omit Qualifications heading to avoid thin section. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's 7 sections. Could be okay.
But we need to ensure each section has real content.
Let's draft:
About the role
Visa is a world leader in payments technology, facilitating transactions between consumers, merchants, financial institutions and government entities across more than 200 countries and territories, dedicated to uplifting everyone, everywhere by being the best way to pay and be paid. At Visa, you'll have the opportunity to create impact at scale — tackling meaningful challenges, growing your skills and seeing your contributions impact lives around the world. Join Visa and do work that matters – to you, to your community, and to the world. Progress starts with you.
Responsibilities
- Conduct analysis, design, programming, debugging, and modification of computer programs for commercial or end user applications.
- Write code, complete programming tasks, and perform testing and debugging of applications.
- Complete documentation and procedures for installation and maintenance.
- Interface with users to define system requirements and/or necessary modifications.
- Develop cost estimates, budgets, and schedules as needed.
- Work with emerging technologies such as Generative AI tools (e.g., ChatGPT, Microsoft Copilot) to support everyday work.
Requirements
- Based in Austin, TX or the Greater Austin metropolitan area.
- Bachelor's degree OR 3+ years of relevant work experience.
- Strong proficiency in Java / Python including async/await patterns, type hints (Pydantic v2), and high-performance serialization (orjson).
- Hands-on experience with LangChain, RAG architectures, LLM API integration, prompt engineering, and agentic AI patterns.
- Familiarity with intent classification and NLP pipelines.
Skills
- Experience with FastAPI for building production APIs.
- Experience in analysis, design, and programming of computer applications.
- Experience in debugging and modifying software programs.
- Experience in writing and maintaining technical documentation.
- Experience in performing software testing and troubleshooting.
- Experience in collaborating with users or stakeholders to gather requirements.
- Experience in developing or supporting installation and maintenance procedures.
- Experience with Model Context Protocol (MCP) JSON-RPC 2.0, REST APIs, Server-Sent Events (SSE), and mTLS; understanding of agent-to-agent communication patterns.
- Ability to design and implement robust APIs using FastAPI, including request validation (Pydantic), authentication (OAuth2, API Key, mTLS), and streaming responses.
- Experience developing and deploying cloud-native containerized applications.
- Practical utilization of Generative AI models for code development and familiarity with LLM API integration patterns (ChatOpenAI, token management, streaming).
Benefits
- Medical
- Dental
- Vision
- 401(k)
- FSA/HSA
- Life Insurance
- Paid Time Off
- Wellness Program
Pay
For roles located in the US, the estimated salary range for this position is $95,500.00 to $148,300.00 USD per year, which may include potential sales incentive payments (if applicable). Salary may vary depending on job-related factors which may include knowledge, skills, experience, and location. In addition, this position may be eligible for bonus and equity.
Schedule
- for any list of duties/requirements/benefits, and
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove duplicated lines. Let's extract content. About Us: "Visa is a world leader in payments technology, facilitating transactions between consumers, merchants, financial institutions and government entities across more than 200 countries and territories, dedicated to uplifting everyone, everywhere by being the best way to pay and be paid. At Visa, you'll have the opportunity to create impact at scale — tackling meaningful challenges, growing your skills and seeing your contributions impact lives around the world. Join Visa and do work that matters – to you, to your community, and to the world. Progress starts with you." We could put that under "About the role"? Actually About the role maybe company overview. We'll use About the role heading. Responsibilities: from Job Description and What You'll Do. Job Description paragraph: "The SW Engineer is responsible for conducting, planning, or overseeing one or more aspects of the analysis, design, programming, debugging, and modification of computer programs for commercial or end user applications. This role involves writing code, completing programming tasks, and performing testing and debugging of applications. The SW Engineer also completes documentation and procedures for installation and maintenance, and may interface with users to define system requirements and/or necessary modifications or develop cost estimates, budgets, and schedules. All roles require digital fluency, including the ability to work with emerging technologies such as Generative AI tools (e.g. ChatGPT, Microsoft Copilot) to support everyday work." What You'll Do list: - Conduct analysis, design, programming, debugging, and modification of computer programs for commercial or end user applications. - Write code, complete programming tasks, and perform testing and debugging of applications. - Complete documentation and procedures for installation and maintenance. - Interface with users to define system requirements and/or necessary modifications. - Develop cost estimates, budgets, and schedules as needed. We need to avoid duplication: The Job Description paragraph already covers many of these; but we should preserve all substantive information, not remove duplication? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to combine and avoid repeating same content. Thus we can produce a concise responsibilities section that captures unique points. Let's list unique responsibilities: - Conduct analysis, design, programming, debugging, and modification of computer programs for commercial or end user applications. - Write code, complete programming tasks, perform testing and debugging of applications. - Complete documentation and procedures for installation and maintenance. - Interface with users to define system requirements and/or necessary modifications. - Develop cost estimates, budgets, and schedules as needed. - Work with emerging technologies such as Generative AI tools (e.g., ChatGPT, Microsoft Copilot) to support everyday work. That covers. Now Qualifications: Basic Qualifications and Preferred Qualifications. Basic Qualifications: - Be based in Austin, TX or the Greater Austin metropolitan area - Bachelor's degree, OR 3+ years of relevant work experience - Programming Languages: Strong proficiency in Java / Python including async/await patterns, type hints (Pydantic v2), and high-performance serialization (orjson). - AI/ML Frameworks: Hands-on experience with LangChain, RAG architectures, LLM API integration, prompt engineering, and agentic AI patterns. - Familiarity with intent classification and NLP pipelines. Preferred Qualifications: - Experience with FastAPI for building production APIs. - Experience in analysis, design, and programming of computer applications. - Experience in debugging and modifying software programs. - Experience in writing and maintaining technical documentation. - Experience in performing software testing and troubleshooting. - Experience in collaborating with users or stakeholders to gather requirements. - Experience in developing or supporting installation and maintenance procedures. - Protocols & Integration: Experience with Model Context Protocol (MCP) JSON-RPC 2.0, REST APIs, Server-Sent Events (SSE), and mTLS. Understanding of agent-to-agent communication patterns. - API Development: Ability to design and implement robust APIs using FastAPI, including request validation (Pydantic), authentication (OAuth2, API Key, mTLS), and streaming responses. - Cloud Computing: Experience developing and deploying cloud-native containerized applications. - GenAI: Practical utilization of Generative AI models for code development and familiarity with LLM API integration patterns (ChatOpenAI, token management, streaming). We can combine into Requirements and Skills sections. The instruction allows sections: Requirements, Qualifications, Skills. We need to decide what to put where. We could put Basic Qualifications under Requirements (or Qualifications). Preferred Qualifications under Skills. Or we could have Requirements = Basic Qualifications, Skills = Preferred Qualifications (technical skills). Let's follow typical: Requirements = Basic Qualifications (must-haves). Skills = Preferred Qualifications (nice-to-haves). Also we could have a Qualifications section maybe combine both? But we have three possible headings: Requirements, Qualifications, Skills. We need to avoid thin sections. Let's use: - Requirements: Basic Qualifications (must-haves) - Skills: Preferred Qualifications (nice-to-haves) - Qualifications: maybe we could omit if redundant. But we have both Requirements and Skills; maybe we don't need Qualifications separate. However we could put Qualifications as a combined section? But we already have Requirements and Skills; maybe we can omit Qualifications heading to avoid thin section. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's 7 sections. Could be okay. But we need to ensure each section has real content. Let's draft:
About the role
Visa is a world leader in payments technology, facilitating transactions between consumers, merchants, financial institutions and government entities across more than 200 countries and territories, dedicated to uplifting everyone, everywhere by being the best way to pay and be paid. At Visa, you'll have the opportunity to create impact at scale — tackling meaningful challenges, growing your skills and seeing your contributions impact lives around the world. Join Visa and do work that matters – to you, to your community, and to the world. Progress starts with you.
Responsibilities
- Conduct analysis, design, programming, debugging, and modification of computer programs for commercial or end user applications.
- Write code, complete programming tasks, and perform testing and debugging of applications.
- Complete documentation and procedures for installation and maintenance.
- Interface with users to define system requirements and/or necessary modifications.
- Develop cost estimates, budgets, and schedules as needed.
- Work with emerging technologies such as Generative AI tools (e.g., ChatGPT, Microsoft Copilot) to support everyday work.
Requirements
- Based in Austin, TX or the Greater Austin metropolitan area.
- Bachelor's degree OR 3+ years of relevant work experience.
- Strong proficiency in Java / Python including async/await patterns, type hints (Pydantic v2), and high-performance serialization (orjson).
- Hands-on experience with LangChain, RAG architectures, LLM API integration, prompt engineering, and agentic AI patterns.
- Familiarity with intent classification and NLP pipelines.
Skills
- Experience with FastAPI for building production APIs.
- Experience in analysis, design, and programming of computer applications.
- Experience in debugging and modifying software programs.
- Experience in writing and maintaining technical documentation.
- Experience in performing software testing and troubleshooting.
- Experience in collaborating with users or stakeholders to gather requirements.
- Experience in developing or supporting installation and maintenance procedures.
- Experience with Model Context Protocol (MCP) JSON-RPC 2.0, REST APIs, Server-Sent Events (SSE), and mTLS; understanding of agent-to-agent communication patterns.
- Ability to design and implement robust APIs using FastAPI, including request validation (Pydantic), authentication (OAuth2, API Key, mTLS), and streaming responses.
- Experience developing and deploying cloud-native containerized applications.
- Practical utilization of Generative AI models for code development and familiarity with LLM API integration patterns (ChatOpenAI, token management, streaming).
Benefits
- Medical
- Dental
- Vision
- 401(k)
- FSA/HSA
- Life Insurance
- Paid Time Off
- Wellness Program
Pay
For roles located in the US, the estimated salary range for this position is $95,500.00 to $148,300.00 USD per year, which may include potential sales incentive payments (if applicable). Salary may vary depending on job-related factors which may include knowledge, skills, experience, and location. In addition, this position may be eligible for bonus and equity.
Schedule