Pre-Sales Solutions Architect
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must remove boilerplate: legal disclaimers, EEO, etc. Also remove navigation, cookie, etc. Also remove "Legal Disclaimers" etc. Also remove "Nice to have:" maybe keep as part of qualifications? It's part of qualifications; we can keep as bullet.
We must preserve all substantive information. So include About Us paragraph, Role Overview paragraph, Responsibilities list, Qualifications list (including nice-to-have), Benefits list (What We Offer), Pay (salary range). No schedule.
We must not include headings with filler text. So we will include headings: About Us? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list About Us but we could use About the role? Actually they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those headings. About Us maybe not needed; we could incorporate into About the role? But there is a Role Overview section. Could treat that as About the role. So we can use About the role
for the Role Overview paragraph. And maybe we don't need About Us separate; but we could include it as a paragraph under About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. It didn't forbid About Us heading, but they gave examples. Safer to follow examples: use About the role for the role overview. The About Us description could be placed as a paragraph before that? Might be considered part of About the role? Could include as a paragraph under About the role? Might be okay.
We need to preserve all substantive information; we can include About Us as a paragraph inside About the role section, or as a separate
before the heading? The instruction says output ONLY the HTML fragment; we can have multiple sections. I think we can include a heading
About the role
and inside include both the company overview and role overview paragraphs. Or we could have two paragraphs: first about company, second about role.
Responsibilities: we have a list of bullet points under Responsibilities heading. We'll make Responsibilities
then with each bullet as - .
Qualifications: we have bullet list under Qualifications. We'll make
Qualifications
then . Include nice-to-have as a bullet maybe prefixed with "Nice to have:".
Benefits: we have What We Offer list. We'll make Benefits
then .
Pay: we have salary range. We'll make Pay
then with the range.
We must not include Schedule heading because no schedule.
We must not include Requirements heading separate; qualifications covers.
We must not include Skills heading separate; we could omit.
Now we need to strip boilerplate: Legal Disclaimers, EEO, E-Verify, visa sponsorship, etc. Also remove "All qualified applicants will receive consideration..." etc. Also remove "SimpliGov does not sponsor applicants for work visas." etc. Also remove "The US base salary range..." we keep that as pay. Actually that is pay info; we keep it but maybe we need to keep the sentence about individual pay determined by factors. That's part of pay info; we can keep.
We must also remove "Company-sponsored life + disabilities insurances11" maybe a typo; keep as is? It's part of benefits.
Now let's extract content.
About Us paragraph: "SimpliGov is the government forms and workflow automation platform that helps agencies ditch the paper, move faster, and serve constituents better. We provide one platform for all government workflows - fill, pay, route, automate, sign, and populate. Built for how government really works, SimpliGov combines modern tech with a human touch: no-code tools, fast support, and proven results across 100+ agencies. We are growing rapidly and looking for talented, high-impact players to join our team!"
Role Overview paragraph: "We are looking for a Pre-Sales Solutions Architect to be the strategic technical partner to Sales, owning the solution narrative throughout the buyer journey, from first discovery call through the post-sales handoff to Customer Success and Professional Services. You'll be the technical authority for prospects, turning business requirements into solution architecture, navigating security and compliance requirements, scoping integrations, and defining the success criteria that get deals across the line. You'll bridge product and sales, bringing the SimpliGov platform to life through use-case relevant demos and, just as importantly, translating platform capabilities into business outcomes that help agencies envision how SimpliGov improves operational efficiency, compliance, employee experience, constituent services, and modernization, rather than simply demonstrating features. Throughout, you'll proactively identify and resolve technical risk before it becomes a blocker. This is a role for a self-starter who thrives in a fast-paced sales environment and takes personal ownership of moving every deal forward. This is a strategic partner to Sales who combines deep technical expertise, consultative discovery, storytelling, and solution design. It's a big role at a fast-growing company, with real opportunity to drive impact and scale what works across a growing sales team."
Responsibilities bullets (as listed):
- Technical Deal Ownership
Own technical solution strategy from discovery through close, partnering with AEs who retain overall opportunity ownership.
Lead technical discovery and solution architecture, including integrations, security, compliance, and success criteria.
Identify and resolve technical risks early in partnership with Product and Engineering.
Lead technical responses for RFPs, RFIs, and security questionnaires.
Document requirements, architecture, risks, and decisions to support accurate forecasting and seamless implementation handoffs.
- Demos & Solution Validation
Build tailored demos and reusable solution assets based on prospect workflows and use cases.
Manage demo environments and workflow templates.
Lead prospect sandbox setup, training, and technical validation.
- Cross-Functional Partnership
Serve as the technical advisor to Sales and build relationships with prospect IT, security, and business stakeholders.
Map technical buying stakeholders and share insights with AEs.
Partner with Sales, Product, Customer Success, Professional Services, and Marketing to improve deal execution.
- Professional Services Scoping
Capture implementation requirements, integrations, complexity, assumptions, and success criteria to support Services scoping.
Partner with Professional Services on solutions that are accurately scoped and deliverable.
Provide structured handoffs that minimize post-sale re-discovery.
- Product & Market Feedback
Translate recurring prospect requirements and gaps into actionable Product feedback.
Advocate for scalable, configurable solutions over one-off custom development.
Help Sales accurately communicate product capabilities, constraints, and roadmap direction.
Represent SimpliGov as a solutions expert at webinars, tradeshows, and industry events.
We need to convert each bullet into
- . The sub-bullets could be separate
- items or we could keep them as part of same
- with line breaks? The instruction: Use
- for any list of duties/requirements/benefits. So each duty is a list item. The sub-bullets are duties; we can treat each line as a separate
- . So we will flatten.
Thus Responsibilities list items:
Own technical solution strategy from discovery through close, partnering with AEs who retain overall opportunity ownership.
Lead technical discovery and solution architecture, including integrations, security, compliance, and success criteria.
Identify and resolve technical risks early in partnership with Product and Engineering.
Lead technical responses for RFPs, RFIs, and security questionnaires.
Document requirements, architecture, risks, and decisions to support accurate forecasting and seamless implementation handoffs.
Build tailored demos and reusable solution assets based on prospect workflows and use cases.
Manage demo environments and workflow templates.
Lead prospect sandbox setup, training, and technical validation.
Serve as the technical advisor to Sales and build relationships with prospect IT, security, and business stakeholders.
Map technical buying stakeholders and share insights with AEs.
Partner with Sales, Product, Customer Success, Professional Services, and Marketing to improve deal execution.
Capture implementation requirements, integrations, complexity, assumptions, and success criteria to support Services scoping.
Partner with Professional Services on solutions that are accurately scoped and deliverable.
Provide structured handoffs that minimize post-sale re-discovery.
Translate recurring prospect requirements and gaps into actionable Product feedback.
Advocate for scalable, configurable solutions over one-off custom development.
Help Sales accurately communicate product capabilities, constraints, and roadmap direction.
Represent SimpliGov as a solutions expert at webinars, tradeshows, and industry events.
That's a lot but okay.
Qualifications bullets:
- 5+ years' experience as a trusted technical advisor to customers (pre- or post-sales), ideally with direct experience in solution architecture, security/compliance requirements gathering, or systems integration
- Strong understanding of enterprise IT landscapes, including security, compliance, and integration patterns common to public sector / regulated environments
- Comfortable owning technical scoping conversations independently, from architecture whiteboard sessions to security questionnaires to integration requirements docs
- Excellent understanding and awareness of the enterprise software sales cycle, and how solution validation gates deal progression
- Ability to read the room, adapt, and build relationships with IT and business stakeholders alike
- Excellent communicator, comfortable presenting complex technical solutions to business leaders, IT, and engineers
- Strong follow-through — able to juggle multiple customers and competing priorities at once
- Working fluency with AI-enabled software — able to explain model behavior, data handling, and usage-based metering to security-conscious public sector buyers
- Hands-on experience with low-code workflow automation, digital forms, or e-signature platforms, or with adjacent govtech systems
- Willing and able to travel up to 50% to meet with prospects, run on-site sessions, and attend industry events
- Nice to have: Experience scoping and/or delivering professional services engagements (SOWs, effort estimation, phased implementation planning)
We'll make each as
- .
Benefits bullets from What We Offer:
- Medical, dental, and vision insurance plans, with significant employer contributions for employees AND dependents (contributions based on base-level plan; buyup plans available at additional costs)
- Company-sponsored life + disabilities insurances
- 11 Paid holidays
- Flexible time off
- 401k plan with 4% employer match
- Monthly stipends for wellness and home office expenses
Note: The original had "Company-sponsored life + disabilities insurances11". Likely a typo; we keep as "Company-sponsored life + disabilities insurances". We'll keep.
Pay: "The US base salary range for this full-time position is approximately $125,000.00 - $150,000.00 + benefits. Individual pay is determined by many factors, including job-related skills, experience, and relevant education or training."
We'll put that in
.
Now we need to output HTML fragment only.
Structure:
About the role
SimpliGov is the government forms
for prose. We must remove boilerplate: legal disclaimers, EEO, etc. Also remove navigation, cookie, etc. Also remove "Legal Disclaimers" etc. Also remove "Nice to have:" maybe keep as part of qualifications? It's part of qualifications; we can keep as bullet. We must preserve all substantive information. So include About Us paragraph, Role Overview paragraph, Responsibilities list, Qualifications list (including nice-to-have), Benefits list (What We Offer), Pay (salary range). No schedule. We must not include headings with filler text. So we will include headings: About Us? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list About Us but we could use About the role? Actually they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those headings. About Us maybe not needed; we could incorporate into About the role? But there is a Role Overview section. Could treat that as About the role. So we can use About the role
for the Role Overview paragraph. And maybe we don't need About Us separate; but we could include it as a paragraph under About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. It didn't forbid About Us heading, but they gave examples. Safer to follow examples: use About the role for the role overview. The About Us description could be placed as a paragraph before that? Might be considered part of About the role? Could include as a paragraph under About the role? Might be okay.
We need to preserve all substantive information; we can include About Us as a paragraph inside About the role section, or as a separate
before the heading? The instruction says output ONLY the HTML fragment; we can have multiple sections. I think we can include a heading
About the role
and inside include both the company overview and role overview paragraphs. Or we could have two paragraphs: first about company, second about role. Responsibilities: we have a list of bullet points under Responsibilities heading. We'll makeResponsibilities
then- with each bullet as
- .
Qualifications: we have bullet list under Qualifications. We'll make
Qualifications
then- . Include nice-to-have as a bullet maybe prefixed with "Nice to have:".
Benefits: we have What We Offer list. We'll make
- . The sub-bullets could be separate
- items or we could keep them as part of same
- with line breaks? The instruction: Use
- for any list of duties/requirements/benefits. So each duty is a list item. The sub-bullets are duties; we can treat each line as a separate
- . So we will flatten. Thus Responsibilities list items: Own technical solution strategy from discovery through close, partnering with AEs who retain overall opportunity ownership. Lead technical discovery and solution architecture, including integrations, security, compliance, and success criteria. Identify and resolve technical risks early in partnership with Product and Engineering. Lead technical responses for RFPs, RFIs, and security questionnaires. Document requirements, architecture, risks, and decisions to support accurate forecasting and seamless implementation handoffs. Build tailored demos and reusable solution assets based on prospect workflows and use cases. Manage demo environments and workflow templates. Lead prospect sandbox setup, training, and technical validation. Serve as the technical advisor to Sales and build relationships with prospect IT, security, and business stakeholders. Map technical buying stakeholders and share insights with AEs. Partner with Sales, Product, Customer Success, Professional Services, and Marketing to improve deal execution. Capture implementation requirements, integrations, complexity, assumptions, and success criteria to support Services scoping. Partner with Professional Services on solutions that are accurately scoped and deliverable. Provide structured handoffs that minimize post-sale re-discovery. Translate recurring prospect requirements and gaps into actionable Product feedback. Advocate for scalable, configurable solutions over one-off custom development. Help Sales accurately communicate product capabilities, constraints, and roadmap direction. Represent SimpliGov as a solutions expert at webinars, tradeshows, and industry events. That's a lot but okay. Qualifications bullets: - 5+ years' experience as a trusted technical advisor to customers (pre- or post-sales), ideally with direct experience in solution architecture, security/compliance requirements gathering, or systems integration - Strong understanding of enterprise IT landscapes, including security, compliance, and integration patterns common to public sector / regulated environments - Comfortable owning technical scoping conversations independently, from architecture whiteboard sessions to security questionnaires to integration requirements docs - Excellent understanding and awareness of the enterprise software sales cycle, and how solution validation gates deal progression - Ability to read the room, adapt, and build relationships with IT and business stakeholders alike - Excellent communicator, comfortable presenting complex technical solutions to business leaders, IT, and engineers - Strong follow-through — able to juggle multiple customers and competing priorities at once - Working fluency with AI-enabled software — able to explain model behavior, data handling, and usage-based metering to security-conscious public sector buyers - Hands-on experience with low-code workflow automation, digital forms, or e-signature platforms, or with adjacent govtech systems - Willing and able to travel up to 50% to meet with prospects, run on-site sessions, and attend industry events - Nice to have: Experience scoping and/or delivering professional services engagements (SOWs, effort estimation, phased implementation planning) We'll make each as
- .
Benefits bullets from What We Offer:
- Medical, dental, and vision insurance plans, with significant employer contributions for employees AND dependents (contributions based on base-level plan; buyup plans available at additional costs)
- Company-sponsored life + disabilities insurances
- 11 Paid holidays
- Flexible time off
- 401k plan with 4% employer match
- Monthly stipends for wellness and home office expenses
Note: The original had "Company-sponsored life + disabilities insurances11". Likely a typo; we keep as "Company-sponsored life + disabilities insurances". We'll keep.
Pay: "The US base salary range for this full-time position is approximately $125,000.00 - $150,000.00 + benefits. Individual pay is determined by many factors, including job-related skills, experience, and relevant education or training."
We'll put that in
. Now we need to output HTML fragment only. Structure:
About the role
SimpliGov is the government forms
Benefits
then- .
Pay: we have salary range. We'll make
Pay
thenwith the range. We must not include Schedule heading because no schedule. We must not include Requirements heading separate; qualifications covers. We must not include Skills heading separate; we could omit. Now we need to strip boilerplate: Legal Disclaimers, EEO, E-Verify, visa sponsorship, etc. Also remove "All qualified applicants will receive consideration..." etc. Also remove "SimpliGov does not sponsor applicants for work visas." etc. Also remove "The US base salary range..." we keep that as pay. Actually that is pay info; we keep it but maybe we need to keep the sentence about individual pay determined by factors. That's part of pay info; we can keep. We must also remove "Company-sponsored life + disabilities insurances11" maybe a typo; keep as is? It's part of benefits. Now let's extract content. About Us paragraph: "SimpliGov is the government forms and workflow automation platform that helps agencies ditch the paper, move faster, and serve constituents better. We provide one platform for all government workflows - fill, pay, route, automate, sign, and populate. Built for how government really works, SimpliGov combines modern tech with a human touch: no-code tools, fast support, and proven results across 100+ agencies. We are growing rapidly and looking for talented, high-impact players to join our team!" Role Overview paragraph: "We are looking for a Pre-Sales Solutions Architect to be the strategic technical partner to Sales, owning the solution narrative throughout the buyer journey, from first discovery call through the post-sales handoff to Customer Success and Professional Services. You'll be the technical authority for prospects, turning business requirements into solution architecture, navigating security and compliance requirements, scoping integrations, and defining the success criteria that get deals across the line. You'll bridge product and sales, bringing the SimpliGov platform to life through use-case relevant demos and, just as importantly, translating platform capabilities into business outcomes that help agencies envision how SimpliGov improves operational efficiency, compliance, employee experience, constituent services, and modernization, rather than simply demonstrating features. Throughout, you'll proactively identify and resolve technical risk before it becomes a blocker. This is a role for a self-starter who thrives in a fast-paced sales environment and takes personal ownership of moving every deal forward. This is a strategic partner to Sales who combines deep technical expertise, consultative discovery, storytelling, and solution design. It's a big role at a fast-growing company, with real opportunity to drive impact and scale what works across a growing sales team." Responsibilities bullets (as listed): - Technical Deal Ownership Own technical solution strategy from discovery through close, partnering with AEs who retain overall opportunity ownership. Lead technical discovery and solution architecture, including integrations, security, compliance, and success criteria. Identify and resolve technical risks early in partnership with Product and Engineering. Lead technical responses for RFPs, RFIs, and security questionnaires. Document requirements, architecture, risks, and decisions to support accurate forecasting and seamless implementation handoffs. - Demos & Solution Validation Build tailored demos and reusable solution assets based on prospect workflows and use cases. Manage demo environments and workflow templates. Lead prospect sandbox setup, training, and technical validation. - Cross-Functional Partnership Serve as the technical advisor to Sales and build relationships with prospect IT, security, and business stakeholders. Map technical buying stakeholders and share insights with AEs. Partner with Sales, Product, Customer Success, Professional Services, and Marketing to improve deal execution. - Professional Services Scoping Capture implementation requirements, integrations, complexity, assumptions, and success criteria to support Services scoping. Partner with Professional Services on solutions that are accurately scoped and deliverable. Provide structured handoffs that minimize post-sale re-discovery. - Product & Market Feedback Translate recurring prospect requirements and gaps into actionable Product feedback. Advocate for scalable, configurable solutions over one-off custom development. Help Sales accurately communicate product capabilities, constraints, and roadmap direction. Represent SimpliGov as a solutions expert at webinars, tradeshows, and industry events. We need to convert each bullet into