Senior Manager Solutions Delivery

for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details from the posting. We need to remove duplicated lines, boilerplate. Let's extract content. Job posting text: "Join us at Entrust At Entrust, we’re shaping the future of identity centric security solutions. From our comprehensive portfolio of solutions to our flexible, global workplace, we empower careers, foster collaboration, and build solutions that help keep the world moving safely. Get to Know Us Headquartered in Minnesota, Entrust is an industry leader in identity-centric security solutions, serving over 150 countries with cutting-edge, scalable technologies. But our secret weapon? Our people. It’s the curiosity, dedication, and innovation that drive our success and help us anticipate the future." That's about company overview; could be part of About the role? Usually "About the role" is position overview. But we have "Position Overview Senior Manager, Solutions Delivery REQ: ..." So we can treat that as About the role. We need to not repeat job title as heading; but we can include content about role. We'll create section About the role with prose summarizing the position overview. But we must not invent or summarize away detail; we need to preserve all substantive information. However we can condense into prose but must keep details. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; but we can rephrase? It says do not summarize away detail. So we need to keep the details, maybe as bullet points? But we can keep them in prose but must not lose detail. It's ambiguous. Safer to keep the original sentences as is, maybe as

paragraphs. Thus for About the role we can put the Position Overview paragraph(s) as is. Let's extract Position Overview: "Position Overview Senior Manager, Solutions Delivery REQ: This role is a highly dynamic, customer-facing leadership position responsible for managing a team of Systems Integrators who deliver complex Entrust solutions within customer environments. The Senior Manager, Solutions Delivery is accountable for leading, coaching, and developing technical integration professionals while ensuring delivery quality, customer satisfaction, operational discipline, and continuous improvement. The position requires strong people leadership combined with enough technical depth to understand integration work, anticipate delivery risks, guide technical escalation, and advocate effectively for the team. The ideal candidate has prior hands-on experience in systems integration, software implementation, development, technical consulting, solution delivery, or support engineering, and can translate complex technical realities into clear business and customer-facing communication. This role reports to the Director, Professional Services and operates as a key bridge between Systems Integrators, Project Managers, Sales, Support, Engineering, Product, customers, and PS leadership. Success requires proactive risk management, structured problem solving, customer maturity, financial awareness, and the ability to build a motivated, capable, and continuously improving technical delivery team." We need to keep that. Now Responsibilities: there are several subheadings: Team Leadership & People Development, Technical Delivery Oversight, Risk Management, Issue Resolution & Continuous Improvement, Customer & Stakeholder Management, Operational & Financial Management. Each has bullet-like paragraphs. We'll turn each into

• items? The instruction: Use
  • for any list of duties/requirements/benefits. So we can treat each responsibility area as a list item, maybe with sub-bullets? But we can just make each paragraph a
  • . Keep the content. We need to preserve all substantive information; we can keep the paragraphs as is inside
  • . Now Requirements: Basic Qualifications section. We'll make a list. Basic Qualifications bullet points: - Bachelor’s degree in Computer Science, Engineering, Management Information Systems, or equivalent practical experience. - Minimum of 8 years of experience in systems integration, software implementation, technical services, solution delivery, software development, support engineering, or a related technical field. - Minimum of 3 years of experience leading, mentoring, coordinating, or managing technical professionals in a customer-facing delivery environment. - Strong technical understanding of system integration concepts, infrastructure, enterprise applications, networking, servers, operating systems, databases, security, validation, documentation, and support handoff. - Experience working with demanding customers in finance, government, identity, payments, secure credential issuance, or similarly regulated environments. - Demonstrated ability to lead people through ambiguity, customer pressure, technical escalation, competing priorities, and emotionally complex management situations. - Strong communication, presentation, relationship-building, negotiation, and stakeholder-management skills. - Ability to understand technical work deeply enough to guide, challenge, support, and advocate for Systems Integrators. - Demonstrated ability to identify risks, perform root-cause analysis, prioritize issues, and drive structured corrective actions. - Understanding of utilization, billable hours, delivery cost, project efficiency, and the financial impact of Professional Services execution. - Strong organizational skills, ownership mindset, follow-through, and ability to convert strategic direction into clear team execution. - Ability and willingness to travel as required based on customer and project needs. - Demonstrated experience leading, growing technical teams, creating career paths, motivating, grooming new and experienced talent. We'll put each as
  • . Now Qualifications: Preferred Qualifications section. We'll list similarly. Preferred Qualifications bullet points: - Prior hands-on experience as a Systems Integrator, Software Engineer, Technical Consultant, Implementation Engineer, Solution Architect, Senior Support Engineer, or similar technical delivery role. - Experience with card personalization systems, EMV, smart card technologies, PKI, key management, HSMs, identity management, biometrics, information security, or secure issuance solutions. - Familiarity with Entrust solutions such as DPP, Adaptive Issuance, Identity Enterprise, IDaaS, CA, Secura, or related platforms. - Experience with Windows/Linux servers, Active Directory, DNS, IIS, networking, databases, cloud platforms, containerization, or enterprise deployment tools. - Experience with scripting or automation using tools such as PowerShell, Python, JavaScript, SQL, or similar technologies. - Experience using collaboration and delivery tools such as Jira, Confluence, Git, Bitbucket, JFrog, Microsoft Teams, SharePoint, and Microsoft Copilot. - Experience building technical communities of practice, mentoring programs, reusable knowledge repositories, training plans, or technical enablement initiatives. - Experience managing customer escalations, scope discussions, delivery-risk conversations, cross-functional conflicts, or executive-level customer communications. - PMP, Security+, cloud, cybersecurity, ITIL, or related technical/project certifications are considered an asset. - Spanish language capability is considered an asset for supporting customers and teams across the Americas. Now Skills: The posting didn't have a separate Skills section; but we could combine some skills from qualifications. However instruction: Prefer a few substantive sections over many thin ones. We could omit Skills if not explicitly present. The posting didn't have a "Skills" heading. So we should not create a Skills section unless there is real specific content. There is no explicit Skills section; but we could treat some of the qualifications as skills. However better to omit Skills section. Benefits: The posting includes: "In addition to your pay, Entrust offers eligible colleagues and their dependents comprehensive health and well-being programs which include medical," then cut off. It's incomplete but still mentions health and well-being programs. We'll include Benefits section with that sentence. Pay: Compensation Range section: "Compensation Range The anticipated starting base pay for this position is: $166,419-$244,081 per year (in the primary posting location). Actual compensation will be determined based on geographic location, education, skills and experience. This position is also eligible for the company’s discretionary annual incentive plan." We'll put that as Pay section. Schedule: Not present, omit. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes at end: "Ready to Make an Impact? If you’re excited by the prospect of innovating, growing your career, and collaborating in a dynamic environment, Entrust is the place for you. Join us in making a difference. Let’s build a more secure world—together. Apply today! For more information, visit www.entrust.com. Follow us on, LinkedIn, Facebook, Instagram, and YouTube". That's application instructions and boilerplate; we should remove. Also earlier: "At Entrust, we don’t just offer jobs – we offer career journeys. Here is what you can expect when you join our team: Career Growth: Whether you’re a budding developer or a seasoned expert, we’re invested in your professional journey. With learning-forward initiatives and exciting challenges, your growth is our priority. Flexibility: Life is all about balance. Whether you’re remote, hybrid, or on-site, we offer flexible options that fit your lifestyle. Collaboration: Here, your voice matters. Our teams thrive on sharing ideas, brainstorming solutions, and working together to build a better tomorrow. We believe in securing identities—but it doesn’t stop there. At Entrust, we’re passionate about valuing all identities. Our culture is built on diversity, inclusion, and respect. From unconscious bias training for our leaders to global affinity groups that connect colleagues across the globe, we’re creating a community where everyone is encouraged to be themselves." This is also benefits/culture but not explicitly Benefits; but we could include as part of Benefits? It's more about culture. However we already have Benefits section with health programs. The culture part could be considered Benefits? But it's not explicitly benefits; it's more about company culture. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The culture content is specific; but we don't have a heading for Culture. We could add a Benefits section that includes both health and culture? But the instruction says Benefits section only if posting actually states them. It does state benefits (health and well-being programs). It also states flexibility, collaboration, etc. Those are more like benefits/perks. Could include them in Benefits section as list items. We need to decide: Should we create a Benefits section that includes health programs, flexibility, career growth, collaboration, diversity inclusion? The posting includes those under "Here is what you can expect when you join our team:" with bullet-like statements. That is substantive content about benefits/perks. So we should include Benefits section with those items. Thus Benefits section will list: -