Client Solutions Architect (contract)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have:
- Job Summary (description) could go under About the role.
- Key Responsibilities list.
- Qualifications list (including required and preferred).
- Benefits: "Benefits Information Optional benefits offering include medical, dental, vision and retirement benefits via Tundra Technical Solutions."
- Pay Rate Range: "Pay Rate Range 92 - 115 USD hourly"
- Schedule: "follows a hybrid schedule of 3 days onsite / 2 days remote, and standard hours are 8:00 AM–5:00 PM with some weekend work expected depending on project needs."
We also have location: New York, NY or Lake Mary, FL. Could be part of About the role or maybe separate? Not required heading.
We must not repeat job title as heading. Do not put Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We must not include application instructions.
We must preserve all substantive info.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
At BNY, our culture allows us to run our company better and enables you to grow and succeed. As a leading global financial services company at the heart of the global financial system, we influence nearly 20% of the world’s investible assets. Every day, our teams harness cutting-edge AI and breakthrough technologies to collaborate with clients, driving transformative solutions that redefine industries and uplift communities worldwide. Recognized as a top destination for innovators and champions of inclusion, BNY is where bold ideas meet advanced technology and exceptional talent. Together, we power the future of finance – and this is what is all about. Join us and be part of something extraordinary. Job Summary: We are seeking a Client Solutions Architect to support client connectivity initiatives within the Infrastructure Platform organization. In this role, you will serve as a technical SME, leading the design of client-specific connectivity solutions and providing technical oversight throughout the onboarding lifecycle. This position is highly client-facing and requires strong expertise in extranet and network design, as well as the ability to understand how applications flow through firewalls, load balancers, routers, and related infrastructure. The role may be based in New York, NY or Lake Mary, FL, follows a hybrid schedule of 3 days onsite / 2 days remote, and standard hours are 8:00 AM–5:00 PM with some weekend work expected depending on project needs.
But schedule and location maybe better placed under Schedule section. However schedule content is also in that paragraph. We could split: keep schedule details in Schedule section, location maybe in About the role. But we must not duplicate info. If we put schedule details in Schedule section, we should remove from About the role to avoid duplication. However instructions: preserve ALL substantive information; do not invent or summarize away detail. It doesn't forbid duplication, but better to avoid duplication. We can keep schedule details in Schedule section and keep location in About the role. Thus About the role paragraph will exclude schedule details. Let's extract About the role content: The initial paragraph about BNY culture and job summary up to before schedule. Original: "At BNY, our culture allows us to run our company better and enables you to grow and succeed. As a leading global financial services company at the heart of the global financial system, we influence nearly 20% of the world’s investible assets. Every day, our teams harness cutting-edge AI and breakthrough technologies to collaborate with clients, driving transformative solutions that redefine industries and uplift communities worldwide. Recognized as a top destination for innovators and champions of inclusion, BNY is where bold ideas meet advanced technology and exceptional talent. Together, we power the future of finance – and this is what is all about. Join us and be part of something extraordinary. Job Summary: We are seeking a Client Solutions Architect to support client connectivity initiatives within the Infrastructure Platform organization. In this role, you will serve as a technical SME, leading the design of client-specific connectivity solutions and providing technical oversight throughout the onboarding lifecycle. This position is highly client-facing and requires strong expertise in extranet and network design, as well as the ability to understand how applications flow through firewalls, load balancers, routers, and related infrastructure. The role may be based in New York, NY or Lake Mary, FL, follows a hybrid schedule of 3 days onsite / 2 days remote, and standard hours are 8:00 AM–5:00 PM with some weekend work expected depending on project needs." We need to remove schedule sentence: "The role may be based in New York, NY or Lake Mary, FL, follows a hybrid schedule of 3 days onsite / 2 days remote, and standard hours are 8:00 AM–5:00 PM with some weekend work expected depending on project needs." We can keep location sentence separate: "The role may be based in New York, NY or Lake Mary, FL." Then schedule details go to Schedule section. Thus About the role paragraph: combine the earlier sentences plus location sentence. Let's craft: "At BNY, our culture allows us to run our company better and enables you to grow and succeed. As a leading global financial services company at the heart of the global financial system, we influence nearly 20% of the world’s investible assets. Every day, our teams harness cutting-edge AI and breakthrough technologies to collaborate with clients, driving transformative solutions that redefine industries and uplift communities worldwide. Recognized as a top destination for innovators and champions of inclusion, BNY is where bold ideas meet advanced technology and exceptional talent. Together, we power the future of finance – and this is what is all about. Join us and be part of something extraordinary. Job Summary: We are seeking a Client Solutions Architect to support client connectivity initiatives within the Infrastructure Platform organization. In this role, you will serve as a technical SME, leading the design of client-specific connectivity solutions and providing technical oversight throughout the onboarding lifecycle. This position is highly client-facing and requires strong expertise in extranet and network design, as well as the ability to understand how applications flow through firewalls, load balancers, routers, and related infrastructure. The role may be based in New York, NY or Lake Mary, FL." Now Responsibilities: list from Key Responsibilities bullet points. We need- for each.
Responsibilities items:
- Client Connectivity Design: Develop client-specific infrastructure and connectivity designs using approved solutions, with a primary focus on network and extranet architecture
- Technical Solution Architecture: Partner with clients, application teams, service owners, and internal infrastructure teams to gather requirements and create end-to-end technical designs for new and existing client onboarding initiatives
- Documentation & Design Artifacts: Create, update, and maintain high-quality technical documentation, including PowerPoint presentations and Visio diagrams, using standardized templates and customized adjustments as needed
- Client-Facing Technical Leadership: Serve as a technical SME for external client connectivity, presenting designs and explaining architecture to clients, vendors, partners, and internal stakeholders
- Application Flow Analysis: Understand and document how applications traverse private extranet connections and supporting infrastructure components, including firewalls, load balancers, and routers
- Troubleshooting Support: Provide technical oversight and support for troubleshooting connectivity and application-flow issues across client onboarding and implementation efforts
- Cross-Functional Coordination: Bring together teams across infrastructure, application support, deployment, and project management to drive high-quality solution design and smooth handoff to implementation teams
- Project Portfolio Management: Support multiple active initiatives simultaneously, often at different stages of the project lifecycle, while maintaining speed, quality, and responsiveness
- Tokenization Initiative Support: Contribute to strategic connectivity work related to tokenization and broader client infrastructure modernization efforts
Now Qualifications: includes required qualifications list (bulleted) and Preferred Experience.
We need to decide sections: Qualifications (maybe includes both required and preferred). Could also have Skills but not needed.
We'll put Qualifications section with required qualifications list, and maybe a subheading? Not allowed; only headings as per list. We could include both required and preferred under Qualifications.
Thus Qualifications list items:
- 10+ years of experience in network engineering, infrastructure engineering, or a related technical architecture role
- Strong background in network engineering with deep understanding of extranet technology and private client connectivity models
- Experience designing technical solutions for client onboarding, connectivity, or infrastructure integration projects
- Ability to understand application flow across network infrastructure, including how applications interact with firewalls, load balancers, routers, and related components
- Strong client-facing communication skills with the ability to present technical designs to external clients, vendors, and partners
- Excellent technical writing and documentation skills, with strong proficiency in PowerPoint and Visio
- Ability to support and manage technical troubleshooting efforts across cross-functional teams
- Experience in securities, financial services, fintech, or other highly regulated technology environments
- Bachelor’s degree in Engineering or a related technical field
Preferred Experience:
- Prior experience in a pre-sales engineering, solutions architecture, or client solutions architect capacity
- Familiarity with Splunk, Forward Networks, or other network diagnostic and observability tools
We could include them as part of same list or separate? Probably just continue list.
Now Benefits section: "Benefits Information Optional benefits offering include medical, dental, vision and retirement benefits via Tundra Technical Solutions."
We need to output as
maybe. Pay section: "Pay Rate Range 92 - 115 USD hourly" Schedule section: "follows a hybrid schedule of 3 days onsite / 2 days remote, and standard hours are 8:00 AM–5:00 PM with some weekend work expected depending on project needs." We should output as
. Now ensure we don't include any boilerplate like "Additional Notes", "Why Join Us" maybe we could include as About the role? Actually "Why Join Us" is a section with content: "Join a high-impact infrastructure team responsible for designing and enabling critical client connectivity solutions. This role offers the opportunity to work at the intersection of network engineering, solution design, and client engagement while partnering with application teams, project managers, and external stakeholders on meaningful initiatives. You’ll gain exposure to strategic modernization efforts, including tokenization-related work, while contributing to a team that values quality, speed, and technical excellence. At BNY, our culture speaks for itself, check out the latest BNY news at: BNY Newsroom BNY LinkedIn Here’s a few of our recent awards: America’s Most Innovative Companies, Fortune, 2025 World’s Most Admired Companies, Fortune 2025 “Most Just Companies”, Just Capital and CNBC, 2025" This is substantive content about why join us. Could be placed under a section like "About the role" or maybe "Why Join Us" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "Why Join Us". So we should incorporate that content into About the role perhaps, or maybe under Qualifications? Better to add to About the role as it describes the role and culture. Thus we can append that "Why Join Us" paragraph to About the role after job summary. Thus About the role paragraph will be longer. Let's combine: Start with BNY culture paragraph, job summary, then Why Join Us paragraph. We must ensure not to duplicate schedule/location. Thus final About the role:
At BNY, our culture allows us to run our company better and enables you to grow and succeed. As a leading global financial services company at the heart of the global financial system, we influence nearly 20% of the world’s investible assets. Every day, our teams harness cutting-edge AI and breakthrough technologies to collaborate with clients, driving transformative solutions that