Principal Engineer/Architect, Application Engineering
Claritev · United States · 1 mo ago
RemoteRemoteEngineering$130/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the job posting.
Job Summary: "The Principal Software Engineer is an individual contributed and an expert full-stack developer on an Agile team who is primarily responsible for defining and building software in support of one or more business products. The incumbent will lead a diverse group of Software Engineers and work closely with the Architects to design, develop, and test highly available, secure, and scalable systems. Candidates must be authorized to work in the United States without current or future sponsorship."
That's about the role.
Job Roles And Responsibilities: list of bullet points.
Mandatory REQUIREMENTS (Education, Experience, and Training): list of requirements.
Desirable: additional.
Compensation: salary range $130-140K, health insurance, 401k, bonus.
About Us: description of company.
What Guides Us: values.
About The Team: My Total Value details.
Our Commitment to Inclusion: EEO.
We need to decide sections: About the role (job summary). Responsibilities (list). Requirements (mandatory). Qualifications (maybe education/experience). Skills (maybe technical stack). Benefits (health insurance, 401k, bonus, etc). Pay (salary range). Schedule (not mentioned). So we should not include Schedule if not present.
We must not include placeholder like "commensurate with experience". Not present.
We need to ensure we don't duplicate content.
We need to output only HTML fragment, no /. Use for headings. Use
for headings. Use - for lists. Use
for prose.
We need to preserve all substantive info. So we need to include all bullet points from responsibilities, mandatory requirements, desirable, benefits, compensation, about us, values, total rewards, inclusion? Possibly include as sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Could also include About Us as a section? Not in list but could be considered "About the role"? But we have "About Us" separate. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we should use those headings where appropriate. Could also add "About the company" but not required. Safer to stick to those headings.
Thus we need to map content:
- About the role: job summary paragraph.
- Responsibilities: list of responsibilities.
- Requirements: mandatory requirements (education, experience, training). Could also include qualifications (education, experience). But we have both Requirements and Qualifications sections. We need to decide what goes where. Typically Requirements = mandatory skills/experience. Qualifications = education/degrees. Skills = technical stack. But we can split.
We have mandatory requirements list includes many technical skills, plus "Computer related Bachelor’s degree is preferred or equivalent work experience". That's qualification.
Desirable: additional nice-to-have.
We could put:
- Requirements: mandatory technical requirements (ASP.Net, .NET Core, etc.) plus maybe "Experience guiding the team with TDD/BDD practices" etc.
- Qualifications: education (Bachelor's degree preferred or equivalent), years of experience (8+ years progressive software experience, 3+ years as a lead), authorization to work in US.
- Skills: maybe list of specific technologies (ASP.Net, .NET Core, C#, Web API, MVC, SQLServer, React, Azure/AWS/OCI, Microservices, DDD, Message brokers, AI-assisted tools, Kubernetes, Helm, TDD/BDD, automated testing frameworks, DevSecOps, DevOps pipelines, relational/non-relational DB, Data access patterns EF Core, design patterns, authentication/authorization, GitHub/GIT, communication, troubleshooting). That's a lot; could be a list.
- Benefits: health insurance, 401k with company match, employee stock purchase plan, flexible spending accounts, health savings accounts, paid time off, company holidays, paid parental leave, mental health resources, tuition reimbursement, financial planning resources, professional development opportunities. Also bonus opportunity.
- Pay: salary range $130-140K.
We must not include fluff like "commensurate with experience". Not present.
We must not include boilerplate like EEO etc. But "Our Commitment to Inclusion" is EEO; we should remove it as per instruction: remove EEO/equal-opportunity boilerplate. So we omit that.
Also remove "About Us", "What Guides Us", "About The Team" maybe? Those are not in the prescribed headings but could be considered "About the role"? However they contain substantive info about company culture, values, total rewards. The instruction says "Prefer a few substantive sections over many thin ones." We could incorporate some of that into Benefits or About the role? But About the role is about the job, not company. However we could add a section "About the company" but not in list. Safer to omit those sections because they are not in the allowed headings list? The instruction says use 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 it gives examples. It might be okay to use other headings if needed, but better to stick to those.
We could incorporate company description into "About the role" as a brief paragraph? But that would mix job role with company info, maybe okay.
But we need to preserve ALL substantive information. If we omit "About Us", "What Guides Us", "About The Team", we lose substantive info about company mission, values, total rewards. However total rewards are similar to Benefits section; we can put those under Benefits. Mission and values could be omitted? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove company description. So we should keep substantive info about company. But we don't have a heading for it. Could we add a heading "About the company"? Not in examples but maybe allowed. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not an exhaustive list. So we can add other headings if needed. But to be safe, we could add a section "About the company" with that info.
But the instruction also says "Prefer a few substantive sections over many thin ones." So we could combine company info into "About the role" or "Benefits". However "About the role" is specifically about the role; adding company mission may be okay but could blur.
Better to add a section "About the company". It's substantive.
Thus headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, About the company (maybe). Schedule omitted.
We must not include placeholder text.
Now craft HTML.
We need to ensure we don't repeat job title. No Job ID.
We'll produce:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
The salary range for this position is $130-140K.
About the company
...
We need to include all substantive info from About Us, What Guides Us, About The Team (Total Rewards). We'll incorporate those into About the company paragraph and Benefits list.
Let's extract:
About Us: "Why Claritev? Healthcare is complex. We help make it clearer. At Claritev, you'll do work that matters. Together, we're helping make healthcare more transparent and affordable for all through the power of data, technology, and expertise. We offer meaningful opportunities to grow your career, collaborate with talented colleagues, and make an impact on the clients and communities we serve. If you're looking for purpose, growth, and a team that succeeds together, you'll find it here."
What Guides Us: "At Claritev, innovation, agility, and a focus on results drive our success. We embrace bold thinking, work as one team, take ownership, and strive for excellence in everything we do — creating meaningful impact for our clients, communities, and each other."
About The Team: My Total Value details: "Competitive compensation and incentive opportunities (where eligible)Medical, dental, and vision coverageLife and disability coverage401(k) with company matchEmployee stock purchase planFlexible spending accounts and health savings accountsPaid time off and company holidaysPaid parental leaveMental health resourcesTuition reimbursementFinancial planning resourcesProfessional development opportunities"
Also "Our Commitment to Inclusion" we will omit.
Thus Benefits list should include: Medical, dental, and vision coverage; Life and disability coverage; 401(k) with company match; Employee stock purchase plan; Flexible spending accounts and health savings accounts; Paid time off and company holidays; Paid parental leave; Mental health resources; Tuition reimbursement; Financial planning resources; Professional development opportunities; Bonus opportunity (mentioned earlier). Also health insurance (already covered). Also maybe "competitive compensation and incentive opportunities" but that's covered by Pay.
Now Responsibilities list: from "Job Roles And Responsibilities":
- Producing stable and high performing applications from scratch
- Work in Agile methodologies and contribute toward the entire lifecycle of a user story with particular emphasis on coding, unit testing and deployment pipeline automation
- Work with other developers on the team to define high level technical design and follow overall architectural guidelines
- Willing to work in a developer focused team with minimal support from QA
- Research and learn new technologies and processes as part of continuous improvement
- Contribute towards fostering a high performant and self-organized team
- Clearly communicate potential and real issues to the team and propose solutions to resolve them
- Work as a contributor on one or more technical practice groups
- Mentor junior software engineers on the team
- Be a champion of Claritev's core culture
- Ensure compliance with HIPAA regulations and requirements
Also there is "8+ years of progressive software experience in relevant technologies and 3+ years as a lead" and "Computer related Bachelor’s degree is preferred or equivalent work experience in software development". Those are qualifications/experience.
Now Mandatory REQUIREMENTS list (Education, Experience, and Training): includes many bullet points:
- Hands on experience with ASP.Net, .NET Core, C#, Web API, MVC, SQLServer
- Hands on experience building UI applications with React
- Experience working with any top cloud providers (Azure/AWS/OCI)
- Experience working with Microservices architecture with thorough understanding of Bounded contexts (DDD)
- Demonstrated Experience with Message brokers (Preferably Azure Service Bus/RabbitMQ) in implementing event driven applications
- Experience leveraging AI-assisted software development tools to improve design, coding, testing, debugging, and documentation while validating all AI-generated artifacts through engineering best practices.
- Experience with containerized applications with Kubernetes and Helm charts
- Experience guiding the team with TDD/BDD practices and maintaining code coverage
- Experience on writing automated tests with any testing framework
- Working knowledge on modern DevSecOps practices
for prose. We need to preserve all substantive info. So we need to include all bullet points from responsibilities, mandatory requirements, desirable, benefits, compensation, about us, values, total rewards, inclusion? Possibly include as sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Could also include About Us as a section? Not in list but could be considered "About the role"? But we have "About Us" separate. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we should use those headings where appropriate. Could also add "About the company" but not required. Safer to stick to those headings.
Thus we need to map content:
- About the role: job summary paragraph.
- Responsibilities: list of responsibilities.
- Requirements: mandatory requirements (education, experience, training). Could also include qualifications (education, experience). But we have both Requirements and Qualifications sections. We need to decide what goes where. Typically Requirements = mandatory skills/experience. Qualifications = education/degrees. Skills = technical stack. But we can split.
We have mandatory requirements list includes many technical skills, plus "Computer related Bachelor’s degree is preferred or equivalent work experience". That's qualification.
Desirable: additional nice-to-have.
We could put:
- Requirements: mandatory technical requirements (ASP.Net, .NET Core, etc.) plus maybe "Experience guiding the team with TDD/BDD practices" etc.
- Qualifications: education (Bachelor's degree preferred or equivalent), years of experience (8+ years progressive software experience, 3+ years as a lead), authorization to work in US.
- Skills: maybe list of specific technologies (ASP.Net, .NET Core, C#, Web API, MVC, SQLServer, React, Azure/AWS/OCI, Microservices, DDD, Message brokers, AI-assisted tools, Kubernetes, Helm, TDD/BDD, automated testing frameworks, DevSecOps, DevOps pipelines, relational/non-relational DB, Data access patterns EF Core, design patterns, authentication/authorization, GitHub/GIT, communication, troubleshooting). That's a lot; could be a list.
- Benefits: health insurance, 401k with company match, employee stock purchase plan, flexible spending accounts, health savings accounts, paid time off, company holidays, paid parental leave, mental health resources, tuition reimbursement, financial planning resources, professional development opportunities. Also bonus opportunity.
- Pay: salary range $130-140K.
We must not include fluff like "commensurate with experience". Not present.
We must not include boilerplate like EEO etc. But "Our Commitment to Inclusion" is EEO; we should remove it as per instruction: remove EEO/equal-opportunity boilerplate. So we omit that.
Also remove "About Us", "What Guides Us", "About The Team" maybe? Those are not in the prescribed headings but could be considered "About the role"? However they contain substantive info about company culture, values, total rewards. The instruction says "Prefer a few substantive sections over many thin ones." We could incorporate some of that into Benefits or About the role? But About the role is about the job, not company. However we could add a section "About the company" but not in list. Safer to omit those sections because they are not in the allowed headings list? The instruction says use 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 it gives examples. It might be okay to use other headings if needed, but better to stick to those.
We could incorporate company description into "About the role" as a brief paragraph? But that would mix job role with company info, maybe okay.
But we need to preserve ALL substantive information. If we omit "About Us", "What Guides Us", "About The Team", we lose substantive info about company mission, values, total rewards. However total rewards are similar to Benefits section; we can put those under Benefits. Mission and values could be omitted? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove company description. So we should keep substantive info about company. But we don't have a heading for it. Could we add a heading "About the company"? Not in examples but maybe allowed. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not an exhaustive list. So we can add other headings if needed. But to be safe, we could add a section "About the company" with that info.
But the instruction also says "Prefer a few substantive sections over many thin ones." So we could combine company info into "About the role" or "Benefits". However "About the role" is specifically about the role; adding company mission may be okay but could blur.
Better to add a section "About the company". It's substantive.
Thus headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, About the company (maybe). Schedule omitted.
We must not include placeholder text.
Now craft HTML.
We need to ensure we don't repeat job title. No Job ID.
We'll produce:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not an exhaustive list. So we can add other headings if needed. But to be safe, we could add a section "About the company" with that info.
But the instruction also says "Prefer a few substantive sections over many thin ones." So we could combine company info into "About the role" or "Benefits". However "About the role" is specifically about the role; adding company mission may be okay but could blur.
Better to add a section "About the company". It's substantive.
Thus headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, About the company (maybe). Schedule omitted.
We must not include placeholder text.
Now craft HTML.
We need to ensure we don't repeat job title. No Job ID.
We'll produce:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
The salary range for this position is $130-140K.
About the company
...
We need to include all substantive info from About Us, What Guides Us, About The Team (Total Rewards). We'll incorporate those into About the company paragraph and Benefits list. Let's extract: About Us: "Why Claritev? Healthcare is complex. We help make it clearer. At Claritev, you'll do work that matters. Together, we're helping make healthcare more transparent and affordable for all through the power of data, technology, and expertise. We offer meaningful opportunities to grow your career, collaborate with talented colleagues, and make an impact on the clients and communities we serve. If you're looking for purpose, growth, and a team that succeeds together, you'll find it here." What Guides Us: "At Claritev, innovation, agility, and a focus on results drive our success. We embrace bold thinking, work as one team, take ownership, and strive for excellence in everything we do — creating meaningful impact for our clients, communities, and each other." About The Team: My Total Value details: "Competitive compensation and incentive opportunities (where eligible)Medical, dental, and vision coverageLife and disability coverage401(k) with company matchEmployee stock purchase planFlexible spending accounts and health savings accountsPaid time off and company holidaysPaid parental leaveMental health resourcesTuition reimbursementFinancial planning resourcesProfessional development opportunities" Also "Our Commitment to Inclusion" we will omit. Thus Benefits list should include: Medical, dental, and vision coverage; Life and disability coverage; 401(k) with company match; Employee stock purchase plan; Flexible spending accounts and health savings accounts; Paid time off and company holidays; Paid parental leave; Mental health resources; Tuition reimbursement; Financial planning resources; Professional development opportunities; Bonus opportunity (mentioned earlier). Also health insurance (already covered). Also maybe "competitive compensation and incentive opportunities" but that's covered by Pay. Now Responsibilities list: from "Job Roles And Responsibilities": - Producing stable and high performing applications from scratch - Work in Agile methodologies and contribute toward the entire lifecycle of a user story with particular emphasis on coding, unit testing and deployment pipeline automation - Work with other developers on the team to define high level technical design and follow overall architectural guidelines - Willing to work in a developer focused team with minimal support from QA - Research and learn new technologies and processes as part of continuous improvement - Contribute towards fostering a high performant and self-organized team - Clearly communicate potential and real issues to the team and propose solutions to resolve them - Work as a contributor on one or more technical practice groups - Mentor junior software engineers on the team - Be a champion of Claritev's core culture - Ensure compliance with HIPAA regulations and requirements Also there is "8+ years of progressive software experience in relevant technologies and 3+ years as a lead" and "Computer related Bachelor’s degree is preferred or equivalent work experience in software development". Those are qualifications/experience. Now Mandatory REQUIREMENTS list (Education, Experience, and Training): includes many bullet points: - Hands on experience with ASP.Net, .NET Core, C#, Web API, MVC, SQLServer - Hands on experience building UI applications with React - Experience working with any top cloud providers (Azure/AWS/OCI) - Experience working with Microservices architecture with thorough understanding of Bounded contexts (DDD) - Demonstrated Experience with Message brokers (Preferably Azure Service Bus/RabbitMQ) in implementing event driven applications - Experience leveraging AI-assisted software development tools to improve design, coding, testing, debugging, and documentation while validating all AI-generated artifacts through engineering best practices. - Experience with containerized applications with Kubernetes and Helm charts - Experience guiding the team with TDD/BDD practices and maintaining code coverage - Experience on writing automated tests with any testing framework - Working knowledge on modern DevSecOps practices