Senior .NET Full Stack Engineer
TEKsystems · Union City, OH · 3 wk ago
On-siteEngineering$55–$60/hrContract
We need to output HTML fragment only, with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Keep substantive info.
We need to parse the description.
Key parts:
- Description: Led a strategic initiative ... (some context). Not needed? Probably part of About the role? The description is about the initiative, but we can include as part of About the role.
- "We are seeking a Sr. Full Stack Engineer to join a high-impact Lending technology team responsible for modernizing critical document imaging and servicing platforms. This role will be instrumental in designing, building, and enhancing scalable microservices and user-facing applications that support key business processes across the lending ecosystem. The ideal candidate is a hands-on engineer with deep experience across both front-end and back-end technologies, strong cloud-native development skills, and a passion for building modern, event-driven applications. While full-stack capabilities are heavily emphasized, we are open to exceptional engineers with a stronger concentration in either back-end or front-end development."
That's About the role.
- Key Responsibilities: list bullet points.
- Top Skills Details: list of skills.
- Required Qualifications: bullet list.
- Preferred Qualifications: bullet list.
- Experience Level: Expert Level (maybe not needed as a section? Could be part of Qualifications? But we have a section for Qualifications; we could include Experience Level under Qualifications or as separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list Experience Level as a heading option, but we could put under Qualifications or Requirements. Probably include under Qualifications.
- Job Type & Location: This is a Contract to Hire position based out of Dayton, OH. That's maybe part of About the role or could be separate but not in allowed headings. Could be included in About the role paragraph.
- Pay And Benefits: includes pay range and benefits list. So we need Pay and Benefits sections. According to rules: include Pay and Benefits sections only if posting actually states them. Yes, they do. So we need
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Keep substantive info.
We need to parse the description.
Key parts:
- Description: Led a strategic initiative ... (some context). Not needed? Probably part of About the role? The description is about the initiative, but we can include as part of About the role.
- "We are seeking a Sr. Full Stack Engineer to join a high-impact Lending technology team responsible for modernizing critical document imaging and servicing platforms. This role will be instrumental in designing, building, and enhancing scalable microservices and user-facing applications that support key business processes across the lending ecosystem. The ideal candidate is a hands-on engineer with deep experience across both front-end and back-end technologies, strong cloud-native development skills, and a passion for building modern, event-driven applications. While full-stack capabilities are heavily emphasized, we are open to exceptional engineers with a stronger concentration in either back-end or front-end development."
That's About the role.
- Key Responsibilities: list bullet points.
- Top Skills Details: list of skills.
- Required Qualifications: bullet list.
- Preferred Qualifications: bullet list.
- Experience Level: Expert Level (maybe not needed as a section? Could be part of Qualifications? But we have a section for Qualifications; we could include Experience Level under Qualifications or as separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list Experience Level as a heading option, but we could put under Qualifications or Requirements. Probably include under Qualifications.
- Job Type & Location: This is a Contract to Hire position based out of Dayton, OH. That's maybe part of About the role or could be separate but not in allowed headings. Could be included in About the role paragraph.
- Pay And Benefits: includes pay range and benefits list. So we need Pay and Benefits sections. According to rules: include Pay and Benefits sections only if posting actually states them. Yes, they do. So we need Pay
and Benefits
. Also maybe Schedule? Not given. So we should not include Schedule heading.
- Workplace Type: fully onsite position in Dayton,OH. Could be part of About the role or maybe under Schedule? Not needed.
- Application Deadline: anticipated to close on Sep 30, 2026. That's application instruction? Might be considered metadata; we should drop it as per instruction: remove application instructions. So drop.
- About TEKsystems etc: boilerplate, remove.
Thus we need sections: About the role, Responsibilities, Skills (maybe Top Skills Details), Qualifications (maybe combine Required and Preferred?), Benefits, Pay.
We need to decide on headings: They gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements and Qualifications separately. But we have Required Qualifications and Preferred Qualifications. Could put Required under Qualifications, Preferred under Requirements? Or combine. Better: Use Qualifications for Required Qualifications, and Requirements for Preferred Qualifications? Actually "Requirements" often refers to mandatory requirements. But they gave both. We'll follow: Qualifications
for Required Qualifications. Requirements
for Preferred Qualifications (or maybe "Preferred Qualifications"). But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications. We'll put Required Qualifications under Qualifications, and Preferred Qualifications under Requirements.
Skills: we have Top Skills Details. So Skills
.
Pay: Pay
with pay range.
Benefits: Benefits
with list.
We must not include filler like "commensurate with experience". Not present.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the bullet points exactly as given (or close). We must not add extra info not present.
Let's extract bullet points.
Key Responsibilities (as listed):
- Design, develop, and maintain full-stack applications supporting Home Lending and document processing platforms.
- Build and enhance APIs, microservices, and distributed systems using modern .NET technologies.
- Develop modern, responsive user interfaces using Angular.
- Collaborate with Product Owners, Business Analysts, Architects, and Engineering teams to deliver scalable solutions.
- Participate in the full Software Development Life Cycle (SDLC), including design, development, testing, deployment, and production support.
- Design and implement event-driven solutions leveraging messaging and streaming technologies.
- Contribute to CI/CD pipelines and DevOps automation practices to improve software quality and delivery speed.
- Ensure applications meet security, scalability, reliability, and performance standards.
- Support application modernization initiatives and cloud-native architectural patterns.
- Mentor junior engineers and provide technical leadership across development teams.
Top Skills Details:
- NET, Angular 20-21, Full Stack, CI/CD, Microservices, Kafka or related messaging tool experience, experience with Event Driven Architecture
We need to keep that as list.
Required Qualifications:
- 5+ years of software engineering experience in enterprise application development.
- Strong Full-stack Development Experience With C# NET 8 / .NET ecosystem (experience with modern .NET versions; exposure to .NET 10 is a plus)
- Angular (Angular 18+, with Angular 20/21 experience preferred)
- Strong understanding of RESTful APIs and service-oriented architecture.
- Experience building and maintaining microservices-based applications.
- Solid knowledge of SQL and relational database design.
- Experience with Kafka or similar event-streaming platforms.
- Understanding of event-driven architecture patterns.
- Experience working within Agile development teams.
- Strong problem-solving, communication, and collaboration skills.
Preferred Qualifications:
- Experience with: CI/CD pipelines and DevOps practices
- Azure DevOps (ADO)
- Containerization and cloud-native application development
- Observability, monitoring, and performance tuning
- Financial Services or Banking experience.
- Mortgage Lending or Home Lending domain knowledge.
- Experience supporting document imaging, workflow, or content management platforms.
- Familiarity with enterprise integration patterns and large-scale distributed systems.
Pay:
- The pay range for this position is $55.00 - $60.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)
We need to keep that as prose or list? The benefits list is a sentence with items separated by spaces. Better to make a - for each benefit. But we must not invent or summarize away detail; we can break the sentence into items. The original sentence: "Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)". It's a bit messy. We can split by commas and "and". But to preserve detail, we could keep as a
with the sentence as is. That's acceptable; we preserve all info. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Benefits is a list, so we should use
- . But we need to parse into items. Let's try to extract items:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
That seems reasonable.
Pay: we can put as
The pay range for this position is $55.00 - $60.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms.
We could also include the sentence about benefits eligibility but we already have benefits section; maybe keep in Pay section only the pay range and factors. The rest about eligibility etc could be moved to Benefits? But it's part of the Pay And Benefits paragraph. To preserve all info, we could keep that sentence in Pay section as well. But then Benefits section would duplicate? Better to keep the eligibility sentence in Pay section, and Benefits section just list benefits. That preserves all info without duplication? The eligibility sentence mentions benefits eligibility; it's not a benefit itself. So we keep it in Pay.
Now About the role: combine the initial description and the "We are seeking..." paragraph plus maybe Job Type & Location. Let's craft:
Led a strategic initiative within PNC's Lending Servicing organization focused on enhancing the document imaging ecosystem and improving integration between two critical applications supporting mortgage servicing operations and acquisition activity. The project centered on increasing acquisition onboarding scalability by modernizing document workflows and strengthening connectivity between the document acquisition platform and the image management application used by servicing teams.
We are seeking a Sr. Full Stack Engineer to join a high-impact Lending technology team responsible for modernizing critical document imaging and servicing platforms. This role will be instrumental in designing, building, and enhancing scalable microservices and user-facing applications that support key business processes across the lending ecosystem. The ideal candidate is a hands-on engineer with deep experience across both front-end and back-end technologies, strong cloud-native development skills, and a passion for building modern, event-driven applications. While full-stack capabilities are heavily emphasized, we are open to exceptional engineers with a stronger concentration in either back-end or front-end development.
This is a Contract to Hire position based out of Dayton, OH. This is a fully onsite position in Dayton, OH.
We could combine location statements.
Now Responsibilities: - ... each bullet.
Skills:
- NET, Angular 20-21, Full Stack, CI/CD, Microservices, Kafka or related messaging tool experience, experience with Event Driven Architecture
(maybe each skill separate? The original is a comma-separated list; we could keep as one - with the list. That's okay.
Qualifications (Required):
- ... each bullet.
Requirements (Preferred):
- ... each bullet.
Benefits:
- ... each benefit.
Pay: <
with the sentence as is. That's acceptable; we preserve all info. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Benefits is a list, so we should use
- . But we need to parse into items. Let's try to extract items:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
That seems reasonable.
Pay: we can put as
The pay range for this position is $55.00 - $60.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms.
We could also include the sentence about benefits eligibility but we already have benefits section; maybe keep in Pay section only the pay range and factors. The rest about eligibility etc could be moved to Benefits? But it's part of the Pay And Benefits paragraph. To preserve all info, we could keep that sentence in Pay section as well. But then Benefits section would duplicate? Better to keep the eligibility sentence in Pay section, and Benefits section just list benefits. That preserves all info without duplication? The eligibility sentence mentions benefits eligibility; it's not a benefit itself. So we keep it in Pay. Now About the role: combine the initial description and the "We are seeking..." paragraph plus maybe Job Type & Location. Let's craft:Led a strategic initiative within PNC's Lending Servicing organization focused on enhancing the document imaging ecosystem and improving integration between two critical applications supporting mortgage servicing operations and acquisition activity. The project centered on increasing acquisition onboarding scalability by modernizing document workflows and strengthening connectivity between the document acquisition platform and the image management application used by servicing teams.
We are seeking a Sr. Full Stack Engineer to join a high-impact Lending technology team responsible for modernizing critical document imaging and servicing platforms. This role will be instrumental in designing, building, and enhancing scalable microservices and user-facing applications that support key business processes across the lending ecosystem. The ideal candidate is a hands-on engineer with deep experience across both front-end and back-end technologies, strong cloud-native development skills, and a passion for building modern, event-driven applications. While full-stack capabilities are heavily emphasized, we are open to exceptional engineers with a stronger concentration in either back-end or front-end development.
This is a Contract to Hire position based out of Dayton, OH. This is a fully onsite position in Dayton, OH.
We could combine location statements. Now Responsibilities:- ... each bullet.
Skills:
- NET, Angular 20-21, Full Stack, CI/CD, Microservices, Kafka or related messaging tool experience, experience with Event Driven Architecture
- with the list. That's okay.
Qualifications (Required):
- ... each bullet.
Requirements (Preferred):
- ... each bullet.
Benefits:
- ... each benefit. Pay: <
- ... each bullet.
Benefits:
- ... each bullet.
Requirements (Preferred):
- ... each bullet.
Skills:
- . But we need to parse into items. Let's try to extract items:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
That seems reasonable.
Pay: we can put as