Full Stack Software Engineer III - Medical Device/Diagnostics
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to extract substantive content: company overview (maybe as About the role? Actually "About the role" is a heading we can use for position summary). The posting includes "Overview Position Summary: Under minimal supervision, perform software development activities including software requirements, design, implementation, and integration." That's the position summary.
Responsibilities: list of key accountabilities essential functions (multiple bullet-like sentences). We'll turn into
- .
Key Relationships: description.
Skills & Capabilities: list.
Qualifications: includes education and experience.
Additional Skills/Knowledge: list.
Also there is some company description at top: "Werfen Werfen is a growing, family-owned, innovative company founded in 1966 in Barcelona, Spain..." That's company overview; could be placed under "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for position summary, maybe also include company overview in a
before sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings only. We can include a brief intro paragraph before any heading (like company description). That's allowed.
We must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines like "We operate directly in over 30 countries..." appears twice; we should keep only once.
We must not include application instructions like "If you are interested... submit your resume or CV." That's application instruction; remove.
Also remove "Closing" etc.
We must preserve all substantive information: company description, position summary, responsibilities, key relationships, skills & capabilities, qualifications, additional skills/knowledge, maybe also mention of travel requirements? There's a line "Travel Requirements" but no detail; it's just heading with no content; we should not create a section for it because no specific content. So ignore.
Also "Closing" etc.
Now craft HTML.
We'll start with a
containing company overview (maybe two paragraphs). Then
About the role
with containing position summary.
Then
Responsibilities
with - each responsibility.
Then
Key Relationships
maybe not in allowed list but we could treat as part of Responsibilities? But it's substantive; we could include as Key Relationships
though not in list. The instruction says use those headings for section headings, but doesn't forbid others; but better to stick to allowed headings. Could we incorporate Key Relationships under Responsibilities? Might be okay but could lose detail. However we could treat Key Relationships as part of Skills? Not ideal. Perhaps we can use Skills
for Skills & Capabilities, and Qualifications
for qualifications, and maybe Additional Skills/Knowledge
could be merged into Skills. But we need to preserve all substantive info; merging is okay as long as we don't lose detail. We can combine Skills & Capabilities and Additional Skills/Knowledge into a single Skills section with lists.
Qualifications section: include education and experience.
We also have "Minimum Knowledge & Experience Required for the Position:" etc.
We'll not include Pay/Benefits/Schedule.
Now produce HTML.
Let's extract details:
Company overview paragraph(s):
- Werfen is a growing, family-owned, innovative company founded in 1966 in Barcelona, Spain.
- We are a worldwide leader in specialized diagnostics in the areas of Hemostasis, Acute Care Diagnostics, Transfusion, Autoimmunity, and Transplant.
- Through our Original Equipment Manufacturing (OEM) business line, we research, develop, and manufacture customized assays and biomaterials.
- We operate directly in 30 countries, and in more than 100 territories through distributors.
- Our Headquarters and Technology Centers are located in the US and Europe, and our workforce is more than 7,000 strong.
- Our success comes from a specific focus in these rapidly evolving diagnostic areas, our commitment to customers, and our dedication to innovation and quality.
- We’re passionate about providing healthcare professionals the most valuable and complete solutions to improve hospital efficiency and enhance patient care.
- Annual revenue is approximately $2 billion and more than 7,000 employees around the world comprise our Werfen team.
- www.werfen.com (maybe keep as link? Not required but could be plain text.)
We should not duplicate the line about operating in 30 countries etc. It appears twice; we keep once.
Now Position Summary: "Under minimal supervision, perform software development activities including software requirements, design, implementation, and integration."
Responsibilities (Key Accountabilities Essential Functions):
List items:
- Participates as an active member on a development team; This includes participating in requirements review, design reviews, code reviews, test case reviews, and team meetings.
- Participates as an active member on a project development team; This includes requirements change control, defect management, risk analysis, and release management
- Creates/Maintains software requirement/functional specifications
- Identifies interfaces between software components and/or hardware
- Creates/Maintains software (component) design documentation
- Creates/Maintains software source code that adheres to design documentation
- Performs unit testing and/or code reviews as per project policy
- Performs integration testing to ensure software functions within application and with devices
- Evaluates, investigates, and implements fixes to assigned software defects
- Evaluates, investigates, and implements assigned software change proposals
Key Relationships:
- To be determined based on department needs, to include interactions such as:
- Provides level of effort for assigned software activities
- Tracks personal estimates over time in order to improve accuracy
- Effectively communicates technical information to a multidisciplinary team in the form of documentation, presentations and technical summaries.
- Makes recommendations or suggestions for department improvements
- Ability to work in a team environment of software developers and testers
Skills & Capabilities:
- Strong written and oral communications skills
- Ability to use software engineering tools: configuration, requirements, and defect management
- Ability to operate instrumentation
Qualifications:
Minimum Knowledge & Experience Required for the Position:
- Education: Associates Degree plus typically 4 to 10 years of related experience or Bachelor’s Degree plus typically 4 to 8 years of related experience or Master’s Degree plus typically 2 to 6 years of related experience or waiver based on experience. Degree should be in a technical discipline such as Chemistry, Math, Physics, Engineering, or Computer Science.
- Experience: Proficiency in computer code (C, C++, Java, C#, etc.) found in product development
Additional Skills/Knowledge:
- Proficiency with a personal computer and software packages
- Ability to use software engineering tools: configuration, requirements, and defect management
- Ability to handle many software components
- Language: English
Travel Requirements: no detail, ignore.
Now we need to avoid duplication: Ability to use software engineering tools appears both in Skills & Capabilities and Additional Skills/Knowledge; we can keep once.
Now produce HTML.
We'll start with a for company overview (maybe multiple
sentences). Could combine into one
but long; better to split into multiple
for readability but still okay.
We must not include any extra headings like "About the company". So just plain paragraphs before first heading.
Then
About the role
Under minimal supervision, perform software development activities including software requirements, design, implementation, and integration.
Then Responsibilities
with each - .
Then
Key Relationships
maybe we can treat as a heading though not in list; but maybe we can incorporate into Responsibilities? However it's distinct. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to prefer those. Safer to use only those headings. Could we put Key Relationships under Responsibilities as a sub-list? Might be okay but could lose nuance. However we could add a Skills
and include both Skills & Capabilities and Additional Skills/Knowledge there. Then we need a section for Qualifications. Key Relationships could be placed under Responsibilities as a bullet list? It's about interactions; could be considered part of responsibilities. I'd include it under Responsibilities as additional bullet items.
Thus we will have sections: About the role, Responsibilities, Qualifications, Skills.
We need to ensure we preserve all substantive info: company overview, position summary, responsibilities (including key relationships), qualifications, skills (including both sets). That covers everything.
Now craft.
Company overview paragraphs: maybe two tags.
Let's write:
Werfen is a growing, family-owned, innovative company founded in 1966 in Barcelona, Spain. We are a worldwide leader in specialized diagnostics in the areas of Hemostasis, Acute Care Diagnostics, Transfusion, Autoimmunity, and Transplant. Through our Original Equipment Manufacturing (OEM) business line, we research, develop, and manufacture customized assays and biomaterials.
We operate directly in 30 countries, and in more than 100 territories through distributors. Our Headquarters and Technology Centers are located in the US and Europe, and our workforce is more than 7,000 strong. Our success comes from a specific focus in these rapidly evolving diagnostic areas, our commitment to customers, and our dedication to innovation and quality. We’re passionate about providing healthcare professionals the most valuable and complete solutions to improve hospital efficiency and enhance patient care. Annual revenue is approximately $2 billion and more than 7,000 employees around the world comprise our Werfen team. www.werfen.com
Now About the role.
Then Responsibilities list: combine the earlier list plus key relationships bullets.
Let's list all responsibilities bullets:
- Participates as an active member on a development team; This includes participating in requirements review, design reviews, code reviews, test case reviews, and team meetings.
- Participates as an active member on a project development team; This includes requirements change control, defect management, risk analysis, and release management
- Creates/Maintains software requirement/functional specifications
- Ident
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract substantive content: company overview (maybe as About the role? Actually "About the role" is a heading we can use for position summary). The posting includes "Overview Position Summary: Under minimal supervision, perform software development activities including software requirements, design, implementation, and integration." That's the position summary. Responsibilities: list of key accountabilities essential functions (multiple bullet-like sentences). We'll turn into
- .
Key Relationships: description.
Skills & Capabilities: list.
Qualifications: includes education and experience.
Additional Skills/Knowledge: list.
Also there is some company description at top: "Werfen Werfen is a growing, family-owned, innovative company founded in 1966 in Barcelona, Spain..." That's company overview; could be placed under "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for position summary, maybe also include company overview in a
before sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings only. We can include a brief intro paragraph before any heading (like company description). That's allowed. We must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines like "We operate directly in over 30 countries..." appears twice; we should keep only once. We must not include application instructions like "If you are interested... submit your resume or CV." That's application instruction; remove. Also remove "Closing" etc. We must preserve all substantive information: company description, position summary, responsibilities, key relationships, skills & capabilities, qualifications, additional skills/knowledge, maybe also mention of travel requirements? There's a line "Travel Requirements" but no detail; it's just heading with no content; we should not create a section for it because no specific content. So ignore. Also "Closing" etc. Now craft HTML. We'll start with a
containing company overview (maybe two paragraphs). Then
About the role
withcontaining position summary. Then
Responsibilities
with- each responsibility.
Then
Key Relationships
maybe not in allowed list but we could treat as part of Responsibilities? But it's substantive; we could include asKey Relationships
though not in list. The instruction says use those headings for section headings, but doesn't forbid others; but better to stick to allowed headings. Could we incorporate Key Relationships under Responsibilities? Might be okay but could lose detail. However we could treat Key Relationships as part of Skills? Not ideal. Perhaps we can useSkills
for Skills & Capabilities, andQualifications
for qualifications, and maybeAdditional Skills/Knowledge
could be merged into Skills. But we need to preserve all substantive info; merging is okay as long as we don't lose detail. We can combine Skills & Capabilities and Additional Skills/Knowledge into a single Skills section with lists. Qualifications section: include education and experience. We also have "Minimum Knowledge & Experience Required for the Position:" etc. We'll not include Pay/Benefits/Schedule. Now produce HTML. Let's extract details: Company overview paragraph(s): - Werfen is a growing, family-owned, innovative company founded in 1966 in Barcelona, Spain. - We are a worldwide leader in specialized diagnostics in the areas of Hemostasis, Acute Care Diagnostics, Transfusion, Autoimmunity, and Transplant. - Through our Original Equipment Manufacturing (OEM) business line, we research, develop, and manufacture customized assays and biomaterials. - We operate directly in 30 countries, and in more than 100 territories through distributors. - Our Headquarters and Technology Centers are located in the US and Europe, and our workforce is more than 7,000 strong. - Our success comes from a specific focus in these rapidly evolving diagnostic areas, our commitment to customers, and our dedication to innovation and quality. - We’re passionate about providing healthcare professionals the most valuable and complete solutions to improve hospital efficiency and enhance patient care. - Annual revenue is approximately $2 billion and more than 7,000 employees around the world comprise our Werfen team. - www.werfen.com (maybe keep as link? Not required but could be plain text.) We should not duplicate the line about operating in 30 countries etc. It appears twice; we keep once. Now Position Summary: "Under minimal supervision, perform software development activities including software requirements, design, implementation, and integration." Responsibilities (Key Accountabilities Essential Functions): List items: - Participates as an active member on a development team; This includes participating in requirements review, design reviews, code reviews, test case reviews, and team meetings. - Participates as an active member on a project development team; This includes requirements change control, defect management, risk analysis, and release management - Creates/Maintains software requirement/functional specifications - Identifies interfaces between software components and/or hardware - Creates/Maintains software (component) design documentation - Creates/Maintains software source code that adheres to design documentation - Performs unit testing and/or code reviews as per project policy - Performs integration testing to ensure software functions within application and with devices - Evaluates, investigates, and implements fixes to assigned software defects - Evaluates, investigates, and implements assigned software change proposals Key Relationships: - To be determined based on department needs, to include interactions such as: - Provides level of effort for assigned software activities - Tracks personal estimates over time in order to improve accuracy - Effectively communicates technical information to a multidisciplinary team in the form of documentation, presentations and technical summaries. - Makes recommendations or suggestions for department improvements - Ability to work in a team environment of software developers and testers Skills & Capabilities: - Strong written and oral communications skills - Ability to use software engineering tools: configuration, requirements, and defect management - Ability to operate instrumentation Qualifications: Minimum Knowledge & Experience Required for the Position: - Education: Associates Degree plus typically 4 to 10 years of related experience or Bachelor’s Degree plus typically 4 to 8 years of related experience or Master’s Degree plus typically 2 to 6 years of related experience or waiver based on experience. Degree should be in a technical discipline such as Chemistry, Math, Physics, Engineering, or Computer Science. - Experience: Proficiency in computer code (C, C++, Java, C#, etc.) found in product development Additional Skills/Knowledge: - Proficiency with a personal computer and software packages - Ability to use software engineering tools: configuration, requirements, and defect management - Ability to handle many software components - Language: English Travel Requirements: no detail, ignore. Now we need to avoid duplication: Ability to use software engineering tools appears both in Skills & Capabilities and Additional Skills/Knowledge; we can keep once. Now produce HTML. We'll start with afor company overview (maybe multiple
sentences). Could combine into one
but long; better to split into multiple
for readability but still okay. We must not include any extra headings like "About the company". So just plain paragraphs before first heading. Then
About the role
Under minimal supervision, perform software development activities including software requirements, design, implementation, and integration.
ThenResponsibilities
- with each
- .
Then
Key Relationships
maybe we can treat as a heading though not in list; but maybe we can incorporate into Responsibilities? However it's distinct. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to prefer those. Safer to use only those headings. Could we put Key Relationships under Responsibilities as a sub-list? Might be okay but could lose nuance. However we could add aSkills
and include both Skills & Capabilities and Additional Skills/Knowledge there. Then we need a section for Qualifications. Key Relationships could be placed under Responsibilities as a bullet list? It's about interactions; could be considered part of responsibilities. I'd include it under Responsibilities as additional bullet items. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills. We need to ensure we preserve all substantive info: company overview, position summary, responsibilities (including key relationships), qualifications, skills (including both sets). That covers everything. Now craft. Company overview paragraphs: maybe twotags. Let's write:
Werfen is a growing, family-owned, innovative company founded in 1966 in Barcelona, Spain. We are a worldwide leader in specialized diagnostics in the areas of Hemostasis, Acute Care Diagnostics, Transfusion, Autoimmunity, and Transplant. Through our Original Equipment Manufacturing (OEM) business line, we research, develop, and manufacture customized assays and biomaterials.
We operate directly in 30 countries, and in more than 100 territories through distributors. Our Headquarters and Technology Centers are located in the US and Europe, and our workforce is more than 7,000 strong. Our success comes from a specific focus in these rapidly evolving diagnostic areas, our commitment to customers, and our dedication to innovation and quality. We’re passionate about providing healthcare professionals the most valuable and complete solutions to improve hospital efficiency and enhance patient care. Annual revenue is approximately $2 billion and more than 7,000 employees around the world comprise our Werfen team. www.werfen.com
Now About the role. Then Responsibilities list: combine the earlier list plus key relationships bullets. Let's list all responsibilities bullets: - Participates as an active member on a development team; This includes participating in requirements review, design reviews, code reviews, test case reviews, and team meetings. - Participates as an active member on a project development team; This includes requirements change control, defect management, risk analysis, and release management - Creates/Maintains software requirement/functional specifications - Ident
- .
Then
- each responsibility.
Then