Jobs · Engineering · New York

AI Native Software Engineer

Accenture · Albany, New York Metropolitan Area · 1 mo ago
Engineering$70k–$235k/yrFull-time
We need to output only HTML fragment, no markdown fences. Must include sections only if real content. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content from posting. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Requesting an Accommodation", "Equal Employment Opportunity Statement", etc. Also remove "Benefits" section? Actually we need Benefits if posting states them. The posting includes a Benefits paragraph: "Benefits Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture". So we need Benefits section. Pay: The posting includes "Compensation at Accenture varies depending on a wide array of factors..." and then a table of salary ranges per location. So we need Pay section with that info. Schedule: Not mentioned explicitly except travel may be required, amount varies 25% to 75%. That's not schedule but travel. No explicit schedule like full-time, part-time, remote. So we should not create Schedule section unless posting actually states it. It does not. So omit Schedule. About the role: The first paragraph: "We Are A forward-thinking services company...". That's about the company and role. We can put that under About the role. Responsibilities: The bullet list under "The Work You’ll partner directly..." etc. We need to capture responsibilities. The posting includes sections: "The Work You’ll partner directly with client stakeholders — acting as both technologist and trusted advisor." then bullet-like paragraphs: "You’ll partner with stakeholders to define use cases, rapidly prototype, and deploy agentic workflows..." then "Agent Architecture & Engineering", "AI Platform Integration", "Cloud-Native Engineering", "Domain-Specific Workflows", "Client Engagement", "Measure & Improve", "Knowledge Sharing". Those are responsibilities. We'll put them under Responsibilities as
  • items. Requirements: The "Here’s What You Need" bullet list of minimum experience etc. That's requirements. Also maybe "Bonus Points If You Have" could be Skills or Qualifications? The instructions: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put qualifications vs skills. Usually qualifications are education/degrees, skills are technical abilities. We have "Minimum of 3 years of engineering experience..." etc. Those are requirements. Also "Bachelor's degree in Computer Science, Engineering or equivalent OR equivalent (minimum 12 years) work experience." That's qualification. Also "Bonus Points If You Have..." could be Skills or Qualifications? Probably Skills. We'll treat "Bonus Points If You Have" as Skills (preferred but not required). Also "Relevant AI certifications or agentic tooling experience are a plus." etc. We need to preserve all substantive info, not invent. So we need to include all bullet points from Requirements and Bonus Points. We must not repeat job title as heading. Not include Job ID/requisition numbers. We must remove duplicated lines, boilerplate. Also remove the link markup inside Benefits? We can keep the link as is? The instruction: output only HTML fragment, we can keep tags. It's okay. We need to ensure we don't include EEO etc. So cut after Benefits section? Actually after Benefits there is "Role Location Annual Salary Range" then list of locations and ranges. That's Pay. Then after that there is "FY25 Arlington, VA ..." list of locations (maybe for role location). That seems like location list, maybe part of Pay? Actually it's under "Role Location Annual Salary Range" then list of locations with ranges. Then after that there is "FY25 Arlington, VA Albany, NY ..." which seems like a list of locations where the role may be located? Might be redundant. We'll treat that as part of Pay (location list). We'll include all location and salary ranges. We must not include "Requesting an Accommodation", "Equal Employment Opportunity Statement", etc. Now craft HTML. Structure:

    About the role

    We Are A forward-thinking services company at the forefront of AI-native innovation. We partner with enterprise clients to create next-generation, agent-powered workflows engineered to scale in real-world settings. Our engineers embed deeply with customers, moving projects beyond experimentation into operational reality. You are An AI Native Engineer with a strong foundation in building cloud-native solutions and hands-on experience designing and deploying agentic systems, especially for enterprise environments. You’re a critical thinker who thrives in ambiguity, delivering concrete results by designing, building, and running AI agents that augment workflows and scale across modern infrastructure. You'll shape how enterprises adopt AI-native engineering - either by leading complex agentic solutions and developing engineering talent, or by owning critical technical areas end-to-end as a senior IC

    But note the text includes "You are An AI Native Engineer..." maybe we keep as is. Now Responsibilities:

    Responsibilities

    • Partner directly with client stakeholders — acting as both technologist and trusted advisor. Partner with stakeholders to define use cases, rapidly prototype, and deploy agentic workflows that are robust, secure, and operational in complex enterprise domains.
    • Agent Architecture & Engineering: Design and build enterprise-ready AI agents incorporating retrieval, orchestration, policy-based routing, tool invocation, evaluation harnesses, and lifecycle observability. Implement resilient, testable, and maintainable agentic workflows that can be iterated on quickly.
    • AI Platform Integration: Develop and/or extend abstraction layers across AI providers (Anthropic, Google, OpenAI, etc.) to enable seamless integration and multi-provider enablement. Contribute to shared libraries, SDKs, and patterns that can be reused across clients.
    • Cloud-Native Engineering: Leverage containerization (Kubernetes, Docker), microservices, serverless, event-driven architectures, CI/CD, and observability stacks to deliver scalable AI-native systems. Own deployment, monitoring, and troubleshooting for your services in production.
    • Domain-Specific Workflows: Tailor and deploy agentic applications across verticals (e.g., finance, healthcare, retail), adapting to domain-specific processes and constraints. Work closely with client SMEs to translate business workflows into agentic solutions.
    • Client Engagement: Participate in and/or lead design workshops, POCs, and code-with sessions to shape data-driven agent workflows with stakeholders, fostering trust and adoption. Communicate trade-offs, risks, and recommendations clearly to both technical and non-technical audiences.
    • Measure & Improve: Define and use key metrics, test harnesses, and evaluation plans to measure agent accuracy, latency, safety, and cost effectiveness. Iterate rapidly based on data, feedback, and changing requirements.
    • Knowledge Sharing: Craft reusable patterns, documentation, and best practices that influence internal assets and client roadmaps. Contribute to internal communities of practice around AI-native and agentic engineering. Travel may be required for this role. The amount of travel will vary from 25% to 75% depending on business need and client requirements.
    Note: Travel mention included in Knowledge Sharing bullet; could be separate but okay. Now Requirements:

    Requirements

    • Minimum of 3 years of engineering experience with cloud-native systems (APIs, microservices, containerization, serverless).
    • Minimum of 1 year of hands-on experience designing and deploying agentic solutions (agents, orchestration, context engineering, RAG, workflows) in production or near-production environments.
    • Minimum of 1 year of experience with modern AI platforms — OpenAI, Claude, Vertex AI, or open-source models — including building or using abstraction layers for multi-provider pipelines.
    • Minimum of 3 years strong Python, Java or equivalent experience building 12 factor applications + Infrastructure as Code (Terraform, Helm)
    • Minimum of 3 years of experience in client-facing communication and collaboration, including leading technical discussions, workshops, or delivery sessions under ambiguity.
    • Bachelor's degree in Computer Science, Engineering or equivalent OR equivalent (minimum 12 years) work experience. (If Associate’s Degree, must have minimum 6 years work experience)
    Now Skills (Bonus Points):

    Skills

    • Relevant AI certifications or agentic tooling experience are a plus.
    • You’ve served as an Agentic / AI Engineer in an enterprise environment.
    • You’ve built multi agent orchestrations using (Lang-graph, Crew AI, Claude SDK, Open AI SDK, etc).
    • Have a GitHub repo with an agent/plugins you have created.
    • You have additional AI certifications or experience with agentic tooling and frameworks.
    • You’ve defined or worked with enterprise-grade architectures for compound AI systems, orchestration frameworks, or agent registry / stream-based architectures.
    • You understand the AI-native paradigm — blending cloud-native with generative model architectures — optimizing for performance, modularity, and efficiency.
    • You’ve delivered solutions across multiple industries (e.g., finance, healthcare) by tailoring agentic workflows to industry needs.
    • Driven execution across multiple workstreams, ensuring quality, delivery, and alignment with client outcomes.
    Now Benefits:

    Benefits

    Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture

    Now Pay:

    Pay

    Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 06/23/2026.

    • California: $70,350 to $235,100
    • Cleveland: $59,100 to $188,100
    • Colorado: $63,800 to $203,100
    • District of Columbia: $68,000 to $216,300
    • Illinois: $59,100 to $203,100
    • Maine: $54,400 to $173,100
    • Maryland: $63,800 to $203,100
    • Massachusetts: $63,800 to $216,300
    • M

Similar jobs