Jobs · Engineering · Texas

AI Native Engineer - Reinvention Center

Accenture · Greater Houston · 3 wk ago
Engineering$70k–$235k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. We need to include sections only when posting has real specific content. So we need to extract content. Let's parse the posting: Intro paragraph: "We Are The Advanced Technology Centers (ATCs) is the engine for reinvention..." This is about the company. Could be "About the role"? Actually "About the role" is typical heading for description of role. The intro includes description of ATCs and the role. Could be considered "About the role". We'll put that as

About the role

with paragraphs. Then "You Are An AI Native Engineer..." That's also role description. Could be part of About the role. Then "The Work You’ll embed directly with clients..." That's responsibilities? Actually responsibilities are listed later. The Work paragraph could be part of About the role or Responsibilities. But we have a separate Responsibilities section later with bullet list. So we can treat "The Work..." as part of About the role. Then we have "Responsibilities" heading with bullet list. We'll output

Responsibilities

with
  • items. Then after responsibilities, we have "This is a hybrid role in Columbus, OH and requires 3 days per week in the office. May consider qualified applicants in Tampa, FL; Atlanta, GA; Dallas, TX or Houston, TX. Travel may be required for this role. The amount of travel will vary from 25% to 75% depending on business need and client requirements." That's schedule and location info. Could be Schedule section (hybrid, days per week) and maybe Location? But we only have Schedule heading allowed. We'll put schedule info under

    Schedule

    with paragraph. Then "Here’s What You Need" list of minimum experience requirements. That's Requirements/Qualifications. We'll put under

    Requirements

    (or Qualifications). The instructions say we can use Requirements, Qualifications, Skills. We'll choose Requirements. Then after that: "Compensation at Accenture varies depending on a wide array of factors..." plus salary ranges table. That's Pay section. We'll put

    Pay

    with paragraph describing compensation varies and maybe include the salary range table? The table lists ranges per location. We need to preserve all substantive info. We can include a
      or

      with the ranges. Probably better to keep as

      summarizing that compensation varies and list ranges per state/city. But we must not invent or summarize away detail. We need to preserve the ranges. Could present as a

      • for each location range. That preserves detail. Then 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" That's Benefits section. We'll put

        Benefits

        with
        • items for each benefit. Then after that there is a lot of boilerplate EEO, accommodation request, etc. We must remove those. Also remove "Requesting an Accommodation", "Equal Employment Opportunity Statement", etc. Also remove "See more information on our benefits here" link? Actually we should keep the benefits description but maybe drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not boilerplate; it's part of benefits. We can keep the link as part of the benefits paragraph. We must not include the "See more information on our benefits here" as separate? It's okay to keep as part of benefits paragraph. We must not include the "Requesting an Accommodation" etc. We must not include the "We anticipate this job posting will be posted until 11/06/2026." That's maybe metadata; could be considered boilerplate? It's a posting date. Might be considered minor metadata; we could drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it. This line is minor metadata; we can drop it. We must not include the "Accenture offers a market competitive suite of benefits..." we already captured. We must not include the "See more information on our benefits here" link? It's part of benefits; we can keep. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

          About the role

          We Are The Advanced Technology Centers (ATCs) is the engine for reinvention in our clients’ transformation journey. Powered by more than 255,000* people across 24 countries, ATCs will provide our clients with seamless access to industry insights and innovative technology solutions. Stronger together! The Advanced Technology Centers (ATCs) make tremendous impact in solving our clients’ business problems leveraging Innovation, Intelligence, Industry insights, new IT and new technology skills. Now, with the global environment changing at a faster pace, our clients are facing unprecedented challenges, and they need us more than ever before. As a Network, ATCs are positioned to unlock greater opportunities and exponential value for our clients. The value for our clients and our people For our clients, the Network provides the strength of our geographic diversity, greater resilience, and seamless access to the deepest industry knowledge, the latest in Gen AI solutions, and tech expertise from around the world. For our people, it brings an opportunity to shape truly boundaryless career paths in a highly collaborative team of experts where they can learn from each other and solve the world’s most complex client challenges You Are An AI Native Engineer with experience building cloud-native solutions, and deep expertise in designing and deploying agentic systems, especially for enterprise environments. You are a critical thinker that thrives in ambiguity, delivering concrete results by designing, building, and running custom AI agents that augment workflows and scale across modern infrastructure. You’ll help shape the playbook for how enterprises adopt and scale AI-native engineering globally. The Work You’ll embed directly with clients — acting as both technologist and trusted advisor. You’ll partner with stakeholders to define use cases, rapidly prototype, and deploy agentic workflows that are robust, secure, and operational in complex enterprise domains. Often, these will be completely net new platforms and systems that need to be stitched together in our clients' environments alongside our Ecosystem partners.

          But note we duplicated some sentences; we need to preserve all substantive info, not remove duplicates unless they are duplicated lines. The intro has some duplicated phrase "The value for our clients and our people". We'll keep as is. Now Responsibilities:

          Responsibilities

          • Design and engineer enterprise-ready AI agents encompassing retrieval, orchestration, policy-based routing, tool invocation, evaluation harnesses, and lifecycle observability.
          • AI Platform Integration: Develop abstraction layers across AI providers (Anthropic, Google, OpenAI, etc. ) to enable seamless integration and enablement.
          • Cloud-Native Engineering: Leverage containerization (Kubernetes, Docker), microservices, serverless, event-driven architectures, CI/CD, and observability to deliver scalable AI-native systems.
          • Domain-Specific Workflows: Tailor and deploy agentic applications across verticals — e.g., finance, healthcare, retail — addressing domain-specific processes via intelligent automation.
          • Client Engagement: Conduct design workshops, POCs, and code-with sessions to shape data-driven agent workflows with stakeholders, fostering trust and adoption.
          • Measure & Improve: Define and use key metrics, test harnesses, and evaluation plans to measure agent accuracy, latency, safety, and cost effectiveness.
          • Knowledge Sharing: Craft reusable patterns, documentation, and best practices to influence internal assets and client roadmaps.
          Now Schedule:

          Schedule

          This is a hybrid role in Columbus, OH and requires 3 days per week in the office. May consider qualified applicants in Tampa, FL; Atlanta, GA; Dallas, TX or Houston, TX. Travel may be required for this role. The amount of travel will vary from 25% to 75% depending on business need and client requirements.

          Now Requirements:

          Requirements

          • Minimum of 3 years engineering experience with cloud-native systems (APIs, microservices, containerization, serverless).
          • Minimum of 3 years experience programming in Python, Java, or equivalent; familiarity with evaluation tooling, logging, monitoring, and agent observability.
          • Minimum of 3 years experience deploying to production — CI/CD, infrastructure as code (Terraform, Helm), monitoring, and debugging.
          • Minimum of 3 years experience with client communication and collaboration, including being capable of leading technical workshops and delivering under ambiguity.
          • Minimum of 2 years experience with AI platforms — OpenAI, Claude, Vertex AI, plus open-source models — including building abstraction layers to manage multi-provider pipelines.
          • Minimum of 1 year expertise in designing and deploying agentic solutions (agents, orchestration, context engineering, RAG, workflows) in production environments.
          • Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate Degree, must have minimum 6 years work experience)
          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.

          • California: $70,350 to $235,100
          • Colorado: $63,800 to $203,100
          • Connecticut: $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
          • Minnesota: $63,800 to $203,100
          • New York: $66,300 to $235,100
          • New Jersey: $68,000 to $235,100
          • Ohio: $59,100 to $188,100
          • Virginia: $59,100 to $216,300
          • Washington: $80,200 to $216,300
          Now Benefits:

          Benefits

          • Medical coverage
          • Dental coverage
          • Vision coverage

Similar jobs

AI Native Engineer

Cayuse HoldingsUnited States· 2 mo ago
RemoteEngineering$70–$100/hrapply on careers-cayuseholdings.icims.com