Senior Manager, Solutions Architect - Supply Chain Planning
Altria · Richmond, VA · 1 mo ago
Hybrid$133k–$202k/yrFull-time
We need to output HTML fragment with 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, no boilerplate. Remove cookie/navigation/legal/EEO etc. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes salary range, hybrid schedule, relocation benefits, benefits list. So we can have Pay, Schedule, Benefits sections.
We need to parse content:
- About the role: The intro paragraphs describing role: "Want to lead the technology architecture that plans and moves products across a Fortune 500 company’s distribution network, from demand and supply planning through transportation, fulfillment, and returns? Join a role where you will take ownership from day one, solve critical business and technology challenges, and deliver solutions with lasting enterprise impact. This position is in Richmond, VA with a hybrid work schedule. Relocation benefits will be provided. We are currently seeking a Sr. Manager, Solutions Architecture - Supply Chain Planning to lead architecture for our Supply Chain Planning and Operations and Logistics platforms. Working within a federated Enterprise Architecture framework, you will be responsible for the plan-to-deliver architecture spanning the distribution infrastructure. You will lead planning platform selection, build SAP integrations, and provide architecture direction to supply chain product and delivery teams."
We can put that as About the role.
- Responsibilities: The bullet list after "What you will be doing:" includes many items. We'll list each as .
- Requirements: The "We want you to have:" includes bullet list of qualifications: Bachelor's degree, 10+ years IT experience including 5+ years as solution architect, hands-on experience architecting supply chain planning platforms and leading enterprise platform selection, strong knowledge of TMS, logistics integration, WMS such as Blue Yonder, SAP integration, experience with S&OP, aligned commercial planning, demand sensing, forecasting, inventory optimization, network optimization, hands-on Microsoft Azure experience including landing zones, PaaS capabilities, identity services, cloud solution blueprinting, experience designing API-led integrations using Azure API Management or iPaaS, knowledge of architecture frameworks such as TOGAF, experience operating within a federated EA model, strong communication and customer leadership skills.
We can separate Requirements (education, experience) and Skills (technical skills). But the instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide what goes where. Usually Requirements = education + experience; Qualifications = maybe certifications? Not present. Skills = technical skills. We'll put education+experience under Requirements. Skills under Skills.
- Benefits: The "Why You’ll Love Building Your Career at Altria" list includes many benefits: hybrid work schedule (in-person three days Tue-Thu, remote Mon-Fri), 15 days PTO, 13 paid holidays, 2 floating holiday days, 37.5-hour workweek, merit increases, performance bonus, 401(k) matching day one, Deferred Profit Sharing (13%-17% of base salary), student loan repayment assistance, conference attendance, professional development stipends, comprehensive medical/dental/vision, paid parental/bonding leave, wellness programs, paid volunteer days. Also relocation benefits mentioned earlier. We'll include these as bullet list.
- Pay: Salary range $132,500.00 - $202,100.00.
- Schedule: Hybrid work schedule: in-person three days a week (Tuesday - Thursday), remote Mondays and Fridays. Also mention 37.5-hour workweek maybe under Benefits but could be schedule. We'll put schedule details.
We must not include filler like "commensurate with experience". Not present.
We must not include duplicated lines. Ensure we preserve all substantive info.
We must not include application instructions, EEO, etc. The posting includes "This position is not eligible for sponsorship." That's substantive? It's a note about sponsorship eligibility. Should we keep? It's not boilerplate; it's a specific condition. Probably keep it under About the role or Requirements? It's a note about eligibility. Could be placed in a short paragraph under About the role or maybe a separate note. Since we must preserve all substantive info, we should include it. Where? Could be in About the role as a sentence.
Also "Relocation benefits will be provided." Already in About the role.
Now produce HTML:
.
Now Requirements list: we have Bachelor's degree, 10+ years IT experience including 5+ years as solution architect
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- Bachelor’s degree in computer science, engineering, or a related field, or equivalent professional experience.
- 10+ years of information technology experience, including 5+ years as a solution architect or technical architect.
Skills
- Hands-on experience architecting supply chain planning platforms and leading enterprise platform selection.
- Strong knowledge of transportation management systems, logistics integration, warehouse management systems such as Blue Yonder, and SAP integration.
- Experience with sales and operations planning, aligned commercial planning, demand sensing, forecasting, inventory optimization, and network optimization.
- Hands-on Microsoft Azure experience, including landing zones, platform-as-a-service capabilities, identity services, and cloud solution blueprinting.
- Experience designing API-led integrations using Azure API Management or an integration platform as a service solution.
- Knowledge of architecture frameworks such as TOGAF, experience operating within a federated Enterprise Architecture model, and strong communication and customer leadership skills.
Benefits
- Relocation benefits provided.
- Hybrid work schedule: in‑person collaboration three days a week (Tuesday‑Thursday) with remote work Mondays and Fridays.
- 15 days of paid time off, 13 paid holidays, 2 floating holiday days.
- 37.5‑hour workweek.
- Annual merit increases and performance bonus.
- 401(k) matching from day one.
- Deferred Profit Sharing – annual company contribution equal to 13%–17% of base salary.
- Student loan repayment assistance.
- Professional development stipends for conferences, certifications, etc.
- Comprehensive medical, dental, and vision coverage for you and your family.
- Paid parental and bonding leave.
- Wellness programs supporting whole‑well‑being.
- Paid volunteer days and a shared commitment to making a difference.
Pay
The salary range for this position is $132,500.00 – $202,100.00.
Schedule
Hybrid schedule: three days in‑office (Tuesday‑Thursday) and two days remote (Monday‑Friday); 37.5‑hour workweek.
We need to ensure no duplicate content: we mentioned hybrid schedule also in Benefits and Schedule; that's okay but could be considered duplicate. Might be better to keep schedule only in Schedule section and not repeat in Benefits. However Benefits list includes hybrid work schedule as a benefit; but we could keep it there and not duplicate in Schedule. But Schedule section should contain schedule specifics; we could keep schedule details there and not duplicate in Benefits. However the instruction: "Prefer a few substantive sections over many thin ones." It's okay to have both but duplication may be considered redundant. Let's avoid duplication: keep hybrid schedule details only in Schedule section, and in Benefits we can mention other benefits but not repeat hybrid schedule. However the benefits list originally includes hybrid schedule as a benefit; we can still mention it but maybe we can rephrase as "Flexible hybrid work arrangement" but that's still duplication. To avoid duplication, we can keep hybrid schedule only in Schedule and not mention it in Benefits. But we must preserve all substantive information; if we omit mention of hybrid schedule from Benefits, we still have it in Schedule, so it's preserved. So it's fine. Thus Benefits list will exclude hybrid schedule. Let's craft Benefits list without hybrid schedule. Also note "Relocation benefits will be provided." We'll keep that. Now ensure we didn't include any boilerplate like "At Altria, we believe a great career starts..." That's substantive? It's more fluff but still part of posting. Could be considered boilerplate but it's describing culture; maybe we keep it as part of Benefits? But it's more like marketing. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The culture paragraph is not explicitly listed as boilerplate to remove, but it's somewhat generic. However it's still substantive? It's describing what you'll find here. Might be considered part of Benefits or About the role. To be safe, we could incorporate some of those points into Benefits (like "Your ideas are welcomed, growth encouraged, impact real", "annual merit increases and performance bonus", "401(k) matching", etc.) We already captured many. The paragraph about "At Altria, we offer more than benefits — we offer a career that fits your life, rewards your ambition, and celebrates your impact." That's fluff; we could omit as it's not specific detail. The instruction says preserve ALL substantive information; fluff may not be substantive. So we can omit generic marketing lines. Thus we keep only concrete benefits. Now produce final HTML. Check for any missing specifics: "Own your time — start with 15 days of paid time off, 13 paid holidays, 2 floating holiday days, and a 37.5-hour workweek so you can recharge and live fully." We captured PTO, holidays, workweek. "Get recognized for your work — annual merit increases and performance bonus." captured. "A future you can count on — 401(k) matching from day one; plus Deferred Profit Sharing, an annual company contribution in an amount equal to 13%–17% of your base salary." captured. "Help with your goals — get help with student loan repayment assistance, attend a conference, or gain a new certification with professional development stipends." captured. "Support for what matters most — comprehensive medical, dental, and vision coverage for you and your family." captured. "Celebrating your milestones — paid parental and bonding leave for life’s biggest moments." captured. "Wellness that goes beyond work — programs that care for your whole well-being at whatever stage you are in your life." captured as wellness programs. "A culture that gives back — paid volunteer days and a shared commitment to making a difference." captured. Now ensure we didn't miss any responsibilities: list them. Responsibilities list from posting: - Leading the architecture and selection of platforms for balancing demand forecasting and supply coordination that support enterprise supply chain requirements. - Designing transportation management, logistics, fulfillment, inventory, and returns capabilities across the distribution network. - Architecting integrations between coordination and distribution platforms, SAP, inventory control systems, suppliers, and contract manufacturing organizations. - Crafting integrated sales and operational planning, coordinated business planning, demand detection, projection, stock level improvement, and supply chain optimization capabilities. - Owning high-level designs and cross-platform integration patterns throughout the Define and Design phases of the architecture lifecycle. - Directing vendor evaluations, product selections, proofs of concept, and solution assessments for alignment with enterprise standards and technology roadmaps. - Defining non-functional requirements for performance, availability, security, scalability, resilience, and operational support. - Preparing Architecture Review Board submissions, resolving findings, conducting post-implementation reviews, and supporting the transition from solution design through build and run. We'll put each as