Senior Solutions Architect
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave a list of allowed headings. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings; we shouldn't invent other headings like Culture and Values. So we must only use those headings. If we don't have content for a heading, we omit it. So we need to map content to those headings.
We have description paragraph: could be About the role.
Responsibilities: the Senior Solutions Architect bullet points.
Requirements: the list after "Requirements". Also there is "Working knowledge of Java, Python..." etc. That's part of requirements.
Qualifications: maybe not separate; we could treat Requirements as qualifications. But we have both Requirements and Qualifications headings allowed. We could split: Requirements could be experience, Qualifications could be technical skills. But we need to avoid thin sections. Better to keep one section: Requirements (or Qualifications). Since they said prefer few substantive sections over many thin ones. So we can use either Requirements or Qualifications, not both. Choose Requirements as it's explicit.
Skills: maybe we could extract technical skills like Java, Python, APIs, cloud platforms, etc. But those are already in requirements. Could create Skills section but might be thin. Better to keep under Requirements.
Benefits: we have mention of competitive bonus and benefits package but no specifics. So we should not create Benefits section because no specific content.
Pay: they mention base salary listed below but not given; no actual number. So we should not create Pay.
Schedule: not given.
Travel Requirement: we have a paragraph about travel. That's not one of the allowed headings exactly, but we could put under About the role or maybe as its own section? Not allowed headings list includes Travel? Not listed. So we must fold travel into a short
or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Travel requirement is not minor metadata? It's a requirement but not a heading. Could be included as a paragraph under About the role or Responsibilities. Probably best to add a
under About the role or Responsibilities. Thus final HTML:
About the role
... description paragraph plus travel requirement maybe.
Responsibilities
- ... ...
Requirements
- ... ...
but no heading. Requirements list: after "Requirements" heading we have: - 10+ years of experience supporting Finance, Treasury, Accounting, Reconciliation, Settlement, BaaS Financial Operations, banking operations, or enterprise solution architecture. - Proven ability to partner directly with business stakeholders and lead technology-driven transformation initiatives. - Strong expertise in enterprise application architecture, APIs, integration patterns, cloud platforms, databases, and data platforms. - Working knowledge of Java, Python, or similar technologies sufficient to guide solution design, review technical approaches, and collaborate effectively with engineering teams. - Experience leading software delivery teams through architecture, development, testing, implementation, and support. - Experience leveraging AI, intelligent automation, operational intelligence, and advanced analytics in business solutions. - Working knowledge of ACH, wires, checks, settlement, funding, reconciliation, cash management, financial controls, and accounting impacts. That's it. We also have culture/values etc but we cannot create heading for that; we could fold into About the role as a paragraph? It's quite long but maybe we can include as part of About the role? The instruction: Prefer a few substantive sections over many thin ones. Including culture might make About the role too long but still okay. However we must not invent headings. We could add a
after About the role that includes the culture/values text. But that is not minor metadata; it's substantive. Could we include it as part of About the role? Probably yes, we can append to the About the role paragraph. But we must not repeat job title as heading. Already not. We must not include boilerplate like cookie/navigation/legal/EEO etc. The disclosure at end includes legal stuff; we should remove that. Also remove "Choice is #PeopleFirst, banking second." etc? That's culture/values; we might keep as part of About the role? It's not boilerplate; it's specific to company culture. Might be okay to keep. But we must also remove duplicated lines. There's no duplication. Thus final HTML:
About the role
The Solutions Architect job family supports the design, delivery, and modernization of technology solutions that enable treasury operations, reconciliation, financial controls, settlement processing, cash management, accounting workflows, and intelligent automation capabilities. These roles partner closely with Finance, Treasury, Operations, Risk, Compliance, and Engineering teams to ensure accurate financial processing, data integrity, regulatory compliance, and scalable operational support. The role is also responsible for identifying opportunities to leverage automation, AI-enabled workflows, operational intelligence, and data-driven decision making to improve efficiency, reduce manual effort, strengthen controls, and enhance the overall effectiveness of finance and treasury operations. Senior Solutions Architect Lead architecture and delivery of complex treasury, reconciliation, settlement, accounting, and BaaS financial operations initiatives. Act as a strategic technology partner to Finance, Treasury, Accounting, and Operations stakeholders. Drive business process transformation through technology modernization, automation, and AI-enabled solutions. Lead solution design across applications, APIs, integrations, enterprise systems, cloud platforms, and data architectures. Guide engineering teams through solution design, implementation, testing, deployment, and production support. Design scalable solutions supporting reconciliation, settlement, cash management, financial controls, and regulatory requirements. Balance business objectives, operational risks, technical complexity, and long-term architecture strategy. This position requires some travel to support business needs, including team collaboration, internal trainings, and cross-functional initiatives. The frequency and duration of travel will vary based on organizational priorities and team needs. Choice is #PeopleFirst, banking second. People don’t need just another bank. People need to be supported by a team of trusted partners who will get to know them and their business, understand their challenges, discover their dreams, and recognize the success in bringing people and banking together in our communities. In contributing to our culture, Choice team members are guided by our core values. Embrace change and encourage innovation. Know when to ask for help and know when to offer help. Better the places we live. Work hard. Do the right thing. Have a little fun. Our vision of Diversity at Choice is supported by our #PeopleFirst mission and our core values. Being #PeopleFirst means that Choice is committed to focusing attention and resources towards creating an environment where everyone feels respected and valued and can do their best work. Doing the right thing means encouraging employees to share their experiences and ideas, and to bring their whole authentic selves to work. Together, we can build an inclusive culture that seeks out, supports, and celebrates diverse voices. We can use our diversity to fuel creativity and innovation and bring us closer to our customers and the communities we serve. Be welcome at Choice. We can see you here.
Responsibilities
- Lead architecture and delivery of complex treasury, reconciliation, settlement, accounting, and BaaS financial operations initiatives.
- Act as a strategic technology partner to Finance, Treasury, Accounting, and Operations stakeholders.
- Drive business process transformation through technology modernization, automation, and AI-enabled solutions.
- Lead solution design across applications, APIs, integrations, enterprise systems, cloud platforms, and data architectures.
- Guide engineering teams through solution design, implementation, testing, deployment, and production support.
- Design scalable solutions supporting reconciliation, settlement, cash management, financial controls, and regulatory requirements.
- Balance business objectives, operational risks, technical complexity, and long-term architecture strategy.
Requirements
- 10+ years of experience supporting Finance, Treasury, Accounting, Reconciliation, Settlement, BaaS Financial Operations, banking operations, or enterprise solution architecture.
- Proven ability to partner directly with business stakeholders and lead technology-driven transformation initiatives.
- Strong expertise in enterprise application architecture, APIs, integration patterns, cloud platforms, databases, and data platforms.
- Working knowledge of Java, Python, or similar technologies sufficient to guide solution design, review technical approaches, and collaborate effectively with engineering teams.
- Experience leading software delivery teams through architecture, development, testing, implementation, and support.
- Experience leveraging AI, intelligent automation, operational intelligence, and advanced analytics in business solutions.
- Working knowledge of ACH, wires, checks, settlement, funding, reconciliation, cash management, financial controls, and accounting impacts.