Senior Software Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content. No filler headings.
We need to parse the posting.
Key content:
- Company description: Verana Health description, mission, DRIVE values, offices, remote, relocation, priority locations, hybrid model (3 days in office). This could be "About the role" or maybe "About Verana". But we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have:
- Why Join Us? (maybe About the role). It includes description of mission, impact, etc.
- We Offer Comprehensive Benefits That Include ... list: Market-leading medical, dental, and vision insurance plans, 401(k) match, Flexible time off programs, Paid parental leave, Annual learning and wellness stipend.
- More About Verana (diversity statement). Could be part of About the role.
- Salary Range: $149,600 - $187,000.
- Hybrid role: requires 3 days a week in New York or San Francisco offices.
- Also earlier: For Bay Area, NYC, Knoxville priority, hybrid model 3 days in office.
- Also: All employees required to have permanent residency in one of listed states; candidates willing to relocate encouraged; priority for Bay Area, NYC, Knoxville.
- Also: Must be legally authorized to work in US; no visa sponsorship.
- Also: "While we are remote friendly, we have a preference for candidates within close commuting proximity to our Bay Area or NYC office hubs."
- Also: "Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time."
- Also: "This is a Hybrid role that requires 3 days a week in our New York or San Francisco offices"
- Also: "Candidates based in the Bay Area, New York City, and Knoxville, Tennessee will be give priority consideration."
- Also: "All employees are required to have permanent residency in one of these states." (list of states). Might be considered location requirement.
- Also: "Candidates who are willing to relocate are also encouraged to apply."
We need to decide sections.
Probably:
- About the role: includes mission, why join us, maybe more about Verana.
- Responsibilities: list bullet points from "Responsibilities" section.
- Requirements: list bullet points from "Requirements" section.
- Qualifications/Skills: maybe combine? The posting has "Preferred" after Requirements. Could treat as "Preferred Qualifications" or "Skills". But we need to follow instruction: Use headings only when posting has real specific content. We have "Preferred" list. Could put under "Preferred Qualifications" or "Skills". But we have headings list: Skills, Qualifications. We could put "Qualifications" for required qualifications (maybe same as Requirements). But we already have Requirements heading. Could have "Preferred Qualifications" as a subsection? Not in allowed headings. Could use "Skills" for preferred skills. Or we could merge preferred into Requirements? But better to separate: Requirements (mandatory) and Skills (preferred). However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Skills for preferred skills.
- Benefits: list bullet points.
- Pay: salary range.
- Schedule: hybrid model details (3 days in office, location priority, remote etc.)
We must not include filler like "commensurate with experience". Not present.
We must remove boilerplate: EEO, scam warning, navigation, cookie, legal, duplicated lines. The posting includes a scam warning at end: "Caution to Job Applicants: Be vigilant...". Must remove that. Also "Final Note" about not needing to match every expectation. That's maybe not boilerplate but could be considered generic; but it's substantive? It's a note encouraging applicants. Might keep? It's not a list; it's prose. Could keep under About the role? But it's more like a note. Might be considered filler? It's not boilerplate but it's generic. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Final Note" is not exactly those, but could be considered application instruction? It's encouraging to apply. Might be considered application instruction? Safer to remove? The instruction says remove application instructions. The final note is not exactly instruction how to apply, but it's a note about not needing to match every expectation. Could be considered part of the posting encouraging applicants. I'd keep it maybe under About the role as prose.
Also "Click here to read more about our culture and values." That's a link; we should remove as it's navigation? Probably remove.
Also "We are driven to create quality real-world data..." etc. That's part of About.
Also "DRIVE defines our internal purpose..." etc. Keep.
Also "Our headquarters are located in San Francisco..." etc. Keep.
Also "All employees are required to have permanent residency in one of these states." Keep.
Also "Candidates who are willing to relocate are also encouraged to apply." Keep.
Also "Candidates based in the Bay Area, New York City, and Knoxville, Tennessee will be give priority consideration." Keep.
Also "For these locations, the position will follow a hybrid work model, with 3 days per week in office and the remaining days working from home." Keep.
Also "Why Join Us?" Keep.
Also "We Offer Comprehensive Benefits That Include ..." Keep.
Also "More About Verana" Keep.
Also "We believe that diverse teams build better products..." Keep.
Also "Candidates must be legally authorized to work in the United States. We are unable to provide visa sponsorship..." Keep.
Also "While we are remote friendly, we have a preference for candidates within close commuting proximity to our Bay Area or NYC office hubs." Keep.
Also "To learn more about Verana Health, please visit veranahealth.com or watch our introduction video." That's navigation/link; remove.
Also "Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." Duplicate of earlier; remove duplicate.
Also "*This is a Hybrid role that requires 3 days a week in our New York or San Francisco offices*" Keep but maybe duplicate; we have schedule.
Also "Job Title: Senior Software Engineer" - we do not repeat as heading.
Also "Why This Role Matters" - could be part of About the role.
Also "Responsibilities:" list.
Also "Requirements:" list.
Also "Preferred" list.
Also "Salary Range: $149,600 - $187,000"
Also "Final Note" maybe keep.
Also "National Pay Range $149,600—$187,000 USD" duplicate; keep one.
Now craft HTML.
We'll have:
About the role
... prose combining mission, why join us, etc.
Responsibilities
- ... each bullet
Requirements
- ... each bullet
Skills
- ... preferred skills bullets
Benefits
- ... benefits bullets
Pay
$149,600 - $187,000 USD
Schedule
Hybrid role requiring 3 days per week in office (New York or San Francisco) with remaining days remote; priority consideration for candidates based in the Bay Area, New York City, and Knoxville, Tennessee; all employees must have permanent residency in one of the listed states (AZ, CA, CO, CT, FL, GA, IL, LA, MA, MN, NC, NJ, NV, NY, OH, PA, SC, TN, TX, VA, WA, D.C.) and willingness to relocate is encouraged.
We need to ensure we don't repeat info unnecessarily but preserve all substantive.
Let's extract bullets.
Responsibilities bullets from posting:
- Design, develop and maintain high-quality, user-centric interfaces and components
- Architect, build and maintain high-performance, robust and scalable services
- Work closely with product and design teams to understand end-user requirements and translate them into effective user interfaces
- Participate in the design and optimization of CI/CD pipelines and infrastructure using Docker, Kubernetes and AWS
- Write clean, testable and well-documented code using JUnit and other testing frameworks
- Ensure application security by following industry best practices (OWASP, OAuth 2.0)
- Guide, coach and mentor junior team members, fostering their professional development
- Actively participate in Agile ceremonies to break down work, deliver new features and write, review and test code
- Stay updated on emerging technologies and industry trends to drive innovation
Requirements bullets:
- 5+ years of real world experience on backend development using Java, Spring Boot and system design, along with a strong focus on performance optimization, security, observability, and modern engineering practices.
- Implemented and managed cloud-base solutions with AWS, GHA/Jenkins CI/CD pipelines, Docker and Kubernetes
- Hands-on experience with TDD practices and JUnit-based unit testing to drive code quality and prevent regressions
- Strong understanding of RESTful API designs and microservices architecture
- Strong understanding of data structures, algorithms and software design principles
- Hands-on experience leveraging AI-assisted development tools to improve productivity and code quality
- Mastery and real world experience on multiple database platforms (RDBMS, Elastic search, NoSQL).
- Expertise with the AWS ecosystem.
- Experience with observability tools: Logging, monitoring, tracing (e.g., Datadog, CloudWatch, OpenTelemetry)
- Experience with Agile/Scrum methodologies
- Strong communication skills and experience collaborating across onshore and offshore teams.
Preferred (Skills) bullets:
- Prior experience with healthcare related products
- Experience with full-stack development (React frontend and Java/Spring Boot backend)
- Experience with realtime communication tools (WebSockets)
- Knowledge of additional programming languages(python) and framework
- Familiarity with event-driven architectures (Kafka, SQS, etc.)
Benefits bullets:
- Market-leading medical, dental, and vision insurance plans
- 401(k) match
- Flexible time off programs
- Paid parental leave
- Annual learning and wellness stipend
Now About the role prose: combine mission, why join us, etc.
We need to include: Verana Health description, mission, DRIVE values, offices, remote, relocation, priority locations, hybrid model, why join us, more about Verana (diversity statement), legal work auth, no visa sponsorship, preference for proximity, etc.
We must not include duplicated lines. We'll craft a concise paragraph covering all.
Let's draft:
Verana Health is a digital health company that delivers drug lifecycle and medical practice insights from an exclusive real‑world data network, focusing on ophthalmology, neurology, urology, and oncology to accelerate insights across the drug lifecycle and within medical practices and to advance patient care and quality of life. The company’s culture is guided by DRIVE — Diversity, Responsibility, Integrity, Voice‑of‑Customer, and End‑Results. Headquartered in San Francisco with additional offices in
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content. No filler headings. We need to parse the posting. Key content: - Company description: Verana Health description, mission, DRIVE values, offices, remote, relocation, priority locations, hybrid model (3 days in office). This could be "About the role" or maybe "About Verana". But we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - Why Join Us? (maybe About the role). It includes description of mission, impact, etc. - We Offer Comprehensive Benefits That Include ... list: Market-leading medical, dental, and vision insurance plans, 401(k) match, Flexible time off programs, Paid parental leave, Annual learning and wellness stipend. - More About Verana (diversity statement). Could be part of About the role. - Salary Range: $149,600 - $187,000. - Hybrid role: requires 3 days a week in New York or San Francisco offices. - Also earlier: For Bay Area, NYC, Knoxville priority, hybrid model 3 days in office. - Also: All employees required to have permanent residency in one of listed states; candidates willing to relocate encouraged; priority for Bay Area, NYC, Knoxville. - Also: Must be legally authorized to work in US; no visa sponsorship. - Also: "While we are remote friendly, we have a preference for candidates within close commuting proximity to our Bay Area or NYC office hubs." - Also: "Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." - Also: "This is a Hybrid role that requires 3 days a week in our New York or San Francisco offices" - Also: "Candidates based in the Bay Area, New York City, and Knoxville, Tennessee will be give priority consideration." - Also: "All employees are required to have permanent residency in one of these states." (list of states). Might be considered location requirement. - Also: "Candidates who are willing to relocate are also encouraged to apply." We need to decide sections. Probably: - About the role: includes mission, why join us, maybe more about Verana. - Responsibilities: list bullet points from "Responsibilities" section. - Requirements: list bullet points from "Requirements" section. - Qualifications/Skills: maybe combine? The posting has "Preferred" after Requirements. Could treat as "Preferred Qualifications" or "Skills". But we need to follow instruction: Use headings only when posting has real specific content. We have "Preferred" list. Could put under "Preferred Qualifications" or "Skills". But we have headings list: Skills, Qualifications. We could put "Qualifications" for required qualifications (maybe same as Requirements). But we already have Requirements heading. Could have "Preferred Qualifications" as a subsection? Not in allowed headings. Could use "Skills" for preferred skills. Or we could merge preferred into Requirements? But better to separate: Requirements (mandatory) and Skills (preferred). However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Skills for preferred skills. - Benefits: list bullet points. - Pay: salary range. - Schedule: hybrid model details (3 days in office, location priority, remote etc.) We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, scam warning, navigation, cookie, legal, duplicated lines. The posting includes a scam warning at end: "Caution to Job Applicants: Be vigilant...". Must remove that. Also "Final Note" about not needing to match every expectation. That's maybe not boilerplate but could be considered generic; but it's substantive? It's a note encouraging applicants. Might keep? It's not a list; it's prose. Could keep under About the role? But it's more like a note. Might be considered filler? It's not boilerplate but it's generic. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Final Note" is not exactly those, but could be considered application instruction? It's encouraging to apply. Might be considered application instruction? Safer to remove? The instruction says remove application instructions. The final note is not exactly instruction how to apply, but it's a note about not needing to match every expectation. Could be considered part of the posting encouraging applicants. I'd keep it maybe under About the role as prose. Also "Click here to read more about our culture and values." That's a link; we should remove as it's navigation? Probably remove. Also "We are driven to create quality real-world data..." etc. That's part of About. Also "DRIVE defines our internal purpose..." etc. Keep. Also "Our headquarters are located in San Francisco..." etc. Keep. Also "All employees are required to have permanent residency in one of these states." Keep. Also "Candidates who are willing to relocate are also encouraged to apply." Keep. Also "Candidates based in the Bay Area, New York City, and Knoxville, Tennessee will be give priority consideration." Keep. Also "For these locations, the position will follow a hybrid work model, with 3 days per week in office and the remaining days working from home." Keep. Also "Why Join Us?" Keep. Also "We Offer Comprehensive Benefits That Include ..." Keep. Also "More About Verana" Keep. Also "We believe that diverse teams build better products..." Keep. Also "Candidates must be legally authorized to work in the United States. We are unable to provide visa sponsorship..." Keep. Also "While we are remote friendly, we have a preference for candidates within close commuting proximity to our Bay Area or NYC office hubs." Keep. Also "To learn more about Verana Health, please visit veranahealth.com or watch our introduction video." That's navigation/link; remove. Also "Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." Duplicate of earlier; remove duplicate. Also "*This is a Hybrid role that requires 3 days a week in our New York or San Francisco offices*" Keep but maybe duplicate; we have schedule. Also "Job Title: Senior Software Engineer" - we do not repeat as heading. Also "Why This Role Matters" - could be part of About the role. Also "Responsibilities:" list. Also "Requirements:" list. Also "Preferred" list. Also "Salary Range: $149,600 - $187,000" Also "Final Note" maybe keep. Also "National Pay Range $149,600—$187,000 USD" duplicate; keep one. Now craft HTML. We'll have:
About the role
... prose combining mission, why join us, etc.
Responsibilities
- ... each bullet
Requirements
- ... each bullet
Skills
- ... preferred skills bullets
Benefits
- ... benefits bullets
Pay
$149,600 - $187,000 USD
Schedule
Hybrid role requiring 3 days per week in office (New York or San Francisco) with remaining days remote; priority consideration for candidates based in the Bay Area, New York City, and Knoxville, Tennessee; all employees must have permanent residency in one of the listed states (AZ, CA, CO, CT, FL, GA, IL, LA, MA, MN, NC, NJ, NV, NY, OH, PA, SC, TN, TX, VA, WA, D.C.) and willingness to relocate is encouraged.
We need to ensure we don't repeat info unnecessarily but preserve all substantive. Let's extract bullets. Responsibilities bullets from posting: - Design, develop and maintain high-quality, user-centric interfaces and components - Architect, build and maintain high-performance, robust and scalable services - Work closely with product and design teams to understand end-user requirements and translate them into effective user interfaces - Participate in the design and optimization of CI/CD pipelines and infrastructure using Docker, Kubernetes and AWS - Write clean, testable and well-documented code using JUnit and other testing frameworks - Ensure application security by following industry best practices (OWASP, OAuth 2.0) - Guide, coach and mentor junior team members, fostering their professional development - Actively participate in Agile ceremonies to break down work, deliver new features and write, review and test code - Stay updated on emerging technologies and industry trends to drive innovation Requirements bullets: - 5+ years of real world experience on backend development using Java, Spring Boot and system design, along with a strong focus on performance optimization, security, observability, and modern engineering practices. - Implemented and managed cloud-base solutions with AWS, GHA/Jenkins CI/CD pipelines, Docker and Kubernetes - Hands-on experience with TDD practices and JUnit-based unit testing to drive code quality and prevent regressions - Strong understanding of RESTful API designs and microservices architecture - Strong understanding of data structures, algorithms and software design principles - Hands-on experience leveraging AI-assisted development tools to improve productivity and code quality - Mastery and real world experience on multiple database platforms (RDBMS, Elastic search, NoSQL). - Expertise with the AWS ecosystem. - Experience with observability tools: Logging, monitoring, tracing (e.g., Datadog, CloudWatch, OpenTelemetry) - Experience with Agile/Scrum methodologies - Strong communication skills and experience collaborating across onshore and offshore teams. Preferred (Skills) bullets: - Prior experience with healthcare related products - Experience with full-stack development (React frontend and Java/Spring Boot backend) - Experience with realtime communication tools (WebSockets) - Knowledge of additional programming languages(python) and framework - Familiarity with event-driven architectures (Kafka, SQS, etc.) Benefits bullets: - Market-leading medical, dental, and vision insurance plans - 401(k) match - Flexible time off programs - Paid parental leave - Annual learning and wellness stipend Now About the role prose: combine mission, why join us, etc. We need to include: Verana Health description, mission, DRIVE values, offices, remote, relocation, priority locations, hybrid model, why join us, more about Verana (diversity statement), legal work auth, no visa sponsorship, preference for proximity, etc. We must not include duplicated lines. We'll craft a concise paragraph covering all. Let's draft: Verana Health is a digital health company that delivers drug lifecycle and medical practice insights from an exclusive real‑world data network, focusing on ophthalmology, neurology, urology, and oncology to accelerate insights across the drug lifecycle and within medical practices and to advance patient care and quality of life. The company’s culture is guided by DRIVE — Diversity, Responsibility, Integrity, Voice‑of‑Customer, and End‑Results. Headquartered in San Francisco with additional offices in