Senior Magento Architect

We need to output HTML fragment with sections: About the role? Actually we need to use 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: Who We Are (company description), then role description, responsibilities, qualifications, etc. There's no explicit Benefits, Pay, Schedule. So we should not create those sections. We can have sections: About the role (maybe summarizing role overview), Responsibilities, Qualifications (maybe combine Requirements and Qualifications). Also maybe Skills? The qualifications list includes many skills; we could put under Qualifications. Could also have a separate Skills section if we want, but we need real content. The posting includes "Key Responsibilities" and then bullet points under subheadings. Also "Qualifications" with bullet points. Also "Bonus Points". Also "Position Type- Full-Time/Regular FSLA Exempt". Also "We are an Equal Opportunity..." which we should remove as boilerplate. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to output only HTML fragment. We need to include sections only when posting has real specific content. So we can have:

  About the role

  with prose summarizing role: leading e-commerce tech stack, restructuring web team, etc. Then

  Responsibilities

  with a list. The responsibilities are grouped under categories: Technical Strategy & Platform Ownership (with subpoints), AWS Cloud Infrastructure & Reliability (subpoints), Team Leadership & Restructuring (subpoints), Business & Marketing Alignment (subpoints). We need to preserve all detail. Could flatten into a single list or keep subheadings? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid additional headings inside? It says use

  for section headings (list). Likely they want only those specific headings as top-level sections. Inside we can use

  or

  • . We could embed subheadings as or just include in list items. Probably better to keep as list items with the substance. We must not invent or summarize away detail. So we need to keep each bullet point as given. We need to extract responsibilities from the text: Under "Key Responsibilities": - Technical Strategy & Platform Ownership - The Configurator: Take full ownership of our custom server configuration tool. Lead initiatives to refactor legacy code, improve load times and enhance mobile usability - The Roadmap: Manage the end-to-end lifecycle of our Magento 2 Commerce platform, balance hands-on development with high-level strategy - Performance & Security: Maintain Core Web Vitals, ensure PCI compliance and manage regular security patching and data protection standards - Standardization: Establish development standards, documentation and deployment processes to eliminate breaking changes in production - Architecture Ownership: Define and document the target-state architecture — application, data, integration, and infrastructure layers — and own the technical decision record for major platform changes - AWS Cloud Infrastructure & Reliability - AWS Architecture: Own the design and cost of our AWS footprint — EC2/ECS, Aurora MySQL (RDS), ElastiCache for Redis, OpenSearch, S3, CloudFront, Route 53, ALB, Auto Scaling Groups, and VPC/subnet/security group design - Infrastructure as Code: Drive everything through Terraform or CloudFormation/CDK — no manual console changes in production - Scalability & Peak Traffic: Architect for promotional spikes and seasonal peaks with auto-scaling, read replicas, queue-based decoupling (SQS/SNS/EventBridge), and load testing ahead of major campaigns - Resilience & DR: Multi-AZ deployments, backup/restore strategy, documented RTO/RPO, and regular failover testing - Security & Compliance in the Cloud: IAM least-privilege, AWS WAF/Shield, Secrets Manager/Parameter Store, KMS encryption, GuardDuty, and CloudTrail auditing in support of PCI-DSS - Observability: CloudWatch metrics, logs, and alarms paired with APM tooling so issues are caught before customers report them - FinOps: Continuously right-size instances, manage reserved/savings plans, and report on cost-per-order infrastructure economics - Team Leadership & Restructuring - Build the “Triad”: Restructure the department into three functional pods Platform Pod: Internal and Agency Backend/Frontend developers Data Pod: Product specialists managing complex compatibility rules Growth Pod: Technical SEO and UX specialists - Agency Management: Act as the primary stakeholder for external agencies, holding them accountable for code quality, budgets, and deadlines - Mentorship: Hire, lead, and mentor technical talent to foster a forward-looking, solution-oriented culture - Cloud Governance: Set the standards for how the team and our agencies work in AWS — access controls, environment parity, change management, and release windows - Business & Marketing Alignment - Technical SEO: Partner with marketing to solve faceted navigation issues, canonical tagging, and schema markup - UX Excellence: Translate complex hardware compatibility rules into a simple, guided buying experience - Integrations: Ensure data integrity between Magento, GA4, and our ERP (NetSuite) / Inventory systems - International Growth: Support expansion into international markets — multi-store views, multi-currency and multi-language storefronts, localized payment methods, tax/VAT/duty handling, cross-border shipping logic, and geo-based CDN routing - Channel Expansion: Architect and maintain integrations with international and third-party sales channels (marketplaces, distributor portals, B2B punchout) so catalog, pricing, and inventory stay consistent across every channel Now Qualifications section: Under "Qualifications": - Deep Magento 2 Knowledge: You must understand the “why” behind performance bottlenecks. Is it a database deadlock, poor Varnish caching, or inefficient request flows? You need the technical authority to overrule agencies who claim the platform can’t run faster. Deep understanding of Magento 2 architecture (Cloud/On-prem), PHP 7/8, MySQL, and caching strategies (Varnish/Redis/Elasticsearch) - Customer-Facing Platform Experience: Proven track record architecting high-traffic, revenue-generating B2C and/or B2B storefronts where uptime, checkout conversion, and page speed directly affect the P&L — not just internal tools or back-office systems - Extensive AWS Experience: 4+ years designing, deploying, and operating production e-commerce workloads on AWS, with hands-on depth in compute, networking, managed databases, caching, CDN, and security services. AWS Solutions Architect (Associate or Professional) certification strongly preferred - International E-Commerce Exposure: Experience supporting cross-border or multi-region commerce — localized storefronts, currency and tax complexity, international shipping/compliance, hreflang and international SEO, and data residency/GDPR considerations - Complex Logic Experience: Our configurator relies on deep dependencies. You should have experience with Rules Engines, ERP integrations or CPQ (configure, price, quote) tools - DevOps Mindset: You care about CI/CD pipelines, automated testing, and server-side performance (New Relic, Blackfire) to ensure sub-2-second load times, and you’ve built pipelines with tools such as CodePipeline/CodeBuild, GitHub Actions, or GitLab CI deploying into AWS - Experience: 7+ years in Web Development/E-commerce, with 3+ years in a technical leadership or architect role - The “Complex Product” Factor: Proven experience managing sites with massive catalogs or configurable products (50+ options) is critical - Stack Proficiency: Familiarity with JavaScript (Knockout.js/React), REST APIs, Linux (RHEL/Ubuntu administration and shell scripting), and AWS/Azure infrastructure - Communication: Able to explain infrastructure trade-offs and cost implications to non-technical executives as comfortably as you debug a slow query - Bonus Points: - Industry Knowledge: Experience in IT Hardware, Servers, or Data Center industries - Certifications: Adobe Certified Expert – Magento Commerce; AWS Certified Solutions Architect or DevOps Engineer - Systems: Previous experience with NetSuite or similar ERP migrations - Modern Frontend: Experience with PWA Studio or Vue Storefront - Adobe Commerce Cloud: Hands-on experience with Adobe Commerce Cloud (which runs on AWS) or a comparable managed Magento hosting platform - Containers & Orchestration: Docker, ECS, or EKS in production - Migration Experience: Having led an on-prem or co-located e-commerce platform migration into AWS - Global Rollouts: Having launched a storefront in a new country or region Also Position Type: Full-Time/Regular FSLA Exempt. Could be included maybe as a short paragraph under About the role or separate? Since we don't have a Pay/Benefits/Schedule section, we could include Position Type in About the role prose. We must not include boilerplate like equal opportunity. Now we need to output HTML fragment. Structure:

    About the role

    ServerMonkey is looking for a strategic and technical leader to own our e-commerce technology stack. We are not just an online store; we are a complex Configure-to-Order (CTO) platform running on a highly customized Magento 2 environment hosted on AWS. This role is fully in the office in Houston, TX. You will lead the restructuring of our web team, bridging the gap between technical engineering, product data, and digital marketing. You’ll stabilize the platform, optimize our complex server configurator for speed and UX, own the cloud architecture end to end, and help extend our storefront into international markets and channels as you build a scalable architecture that drives revenue growth. Position Type: Full-Time/Regular, FSLA Exempt.

    Then

    Responsibilities

    • Technical Strategy & Platform Ownership
      • The Configurator: Take full ownership of our custom server configuration tool. Lead initiatives to refactor legacy code, improve load times and enhance mobile usability
      • The Roadmap: Manage the end-to-end lifecycle of our Magento 2 Commerce platform, balance hands-on development with high-level strategy
      • Performance & Security: Maintain Core Web Vitals, ensure PCI compliance and manage regular security patching and data protection standards
      • Standardization: Establish development standards, documentation and deployment processes to eliminate breaking changes in production
      • Architecture Ownership: Define and document the target-state architecture — application, data, integration, and infrastructure layers — and own the technical decision record for major platform changes
    • AWS Cloud Infrastructure & Reliability
      • AWS Architecture: Own the design and cost of our AWS footprint — EC2/ECS, Aurora MySQL (RDS), ElastiCache for Redis, OpenSearch, S3, CloudFront, Route 53, ALB, Auto Scaling Groups, and VPC/subnet/security group design
      • Infrastructure as Code: Drive everything through Terraform or CloudFormation/CDK — no manual console changes in production
      • Scalability & Peak Traffic: Architect for promotional spikes and seasonal peaks with auto-scaling, read replicas, queue-based decoupling (SQS/SNS/EventBridge), and load testing ahead of major campaigns
      • Resilience & DR: Multi-AZ deployments, backup/restore strategy, documented RTO/RPO, and regular failover testing