Senior Fullstack Software Engineer (.NET, RESTAPI, Spark, Angular)- NC
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove Job ID etc.
We need to include sections only when posting has real specific content.
Let's extract content:
Role Overview: "In this role, you will consult on complex software engineering initiatives with broad impact. You will be responsible for reviewing and analyzing large-scale software engineering challenges, contributing to the resolution of multifaceted situations, and collaborating with personnel to meet deliverables. This position requires an understanding of function, policies, procedures, and compliance requirements."
Key Responsibilities: list bullet points.
Required Qualifications: Experience: 5+ years... Technical Skills list. Professional Skills.
Preferred Qualifications: Experience with Azure Data Factory, knowledge of cloud platforms.
Work Environment: on-site five days a week, workday begins approx 8:00 AM.
Benefits: described.
Pay Rate: $69/hr - $72/hr.
Duration: 18 Months (maybe not needed as schedule but could be included in Schedule? The instruction: include Schedule section only if posting actually states them. It states Duration: 18 Months. That's not schedule but maybe we can treat as Schedule? The schedule section is for work schedule (hours, days). Duration is contract length. Might be considered schedule? The instruction says "Schedule" heading for schedule info. Probably we should not create Schedule unless posting states work schedule. It does state workday begins approx 8:00 AM and five days a week. That's schedule. So we can put Schedule section with that info. Duration maybe not needed; could be omitted or included in a brief p? The instruction: do not create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule (workday, days). So include Schedule. Duration maybe not needed; could be omitted or placed elsewhere? Might be considered part of schedule? Probably better to omit duration as not requested. But we could include a short p under Schedule? The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine schedule info in Schedule section.
Benefits: we have detailed benefits.
Pay: we have pay rate.
Now we need to format.
We must not repeat job title as heading. So we start with maybe
About the role
for Role Overview.
Then Responsibilities
with ul.
Then Requirements
maybe combine Required Qualifications and Preferred? Could separate but we can have Requirements section with required qualifications and maybe preferred as separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Skills separate. Let's do Requirements for experience and qualifications, Skills for technical and professional skills.
Thus:
About the role
...
Responsibilities
- ...
...
Requirements
Experience: 5+ years of Software Engineering experience, or equivalent demonstrated through a combination of work or consulting experience, training, or education. Candidates must have at least 4 years of experience with the specified required technologies.
maybe also include Preferred Qualifications? Could add another paragraph for preferred.
But we could also have Qualifications
for required and preferred. However we already have Requirements heading; maybe we split: Requirements (required) and Qualifications (preferred). But the list includes both Requirements and Qualifications as possible headings. Let's do:
Requirements
Experience: 5+ years of Software Engineering experience, or equivalent demonstrated through a combination of work or consulting experience, training, or education. Candidates must have at least 4 years of experience with the specified required technologies.
Qualifications
Preferred: Experience with Azure Data Factory (ADF). Knowledge of cloud platforms such as Azure App Service, Key Vault, or Storage.
Then Skills: technical and professional.
We need to list technical skills: MS SQL Server, Spark, REST API, Angular, .NET Core, Backend: .NET 6/7+, ASP.NET Core, EF Core, JBPM, Frontend: Angular 13+, TypeScript, Jasmine/Karma, Data & ETL: Spark-SQL, DevOps & Cloud Native: Azure DevOps, GitHub Actions, Docker, OpenShift (OCP), Kubernetes, YAML deployments, Testing: xUnit, NUnit, Playwright, iCEDQ, Octane, Architecture: SOLID principles, Mediator and Repository patterns, Dependency Injection.
Professional Skills: Effective communication skills. Proven ability to collaborate effectively within and across teams.
We can combine into one Skills section with two sub-lists? But we must use - for any list. Could have two separate
under Skills heading.
Now Benefits: we have a paragraph describing benefits. Could break into list? The description includes many items; we could make a list of benefits: medical, dental, vision, life, disability, other insurance plans, ESPP, 401K with company match after 12 months, HSA, SupportLinc EAP up to 8 free counseling sessions, corporate discount savings program, on-demand training program, access to certification prep and library of technical and leadership courses/books/seminars after 6+ months tenure, certification discounts and perks to associations (CompTIA, IIBA), dedicated customer service team for consultants, certified Career Coach. We'll preserve all.
Pay: Pay Rate: $69/hr - $72/hr
Schedule: On-site role requiring five days a week in the office. Workday begins at approximately 8:00 AM to facilitate collaboration with offshore teams.
We must not include boilerplate like EEO, legal, application instructions, etc.
Now produce HTML fragment.
Check for any repeated content: Ensure we didn't include job ID, job title, location? Location maybe not required as heading but could be included in About the role? The instruction: do not repeat job title as heading; location not prohibited but we might include it in About the role paragraph? The location is Charlotte, NC (Onsite). Could be included in About the role or maybe separate? Not required but we can include as part of About the role paragraph. However the instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should include location. Where to put? Could be in About the role paragraph after overview. Let's add: "Location: Charlotte, NC (Onsite)." as part of that paragraph.
Also Duration: 18 Months maybe we could include in About the role or maybe separate? Not required but we could add to About the role as "Duration: 18 Months." However the instruction says prefer few substantive sections over many thin ones; we could add to About the role.
But we already have Schedule section for work schedule; duration is contract length, not schedule. Could be included in About the role.
Let's include location and duration in About the role paragraph.
Now craft HTML.
We'll output:
About the role
In this role, you will consult on complex software engineering initiatives with broad impact. You will be responsible for reviewing and analyzing large-scale software engineering challenges, contributing to the resolution of multifaceted situations, and collaborating with personnel to meet deliverables. This position requires an understanding of function, policies, procedures, and compliance requirements. Location: Charlotte, NC (Onsite). Duration: 18 Months.
Responsibilities
- Build scalable backend APIs and services using C#/.NET 6/7+, ASP.NET Core, EF Core, and JBPM.
- Develop intuitive, performant Angular (13+) UI components using TypeScript, RxJS, and modular architecture.
- Design and enhance Spark ETL/ELT pipelines, including transformations, data quality rules, and performance tuning.
- Write high-coverage unit tests for both backend (xUnit/NUnit) and frontend (Jasmine/Karma) applications.
- Write test scripts using Playwright and iCEDQ, and utilize Octane for test management.
- Containerize applications and manage deployments on OpenShift (OCP), including build configurations and scaling strategies.
- Work with Kubernetes concepts such as pods, deployments, services, and configuration maps.
- Contribute to CI/CD automation using Azure DevOps or GitHub Actions and YAML pipelines.
- Optimize SQL queries, database structures, and ETL load patterns for performance and reliability.
Requirements
Experience: 5+ years of Software Engineering experience, or equivalent demonstrated through a combination of work or consulting experience, training, or education. Candidates must have at least 4 years of experience with the specified required technologies.
Qualifications
Preferred: Experience with Azure Data Factory (ADF). Knowledge of cloud platforms such as Azure App Service, Key Vault, or Storage.
Skills
- MS SQL Server
- Spark
- REST API
- Angular
- .NET Core
- Backend: .NET 6/7+, ASP.NET Core, EF Core, JBPM
- Frontend: Angular 13+, TypeScript, Jasmine/Karma
- Data & ETL: Spark-SQL
- DevOps & Cloud Native: Azure DevOps, GitHub Actions, Docker, OpenShift (OCP), Kubernetes, YAML deployments
- Testing: xUnit, NUnit, Playwright, iCEDQ, Octane
- Architecture: SOLID principles, Mediator and Repository patterns, Dependency Injection
- Effective communication skills
- Proven ability to collaborate effectively within and across teams
Benefits
- Medical, dental, vision, life, disability, and other insurance plans
- ESPP (employee stock purchase program)
- 401K program with company match after 12 months of tenure
- HSA (Health Savings Account on the HDHP plan)
- SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions
- Corporate discount savings program and other discounts
- On-demand training program
- Access to certification prep and a library of technical and leadership courses/books/seminars after 6+ months tenure
- Certification discounts and perks to associations including CompTIA and IIBA
- Dedicated customer service team for consultants
- Certified Career Coach
Pay
Pay Rate: $69/hr - $72/hr
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove Job ID etc. We need to include sections only when posting has real specific content. Let's extract content: Role Overview: "In this role, you will consult on complex software engineering initiatives with broad impact. You will be responsible for reviewing and analyzing large-scale software engineering challenges, contributing to the resolution of multifaceted situations, and collaborating with personnel to meet deliverables. This position requires an understanding of function, policies, procedures, and compliance requirements." Key Responsibilities: list bullet points. Required Qualifications: Experience: 5+ years... Technical Skills list. Professional Skills. Preferred Qualifications: Experience with Azure Data Factory, knowledge of cloud platforms. Work Environment: on-site five days a week, workday begins approx 8:00 AM. Benefits: described. Pay Rate: $69/hr - $72/hr. Duration: 18 Months (maybe not needed as schedule but could be included in Schedule? The instruction: include Schedule section only if posting actually states them. It states Duration: 18 Months. That's not schedule but maybe we can treat as Schedule? The schedule section is for work schedule (hours, days). Duration is contract length. Might be considered schedule? The instruction says "Schedule" heading for schedule info. Probably we should not create Schedule unless posting states work schedule. It does state workday begins approx 8:00 AM and five days a week. That's schedule. So we can put Schedule section with that info. Duration maybe not needed; could be omitted or included in a brief p? The instruction: do not create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule (workday, days). So include Schedule. Duration maybe not needed; could be omitted or placed elsewhere? Might be considered part of schedule? Probably better to omit duration as not requested. But we could include a short p under Schedule? The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine schedule info in Schedule section. Benefits: we have detailed benefits. Pay: we have pay rate. Now we need to format. We must not repeat job title as heading. So we start with maybe
About the role
for Role Overview. ThenResponsibilities
with ul. ThenRequirements
maybe combine Required Qualifications and Preferred? Could separate but we can have Requirements section with required qualifications and maybe preferred as separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Skills separate. Let's do Requirements for experience and qualifications, Skills for technical and professional skills. Thus:About the role
...
Responsibilities
- ... ...
Requirements
Experience: 5+ years of Software Engineering experience, or equivalent demonstrated through a combination of work or consulting experience, training, or education. Candidates must have at least 4 years of experience with the specified required technologies.
maybe also include Preferred Qualifications? Could add another paragraph for preferred. But we could also haveQualifications
for required and preferred. However we already have Requirements heading; maybe we split: Requirements (required) and Qualifications (preferred). But the list includes both Requirements and Qualifications as possible headings. Let's do:Requirements
Experience: 5+ years of Software Engineering experience, or equivalent demonstrated through a combination of work or consulting experience, training, or education. Candidates must have at least 4 years of experience with the specified required technologies.
Qualifications
Preferred: Experience with Azure Data Factory (ADF). Knowledge of cloud platforms such as Azure App Service, Key Vault, or Storage.
Then Skills: technical and professional. We need to list technical skills: MS SQL Server, Spark, REST API, Angular, .NET Core, Backend: .NET 6/7+, ASP.NET Core, EF Core, JBPM, Frontend: Angular 13+, TypeScript, Jasmine/Karma, Data & ETL: Spark-SQL, DevOps & Cloud Native: Azure DevOps, GitHub Actions, Docker, OpenShift (OCP), Kubernetes, YAML deployments, Testing: xUnit, NUnit, Playwright, iCEDQ, Octane, Architecture: SOLID principles, Mediator and Repository patterns, Dependency Injection. Professional Skills: Effective communication skills. Proven ability to collaborate effectively within and across teams. We can combine into one Skills section with two sub-lists? But we must use- for any list. Could have two separate
- under Skills heading.
Now Benefits: we have a paragraph describing benefits. Could break into list? The description includes many items; we could make a
- Build scalable backend APIs and services using C#/.NET 6/7+, ASP.NET Core, EF Core, and JBPM.
- Develop intuitive, performant Angular (13+) UI components using TypeScript, RxJS, and modular architecture.
- Design and enhance Spark ETL/ELT pipelines, including transformations, data quality rules, and performance tuning.
- Write high-coverage unit tests for both backend (xUnit/NUnit) and frontend (Jasmine/Karma) applications.
- Write test scripts using Playwright and iCEDQ, and utilize Octane for test management.
- Containerize applications and manage deployments on OpenShift (OCP), including build configurations and scaling strategies.
- Work with Kubernetes concepts such as pods, deployments, services, and configuration maps.
- Contribute to CI/CD automation using Azure DevOps or GitHub Actions and YAML pipelines.
- Optimize SQL queries, database structures, and ETL load patterns for performance and reliability.
- MS SQL Server
- Spark
- REST API
- Angular
- .NET Core
- Backend: .NET 6/7+, ASP.NET Core, EF Core, JBPM
- Frontend: Angular 13+, TypeScript, Jasmine/Karma
- Data & ETL: Spark-SQL
- DevOps & Cloud Native: Azure DevOps, GitHub Actions, Docker, OpenShift (OCP), Kubernetes, YAML deployments
- Testing: xUnit, NUnit, Playwright, iCEDQ, Octane
- Architecture: SOLID principles, Mediator and Repository patterns, Dependency Injection
- Effective communication skills
- Proven ability to collaborate effectively within and across teams
- Medical, dental, vision, life, disability, and other insurance plans
- ESPP (employee stock purchase program)
- 401K program with company match after 12 months of tenure
- HSA (Health Savings Account on the HDHP plan)
- SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions
- Corporate discount savings program and other discounts
- On-demand training program
- Access to certification prep and a library of technical and leadership courses/books/seminars after 6+ months tenure
- Certification discounts and perks to associations including CompTIA and IIBA
- Dedicated customer service team for consultants
- Certified Career Coach
- list of benefits: medical, dental, vision, life, disability, other insurance plans, ESPP, 401K with company match after 12 months, HSA, SupportLinc EAP up to 8 free counseling sessions, corporate discount savings program, on-demand training program, access to certification prep and library of technical and leadership courses/books/seminars after 6+ months tenure, certification discounts and perks to associations (CompTIA, IIBA), dedicated customer service team for consultants, certified Career Coach. We'll preserve all.
Pay:
Pay Rate: $69/hr - $72/hr
Schedule:On-site role requiring five days a week in the office. Workday begins at approximately 8:00 AM to facilitate collaboration with offshore teams.
We must not include boilerplate like EEO, legal, application instructions, etc. Now produce HTML fragment. Check for any repeated content: Ensure we didn't include job ID, job title, location? Location maybe not required as heading but could be included in About the role? The instruction: do not repeat job title as heading; location not prohibited but we might include it in About the role paragraph? The location is Charlotte, NC (Onsite). Could be included in About the role or maybe separate? Not required but we can include as part of About the role paragraph. However the instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should include location. Where to put? Could be in About the role paragraph after overview. Let's add: "Location: Charlotte, NC (Onsite)." as part of that paragraph. Also Duration: 18 Months maybe we could include in About the role or maybe separate? Not required but we could add to About the role as "Duration: 18 Months." However the instruction says prefer few substantive sections over many thin ones; we could add to About the role. But we already have Schedule section for work schedule; duration is contract length, not schedule. Could be included in About the role. Let's include location and duration in About the role paragraph. Now craft HTML. We'll output:About the role
In this role, you will consult on complex software engineering initiatives with broad impact. You will be responsible for reviewing and analyzing large-scale software engineering challenges, contributing to the resolution of multifaceted situations, and collaborating with personnel to meet deliverables. This position requires an understanding of function, policies, procedures, and compliance requirements. Location: Charlotte, NC (Onsite). Duration: 18 Months.
Responsibilities
Requirements
Experience: 5+ years of Software Engineering experience, or equivalent demonstrated through a combination of work or consulting experience, training, or education. Candidates must have at least 4 years of experience with the specified required technologies.
Qualifications
Preferred: Experience with Azure Data Factory (ADF). Knowledge of cloud platforms such as Azure App Service, Key Vault, or Storage.
Skills
Benefits
Pay
Pay Rate: $69/hr - $72/hr