Principal Solution Architect

The user wants me to convert this job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. About the role / Company overview (the first paragraph about 7-Eleven) 2. Key Duties And Responsibilities (long list) 3. Education And Experience 4. Specific Knowledge And Skills 5. Preferred Experience 6. Technical skills/technologies listed at the end (Application Development & Architecture, Cloud & Platform Engineering, DevOps & Observability, Methodologies & Delivery) The rules say: - Use

for section headings - Use

• for lists - Use

  for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, legal, application instructions, etc.) - Only include sections with real content - No filler/placeholder text - Output only HTML fragment The posting has a lot of content. Let me structure it: 1. About the role / Company overview - first paragraph is company description, second paragraph describes the role. I'll combine into an "About the role" section with prose. 2. Responsibilities - the "Key Duties And Responsibilities" list. This is a long list of bullet points. I'll make a

  with each duty as
  • . 3. Requirements - "Education And Experience" and "Specific Knowledge And Skills" - these are requirements. I'll combine into a "Requirements" section with sub-sections or just list them. The rules say use

    for section headings like "Requirements". I'll make one Requirements section with two sub-lists: Education/Experience and Knowledge/Skills. 4. Qualifications - "Preferred Experience" - this is preferred qualifications. I'll make a "Qualifications" section. 5. Skills - the technical skills at the end are categorized. This could be a "Skills" section with sub-categories. But the rules say: "Prefer a few substantive sections over many thin ones." So I should consolidate. Let me think about the sections: - About the role (prose) - Responsibilities (list) - Requirements (list - combining education/experience and knowledge/skills) - Qualifications (list - preferred experience) - Skills (list - the technical categories) The posting also has a disclaimer at the end about job description not exhaustive, management rights, compensation range, benefits links. That's boilerplate - should remove. Also the "If an hourly or salary range is included..." paragraph - no actual range given, just boilerplate. Remove. Benefits links - boilerplate. Remove. Now, let me write the HTML. I'll start with

    About the role

    then

    for the company description and role description. Then

    Responsibilities

    with
    of all the duties. Then

    Requirements

    with two subsections: Education & Experience, and Knowledge & Skills. But the rules say use

    for section headings. Should I use

    for subsections? The rules only mention

    for section headings. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So only those top-level sections get

    . Subsections maybe just use or

    ? But the content is lists. I think I can use

    for main sections only. For subsections within Requirements, I can use a

    with bold text or just separate lists with a heading-like

    . But the rules don't forbid other heading levels, but they say "use

    for section headings". I'll stick to

    for the main sections only. For subsections, I'll use a

    Education & Experience

    then

    , etc. Similarly for Skills, there are categories. I'll make a Skills section with

    Skills

    then for each category, a

    Category

    and
    . But the rules say "Use
    • for any list of duties/requirements/benefits, and

      for prose." So I can have multiple

      within a section. Let me structure:

      About the role

      7-Eleven is an iconic family of brands with over 86,000 locations, surpassing every retailer in the world. We revolutionize convenience, restaurants and fuel through cutting edge innovation — working hard to be the customer's first choice. 7-Eleven empowers our employees to "activate awesome" and make a meaningful impact in their stores and communities every day. If you're ready to grow, lead and make a difference, come join our team and help shape the future of convenience.

      7-Eleven’s Store Technology organization is seeking an experienced Principal Architect to lead the technical architecture for point-of-sale and related store technology platforms. This fully hands-on role supports the POS team through solution design, coding, prototyping, code reviews, troubleshooting, and production issue resolution. The architect partners with Product, Store Operations, Enterprise Architecture, Cyber Security, Infrastructure, and business stakeholders to deliver secure, scalable, reliable, and maintainable software. The ideal candidate brings deep POS or transaction-processing expertise, strong distributed-systems and cloud-native experience, and the ability to connect enterprise architecture with implementation details.

      Responsibilities

      • Own the technical vision, target architecture, and architecture roadmap for POS applications, services, integrations, APIs, data, and supporting store technology platforms.
      • Remain hands-on by writing production-quality code, building prototypes and proofs of concept, troubleshooting complex defects, and contributing to critical implementation work with engineering teams.
      • Translate business, product, and store requirements into pragmatic solution designs, technical specifications, architecture decision records, and executable delivery plans.
      • Define and evolve architecture patterns for POS application services, REST APIs, integrations, data access, messaging, event-driven workflows, offline capabilities, and store-to-cloud communication.
      • Lead architecture, design, code, and technical deep-dive reviews; set engineering standards; and provide clear, actionable guidance that improves software quality and maintainability.
      • Design transaction-oriented systems for high volume, low latency, strong availability, resiliency, security, and graceful operation during connectivity or downstream service interruptions; define the non-functional requirements needed to support them.
      • Evaluate technologies, frameworks, platforms, and vendor solutions through hands-on experimentation, benchmarks, technical assessments, and total-cost-of-ownership analysis.
      • Guide modernization of legacy POS and store systems toward maintainable cloud-native services while managing technical risk, compatibility, migration sequencing, and business disruption.
      • Partner with Cyber Security and Enterprise Architecture to embed security controls, privacy, compliance, governance, threat modeling, and secure software development practices into solutions.
      • Drive CI/CD automation, Infrastructure as Code, containerized deployments, automated testing, release engineering, and disciplined environment management.
      • Work with engineering and operations teams to diagnose incidents, lead root-cause analysis, and improve monitoring, alerting, observability dashboards, and actionable metrics.
      • Define practical quality engineering strategies across unit, integration, contract, functional, performance, resilience, and regression testing for POS and retail systems.
      • Mentor engineers and technical leads through design collaboration, pairing, reviews, and knowledge sharing; create concise architecture documentation, API contracts, runbooks, release plans, and sustainable handoffs.
      • Communicate architecture options, trade-offs, risks, dependencies, estimates, and recommendations to engineering teams, stakeholders, and senior leadership.
      • Establish and champion a KPI-driven engineering culture, using data, operational metrics, customer impact, and business outcomes to guide architecture, prioritization, investment decisions, and continuous improvement initiatives.
      • Provide technical leadership during major production incidents, driving rapid mitigation, root-cause analysis, and resilient architectural improvements that eliminate repeat failure patterns and minimize future business impact.

      Requirements

      Education & Experience

      • Bachelor's/4-year degree required; Master's degree highly preferred.
      • 12+ years of relevant work experience.

      Knowledge & Skills

      • 12+ years of software engineering experience, including 8+ years of hands-on architecture or technical leadership on enterprise-scale systems.
      • Deep expertise in enterprise architecture, distributed systems, microservices, event-driven architecture, domain-driven design, integration patterns, and secure software development.
      • Hands-on programming and software design skills, including the ability to read, write, debug, and review production code for POS systems.
      • Experience designing transaction-processing systems for high volume, low latency, availability, resiliency, and offline or intermittently connected operation.
      • Expertise in APIs, messaging, data modeling, relational and NoSQL databases, service boundaries, and integration contracts.
      • Advanced cloud, DevOps, CI/CD, Infrastructure as Code, containerization, platform engineering, observability dashboards, service health metrics, SLOs/SLIs, and production operations experience.
      • Quality Engineering expertise across automation frameworks, performance and resilience testing, TDD, BDD, and test strategy.
      • Experience with security architecture, threat modeling, identity and access controls, encryption, secrets management, compliance, and secure delivery.
      • Ability to modernize legacy systems to maintainable cloud-native services with minimal business disruption.
      • Strong troubleshooting experience with monitoring, distributed tracing, incident response, disaster recovery, root-cause analysis, and problem management.
      • Sound architecture judgment in ambiguous environments, balancing near-term delivery with long-term maintainability and clearly explaining trade-offs.
      • Strong documentation, stakeholder management, vendor evaluation, estimation, planning, and cross-functional collaboration skills.

      Qualifications

      • Experience in retail, store technology, POS, self-checkout, or payments.
      • Experience designing or modernizing legacy POS, store, edge, or device-integrated systems to cloud-native architectures.
      • Experience with payment flows, transaction integrity, device integrations, store networking, offline processing, reconciliation, or near-zero-downtime migrations.
      • Experience partnering with product, store operations, vendors, security, infrastructure, and cross-functional technology teams.
      • Experience integrating hardware through JPOS/OPOS interfaces or vendor device drivers/SDKs using Java or C++.
      • Knowledge of PCI DSS, EMV, payment-terminal integration, encryption, tokenization, and key management.
      • Experience containerizing and running Windows-based applications on Linux using Docker-compatible runtimes.
      • Experience applying AI/ML, generative AI, or intelligent automation to software delivery, observability, support, or retail operations.

      Skills

      Application Development & Architecture

      • Java, C, C++, Node.js, React, Windows Application Development, REST APIs, Spring Boot Framework, JSON, MongoDB, NoSQL Databases, Microservices Architecture, Event-Driven Architecture, Distributed Systems, Enterprise Integration Patterns, Domain-Driven Design

      Cloud & Platform Engineering

      • AWS, Azure, EC2, Lambda, Fargate, S3, SNS, SQS, API Gateway, Kinesis, Auto Scaling, CloudFormation, Terraform, Docker, Kubernetes

      DevOps &