Senior Cloud Solutions Architect
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it. Never emit heading with filler placeholder. Prefer few substantive sections over many thin ones.
We need to parse the job posting and extract relevant content.
Job Title: Senior Cloud Solutions Architect (not heading). Locations: Hybrid: Waltham, MA or Dallas, TX. Remote: TX, FL, GA, TN, or NC.
We need sections: maybe About the role (intro), Responsibilities (What You Will Get To Do), Requirements/Qualifications (What You Will Bring), Skills (maybe part of requirements), Benefits (What You Will Love It Here! and later benefits), Pay (salary range), Schedule (maybe hybrid/remote info). Also maybe "How You Work" could be part of Skills or Qualities.
We must not create sections with placeholder content. So we need to ensure each section has actual content.
Let's extract:
About the role: The first paragraph after "Job Description" maybe: "SS&C is a leading provider...". Also "Get To Know The Team: Intralinks | SS&C Technologies is looking for a Senior Cloud Solutions Architect to join a team to design secure, resilient, and highly scalable AWS and Private Cloud multi-region environments for our most strategic customers and internal platforms. You will own architectural tasks end-to-end — from network topology and identity boundaries to workload placement, data protection, and operational readiness — partnering with your team, engineering, security, and operations teams to turn ambiguous requirements into reference architectures that ship. This is a hands-on, senior individual-contributor role for someone who has spent years in the weeds of AWS (or other public clouds) networking and cloud security and now wants to shape the platform decisions that others build on."
That's good for About the role.
Responsibilities: "What You Will Get To Do:" bullet list.
List items:
- Design and review AWS architectures across compute, storage, data, and serverless — with an emphasis on multi-account, multi-region, and hybrid connectivity patterns.
- Lead the design of enterprise-grade AWS networking: VPC design, CloudWAN, Transit Gateways, endpoints, Direct Connect, Route 53, hybrid DNS, and segmentation strategies for regulated workloads.
- Define and evolve the cloud security architecture: IAM and identity federation, KMS and key management, encryption in transit and at rest, secrets management, network security controls, and detection/response tooling (GuardDuty, Security Hub, CloudTrail, Config, Inspector, etc).
- Partner with Operations, SRE, and engineering to codify architecture as Terraform / CDK modules and guardrails (SCPs, Config rules, Control Tower).
- Serve as the escalation point for the hardest cloud problems — performance, cost, blast radius, compliance — and drive them to resolution.
- Coach engineers and architects; raise the bar on cloud, networking, and security craft across the organization.
That's responsibilities.
Requirements/Qualifications: "What You Will Bring:" Required and Nice to Have.
Required:
- 7+ years of experience designing and operating production cloud environments, with 5+ years focused primarily on AWS.
- Deep expertise across AWS networking: VPC design, subnetting, routing, Transit Gateway, VPN and Direct Connect, PrivateLink, Global Accelerator, CloudWAN, and inspection architectures.
- Strong cloud security background: IAM policy authoring, least-privilege design, KMS, encryption strategy, network segmentation, WAF/Shield, and cloud-native detection and response.
- Hands-on infrastructure-as-code (Terraform, AWS CDK, or CloudFormation) and capable of contributing to code, pull requests, and GitHub Actions writing a plus
- Excellent written and verbal communication — you can move fluidly between whiteboard, executive slide, and CLI.
Nice to Have:
- AWS certifications such as Solutions Architect Professional, Advanced Networking Specialty, or Security Specialty.
- Experience designing for regulated environments (SOC 2, ISO 27001, PCI, FedRAMP, or similar) and translating controls into concrete architecture and guardrails.
- Track record of leading architecture reviews, threat models, and well-architected assessments for real workloads.
- Experience with multi-cloud or hybrid architectures (Azure, GCP, Private Cloud interconnect).
- Familiarity with container and platform ecosystems (EKS, service mesh, API gateways).
We could combine Required and Nice to Have under Requirements (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills. We can decide to have a "Requirements" section for required, and maybe "Preferred Qualifications" for nice to have, but we should avoid many thin sections. Perhaps combine into one "Requirements" with sub-lists? But we must use
- for any list. Could have two lists under same heading? That's okay.
We could have a "Requirements" heading with required list, then a "Preferred Qualifications" heading with nice-to-have list. That's two sections but both have real content. That's okay.
Skills: maybe we could extract from "How You Work" and "What Could Set You Apart". But we might not need a separate Skills section if we covered skills in Requirements. The instruction says prefer few substantive sections over many thin ones. So we could combine Skills into Requirements or Qualifications. But we need to follow headings list: we can use only those headings that have real content. So we could have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections. Could we combine Benefits and Pay? They are separate headings but both have content. That's okay.
Schedule: we have location/hybrid/remote info. That could be Schedule (work arrangement). So we can put location info under Schedule.
Benefits: from "What You Will Love It Here!" and later benefits paragraph.
Let's extract benefits:
"What You Will Love It Here! Flexibility: Hybrid Work Model & a Business Casual Dress Code, including jeansYour Future: 401k Matching Program, Professional Development ReimbursementWork/Life Balance: Flexible Personal/Vacation Time Off, Sick Leave, Paid HolidaysYour Wellbeing: Medical, Dental, Vision, Employee Assistance Program, Parental LeaveWide-Ranging Perspectives: Committed to Celebrating the Variety of Backgrounds, Talents, and Experiences of Our EmployeesTraining: Hands-On, Team-Customized, including SS&C UniversityExtra Perks: Discounts on fitness clubs, travel and more!"
Also later: "SS&C Technologies offers a comprehensive total rewards package designed to support your wellbeing, growth, and future. Our benefits include medical, dental, and vision coverage; a 401(k) plan with company match; paid time off, holidays, and parental leave; and professional development reimbursement opportunity."
We should combine and deduplicate.
We can list benefits as bullet list:
- Hybrid work model (flexibility)
- Business casual dress code (jeans allowed)
- 401(k) matching program
- Professional development reimbursement
- Flexible personal/vacation time off
- Sick leave
- Paid holidays
- Medical, dental, vision coverage
- Employee assistance program
- Parental leave
- Training: hands-on, team-customized (including SS&C University)
- Extra perks: discounts on fitness clubs, travel, etc.
We should avoid duplication.
Pay: "Actual base salary will vary based on several factors... Massachusetts: The expected base salary for the position is between 130,000.00 USD to 170,000.00 USD."
We can put that as Pay section.
Schedule: location/hybrid/remote: "Locations: Hybrid: Waltham, MA or Dallas, TX. Remote: TX, FL, GA, TN, or NC". Also maybe mention hybrid work model.
We can put schedule info.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Preferred Qualifications
- ...
...
Benefits
- ...
...
Pay
...
Schedule
...
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, application instructions, etc. Already removed.
Check for duplicated lines: we should not repeat same content.
Now craft the prose for About the role: combine the introductory paragraphs.
Let's write:
SS&C is a leading provider of mission-critical, AI-powered technology and services empowering financial services and healthcare organizations to work smarter, faster, and securely. Founded in 1986, SS&C is headquartered in Windsor, Connecticut, and has offices worldwide. More than 23,000 financial services and healthcare organizations rely on SS&C for expertise, scale, and technology. Intralinks | SS&C Technologies is looking for a Senior Cloud Solutions Architect to join a team to design secure, resilient, and highly scalable AWS and Private Cloud multi-region environments for our most strategic customers and internal platforms. You will own architectural tasks end-to-end — from network topology and identity boundaries to workload placement, data protection, and operational readiness — partnering with your team, engineering, security, and operations teams to turn ambiguous requirements into reference architectures that ship. This is a hands-on, senior individual-contributor role for someone who has spent years in the weeds of AWS (or other public clouds) networking and cloud security and now wants to shape the platform decisions that others build on.
That seems good.
Now Responsibilities list as above.
Now Requirements list required.
Now Preferred Qualifications list nice-to-have.
Now Benefits list.
Now Pay paragraph.
Now Schedule paragraph.
Check for any leftover boilerplate: "Thank you for your interest in SS&C! To further explore this opportunity, please apply through our careers page on the corporate website at www.ssctech.com/careers. Unless explicitly requested or approached by SS&C Technologies, Inc. or any of its affiliated companies, the company will not accept unsolicited resumes from headhunters, recruitment agencies, or fee-based recruitment services." That's application instructions and legal; remove.
Also "SS&C Technologies offers a comprehensive total rewards package..." we used for benefits; but we need to ensure we didn't duplicate content. We'll incorporate that into benefits list but not repeat.
Now ensure we don't include any heading like "How You Work" or "What Could Set You Apart". Those could be considered Skills but we can omit if we think they are covered elsewhere. The "How You Work" describes attributes: Systems thinker, Pragmatic, Security-first, Teacher. Could be considered Skills or personal qualities. But we already have Requirements and Preferred Qualifications; we could add a "Skills" section for those soft skills. However instruction says prefer few substantive sections over many thin ones. Adding another section may be okay if it has real content. But we could incorporate those into Requirements as bullet points under "Required" or "Preferred". However they are not exactly requirements but rather "How You Work". Might be better to include a "Skills" section for those attributes. But we already have many sections; maybe we can combine them into Requirements as "Key competencies". But we need to decide.
We have About the role, Responsibilities, Requirements, Preferred Qualifications,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it. Never emit heading with filler placeholder. Prefer few substantive sections over many thin ones. We need to parse the job posting and extract relevant content. Job Title: Senior Cloud Solutions Architect (not heading). Locations: Hybrid: Waltham, MA or Dallas, TX. Remote: TX, FL, GA, TN, or NC. We need sections: maybe About the role (intro), Responsibilities (What You Will Get To Do), Requirements/Qualifications (What You Will Bring), Skills (maybe part of requirements), Benefits (What You Will Love It Here! and later benefits), Pay (salary range), Schedule (maybe hybrid/remote info). Also maybe "How You Work" could be part of Skills or Qualities. We must not create sections with placeholder content. So we need to ensure each section has actual content. Let's extract: About the role: The first paragraph after "Job Description" maybe: "SS&C is a leading provider...". Also "Get To Know The Team: Intralinks | SS&C Technologies is looking for a Senior Cloud Solutions Architect to join a team to design secure, resilient, and highly scalable AWS and Private Cloud multi-region environments for our most strategic customers and internal platforms. You will own architectural tasks end-to-end — from network topology and identity boundaries to workload placement, data protection, and operational readiness — partnering with your team, engineering, security, and operations teams to turn ambiguous requirements into reference architectures that ship. This is a hands-on, senior individual-contributor role for someone who has spent years in the weeds of AWS (or other public clouds) networking and cloud security and now wants to shape the platform decisions that others build on." That's good for About the role. Responsibilities: "What You Will Get To Do:" bullet list. List items: - Design and review AWS architectures across compute, storage, data, and serverless — with an emphasis on multi-account, multi-region, and hybrid connectivity patterns. - Lead the design of enterprise-grade AWS networking: VPC design, CloudWAN, Transit Gateways, endpoints, Direct Connect, Route 53, hybrid DNS, and segmentation strategies for regulated workloads. - Define and evolve the cloud security architecture: IAM and identity federation, KMS and key management, encryption in transit and at rest, secrets management, network security controls, and detection/response tooling (GuardDuty, Security Hub, CloudTrail, Config, Inspector, etc). - Partner with Operations, SRE, and engineering to codify architecture as Terraform / CDK modules and guardrails (SCPs, Config rules, Control Tower). - Serve as the escalation point for the hardest cloud problems — performance, cost, blast radius, compliance — and drive them to resolution. - Coach engineers and architects; raise the bar on cloud, networking, and security craft across the organization. That's responsibilities. Requirements/Qualifications: "What You Will Bring:" Required and Nice to Have. Required: - 7+ years of experience designing and operating production cloud environments, with 5+ years focused primarily on AWS. - Deep expertise across AWS networking: VPC design, subnetting, routing, Transit Gateway, VPN and Direct Connect, PrivateLink, Global Accelerator, CloudWAN, and inspection architectures. - Strong cloud security background: IAM policy authoring, least-privilege design, KMS, encryption strategy, network segmentation, WAF/Shield, and cloud-native detection and response. - Hands-on infrastructure-as-code (Terraform, AWS CDK, or CloudFormation) and capable of contributing to code, pull requests, and GitHub Actions writing a plus - Excellent written and verbal communication — you can move fluidly between whiteboard, executive slide, and CLI. Nice to Have: - AWS certifications such as Solutions Architect Professional, Advanced Networking Specialty, or Security Specialty. - Experience designing for regulated environments (SOC 2, ISO 27001, PCI, FedRAMP, or similar) and translating controls into concrete architecture and guardrails. - Track record of leading architecture reviews, threat models, and well-architected assessments for real workloads. - Experience with multi-cloud or hybrid architectures (Azure, GCP, Private Cloud interconnect). - Familiarity with container and platform ecosystems (EKS, service mesh, API gateways). We could combine Required and Nice to Have under Requirements (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills. We can decide to have a "Requirements" section for required, and maybe "Preferred Qualifications" for nice to have, but we should avoid many thin sections. Perhaps combine into one "Requirements" with sub-lists? But we must use
- for any list. Could have two lists under same heading? That's okay.
We could have a "Requirements" heading with required list, then a "Preferred Qualifications" heading with nice-to-have list. That's two sections but both have real content. That's okay.
Skills: maybe we could extract from "How You Work" and "What Could Set You Apart". But we might not need a separate Skills section if we covered skills in Requirements. The instruction says prefer few substantive sections over many thin ones. So we could combine Skills into Requirements or Qualifications. But we need to follow headings list: we can use only those headings that have real content. So we could have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections. Could we combine Benefits and Pay? They are separate headings but both have content. That's okay.
Schedule: we have location/hybrid/remote info. That could be Schedule (work arrangement). So we can put location info under Schedule.
Benefits: from "What You Will Love It Here!" and later benefits paragraph.
Let's extract benefits:
"What You Will Love It Here! Flexibility: Hybrid Work Model & a Business Casual Dress Code, including jeansYour Future: 401k Matching Program, Professional Development ReimbursementWork/Life Balance: Flexible Personal/Vacation Time Off, Sick Leave, Paid HolidaysYour Wellbeing: Medical, Dental, Vision, Employee Assistance Program, Parental LeaveWide-Ranging Perspectives: Committed to Celebrating the Variety of Backgrounds, Talents, and Experiences of Our EmployeesTraining: Hands-On, Team-Customized, including SS&C UniversityExtra Perks: Discounts on fitness clubs, travel and more!"
Also later: "SS&C Technologies offers a comprehensive total rewards package designed to support your wellbeing, growth, and future. Our benefits include medical, dental, and vision coverage; a 401(k) plan with company match; paid time off, holidays, and parental leave; and professional development reimbursement opportunity."
We should combine and deduplicate.
We can list benefits as bullet list:
- Hybrid work model (flexibility)
- Business casual dress code (jeans allowed)
- 401(k) matching program
- Professional development reimbursement
- Flexible personal/vacation time off
- Sick leave
- Paid holidays
- Medical, dental, vision coverage
- Employee assistance program
- Parental leave
- Training: hands-on, team-customized (including SS&C University)
- Extra perks: discounts on fitness clubs, travel, etc.
We should avoid duplication.
Pay: "Actual base salary will vary based on several factors... Massachusetts: The expected base salary for the position is between 130,000.00 USD to 170,000.00 USD."
We can put that as Pay section.
Schedule: location/hybrid/remote: "Locations: Hybrid: Waltham, MA or Dallas, TX. Remote: TX, FL, GA, TN, or NC". Also maybe mention hybrid work model.
We can put schedule info.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Preferred Qualifications
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
We need to ensure we don't include filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, application instructions, etc. Already removed. Check for duplicated lines: we should not repeat same content. Now craft the prose for About the role: combine the introductory paragraphs. Let's write:SS&C is a leading provider of mission-critical, AI-powered technology and services empowering financial services and healthcare organizations to work smarter, faster, and securely. Founded in 1986, SS&C is headquartered in Windsor, Connecticut, and has offices worldwide. More than 23,000 financial services and healthcare organizations rely on SS&C for expertise, scale, and technology. Intralinks | SS&C Technologies is looking for a Senior Cloud Solutions Architect to join a team to design secure, resilient, and highly scalable AWS and Private Cloud multi-region environments for our most strategic customers and internal platforms. You will own architectural tasks end-to-end — from network topology and identity boundaries to workload placement, data protection, and operational readiness — partnering with your team, engineering, security, and operations teams to turn ambiguous requirements into reference architectures that ship. This is a hands-on, senior individual-contributor role for someone who has spent years in the weeds of AWS (or other public clouds) networking and cloud security and now wants to shape the platform decisions that others build on.
That seems good. Now Responsibilities list as above. Now Requirements list required. Now Preferred Qualifications list nice-to-have. Now Benefits list. Now Pay paragraph. Now Schedule paragraph. Check for any leftover boilerplate: "Thank you for your interest in SS&C! To further explore this opportunity, please apply through our careers page on the corporate website at www.ssctech.com/careers. Unless explicitly requested or approached by SS&C Technologies, Inc. or any of its affiliated companies, the company will not accept unsolicited resumes from headhunters, recruitment agencies, or fee-based recruitment services." That's application instructions and legal; remove. Also "SS&C Technologies offers a comprehensive total rewards package..." we used for benefits; but we need to ensure we didn't duplicate content. We'll incorporate that into benefits list but not repeat. Now ensure we don't include any heading like "How You Work" or "What Could Set You Apart". Those could be considered Skills but we can omit if we think they are covered elsewhere. The "How You Work" describes attributes: Systems thinker, Pragmatic, Security-first, Teacher. Could be considered Skills or personal qualities. But we already have Requirements and Preferred Qualifications; we could add a "Skills" section for those soft skills. However instruction says prefer few substantive sections over many thin ones. Adding another section may be okay if it has real content. But we could incorporate those into Requirements as bullet points under "Required" or "Preferred". However they are not exactly requirements but rather "How You Work". Might be better to include a "Skills" section for those attributes. But we already have many sections; maybe we can combine them into Requirements as "Key competencies". But we need to decide. We have About the role, Responsibilities, Requirements, Preferred Qualifications,