Senior Software Engineer - Evinova
maybe under a generic intro? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we can have a leading paragraph describing company (maybe not a heading). Then we have "About the Role" heading. Then "Key Responsibilities". Then "Required Skills And Experience". Then "Desired Skills And Experience". Then later "SO, WHAT’S NEXT?" etc (application instructions) - we must remove application instructions. Then "Where can I find out more?" etc - also remove. Then "Evinova is an equal opportunity employer..." remove EEO boilerplate. Then "The annual base pay for this position ranges from $127,352.00 - $167,149.50 USD." That's pay info -> include Pay section. Then "In addition, our positions offer a short-term incentive bonus opportunity; eligibility to participate in our equity-based long-term incentive program." That's benefits? Could be part of Benefits. Then "Benefits offered included a qualified retirement program [401(k) plan]; paid vacation and holidays; paid leaves; and, health benefits including medical, prescription drug, dental, and vision coverage in accordance with the terms and conditions of the applicable plans." That's benefits. Then "Additional details of participation in these benefit plans will be provided if an employee receives an offer of employment." That's generic; we can keep as part of benefits but not filler. Then "If hired, employee will be in an “at-will position” and the Company reserves the right to modify base pay..." that's maybe not needed but could be considered boilerplate? It's about employment terms; maybe we keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This statement about at-will position might be considered legal boilerplate; better to remove. Also "Date Posted 23-Sept-2026 Closing Date 27-Sept-2026" - minor metadata; we can fold into short
or drop. Probably drop. Also "Our ways of working support both individual needs and team collaboration. To foster connection and collaboration, employees are expected to work from the office three days per week, creating opportunities for in-person teamwork, innovation, and meaningful connection." That's schedule info (office three days per week). So we can include Schedule section. Also location: "This role is located in Gaithersburg, Maryland. Candidates must reside within commuting distance of Gaithersburg or be willing to relocate for this opportunity." That's location; could be part of About the role or maybe a separate section? Not in list of headings; we could incorporate into About the role paragraph. We need to preserve all substantive information. So we need to include company description, role description, responsibilities, required skills, desired skills, pay, benefits, schedule. Possibly also qualifications? Not separate; required skills includes education etc. We must not invent sections. Use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which sections to include: About the role (the paragraph after "About the Role"), Responsibilities (Key Responsibilities), Requirements (maybe combine Required Skills And Experience and Desired Skills And Experience? Could split into Requirements and Desired Skills? The instruction list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to have Requirements (covering required skills) and Skills (maybe desired skills). Or we could have Requirements and Skills. Let's map:
- About the role: description of role and team.
- Responsibilities: list of key responsibilities.
- Requirements: required skills and experience (education, years, etc.)
- Skills: desired skills and experience (optional)
- Benefits: benefits description.
- Pay: salary range.
- Schedule: office three days per week.
We must not create sections with filler. All have content.
Now we need to extract content precisely.
Company description paragraph: "WHY JOIN US?Evinova is a health-tech business focused on accelerating better health outcomes by advancing digital transformation across the life sciences sector. By combining science-based expertise, evidence-led rigor, and deep human insight, we design digital solutions that enable healthcare to work better for everyone. Operating at the intersection of healthcare, technology, data, and analytics, we are helping unlock the full potential of digital health, transforming how clinical research is conducted, how care is delivered, and how patients experience healthcare. Our solutions are built to scale, driving efficiency, improving decision-making, and ultimately delivering better outcomes for patients worldwide. At Evinova, we are driven by a shared purpose to transform health through data and digital innovation. Our teams collaborate across disciplines to solve complex challenges, continuously learning and evolving in a fast-paced, high-impact environment. We also recognize the importance of flexibility and balance. Our ways of working support both individual needs and team collaboration. To foster connection and collaboration, employees are expected to work from the office three days per week, creating opportunities for in-person teamwork, innovation, and meaningful connection.This role is located in Gaithersburg, Maryland. Candidates must reside within commuting distance of Gaithersburg or be willing to relocate for this opportunity."
We need to split: The part about ways of working and office three days per week is schedule; we might move that to Schedule section. The location sentence could be part of About the role or maybe separate but we can keep in About the role.
Thus About the role paragraph: everything up to before "Our ways of working..."? Actually the sentence about ways of working is part of company description; but we can keep it in About the role? However schedule section will contain that detail. We could keep the sentence in Schedule section only. So we remove it from About the role.
Thus About the role paragraph: "Evinova is a health-tech business focused on accelerating better health outcomes by advancing digital transformation across the life sciences sector. By combining science-based expertise, evidence-led rigor, and deep human insight, we design digital solutions that enable healthcare to work better for everyone. Operating at the intersection of healthcare, technology, data, and analytics, we are helping unlock the full potential of digital health, transforming how clinical research is conducted, how care is delivered, and how patients experience healthcare. Our solutions are built to scale, driving efficiency, improving decision-making, and ultimately delivering better outcomes for patients worldwide. At Evinova, we are driven by a shared purpose to transform health through data and digital innovation. Our teams collaborate across disciplines to solve complex challenges, continuously learning and evolving in a fast-paced, high-impact environment. We also recognize the importance of flexibility and balance." Then location sentence: "This role is located in Gaithersburg, Maryland. Candidates must reside within commuting distance of Gaithersburg or be willing to relocate for this opportunity." Could be part of About the role.
Now Responsibilities: list from "Key Responsibilities" bullet points (they are separated by periods). We'll make
- each.
List:
- Design and build authentication and authorization services used platform-wide, including token issuance and permission resolution.
- Operate and extend our Keycloak-based SSO, covering multi-tenant login, MFA, and IdP federation.
- Build and maintain an analytics SDK that products integrate to send usage data, and a tool for visualizing that data.
- Build notification services (email, in-app, etc.) consumed by products across Evinova.
- Build a customer portal content platform that lets internal Evinova teams publish and manage content for external users.
- Collaborate with product teams adopting shared platform services, defining requirements and driving consensus on deliverables.
- Mentor engineers to promote technical growth and knowledge-sharing within the team.
- Build, deploy, and support applications in production, using AWS native services and CI/CD pipelines through GitHub Actions.
Now Required Skills And Experience: paragraph includes multiple sentences. We'll extract as prose or list? It's a mix. Could make
- for each requirement? The instruction: Use
- for any list of duties/requirements/benefits. So we can treat each requirement as list item.
Let's parse:
- Bachelor's degree in Computer Science, Computer Engineering, or a related field is preferred but not required.
- We will consider self-taught engineers with a strong track record of shipping software.
- 5+ years' experience in software engineering, specializing in API and full-stack development.
- 2+ years of leadership responsibilities on software delivery projects.
- A long history of hands-on coding and enjoying solving complex problems, not just architecture and design.
- Skilled in TypeScript, Java, or Python for scalable systems.
- Experience building and operating shared/platform services (SDKs, APIs) consumed by multiple teams.
- Experi.
- Experienced with AWS services.
- Strong in SQL and NoSQL databases.
- Familiar with GitHub Actions for CI/CD.
- Excellent communication and collaboration skills.
Now Desired Skills And Experience: list:
- Experience with authentication/authorization systems (OAuth2/OIDC, JWTs, SSO, RBAC) or Keycloak.
- Familiarity with client SDK design or data visualization tooling.
- Experience with notification systems or customer-facing portal/content products.
We'll put these under Skills section as list.
Benefits: from "Benefits offered included a qualified retirement program [401(k) plan]; paid vacation and holidays; paid leaves; and, health benefits including medical, prescription drug, dental, and vision coverage in accordance with the terms and conditions of the applicable plans." Also "In addition, our positions offer a short-term incentive bonus opportunity; eligibility to participate in our equity-based long-term incentive program." Also maybe "Additional details of participation in these benefit plans will be provided if an employee receives an offer of employment." That's somewhat generic but we can keep as part of benefits prose.
We'll make a
- list for each benefit item.
List:
- Qualified retirement program [401(k) plan]
- Paid vacation and holidays
- Paid leaves
- Health benefits including medical, prescription drug, dental, and vision coverage (per applicable plans)
- Short-term incentive bonus opportunity
- Eligibility to participate in equity-based long-term incentive program
We could also note that additional details provided upon offer.
Pay: The annual base pay range: $127,352.00 - $167,149.50 USD. Also note that base pay offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. That's substantive; we can include as prose.
Schedule: "Our ways of working support both individual needs and team collaboration. To foster connection and collaboration, employees are expected to work from the office three days per week, creating opportunities for in-person teamwork, innovation, and meaningful connection." Also maybe mention flexibility and balance earlier but that's covered.
We'll make a
for schedule.
Now we need to output only HTML fragment, no markdown fences.
Structure:
Company description (about Evinova) maybe as intro.
About the Role
... role description and location.
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
Schedule
...
We must ensure
for prose. We need to decide which sections to include: About the role (the paragraph after "About the Role"), Responsibilities (Key Responsibilities), Requirements (maybe combine Required Skills And Experience and Desired Skills And Experience? Could split into Requirements and Desired Skills? The instruction list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to have Requirements (covering required skills) and Skills (maybe desired skills). Or we could have Requirements and Skills. Let's map: - About the role: description of role and team. - Responsibilities: list of key responsibilities. - Requirements: required skills and experience (education, years, etc.) - Skills: desired skills and experience (optional) - Benefits: benefits description. - Pay: salary range. - Schedule: office three days per week. We must not create sections with filler. All have content. Now we need to extract content precisely. Company description paragraph: "WHY JOIN US?Evinova is a health-tech business focused on accelerating better health outcomes by advancing digital transformation across the life sciences sector. By combining science-based expertise, evidence-led rigor, and deep human insight, we design digital solutions that enable healthcare to work better for everyone. Operating at the intersection of healthcare, technology, data, and analytics, we are helping unlock the full potential of digital health, transforming how clinical research is conducted, how care is delivered, and how patients experience healthcare. Our solutions are built to scale, driving efficiency, improving decision-making, and ultimately delivering better outcomes for patients worldwide. At Evinova, we are driven by a shared purpose to transform health through data and digital innovation. Our teams collaborate across disciplines to solve complex challenges, continuously learning and evolving in a fast-paced, high-impact environment. We also recognize the importance of flexibility and balance. Our ways of working support both individual needs and team collaboration. To foster connection and collaboration, employees are expected to work from the office three days per week, creating opportunities for in-person teamwork, innovation, and meaningful connection.This role is located in Gaithersburg, Maryland. Candidates must reside within commuting distance of Gaithersburg or be willing to relocate for this opportunity." We need to split: The part about ways of working and office three days per week is schedule; we might move that to Schedule section. The location sentence could be part of About the role or maybe separate but we can keep in About the role. Thus About the role paragraph: everything up to before "Our ways of working..."? Actually the sentence about ways of working is part of company description; but we can keep it in About the role? However schedule section will contain that detail. We could keep the sentence in Schedule section only. So we remove it from About the role. Thus About the role paragraph: "Evinova is a health-tech business focused on accelerating better health outcomes by advancing digital transformation across the life sciences sector. By combining science-based expertise, evidence-led rigor, and deep human insight, we design digital solutions that enable healthcare to work better for everyone. Operating at the intersection of healthcare, technology, data, and analytics, we are helping unlock the full potential of digital health, transforming how clinical research is conducted, how care is delivered, and how patients experience healthcare. Our solutions are built to scale, driving efficiency, improving decision-making, and ultimately delivering better outcomes for patients worldwide. At Evinova, we are driven by a shared purpose to transform health through data and digital innovation. Our teams collaborate across disciplines to solve complex challenges, continuously learning and evolving in a fast-paced, high-impact environment. We also recognize the importance of flexibility and balance." Then location sentence: "This role is located in Gaithersburg, Maryland. Candidates must reside within commuting distance of Gaithersburg or be willing to relocate for this opportunity." Could be part of About the role. Now Responsibilities: list from "Key Responsibilities" bullet points (they are separated by periods). We'll make
- each.
List:
- Design and build authentication and authorization services used platform-wide, including token issuance and permission resolution.
- Operate and extend our Keycloak-based SSO, covering multi-tenant login, MFA, and IdP federation.
- Build and maintain an analytics SDK that products integrate to send usage data, and a tool for visualizing that data.
- Build notification services (email, in-app, etc.) consumed by products across Evinova.
- Build a customer portal content platform that lets internal Evinova teams publish and manage content for external users.
- Collaborate with product teams adopting shared platform services, defining requirements and driving consensus on deliverables.
- Mentor engineers to promote technical growth and knowledge-sharing within the team.
- Build, deploy, and support applications in production, using AWS native services and CI/CD pipelines through GitHub Actions.
Now Required Skills And Experience: paragraph includes multiple sentences. We'll extract as prose or list? It's a mix. Could make
- for each requirement? The instruction: Use
- for any list of duties/requirements/benefits. So we can treat each requirement as list item.
Let's parse:
- Bachelor's degree in Computer Science, Computer Engineering, or a related field is preferred but not required.
- We will consider self-taught engineers with a strong track record of shipping software.
- 5+ years' experience in software engineering, specializing in API and full-stack development.
- 2+ years of leadership responsibilities on software delivery projects.
- A long history of hands-on coding and enjoying solving complex problems, not just architecture and design.
- Skilled in TypeScript, Java, or Python for scalable systems.
- Experience building and operating shared/platform services (SDKs, APIs) consumed by multiple teams.
- Experi.
- Experienced with AWS services.
- Strong in SQL and NoSQL databases.
- Familiar with GitHub Actions for CI/CD.
- Excellent communication and collaboration skills.
Now Desired Skills And Experience: list:
- Experience with authentication/authorization systems (OAuth2/OIDC, JWTs, SSO, RBAC) or Keycloak.
- Familiarity with client SDK design or data visualization tooling.
- Experience with notification systems or customer-facing portal/content products.
We'll put these under Skills section as list.
Benefits: from "Benefits offered included a qualified retirement program [401(k) plan]; paid vacation and holidays; paid leaves; and, health benefits including medical, prescription drug, dental, and vision coverage in accordance with the terms and conditions of the applicable plans." Also "In addition, our positions offer a short-term incentive bonus opportunity; eligibility to participate in our equity-based long-term incentive program." Also maybe "Additional details of participation in these benefit plans will be provided if an employee receives an offer of employment." That's somewhat generic but we can keep as part of benefits prose.
We'll make a
- list for each benefit item.
List:
- Qualified retirement program [401(k) plan]
- Paid vacation and holidays
- Paid leaves
- Health benefits including medical, prescription drug, dental, and vision coverage (per applicable plans)
- Short-term incentive bonus opportunity
- Eligibility to participate in equity-based long-term incentive program
We could also note that additional details provided upon offer.
Pay: The annual base pay range: $127,352.00 - $167,149.50 USD. Also note that base pay offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. That's substantive; we can include as prose.
Schedule: "Our ways of working support both individual needs and team collaboration. To foster connection and collaboration, employees are expected to work from the office three days per week, creating opportunities for in-person teamwork, innovation, and meaningful connection." Also maybe mention flexibility and balance earlier but that's covered.
We'll make a
for schedule. Now we need to output only HTML fragment, no markdown fences. Structure:
Company description (about Evinova) maybe as intro.
About the Role
... role description and location.
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
We must ensure
- list for each benefit item.
List:
- Qualified retirement program [401(k) plan]
- Paid vacation and holidays
- Paid leaves
- Health benefits including medical, prescription drug, dental, and vision coverage (per applicable plans)
- Short-term incentive bonus opportunity
- Eligibility to participate in equity-based long-term incentive program
We could also note that additional details provided upon offer.
Pay: The annual base pay range: $127,352.00 - $167,149.50 USD. Also note that base pay offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. That's substantive; we can include as prose.
Schedule: "Our ways of working support both individual needs and team collaboration. To foster connection and collaboration, employees are expected to work from the office three days per week, creating opportunities for in-person teamwork, innovation, and meaningful connection." Also maybe mention flexibility and balance earlier but that's covered.
We'll make a
- for any list of duties/requirements/benefits. So we can treat each requirement as list item.
Let's parse:
- Bachelor's degree in Computer Science, Computer Engineering, or a related field is preferred but not required.
- We will consider self-taught engineers with a strong track record of shipping software.
- 5+ years' experience in software engineering, specializing in API and full-stack development.
- 2+ years of leadership responsibilities on software delivery projects.
- A long history of hands-on coding and enjoying solving complex problems, not just architecture and design.
- Skilled in TypeScript, Java, or Python for scalable systems.
- Experience building and operating shared/platform services (SDKs, APIs) consumed by multiple teams.
- Experi.
- Experienced with AWS services.
- Strong in SQL and NoSQL databases.
- Familiar with GitHub Actions for CI/CD.
- Excellent communication and collaboration skills.
Now Desired Skills And Experience: list:
- Experience with authentication/authorization systems (OAuth2/OIDC, JWTs, SSO, RBAC) or Keycloak.
- Familiarity with client SDK design or data visualization tooling.
- Experience with notification systems or customer-facing portal/content products.
We'll put these under Skills section as list.
Benefits: from "Benefits offered included a qualified retirement program [401(k) plan]; paid vacation and holidays; paid leaves; and, health benefits including medical, prescription drug, dental, and vision coverage in accordance with the terms and conditions of the applicable plans." Also "In addition, our positions offer a short-term incentive bonus opportunity; eligibility to participate in our equity-based long-term incentive program." Also maybe "Additional details of participation in these benefit plans will be provided if an employee receives an offer of employment." That's somewhat generic but we can keep as part of benefits prose.
We'll make a
- for each requirement? The instruction: Use