Application Support Specialist
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have content for Responsibilities (list). About you (requirements/qualifications/skills). Pay: there is a pay range "$85,000 - $105,000/yr." Also mention bonus and RSU. So Pay section. Schedule: mention hybrid schedule: onsite attendance one to three days per week, depending on business and operational needs. Also later: "We offer a flexible, trust-based hybrid working model... Employees are asked to be in the office an average of three days per week..." So schedule content exists. Benefits: "This position may also be eligible for an annual bonus and restricted stock unit grant in addition to a full range of benefits." Also "We offer a flexible, trust-based hybrid working model..." That's more schedule. Benefits: "full range of benefits" but not specific. Might be considered vague; but we have mention of bonus and RSU as part of compensation, not benefits. The instruction: never create Benefits section unless posting actually states them. It says "in addition to a full range of benefits." That's a statement of benefits existing but not specific. Might be considered too vague; but we could still include Benefits section with that statement? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "full range of benefits" is vague but still states that benefits exist. Might be acceptable? Safer to include Benefits section with that statement? However they said prefer a few substantive sections over many thin ones. Could combine Benefits with Pay? But they want separate headings if content. I'd include Benefits with the statement about full range of benefits plus bonus and RSU maybe. But bonus and RSU are compensation, not benefits. Could put them under Pay. Let's decide: Pay section includes salary range and eligibility for annual bonus and RSU. Benefits section: "full range of benefits" (maybe also mention flexible hybrid working model? That's schedule). We'll keep Benefits brief.
Now About the role: The job summary paragraph could be considered About the role. We'll put that as About the role
with
containing the job summary prose (first paragraph). Ensure we don't repeat job title. Responsibilities: list of duties. Use
- .
Requirements/Qualifications/Skills: The "About you:" section includes many bullet-like sentences. Could split into Requirements (experience, education), Qualifications (maybe degree), Skills (analytical, communication, etc.). But we can combine into one section? The instruction: prefer a few substantive sections over many thin ones. Could make a single "Requirements" section containing all. But we have headings list; we can choose to include Requirements and maybe Skills. However we need to avoid filler. Let's create a Requirements section with experience, education, etc. And a Skills section for analytical, communication, organizational, etc. But many of those overlap. Might be thin. Better to have one "Requirements" that includes experience, education, and skills. But we have separate headings allowed; we can just use Requirements and omit Qualifications/Skills if they'd be thin. Let's do Requirements only.
Thus sections: About the role, Responsibilities, Requirements, Pay, Schedule, Benefits.
Now we need to strip boilerplate: remove EEO, legal, etc. Also remove duplicated lines. Also remove "NOVOFLEX" weird line? That seems like a typo; we should drop it as it's not substantive. Also remove "About Novocure:" paragraph? That's company description; could be considered boilerplate? It's not required to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description might be considered not boilerplate but maybe not needed? It's substantive about mission. Could keep? It's not a required section; we could include as part of About the role? But we already have About the role summary. The company description could be extra but not requested sections. Safer to omit it as it's not asked for. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive about Novocure mission. Should we keep? It's not part of the defined sections but we could still include as a
outside sections? The instruction: Output ONLY the HTML fragment. It didn't say we must wrap everything in sections; we can have
for prose not under a heading. So we could include a
with company description after sections. However they said prefer a few substantive sections over many thin ones. Adding extra paragraph may be okay. But we might just incorporate into About the role? The About the role currently is job summary; we could add company description as another paragraph under same heading? Might be okay. But to be safe, include company description as a separate
after sections, not as a heading. Now compile. Let's extract exact text for About the role: The first paragraph: "Job Summary A the Application Support Specialist you will be responsible for supporting internally developed applications, custom external-facing business applications, and third-party enterprise platforms. This role serves as a primary operational support resource, collaborating with business stakeholders, development teams, consultants, vendors, and internal IT teams to ensure that incidents, defects, service requests, and other application issues are effectively investigated, tracked, communicated, escalated, and resolved in accordance with Novocure’s operational standards. In addition to supporting priority applications, you will provide broader support across Novocure’s application portfolio. Responsibilities include troubleshooting, user guidance and training, testing coordination, documentation, implementation of approved workarounds, and operational readiness activities. The role contributes to application stability, continuous improvement, and an effective user experience across supported platforms. The ideal candidate will have strong analytical, technical, organizational, and communication skills, as well as the ability to develop deep functional expertise in priority applications within a fast-paced, global environment. This is a full-time, exempt position based in our Portsmouth, New Hampshire office. The role follows a hybrid schedule, requiring onsite attendance one to three days per week, depending on business and operational needs. The position reports to the Lead, Application Support." We need to remove "Job Summary A" weird. Probably it's a typo: "Job Summary A the Application Support Specialist". We'll correct to "As the Application Support Specialist". But we must not invent detail; we can keep as is? The phrase "Job Summary A the Application Support Specialist" is garbled. We should maybe fix minor grammar? The instruction: do NOT invent or summarize away detail. Fixing grammar could be considered altering detail but not adding. Might be okay to correct obvious typo. Safer to keep as is? It reads weird. I'd adjust to "As the Application Support Specialist". That's a minor edit but still preserves meaning. I'll do that. Now Responsibilities list: extract bullet points from responsibilities section. They are sentences starting with verbs. We'll make each as
- . List: - Serve as a primary support resource and escalation point for internally developed applications, custom external-facing applications, and third-party enterprise platforms, including applications supporting patient and healthcare provider operations. - Manage assigned tickets and triage, investigate, and coordinate the resolution of application incidents, service requests, defects, and operational issues in accordance with established support processes and service-level expectations. - Develop and maintain deep functional knowledge of supported application workflows, integrations, business processes, and user experience considerations. - Partner closely with business stakeholders, application owners, development teams, consultants, vendors, and internal IT teams to resolve issues, improve system reliability, and support continuous improvement initiatives. - Participate in application projects, enhancements, upgrades, and go-lives by supporting testing, validation, release coordination, operational readiness, knowledge transfer, and the transition to ongoing application support. - Clearly document and communicate root causes, reproduction steps, business impact, and proposed solutions to technical teams and business stakeholders. - Provide timely and professional user support, guidance, training, and approved workarounds. - Create and maintain application documentation, support procedures, knowledge base content, and training materials to promote knowledge sharing and consistent support. - Identify recurring issues and operational risks, assess their business impact, and coordinate appropriate escalations across teams. - Support continuous improvement by identifying opportunities to strengthen application stability, support processes, and the overall user experience. Now Requirements: from "About you:" and other requirements. We need to capture: - 3+ years of experience supporting custom, external-facing, or enterprise business applications in a corporate environment. - Demonstrated experience serving as a primary operational support resource for critical business applications. - Ability to develop and maintain deep functional expertise in priority platforms while supporting a broader application portfolio. - Experience working with application vendors, consultants, development teams, and internal IT teams to troubleshoot issues and implement operational solutions. - Experience supporting applications in healthcare, life sciences, medical devices, or another regulated industry is preferred. - Bachelor’s degree in Information Systems, Computer Science, Business Technology, or a related field, or an equivalent combination of education and relevant professional experience, preferred. - Strong application triage, troubleshooting, root cause analysis, and incident coordination skills. - Ability to translate business processes and user needs into practical support solutions and clear technical documentation. - Strong customer service orientation, with effective written and verbal communication skills for both technical and nontechnical audiences. - Strong organizational and time management skills, with the ability to balance competing priorities based on business impact and operational urgency. - Experience creating and maintaining training materials, operational procedures, functional documentation, and knowledge base content. - Working knowledge of application workflows, system integrations, user access, and dependencies between business systems. - Ability to act as a calm and reliable escalation point during incidents and other high-impact operational events. - Strong analytical and problem-solving skills, including the ability to identify opportunities for continuous process improvement. - Ability to build effective working relationships with global and regional business and IT stakeholders. - Cultural awareness and sensitivity when working with geographically diverse teams. - Self-motivated, adaptable, and persistent in driving issues through to resolution while contributing effectively within a collaborative team environment. - Other Requirements: Expected to be available to respond to site emergencies when required. - Ability to occasionally lift and/or move standard office technology equipment weighing up to 25 pounds. We'll put each as
- under Requirements.
Now Pay: The posting says: "What We Offer This pay range which Novocure expects to pay for this role at the time of this posting is $85,000 - $105,000/yr. This position may also be eligible for an annual bonus and restricted stock unit grant in addition to a full range of benefits. Individual compensation within this range depends on a variety of factors, including, but not limited to, prior education and experience, job-related knowledge and skills demonstrated."
We'll make a
with that. Schedule: The posting says: "This is a full-time, exempt position based in our Portsmouth, New Hampshire office. The role follows a hybrid schedule, requiring onsite attendance one to three days per week, depending on business and operational needs." Also later: "We offer a flexible, trust-based hybrid working model for most of our office-based roles. Employees are asked to be in the office an average of three days per week, with the flexibility to choose which days’ work best for them. We understand that life is not always predictable, so if you need to adjust your schedule, such as leaving early or starting late occasionally, we trust you to balance your time in a way that works for both you and Novocure." We'll combine schedule info into a
. Benefits: "This position may also be eligible for an annual bonus and restricted stock unit grant in addition to a full range of benefits." Actually bonus and RSU already mentioned under Pay. Benefits: "full range of benefits". We'll make a
stating that Novocure offers a full