AI Native Staff Architect (Remote)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: Company Description (Experian description) maybe "About the role"? Actually "Job Description" includes responsibilities. There's "Qualifications". There's "Additional Information" includes benefits, compensation, remote role. There's "Benefits/Perks:" list. There's "Our compensation reflects..." includes pay range? It says "The base pay range for this position is listed above." but we don't see a range listed above in the snippet. So we cannot infer pay; we should not create Pay section unless actual numbers given. There's no explicit pay range. So we omit Pay. Schedule: It says "This is a remote role." That's schedule/location info. Could be considered Schedule? Might be considered "Work Arrangement". But we only have Schedule heading if posting actually states schedule. It says remote role. That's schedule info. We could include Schedule section with that. Benefits: we have Benefits/Perks list. So include Benefits. Responsibilities: The "You'll Have The Opportunity To:" list is responsibilities. So include Responsibilities. Requirements: There's "Qualifications" section with bullet list? Actually Qualifications heading then list of qualifications. So we can map that to Requirements or Qualifications. The instruction says use headings like Qualifications, Skills, etc. We have Qualifications heading already. So we should output

Qualifications

with list. Also we have "About the role" maybe from company description? Could include About the role as a short paragraph summarizing company description. The posting includes "Company Description Experian is a global data and technology company..." That's about the company, not role. Could be About the role? Probably we can treat that as About the role (or Company). But we have no explicit "About the role" heading. However we can include a section "About the role" with that description. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role if we have content. The company description is substantive. So include About the role. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, recruitment fraud awareness, legal, etc. Also remove duplicated lines, application instructions. We need to preserve all substantive information. Let's extract: About the role (company description): "Experian is a global data and technology company, powering opportunities for people and businesses around the world. We operate across a range of markets, from financial services to healthcare, automotive, agribusiness, insurance, and many more. Experian invests in people and new advanced technologies to unlock the power of data. We have an amazing team of 25,200 people in 32 countries." Responsibilities (You'll Have The Opportunity To:): List items: - Lead architecture design and implementation of cloud native solutions for identity fraud detection, risk analysis, and digital intelligence platforms on AWS. - Ensure solutions are scalable, resilient, secure, and efficient while maintaining agreement on goals. - Make architecture decisions and manage technical strategy for the digital intelligence and device fingerprinting domains. - Establish coding standards, conduct architecture reviews, and mentor engineers on best practices. - Design and implement RESTful services that can handle large volumes of real-time data with low latency and high availability. - Architect systems using Java, Spring Boot, Docker, Kubernetes, AWS services, Apache, Kafka, and NoSQL and SQL databases. - Provide technical leadership across engineering teams on solution design, architecture patterns, and technology choices. - Partner with product, engineering, data science, security, and strategic partners to translate fraud and risk requirements into technical solutions. - Build event-driven data-intensive platforms processing device signals, behavioral data, fraud indicators, and risk scoring at scale. - Architect systems supporting continuous delivery, observability, security, compliance, and cost optimization for operational efficiency. - Guide AI native engineering practices and embed AI and ML capabilities into product features, including fraud detection, anomaly detection, risk scoring, and device intelligence. - Promote AI tool adoption for development, productivity testing, and operational efficiency. Qualifications: List: - 10+ years of experience designing cloud-native solutions on AWS and expertise in AWS services (EC2, RDS, DynamoDB, Kinesis, Lambda), Docker/Kubernetes, and infrastructure-as-code. - Experience designing scalable, resilient, and cost-optimized Java architectures for high-volume, low-latency, cloud-native applications. - Experience architecting complex, mission-critical systems serving millions of requests with performance and availability requirements. - Track record translating requirements into technical solutions while managing multiple engineering teams and partner dependencies. - Expertise in designing event-driven, data-intensive platforms and APIs. - Knowledge of asynchronous processing, message brokers (Kafka), database optimization, API design principles, and techniques for achieving low-latency, high-throughput systems. - Experience leading technical strategy, establishing architecture standards, and mentoring engineers. - Experience translating technical concepts and aligning engineering with business objectives. Benefits/Perks: - Great compensation package and bonus plan. - Core benefits including medical, dental, vision, and matching 401K. - Flexible work environment, ability to work remote, hybrid or in-office. - Flexible time off including volunteer time off, vacation, sick and 12-paid holidays. - Explore all our exciting benefits here: https://myexperianbenefits.com/. Schedule: "This is a remote role." Could be a short paragraph. Pay: Not given explicit range, so omit. Skills: Not separate; qualifications cover. We must not include boilerplate like "Our uniqueness is that we celebrate yours..." etc. That's fluff but maybe considered substantive? It's about culture; could be considered About the role? But we already have About the role with company description. The "Our uniqueness..." is more about culture and benefits; but we already have Benefits section. Could include that as part of Benefits? It's not a benefit per se but culture. Might be considered fluff; but instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Our uniqueness..." is not boilerplate; it's culture description. Could be included in About the role or maybe a separate section like "Culture". But we only allowed headings list; we could add it to About the role as extra paragraph. However we must not invent sections. It's okay to add to About the role. But we must preserve ALL substantive information. So we should include that culture paragraph somewhere. Could add to About the role after company description. Also "Check out Experian Life on social or explore our Careers Site to understand why." That's promotional; maybe not essential but substantive? Might be considered fluff. Could omit as it's basically a call to action; but it's not boilerplate. However it's like "explore our Careers Site". Might be considered application instruction? Not exactly. Safer to keep? The instruction says remove duplicated lines and application instructions. This is not application instruction. It's more marketing. I'd keep it as part of About the role. Also "Our compensation reflects the cost of labor across several U.S. geographic markets. The base pay range for this position is listed above. Within this range, individual pay is determined by work location and additional factors such as job-related skills, experience, and education. You will be also eligible for a variable pay opportunity." This mentions pay but no actual range. Since we cannot give numbers, we should not create Pay section. However we could include this paragraph in About the role or maybe a separate "Compensation" but not allowed heading. Since we cannot create Pay heading, we could incorporate that info into Benefits? But it's about pay. Might be better to omit because we cannot create Pay section and we shouldn't invent heading. However we must preserve ALL substantive information; omitting pay info would lose substantive info. But we cannot create Pay heading; maybe we can include it under Benefits? But it's not a benefit. Could we add a

under Benefits about compensation? The Benefits section already has list; we could add a paragraph about compensation. That would preserve info without creating a Pay heading. The instruction: "Prefer a few substantive sections over many thin ones." So we can add compensation details to Benefits section. Similarly, "This is a remote role." could go under Benefits or Schedule. Since we have Schedule heading allowed, we can create Schedule section with that line. Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Schedule. We need to output HTML fragment only, no markdown. Let's craft:

About the role

Experian is a global data and technology company, powering opportunities for people and businesses around the world. We operate across a range of markets, from financial services to healthcare, automotive, agribusiness, insurance, and many more. Experian invests in people and new advanced technologies to unlock the power of data. We have an amazing team of 25,200 people in 32 countries. Our uniqueness is that we celebrate yours. Experian's people first, inclusive and purpose driven culture is multi award-winning; World's Best Workplaces™ 2025 (Fortune Global Top 25), Great Place To Work™ in 26 countries to name a few. Check out Experian Life on social or explore our Careers Site to understand why. Our compensation reflects the cost of labor across several U.S. geographic markets. The base pay range for this position is listed above. Within this range, individual pay is determined by work location and additional factors such as job-related skills, experience, and education. You will be also eligible for a variable pay opportunity.

Responsibilities

• Lead architecture design and implementation of cloud native solutions for identity fraud detection, risk analysis, and digital intelligence platforms on AWS.
• Ensure solutions are scalable, resilient, secure, and efficient while maintaining agreement on goals.
• Make architecture decisions and manage technical strategy for the digital intelligence and device fingerprinting domains.
• Establish coding standards, conduct architecture reviews, and mentor engineers on best practices.
• Design and implement RESTful services that can handle large volumes of real-time data with low latency and high availability.
• Architect systems using Java, Spring Boot, Docker, Kubernetes, AWS services, Apache, Kafka, and NoSQL and SQL databases.
• Provide technical leadership across engineering teams on solution design, architecture patterns, and technology choices.
• Partner with product, engineering, data science, security, and strategic partners to translate fraud and risk requirements into technical solutions.
• Build event-driven data-intensive platforms processing device signals, behavioral data, fraud indicators, and risk scoring at scale.
• Architect systems supporting continuous delivery, observability, security, compliance, and cost optimization for operational efficiency.
• Guide AI native engineering practices and embed AI and ML capabilities into product features, including fraud detection, anomaly detection, risk scoring, and device intelligence.
• Promote AI tool adoption for development, productivity testing, and operational efficiency.

Qualifications

• 10+ years of experience designing cloud-native solutions on AWS and expertise in AWS services (EC2, RDS, DynamoDB, Kinesis, Lambda), Docker/Kubernetes, and infrastructure-as-code.
• Experience designing scalable, resilient, and cost-optimized Java architectures for high-volume, low-latency, cloud-native applications.
• Experience architecting complex, mission-critical systems serving millions of requests with performance and availability requirements.
• Track record translating requirements into technical solutions while managing multiple engineering teams and partner dependencies.
• Expertise in designing event-driven, data-intensive platforms and APIs.
• Knowledge of asynchronous processing, message brokers (Kafka), database optimization, API design principles, and techniques for achieving low-latency