Principal Tech Consultant - Solution Architect

We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". So we need to parse the posting. Let's extract content: - Req ID: 389041 (metadata, drop) - NTT DATA strives to hire... (intro paragraph) maybe part of About the role? Actually "About NTT DATA" later. The initial paragraph: "NTT DATA strives to hire exceptional, innovative and passionate individuals who want to grow with us. If you want to be part of an inclusive, adaptable, and forward-thinking organization, apply now." That's generic company statement; could be part of About the role? Might be considered boilerplate? It's not EEO but still generic. Might keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories, but it's a generic marketing statement. Might be okay to keep as part of About the role? However we have a later "About NTT DATA" section with more detail. The initial statement could be considered part of About the role? Might be considered filler but not prohibited. I'd keep it as part of About the role. - "We are currently seeking a Principal Tech Consultant - Solution Architect to join our team in New York, New York (US-NY), United States (US)." This is location info; we can include in a short p maybe under About the role? Or we could have a location line but not as heading. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location in a p. - "Job Title: Principal Tech Consultant – Solution Architect (Hands-on Engineering)" - we should not repeat job title as heading; we can drop it or include in p? Probably drop as it's redundant. - "Location: Arlington, VA, New York, NY and St. Louis, MO; Hybrid work model" - location details. - "Overall Experience: 10+ Years" - maybe part of Requirements. - "Employment Type: Contract/Permanent" - maybe part of About the role? Could be included in a p. - "Role Summary" heading? Not in our allowed headings list but we could treat as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "Role Summary" could be About the role. - Then paragraphs describing role. - Then "Day To Day Job Duties" -> Responsibilities. - Then list of duties (bullet points). We'll output as

• . - Then "Basic Qualifications" -> Requirements or Qualifications? The headings list includes Requirements and Qualifications separate. Usually Requirements = basic qualifications, Qualifications = nice-to-have? But we have "Basic Qualifications" and "Nice to Have". So we can map Basic Qualifications to Requirements (or Qualifications). Nice to Have to Skills? Or Qualifications? The list includes Skills as a possible heading. We could put Nice to Have under Skills. Or we could have Requirements (basic) and Qualifications (nice). Let's decide: Use Requirements for basic qualifications, Skills for nice-to-have. Or we could have Qualifications for basic and Skills for nice. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications? But we have distinct content; we could have Requirements (basic) and Skills (nice). That seems reasonable. - Then "About NTT DATA" -> About the role? Actually we already have About the role maybe from role summary. But we could have About the role section containing the role summary and company description. However we must not repeat headings. We could have About the role containing the role summary and company description. Or we could have About the role (role summary) and then a separate section for company? Not in allowed headings. So we put company description under About the role as well. - Then later paragraphs about NTT DATA being $30B etc. That's substantive. - Then "Whenever possible, we hire locally..." etc. That's more about work arrangements; could be part of About the role or maybe Schedule? Not exactly. Could be part of About the role. - Then "NTT DATA recruiters will never ask for payment..." that's a scam warning; we should remove as per instruction: remove scam-warning boilerplate. - Then accessibility statement etc. That's maybe legal boilerplate; remove. - Then EEO statements etc. Remove. - Then "For Pay Transparency information, please click here." That's about pay but no actual pay info; we should not create Pay section unless posting actually states them. It does not state pay; it's just a link. So we should not create Pay section. - No explicit Benefits, Pay, Schedule info. So we should not include those sections. Thus sections we will output:

  About the role

  containing: role summary paragraph(s), location, employment type, maybe company description.

  Responsibilities

  containing list of duties.

  Requirements

  containing basic qualifications list.

  Skills

  containing nice-to-have list. We must not include headings with empty content. Now we need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from Day To Day Job Duties, Basic Qualifications, Nice to Have, and the role summary paragraphs, and the About NTT DATA description. We must not include duplicated lines. Check for duplicates: The role summary includes some sentences that may appear elsewhere? Not sure. We need to format as HTML fragment only, no or . Use

  ,

  ,

  • . Ensure proper nesting. Let's extract the role summary paragraphs: From text: "Role Summary We are seeking an experienced Solution Architect with strong hands-on coding capabilities to design and deliver scalable, secure, resilient, and high-performing enterprise applications. The ideal candidate should combine deep software engineering expertise with strong solution architecture capabilities and remain actively involved in development, prototyping, and technical problem-solving. The role requires close collaboration with business stakeholders, product owners, engineering teams, DevOps, security, and enterprise architects to translate business requirements into practical technology solutions while providing hands-on technical leadership throughout the delivery lifecycle." That's one paragraph (maybe two sentences). We'll keep as

    . Then after that we have location and employment type lines: "We are currently seeking a Principal Tech Consultant - Solution Architect to join our team in New York, New York (US-NY), United States (US)." Actually that appears earlier before Role Summary. But we can include location and employment type in About the role. Let's gather location and employment type lines: - "We are currently seeking a Principal Tech Consultant - Solution Architect to join our team in New York, New York (US-NY), United States (US)." (This is location: New York, NY) - "Location: Arlington, VA, New York, NY and St. Louis, MO; Hybrid work model" - "Overall Experience: 10+ Years" - "Employment Type: Contract/Permanent" We could combine these into a short p: maybe "Location: Arlington, VA, New York, NY and St. Louis, MO; Hybrid work model. Overall Experience: 10+ Years. Employment Type: Contract/Permanent." Also include the earlier line about New York? Might be duplicate. We'll keep the location line as given. Now About NTT DATA description: "NTT DATA is a $30 billion business and technology services leader, serving 75% of the Fortune Global 100. We are committed to accelerating client success and positively impacting society through responsible innovation. We are one of the world's leading AI and digital infrastructure providers, with unmatched capabilities in enterprise-scale AI, cloud, security, connectivity, data centers and application services. our consulting and Industry solutions help organizations and society move confidently and sustainably into the digital future. As a Global Top Employer, we have experts in more than 50 countries. We also offer clients access to a robust ecosystem of innovation centers as well as established and start-up partners. NTT DATA is a part of NTT Group, which invests over $3 billion each year in R&D. Whenever possible, we hire locally to NTT DATA offices or client sites. This ensures we can provide timely and effective support tailored to each client’s needs. While many positions offer remote or hybrid work options, these arrangements are subject to change based on client requirements. For employees near an NTT DATA office or client site, in-office attendance may be required for meetings or events, depending on business needs. At NTT DATA, we are committed to staying flexible and meeting the evolving needs of both our clients and employees." We should keep that as part of About the role (maybe after role summary). Ensure we preserve the text exactly, but we can fix capitalization of "our" to "Our"? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Changing case might be considered altering? It's minor but could be considered altering. Better to keep as is. The original has "our consulting and Industry solutions help..." with lower case "our". We'll keep it. Now Responsibilities: list of duties from "Day To Day Job Duties". Let's extract each bullet: - Define end-to-end solution architecture for complex enterprise applications and platforms. - Remain actively involved in hands-on coding, development, prototyping, and implementation of critical application components. - Design scalable Microservices, REST APIs, distributed systems, and cloud-native applications. - Develop Proof of Concepts (PoCs) to evaluate technologies, frameworks, and architectural approaches. - Translate business and functional requirements into scalable technical designs and implementation strategies. - Establish application architecture, coding standards, design patterns, and engineering best practices. - Conduct architecture reviews, technical design reviews, and code reviews. - Work closely with engineering teams to resolve complex technical and performance challenges. - Mentor senior developers and provide hands-on technical guidance to development teams. - Drive application modernization, refactoring, and cloud transformation initiatives. - Collaborate with DevOps teams to improve CI/CD, deployment automation, and application reliability. - Ensure solutions meet requirements for security, scalability, availability, performance, and maintainability. - Troubleshoot complex production issues and provide architectural and code-level solutions. - Evaluate emerging technologies and recommend their adoption based on business and technical requirements. We need to output each as

  • . Now Requirements (Basic Qualifications): List: - 10+ years of experience in software engineering, application development, and enterprise solution design. - 7+ years of strong hands-on coding experience with Java/Spring Boot, .NET, Python, or similar enterprise technologies. - 5+ years of experience designing and developing Microservices, REST APIs, distributed systems, and enterprise integrations. - 3+ years of experience designing and developing cloud-native applications on AWS, Azure, or Google Cloud Platform. We'll output as
  • . Now Skills (Nice to Have): List: - Strong expertise in software architecture, object-oriented design, design patterns, and clean coding principles. - Experience with modern frontend technologies such as React or Angular. - Strong understanding of Microservices and event-driven architecture. - Experience with Kafka, RabbitMQ, IBM MQ, or similar messaging technologies. - Knowledge of SQL and NoSQL databases. - Experience with Docker and Kubernetes. - Knowledge of Terraform and Infrastructure as Code. - Experience with Jenkins, GitHub Actions, GitLab CI, or Azure DevOps. - Understanding of application security, IAM,