Solutions Architect
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Do not include Job ID etc. Remove boilerplate like EEO etc. We can keep some culture description but not the EEO statement. The posting includes equal opportunity employer statement; we should remove that as boilerplate. Also remove accommodation statement? Might be considered boilerplate but it's about accommodation; maybe keep? It's somewhat generic but could be considered part of culture. Safer to remove generic EEO and accommodation lines.
We need to preserve all substantive information. Let's extract sections.
We'll create sections:
- About the role (maybe Position Summary). Could use "About the role" heading.
- Responsibilities (WHAT DOES OUR SOLUTIONS ARCHITECT DO?)
- Requirements / Qualifications (maybe combine). But we have separate sections: WHAT DO I NEED TO BE A SUCCESSFUL? (personal skills), WHAT ARE THE QUALIFICATIONS I NEED TO HAVE? (experience/knowledge), WHAT QUALIFICATIONS WOULD REALLY HELP SET ME APART... (preferred qualifications). Could combine into Requirements and Preferred Qualifications. But we need to follow instruction: prefer a few substantive sections over many thin ones. Could have sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Work Environment, Benefits.
We must not create sections with filler text. Ensure each section has real content.
Let's extract content.
About the role: Position Summary paragraph: "The Solutions Architect is responsible for providing project proposals and architectural consulting expertise. The Solutions Architect works with and supports our Professional Services and Business Services Teams. This role requires an organized individual with a drive to learn, the ability to manage multiple priorities, and excellent customer service skills. This role will be required to work closely with our vCIOs by participating in Client-facing meetings to support the vCIO as a technical Subject Matter Expert."
We can put that as
.
Responsibilities: The bullet list under "WHAT DOES OUR SOLUTIONS ARCHITECT DO?" It's a series of sentences each starting with a verb. We can turn each into
- . Let's list:
- Analyze, validate and establish business requirements.
- Collaborate with internal and external stakeholders to ensure the proposed solution meets established Convergence standards and will meet the Client’s stated objectives.
- Design solution(s) that are aligned with Convergence Network’s standard stack and that meet the Client’s requirements.
- Identify functional and non-functional requirements related to integrations, scalability and security.
- Conduct comprehensive research to identify the solution, including the technologies, platforms and/or vendors that most effectively meet the business goals.
- Identify, prioritize and manage architectural constraints and adapt solutions to reduce risk, work within budget and ensure alignment with the Convergence stack.
- Prepare budgets with a +/-% level of confidence.
- Upon approval of the budget, prepare a detailed quote that includes all elements of the solution (e.g. consulting, hardware, software, Professional Services resources, etc.)
- Assist in continued development of Convergence’s technology standards and continuous improvement.
- Provide guidance, mentorship, and support to team members (combination of on-site and remote team).
- Provide escalation guidance/mentoring when required.
- Design, development and/or implementation of new products from design to production.
We'll put these in
.
Requirements (mandatory): From "WHAT DO I NEED TO BE A SUCCESSFUL?" (personal skills) and "WHAT ARE THE QUALIFICATIONS I NEED TO HAVE?" (experience). Combine maybe.
Personal skills list:
- Dedication to exceptional, professional service through patience, empathy, solution orientation, follow-up, and effective communication.
- Excellent communication skills (verbal and written in English; feedback, active listening and comprehension).
- Exceptional documentation skills, particularly the ability to position highly technical information for a business audience.
- Build rapport and work productively with others (Clients, teammates and cross-functional teams).
- Ability to work independently.
- Ability to manage conflict and stressful situations.
- Strong sense of initiative, ownership and accountability of your work.
- Provide an exceptional Client experience.
Experience/knowledge list:
- On-premises and cloud-native networking
- On-premises to cloud migrations
- Azure AD, Azure Backup Tools and Microsoft 365 stack
- Network, remote and onsite support; troubleshooting Cisco/Meraki hardware
- Folder redirection and how to safely dismantle MFA and Conditional Access policies
- Bachelors/university degree or equivalent relevant work experience.
- 5+ years of MSP project/solution design experience.
- Previous solution architecting experience: Writing proposals, Developing standard solutions, Performing Client demos, Supporting sales resources in Client calls, Research new products and technology.
We can split into two sub-sections? But we need to keep sections minimal. Could have a single Requirements section with both personal skills and experience as lists.
Preferred Qualifications: "WHAT QUALIFICATIONS WOULD REALLY HELP SET ME APART FROM OTHER APPLICANTS?" list:
- AZ-104 and AZ-305 certifications
- CCDE, CCIE Enterprise Infrastructure, 500-220 ECMS Cisco Certifications
- Experience creating proposals/quotes and working with internal team to develop solutions
- Experience with cloud solutions, Microsoft technology stack
- Understanding of, and a background in, working within the IT Managed Services Provider business model, particularly in a support role.
- Experience with ConnectWise, Kaseya, or other similar MSP tools and software.
Work Environment: "WHAT IS THE WORK ENVIRONMENT LIKE?" paragraph.
We need to preserve all details: Normal office working conditions. Work requires regular sitting/standing at a desk and working with a computer. This position requires standing, walking, sitting, using hands, seeing, reaching, talking, writing, and hearing; it may require occasionally carrying or lifting equipment (10-50 pounds) if working on-site. Position requires contact with others - in meetings, by phone or by email. Interactions focus on data collection, problem solving, needs analysis and technical work.Interactions are initiated in person or electronically. Position may require some travel to customer sites and/or other Convergence office locations. Required to submit daily time sheets that identify work completed each day.
We'll put as .
Benefits: "WHY SHOULD YOU WORK HERE?" paragraph includes culture, benefits, etc. We need to extract benefits specifics: Group benefits plans, including medical, dental, vision in US and health savings and supplement insurance (including dental) in Canada, including retirement plans (401k and RRSP). Education and certification reimbursement is also available. Regular internal training opportunities, training and certification reimbursement. Regular meetings with manager and quarterly conversations about performance and growth. Outstanding teammates, teambuilding and company events, families included. Also culture of unity, transparency, trust. Leadership wants you to be successful. Feedback etc.
We should keep substantive benefits: medical, dental, vision, health savings, supplement insurance, retirement plans (401k RRSP), education and certification reimbursement, internal training opportunities, teambuilding events, etc. Also mention culture aspects maybe as part of Benefits or separate section? Could include a "Culture" section but we already have many sections. Perhaps combine culture and benefits into "Why work here" section. But we need headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect us to use those exact headings if we have content. So we should map our content to those headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly Skills separate from Requirements? The posting has personal skills and qualifications. Could map:
- About the role: Position Summary.
- Responsibilities: WHAT DOES OUR SOLUTIONS ARCHITECT DO?
- Requirements: WHAT ARE THE QUALIFICATIONS I NEED TO HAVE? (experience/knowledge)
- Qualifications: WHAT QUALIFICATIONS WOULD REALLY HELP SET ME APART FROM OTHER APPLICANTS? (preferred)
- Skills: WHAT DO I NEED TO BE A SUCCESSFUL? (personal skills)
- Benefits: WHY SHOULD YOU WORK HERE? (benefits and culture)
- Work Environment maybe not in list; but we could include under About the role? Or maybe we can add a section not in list? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be safer to stick to those headings only. However we have valuable info about Work Environment; we could incorporate it into About the role or Benefits? Probably better to include as a separate section but not in the list? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can add other headings if needed. But to be safe, we could add a Work Environment section with heading "Work Environment". That seems reasonable.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Work Environment.
We must not include Pay or Schedule as they lack specifics.
Now craft HTML.
We'll output:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
- ...
...
Work Environment
...
Make sure to preserve all details.
Let's extract exact phrasing.
About the role: Use the Position Summary paragraph exactly as given.
"The Solutions Architect is responsible for providing project proposals and architectural consulting expertise. The Solutions Architect works with and supports our Professional Services and Business Services Teams. This role requires an organized individual with a drive to learn, the ability to manage multiple priorities, and excellent customer service skills. This role will be required to work closely with our vCIOs by participating in Client-facing meetings to support the vCIO as a technical Subject Matter Expert."
We'll keep that.
Responsibilities: list each
for prose. We must not repeat job title as heading. Do not include Job ID etc. Remove boilerplate like EEO etc. We can keep some culture description but not the EEO statement. The posting includes equal opportunity employer statement; we should remove that as boilerplate. Also remove accommodation statement? Might be considered boilerplate but it's about accommodation; maybe keep? It's somewhat generic but could be considered part of culture. Safer to remove generic EEO and accommodation lines. We need to preserve all substantive information. Let's extract sections. We'll create sections: - About the role (maybe Position Summary). Could use "About the role" heading. - Responsibilities (WHAT DOES OUR SOLUTIONS ARCHITECT DO?) - Requirements / Qualifications (maybe combine). But we have separate sections: WHAT DO I NEED TO BE A SUCCESSFUL? (personal skills), WHAT ARE THE QUALIFICATIONS I NEED TO HAVE? (experience/knowledge), WHAT QUALIFICATIONS WOULD REALLY HELP SET ME APART... (preferred qualifications). Could combine into Requirements and Preferred Qualifications. But we need to follow instruction: prefer a few substantive sections over many thin ones. Could have sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Work Environment, Benefits. We must not create sections with filler text. Ensure each section has real content. Let's extract content. About the role: Position Summary paragraph: "The Solutions Architect is responsible for providing project proposals and architectural consulting expertise. The Solutions Architect works with and supports our Professional Services and Business Services Teams. This role requires an organized individual with a drive to learn, the ability to manage multiple priorities, and excellent customer service skills. This role will be required to work closely with our vCIOs by participating in Client-facing meetings to support the vCIO as a technical Subject Matter Expert." We can put that as
. Responsibilities: The bullet list under "WHAT DOES OUR SOLUTIONS ARCHITECT DO?" It's a series of sentences each starting with a verb. We can turn each into
- .
Requirements (mandatory): From "WHAT DO I NEED TO BE A SUCCESSFUL?" (personal skills) and "WHAT ARE THE QUALIFICATIONS I NEED TO HAVE?" (experience). Combine maybe.
Personal skills list:
- Dedication to exceptional, professional service through patience, empathy, solution orientation, follow-up, and effective communication.
- Excellent communication skills (verbal and written in English; feedback, active listening and comprehension).
- Exceptional documentation skills, particularly the ability to position highly technical information for a business audience.
- Build rapport and work productively with others (Clients, teammates and cross-functional teams).
- Ability to work independently.
- Ability to manage conflict and stressful situations.
- Strong sense of initiative, ownership and accountability of your work.
- Provide an exceptional Client experience.
Experience/knowledge list:
- On-premises and cloud-native networking
- On-premises to cloud migrations
- Azure AD, Azure Backup Tools and Microsoft 365 stack
- Network, remote and onsite support; troubleshooting Cisco/Meraki hardware
- Folder redirection and how to safely dismantle MFA and Conditional Access policies
- Bachelors/university degree or equivalent relevant work experience.
- 5+ years of MSP project/solution design experience.
- Previous solution architecting experience: Writing proposals, Developing standard solutions, Performing Client demos, Supporting sales resources in Client calls, Research new products and technology.
We can split into two sub-sections? But we need to keep sections minimal. Could have a single Requirements section with both personal skills and experience as lists.
Preferred Qualifications: "WHAT QUALIFICATIONS WOULD REALLY HELP SET ME APART FROM OTHER APPLICANTS?" list:
- AZ-104 and AZ-305 certifications
- CCDE, CCIE Enterprise Infrastructure, 500-220 ECMS Cisco Certifications
- Experience creating proposals/quotes and working with internal team to develop solutions
- Experience with cloud solutions, Microsoft technology stack
- Understanding of, and a background in, working within the IT Managed Services Provider business model, particularly in a support role.
- Experience with ConnectWise, Kaseya, or other similar MSP tools and software.
Work Environment: "WHAT IS THE WORK ENVIRONMENT LIKE?" paragraph.
We need to preserve all details: Normal office working conditions. Work requires regular sitting/standing at a desk and working with a computer. This position requires standing, walking, sitting, using hands, seeing, reaching, talking, writing, and hearing; it may require occasionally carrying or lifting equipment (10-50 pounds) if working on-site. Position requires contact with others - in meetings, by phone or by email. Interactions focus on data collection, problem solving, needs analysis and technical work.Interactions are initiated in person or electronically. Position may require some travel to customer sites and/or other Convergence office locations. Required to submit daily time sheets that identify work completed each day.
We'll put as
- ... ...
- ... ...
- ... ...
- ... ...
- ... ...
. Benefits: "WHY SHOULD YOU WORK HERE?" paragraph includes culture, benefits, etc. We need to extract benefits specifics: Group benefits plans, including medical, dental, vision in US and health savings and supplement insurance (including dental) in Canada, including retirement plans (401k and RRSP). Education and certification reimbursement is also available. Regular internal training opportunities, training and certification reimbursement. Regular meetings with manager and quarterly conversations about performance and growth. Outstanding teammates, teambuilding and company events, families included. Also culture of unity, transparency, trust. Leadership wants you to be successful. Feedback etc. We should keep substantive benefits: medical, dental, vision, health savings, supplement insurance, retirement plans (401k RRSP), education and certification reimbursement, internal training opportunities, teambuilding events, etc. Also mention culture aspects maybe as part of Benefits or separate section? Could include a "Culture" section but we already have many sections. Perhaps combine culture and benefits into "Why work here" section. But we need headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect us to use those exact headings if we have content. So we should map our content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly Skills separate from Requirements? The posting has personal skills and qualifications. Could map: - About the role: Position Summary. - Responsibilities: WHAT DOES OUR SOLUTIONS ARCHITECT DO? - Requirements: WHAT ARE THE QUALIFICATIONS I NEED TO HAVE? (experience/knowledge) - Qualifications: WHAT QUALIFICATIONS WOULD REALLY HELP SET ME APART FROM OTHER APPLICANTS? (preferred) - Skills: WHAT DO I NEED TO BE A SUCCESSFUL? (personal skills) - Benefits: WHY SHOULD YOU WORK HERE? (benefits and culture) - Work Environment maybe not in list; but we could include under About the role? Or maybe we can add a section not in list? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be safer to stick to those headings only. However we have valuable info about Work Environment; we could incorporate it into About the role or Benefits? Probably better to include as a separate section but not in the list? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can add other headings if needed. But to be safe, we could add a Work Environment section with heading "Work Environment". That seems reasonable.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Work Environment.
We must not include Pay or Schedule as they lack specifics.
Now craft HTML.
We'll output:
About the role
...
Responsibilities
Requirements
Qualifications
Skills
Benefits
Work Environment
...
Make sure to preserve all details. Let's extract exact phrasing. About the role: Use the Position Summary paragraph exactly as given. "The Solutions Architect is responsible for providing project proposals and architectural consulting expertise. The Solutions Architect works with and supports our Professional Services and Business Services Teams. This role requires an organized individual with a drive to learn, the ability to manage multiple priorities, and excellent customer service skills. This role will be required to work closely with our vCIOs by participating in Client-facing meetings to support the vCIO as a technical Subject Matter Expert." We'll keep that. Responsibilities: list each