ServiceNow 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 put Job ID etc. Remove boilerplate: navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. So we should remove "How to Apply", "Learn more...", EEO statement, "Powered by JazzHR DD1eCh8RRF". Also remove "Job Title:", "Location:", "Position Type:", "Salary Range:", "Experience Required:", "Sponsorship:"? Those are metadata; we can fold minor metadata 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." So we can include a short paragraph with location, type, salary, sponsorship maybe. But we should not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Salary Range: $150,000–$200,000 Annually. That's pay info. So we can include a Pay section? The rule: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Salary is specific. So we could have a
Pay
with $150,000–$200,000 Annually
. Similarly schedule? Not given. Benefits? Not given. So we omit Benefits and Schedule.
We need sections: About the role (maybe Job Summary), Responsibilities, Requirements, Qualifications, Skills, Benefits (if any), Pay, Schedule. We have content for About the role (Job Summary). Responsibilities? The posting includes responsibilities in the summary: lead design, governance, long-term evolution, drive standards, etc. Could treat as Responsibilities. Requirements? There's Required Qualifications list. Qualifications? There's Preferred Qualifications list. Skills? Could be derived from required qualifications but we might combine. The instruction: "Use - for any list of duties/requirements/benefits". So we need to turn lists into
- . For Required Qualifications we have bullet-like sentences each on new line. We'll make a
. Similarly Preferred Qualifications.
We also have "Experience Required: 6+ years" etc. That's metadata; we could incorporate into a short paragraph.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting: company description, opportunity statement, job summary, responsibilities (the design, governance, etc.), required qualifications (list), preferred qualifications (list), sponsorship note, salary range, location, position type, maybe the note about not sponsoring new H-1B. Also the note about "We are unable to sponsor new H-1B visa petitions for this position." That's substantive.
We need to remove duplicated lines, cookie/navigation/legal/EEO etc. So we remove the EEO statement and the "Learn more about Bright Vision Technologies at www.bvteck.com." and "How to Apply" etc.
We also need to remove the "Job Title:", "Location:", etc as headings but we can include them in a short paragraph.
Let's craft:
About the role
ServiceNow Solutions Architect – Remote. Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.
Maybe we combine company description and opportunity.
Then responsibilities:
Responsibilities
- Lead the design, governance, and long-term evolution of the ServiceNow platform across ITSM, ITOM, HRSD, CSM, SecOps, and custom applications.
- Combine deep platform mastery with enterprise architecture judgment, driving standards for data, integration, security, and customization that keep the platform scalable, maintainable, and aligned with business priorities.
- Shape multi-year roadmaps and influence engineering, business, and executive stakeholders.
But note that the last bullet about shaping roadmaps and influence is from the summary: "The ideal candidate has architected ServiceNow at enterprise scale, can confidently shape multi-year roadmaps, and brings strong influence across engineering, business, and executive stakeholders." That's more about ideal candidate, but could be responsibilities. We'll keep.
Now Required Qualifications:
Required Qualifications
- Bachelor’s or Master’s degree in Computer Science, Information Systems, or a related field
- Eight or more years of ServiceNow experience, with significant time in architecture or technical leadership roles
- Deep expertise across multiple ServiceNow modules
- Strong understanding of the ServiceNow data model, scripting, scoped apps, and platform internals
- Hands-on experience with IntegrationHub, REST APIs, and complex integration scenarios
- Experience designing CMDB, discovery, and service mapping implementations
- Strong understanding of platform security, ACLs, and role design at scale
- Experience leading major upgrades and release planning
- Excellent communication and stakeholder management skills
- ServiceNow CTA, CIS, or CSA certifications
Preferred Qualifications:
Preferred Qualifications
- ServiceNow Certified Technical Architect (CTA) credential
- Experience with Now Assist, GenAI Controller, or AI-driven ServiceNow features
- Exposure to multi-instance, multi-region ServiceNow deployments
- Experience integrating ServiceNow with major SaaS platforms (Workday, Salesforce, SAP)
- Familiarity with HAM Pro, SAM Pro, or App Engine Studio
Now we need to include metadata: location, position type, salary, sponsorship note, and note about not sponsoring new H-1B. Could be a short paragraph after the sections or within an "About the role" paragraph. Let's add a after the sections maybe as a separate
Job Details
but we shouldn't create thin sections. Better to incorporate into a short paragraph under About the role or as a separate without heading. The instruction: "fold minor metadata into a short
or drop it." So we can add a
containing: Location: 100% Remote (U.S.); Position Type: Full-time, Direct W2; Salary Range: $150,000–$200,000 Annually; Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position.
We must not repeat job title as heading. Already we didn't.
Now ensure we removed all boilerplate: no "How to Apply", no EEO, no "Learn more", no "Powered by JazzHR". Also removed duplicated lines like "Job Title:", etc. We have not included those labels explicitly; we just included the info in a paragraph without labels? The paragraph currently includes labels like "Location:", "Position Type:", etc. That's okay; they are not headings. It's minor metadata.
Check for any leftover boilerplate: The original had "Job Title: ServiceNow Solutions Architect Location: 100% Remote (U.S.) Position Type: Full-time, Direct W2 Salary Range: $150,000–$200,000 Annually Experience Required: 6+ years Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." We included location, position type, salary, sponsorship note. We omitted Experience Required: 6+ years because we have Required Qualifications list includes eight or more years. The 6+ years is redundant; we can drop it as it's covered. Good.
Now check that we didn't miss any substantive info: The company description: "Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States." Included. "This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential." Included.
Job Summary: "We are seeking a ServiceNow Solutions Architect to lead the design, governance, and long-term evolution of our ServiceNow platform across ITSM, ITOM, HRSD, CSM, SecOps, and custom applications. The role combines deep platform mastery with enterprise architecture judgment, driving standards for data, integration, security, and customization that keep the platform scalable, maintainable, and aligned with business priorities. The ideal candidate has architected ServiceNow at enterprise scale, can confidently shape multi-year roadmaps, and brings strong influence across engineering, business, and executive stakeholders." We captured design/governance etc in responsibilities, and shaping roadmaps/influence maybe also in responsibilities. We might want to include the "ideal candidate has architected ServiceNow at enterprise scale" as part of responsibilities or maybe as a note. But it's covered by required qualifications (8+ years experience). It's okay.
We also have "The role combines deep platform mastery with enterprise architecture judgment, driving standards for data, integration, security, and customization that keep the platform scalable, maintainable, and aligned with business priorities." That's in responsibilities bullet.
We have "The ideal candidate has architected ServiceNow at enterprise scale, can confidently shape multi-year roadmaps, and brings strong influence across engineering, business, and executive stakeholders." We could add a bullet under responsibilities: "Architect ServiceNow at enterprise scale, shape multi-year roadmaps, and influence engineering, business, and executive stakeholders." Already we have bullet about shaping roadmaps and influence. We could add a bullet about architecting at enterprise scale. Let's add.
Now check for any other substantive info: "Experience designing CMDB, discovery, and service mapping implementations" included. "Strong understanding of platform security, ACLs, and role design at scale" included. "Experience leading major upgrades and release planning" included. "Excellent communication and stakeholder management skills" included. "ServiceNow CTA, CIS, or CSA certifications" included.
Preferred qualifications: all included.
Now ensure we didn't include any filler like "commensurate with experience". Not present.
Now output only HTML fragment.
Let's construct:
About the role
ServiceNow Solutions Architect – Remote. Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.
Location: 100% Remote (U.S.); Position Type: Full-time, Direct W2; Salary Range: $150,000–$200,000 Annually; Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position.
Responsibilities
- Lead the design, governance, and long-term evolution of the ServiceNow platform across ITSM, ITOM, HRSD, CSM, SecOps, and custom applications.
for prose. We must not repeat job title as heading. Do not put Job ID etc. Remove boilerplate: navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. So we should remove "How to Apply", "Learn more...", EEO statement, "Powered by JazzHR DD1eCh8RRF". Also remove "Job Title:", "Location:", "Position Type:", "Salary Range:", "Experience Required:", "Sponsorship:"? Those are metadata; we can fold minor metadata 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." So we can include a short paragraph with location, type, salary, sponsorship maybe. But we should not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Salary Range: $150,000–$200,000 Annually. That's pay info. So we can include a Pay section? The rule: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Salary is specific. So we could have a
Pay
with$150,000–$200,000 Annually
. Similarly schedule? Not given. Benefits? Not given. So we omit Benefits and Schedule. We need sections: About the role (maybe Job Summary), Responsibilities, Requirements, Qualifications, Skills, Benefits (if any), Pay, Schedule. We have content for About the role (Job Summary). Responsibilities? The posting includes responsibilities in the summary: lead design, governance, long-term evolution, drive standards, etc. Could treat as Responsibilities. Requirements? There's Required Qualifications list. Qualifications? There's Preferred Qualifications list. Skills? Could be derived from required qualifications but we might combine. The instruction: "Use- for any list of duties/requirements/benefits". So we need to turn lists into
- . For Required Qualifications we have bullet-like sentences each on new line. We'll make a
- . Similarly Preferred Qualifications.
We also have "Experience Required: 6+ years" etc. That's metadata; we could incorporate into a short paragraph.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting: company description, opportunity statement, job summary, responsibilities (the design, governance, etc.), required qualifications (list), preferred qualifications (list), sponsorship note, salary range, location, position type, maybe the note about not sponsoring new H-1B. Also the note about "We are unable to sponsor new H-1B visa petitions for this position." That's substantive.
We need to remove duplicated lines, cookie/navigation/legal/EEO etc. So we remove the EEO statement and the "Learn more about Bright Vision Technologies at www.bvteck.com." and "How to Apply" etc.
We also need to remove the "Job Title:", "Location:", etc as headings but we can include them in a short paragraph.
Let's craft:
- Lead the design, governance, and long-term evolution of the ServiceNow platform across ITSM, ITOM, HRSD, CSM, SecOps, and custom applications.
- Combine deep platform mastery with enterprise architecture judgment, driving standards for data, integration, security, and customization that keep the platform scalable, maintainable, and aligned with business priorities.
- Shape multi-year roadmaps and influence engineering, business, and executive stakeholders.
- Bachelor’s or Master’s degree in Computer Science, Information Systems, or a related field
- Eight or more years of ServiceNow experience, with significant time in architecture or technical leadership roles
- Deep expertise across multiple ServiceNow modules
- Strong understanding of the ServiceNow data model, scripting, scoped apps, and platform internals
- Hands-on experience with IntegrationHub, REST APIs, and complex integration scenarios
- Experience designing CMDB, discovery, and service mapping implementations
- Strong understanding of platform security, ACLs, and role design at scale
- Experience leading major upgrades and release planning
- Excellent communication and stakeholder management skills
- ServiceNow CTA, CIS, or CSA certifications
- ServiceNow Certified Technical Architect (CTA) credential
- Experience with Now Assist, GenAI Controller, or AI-driven ServiceNow features
- Exposure to multi-instance, multi-region ServiceNow deployments
- Experience integrating ServiceNow with major SaaS platforms (Workday, Salesforce, SAP)
- Familiarity with HAM Pro, SAM Pro, or App Engine Studio
- Lead the design, governance, and long-term evolution of the ServiceNow platform across ITSM, ITOM, HRSD, CSM, SecOps, and custom applications.
About the role
ServiceNow Solutions Architect – Remote. Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.
Maybe we combine company description and opportunity. Then responsibilities:Responsibilities
Required Qualifications
Preferred Qualifications
after the sections maybe as a separate
Job Details
but we shouldn't create thin sections. Better to incorporate into a short paragraph under About the role or as a separatewithout heading. The instruction: "fold minor metadata into a short
or drop it." So we can add a
containing: Location: 100% Remote (U.S.); Position Type: Full-time, Direct W2; Salary Range: $150,000–$200,000 Annually; Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position. We must not repeat job title as heading. Already we didn't. Now ensure we removed all boilerplate: no "How to Apply", no EEO, no "Learn more", no "Powered by JazzHR". Also removed duplicated lines like "Job Title:", etc. We have not included those labels explicitly; we just included the info in a paragraph without labels? The paragraph currently includes labels like "Location:", "Position Type:", etc. That's okay; they are not headings. It's minor metadata. Check for any leftover boilerplate: The original had "Job Title: ServiceNow Solutions Architect Location: 100% Remote (U.S.) Position Type: Full-time, Direct W2 Salary Range: $150,000–$200,000 Annually Experience Required: 6+ years Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." We included location, position type, salary, sponsorship note. We omitted Experience Required: 6+ years because we have Required Qualifications list includes eight or more years. The 6+ years is redundant; we can drop it as it's covered. Good. Now check that we didn't miss any substantive info: The company description: "Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States." Included. "This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential." Included. Job Summary: "We are seeking a ServiceNow Solutions Architect to lead the design, governance, and long-term evolution of our ServiceNow platform across ITSM, ITOM, HRSD, CSM, SecOps, and custom applications. The role combines deep platform mastery with enterprise architecture judgment, driving standards for data, integration, security, and customization that keep the platform scalable, maintainable, and aligned with business priorities. The ideal candidate has architected ServiceNow at enterprise scale, can confidently shape multi-year roadmaps, and brings strong influence across engineering, business, and executive stakeholders." We captured design/governance etc in responsibilities, and shaping roadmaps/influence maybe also in responsibilities. We might want to include the "ideal candidate has architected ServiceNow at enterprise scale" as part of responsibilities or maybe as a note. But it's covered by required qualifications (8+ years experience). It's okay. We also have "The role combines deep platform mastery with enterprise architecture judgment, driving standards for data, integration, security, and customization that keep the platform scalable, maintainable, and aligned with business priorities." That's in responsibilities bullet. We have "The ideal candidate has architected ServiceNow at enterprise scale, can confidently shape multi-year roadmaps, and brings strong influence across engineering, business, and executive stakeholders." We could add a bullet under responsibilities: "Architect ServiceNow at enterprise scale, shape multi-year roadmaps, and influence engineering, business, and executive stakeholders." Already we have bullet about shaping roadmaps and influence. We could add a bullet about architecting at enterprise scale. Let's add. Now check for any other substantive info: "Experience designing CMDB, discovery, and service mapping implementations" included. "Strong understanding of platform security, ACLs, and role design at scale" included. "Experience leading major upgrades and release planning" included. "Excellent communication and stakeholder management skills" included. "ServiceNow CTA, CIS, or CSA certifications" included. Preferred qualifications: all included. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now output only HTML fragment. Let's construct:
About the role
ServiceNow Solutions Architect – Remote. Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.
Location: 100% Remote (U.S.); Position Type: Full-time, Direct W2; Salary Range: $150,000–$200,000 Annually; Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position.
Responsibilities
- . For Required Qualifications we have bullet-like sentences each on new line. We'll make a