Senior Director, Technical Services
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We need to include sections only when posting has real specific content.
We have content: About Parsec (company description) maybe "About the role"? Actually "About Parsec" is company overview, not role. Could be "About the role" heading with description of role? The posting includes "The Role" paragraph describing role. So we can put that under About the role
with paragraphs.
Then we have "Role Characteristics" bullet list? Actually after "The Role" there is "Role Characteristics" with bullet points. Could be part of responsibilities? Might be better to treat as part of responsibilities or separate? The instruction: Use - for any list of duties/requirements/benefits. So we can create sections: Responsibilities (list), Qualifications (list), Benefits (list). Also maybe "Pay" section: they gave salary range $200,000–$255,000 base, plus bonus eligibility. That's pay info, so we should include Pay section.
Schedule: location says fully remote position. That's schedule? Could be Schedule section: "Fully remote". Might be considered schedule? The instruction: include Schedule only if posting actually states them. It does state location fully remote, which could be schedule? Might be better to put under Schedule? But they said Schedule section for work schedule/hours. Not given. Location is not schedule. So we may omit Schedule.
Benefits: they list benefits bullet points. So Benefits section.
We need to preserve all substantive information, not invent. Remove boilerplate like cookie/navigation/legal/EEO etc. Not present.
We need to not repeat job title as heading. So no heading for "Senior Director, Technical Services". Good.
We need to not put Job ID/requisition numbers as headings. None.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
Parsec is hiring a Senior Director, Technical Services to unify and scale the technical backbone of its Professional Services organization. This role owns three distinct but interdependent workstreams: Advisory, Delivery, and Support. Each currently operates with its own rhythm, skill set, and client touchpoints. The mandate for this role is to bring these workstreams together under one operating model so that clients, SI partners, and internal teams experience a consistent standard of technical excellence, regardless of which workstream is engaged. This is a build-and-run role. The teams exist today; the person in this seat will professionalize how they operate, scale them as the business grows, and ensure new hires ramp to full productivity on a defined timeline. Success is measured by predictable delivery, fewer escalations, improved resource utilization across workstreams, and a technical organization that partners with Enablement, Sales, and SI/GSI partners as a single, credible voice on TrakSYS.
Then maybe a paragraph for Role Characteristics? Could be included under About the role or separate? Might be better to incorporate into Responsibilities? But we have a separate Responsibilities section with bullet points.
We have "Key Responsibilities" with sub-bullets for Advisory, Delivery, Support, Cross-Workstream Responsibilities. We'll output a - list, each item maybe containing sub-lists? The instruction: use
- for any list of duties/requirements/benefits. Could nest lists? Probably okay but we can flatten.
We'll produce:
Responsibilities
- Advisory Workstream: Own the quality bar for design artifacts produced by Solution Architects and Tech Leads, ensuring consistency across SI partner-led and Parsec-led engagements; Deploy Advisory resources across concurrent engagements, balancing SI support requests against direct delivery needs; Build and maintain design standards, reference architectures, and reusable artifacts that reduce rework across engagements; Serve as the escalation point for design decisions that carry architectural or precedent-setting weight.
- Delivery Workstream: Manage the engineering resource pool as a shared capacity model: intake, prioritization, staffing, and rebalancing across concurrent projects; Partner with assigned Project Managers on scope, timelines, and quality gates without owning the PM function; Set and enforce engineering and QA standards across POC, enhancement, and targeted delivery work; Track velocity and throughput to inform capacity planning and hiring timing.
- Support Workstream: Own support SLAs, coverage models, and on-call structures across a 24/7, multi-region team; Ensure upgrade assessments, upgrades, and technical reviews follow a consistent methodology and artifact set; Develop a repeatable mentoring and knowledge-transfer offering for clients and SI partners; Feed recurring support themes and technical debt patterns back into Advisory and Engineering to address root causes.
- Cross-Workstream Responsibilities: Establish shared standards and communication norms so clients and SI partners receive a consistent experience across Advisory, Delivery, and Support; Build the metrics, reporting cadence, and operating rhythm that make delivery predictable and visible to leadership (dashboard support provided by the Operations team); Partner with Enablement to define ramp paths and curricula for new hires and ongoing development paths for tenured staff; Report on workstream health, capacity, and delivery metrics to PS leadership, and translate technical delivery performance into terms an executive audience can act on.
Then Qualifications: we have a paragraph with bullet-like items. We'll make a list.
Qualifications
- Experience: 10+ years in technical delivery, professional services, or engineering leadership within enterprise software, industrial software, or MES/manufacturing operations platforms.
- Multi-Function Leadership: Demonstrated experience managing multiple technical functions concurrently (e.g., solution architecture/advisory, engineering delivery, and technical support) as a unified organization.
- Distributed Teams: Experience managing distributed, international teams; direct experience with US/Europe (Spain in particular) team structures is a strong plus.
- Scaling: Track record of building or scaling a technical delivery function during a growth phase, including hiring plans and ramp/enablement design.
- Operational Skills: Strong operational instincts in capacity planning, utilization management, SLA and escalation frameworks, and delivery metrics.
- Range: Comfortable operating at both the strategic level (org design, executive reporting) and the technical level (credible in design and architecture conversations).
- Partner Ecosystem: Experience working with or alongside System Integrator (SI) and Global SI (GSI) partner ecosystems.
- Platform Experience: Direct experience with MES, MOM, or industrial automation platforms (TrakSYS or comparable platforms) preferred.
Then Benefits: list.
Benefits
- $200,000–$255,000 base, plus bonus eligibility
- Comprehensive medical, dental, and vision coverage
- 401(k) with company match
- Generous paid time off and company holidays
- Professional development and career growth opportunities
- Collaborative and innovative work environment
- Opportunity to make a meaningful impact at a growing global software company
Pay: Actually the salary is already in Benefits list as first item. But we could also have a Pay section separate. The instruction: include Pay section only if posting actually states them. It does state salary range. We could either put it in Benefits or Pay. Since they gave a list of benefits including salary, we could keep it under Benefits. But they also have a separate Benefits bullet list after salary. The salary line is part of the Benefits section in the posting: "Benefits $200,000–$255,000 base, plus bonus eligibility Comprehensive medical..." So it's part of benefits. So we can keep it as first item in Benefits.
Schedule: not given.
We might also include a short paragraph about Location: "This is a fully remote position." Could be under a section? Not specified headings for Location. Could be included under About the role or maybe a separate after Benefits. Since they said do not create Pay/Schedule/Benefits sections unless posting actually states them. Location is not a defined heading. We could just add a
after Benefits: "Location: This is a fully remote position." But that might be considered minor metadata; we could fold into a short
. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can add a
for location.
Thus final HTML:
About the role
...
Responsibilities
...
Qualifications
...
Benefits
...
Location: This is a fully remote position.
Make sure no extra whitespace? It's fine.
Check that we didn't include any boilerplate. All content preserved.
Let's craft the About the role paragraph: combine the two paragraphs from "The Role" and maybe "Role Characteristics"? Actually Role Characteristics is separate but could be considered part of responsibilities. But we already have Responsibilities list covering many points. Role Characteristics includes Organizational Span, Delivery Accountability, Governance & Control, Cross-Functional Leadership, Collaboration, Scaling. Those are more about the role's scope, not duties. Could be included under About the role as additional description. To preserve all substantive info, we should include them somewhere. We could add another paragraph after About the role paragraph describing Role Characteristics. Or we could incorporate them into About the role as a paragraph.
Let's create About the role paragraph that includes the description from "The Role" and then a second paragraph for Role Characteristics.
Thus:
About the role
Parsec is hiring a Senior Director, Technical Services to unify and scale the technical backbone of its Professional Services organization. This role owns three distinct but interdependent workstreams: Advisory, Delivery, and Support. Each currently operates with its own rhythm, skill set, and client touchpoints. The mandate for this role is to bring these workstreams together under one operating model so that clients, SI partners, and internal teams experience a consistent standard of technical excellence, regardless of which workstream is engaged. This is a build-and-run role. The teams exist today; the person in this seat will professionalize how they operate, scale them as the business grows, and ensure new hires ramp to full productivity on a defined timeline. Success is measured by predictable delivery, fewer escalations, improved resource utilization across workstreams, and a technical organization that partners with Enablement, Sales, and SI/GSI partners as a single, credible voice on TrakSYS.
The role’s organizational span covers the Advisory, Delivery, and Support workstreams (approximately 30–40 FTEs based primarily in the US and Spain, with additional coverage across Europe). It is accountable for delivery outcomes across all three workstreams, including quality, timeliness, and client/partner satisfaction. The role establishes shared standards, handoff protocols, and reporting cadence across workstreams (capacity planning, utilization, backlog health, escalation tracking). It serves as the primary point of contact for workstream health, capacity, and delivery status communications to PS leadership, works closely with Project Managers (who retain ownership of individual engagements), Enablement, Sales, and SI/GSI partners, and builds hiring plans, role profiles, interview standards, and leveling criteria to support growth across all three workstreams.
That captures Role Characteristics.
Now Responsibilities list as earlier.
Qualifications
About the role
Parsec is hiring a Senior Director, Technical Services to unify and scale the technical backbone of its Professional Services organization. This role owns three distinct but interdependent workstreams: Advisory, Delivery, and Support. Each currently operates with its own rhythm, skill set, and client touchpoints. The mandate for this role is to bring these workstreams together under one operating model so that clients, SI partners, and internal teams experience a consistent standard of technical excellence, regardless of which workstream is engaged. This is a build-and-run role. The teams exist today; the person in this seat will professionalize how they operate, scale them as the business grows, and ensure new hires ramp to full productivity on a defined timeline. Success is measured by predictable delivery, fewer escalations, improved resource utilization across workstreams, and a technical organization that partners with Enablement, Sales, and SI/GSI partners as a single, credible voice on TrakSYS.
Then maybe a paragraph for Role Characteristics? Could be included under About the role or separate? Might be better to incorporate into Responsibilities? But we have a separate Responsibilities section with bullet points. We have "Key Responsibilities" with sub-bullets for Advisory, Delivery, Support, Cross-Workstream Responsibilities. We'll output a- list, each item maybe containing sub-lists? The instruction: use
- for any list of duties/requirements/benefits. Could nest lists? Probably okay but we can flatten.
We'll produce:
Responsibilities
- Advisory Workstream: Own the quality bar for design artifacts produced by Solution Architects and Tech Leads, ensuring consistency across SI partner-led and Parsec-led engagements; Deploy Advisory resources across concurrent engagements, balancing SI support requests against direct delivery needs; Build and maintain design standards, reference architectures, and reusable artifacts that reduce rework across engagements; Serve as the escalation point for design decisions that carry architectural or precedent-setting weight.
- Delivery Workstream: Manage the engineering resource pool as a shared capacity model: intake, prioritization, staffing, and rebalancing across concurrent projects; Partner with assigned Project Managers on scope, timelines, and quality gates without owning the PM function; Set and enforce engineering and QA standards across POC, enhancement, and targeted delivery work; Track velocity and throughput to inform capacity planning and hiring timing.
- Support Workstream: Own support SLAs, coverage models, and on-call structures across a 24/7, multi-region team; Ensure upgrade assessments, upgrades, and technical reviews follow a consistent methodology and artifact set; Develop a repeatable mentoring and knowledge-transfer offering for clients and SI partners; Feed recurring support themes and technical debt patterns back into Advisory and Engineering to address root causes.
- Cross-Workstream Responsibilities: Establish shared standards and communication norms so clients and SI partners receive a consistent experience across Advisory, Delivery, and Support; Build the metrics, reporting cadence, and operating rhythm that make delivery predictable and visible to leadership (dashboard support provided by the Operations team); Partner with Enablement to define ramp paths and curricula for new hires and ongoing development paths for tenured staff; Report on workstream health, capacity, and delivery metrics to PS leadership, and translate technical delivery performance into terms an executive audience can act on.
Qualifications
- Experience: 10+ years in technical delivery, professional services, or engineering leadership within enterprise software, industrial software, or MES/manufacturing operations platforms.
- Multi-Function Leadership: Demonstrated experience managing multiple technical functions concurrently (e.g., solution architecture/advisory, engineering delivery, and technical support) as a unified organization.
- Distributed Teams: Experience managing distributed, international teams; direct experience with US/Europe (Spain in particular) team structures is a strong plus.
- Scaling: Track record of building or scaling a technical delivery function during a growth phase, including hiring plans and ramp/enablement design.
- Operational Skills: Strong operational instincts in capacity planning, utilization management, SLA and escalation frameworks, and delivery metrics.
- Range: Comfortable operating at both the strategic level (org design, executive reporting) and the technical level (credible in design and architecture conversations).
- Partner Ecosystem: Experience working with or alongside System Integrator (SI) and Global SI (GSI) partner ecosystems.
- Platform Experience: Direct experience with MES, MOM, or industrial automation platforms (TrakSYS or comparable platforms) preferred.
Benefits
- $200,000–$255,000 base, plus bonus eligibility
- Comprehensive medical, dental, and vision coverage
- 401(k) with company match
- Generous paid time off and company holidays
- Professional development and career growth opportunities
- Collaborative and innovative work environment
- Opportunity to make a meaningful impact at a growing global software company
after Benefits. Since they said do not create Pay/Schedule/Benefits sections unless posting actually states them. Location is not a defined heading. We could just add a
after Benefits: "Location: This is a fully remote position." But that might be considered minor metadata; we could fold into a short
. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can add a
for location. Thus final HTML:
About the role
...
Responsibilities
- ...
Qualifications
- ...
Benefits
- ...
Location: This is a fully remote position.
Make sure no extra whitespace? It's fine. Check that we didn't include any boilerplate. All content preserved. Let's craft the About the role paragraph: combine the two paragraphs from "The Role" and maybe "Role Characteristics"? Actually Role Characteristics is separate but could be considered part of responsibilities. But we already have Responsibilities list covering many points. Role Characteristics includes Organizational Span, Delivery Accountability, Governance & Control, Cross-Functional Leadership, Collaboration, Scaling. Those are more about the role's scope, not duties. Could be included under About the role as additional description. To preserve all substantive info, we should include them somewhere. We could add another paragraph after About the role paragraph describing Role Characteristics. Or we could incorporate them into About the role as a paragraph. Let's create About the role paragraph that includes the description from "The Role" and then a second paragraph for Role Characteristics. Thus:About the role
Parsec is hiring a Senior Director, Technical Services to unify and scale the technical backbone of its Professional Services organization. This role owns three distinct but interdependent workstreams: Advisory, Delivery, and Support. Each currently operates with its own rhythm, skill set, and client touchpoints. The mandate for this role is to bring these workstreams together under one operating model so that clients, SI partners, and internal teams experience a consistent standard of technical excellence, regardless of which workstream is engaged. This is a build-and-run role. The teams exist today; the person in this seat will professionalize how they operate, scale them as the business grows, and ensure new hires ramp to full productivity on a defined timeline. Success is measured by predictable delivery, fewer escalations, improved resource utilization across workstreams, and a technical organization that partners with Enablement, Sales, and SI/GSI partners as a single, credible voice on TrakSYS.
The role’s organizational span covers the Advisory, Delivery, and Support workstreams (approximately 30–40 FTEs based primarily in the US and Spain, with additional coverage across Europe). It is accountable for delivery outcomes across all three workstreams, including quality, timeliness, and client/partner satisfaction. The role establishes shared standards, handoff protocols, and reporting cadence across workstreams (capacity planning, utilization, backlog health, escalation tracking). It serves as the primary point of contact for workstream health, capacity, and delivery status communications to PS leadership, works closely with Project Managers (who retain ownership of individual engagements), Enablement, Sales, and SI/GSI partners, and builds hiring plans, role profiles, interview standards, and leveling criteria to support growth across all three workstreams.
That captures Role Characteristics. Now Responsibilities list as earlier. Qualifications
- for any list of duties/requirements/benefits. Could nest lists? Probably okay but we can flatten.
We'll produce: