Staff Software Engineer, Application Modernization
HCVT · Fort Worth, TX · 1 mo ago
HybridEngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule headings only if content exists. The posting includes: About The Role (section). Then responsibilities list (the bullet points after "As the Staff Software Engineer, you will be responsible for, but not limited to, the following:" then many bullet points). Then qualifications list (the "We expect that our Staff Software Engineer will have the following qualifications:" then numbered list). Then Preferred Qualifications (list). Then Benefits mention: "You Matter - HCVT provides a variety of benefits and perks that help sustain a healthy and thriving work environment. Visit the Benefits section to learn more." No specific benefits listed, so we should NOT create Benefits section because no specific content. Pay and Schedule not mentioned. Hybrid Work mentioned earlier: "Hybrid Work HCVT currently offers a hybrid work model..." That's schedule/location info. Could be considered Schedule? It's about work model. The instruction: include a section ONLY when posting has real, specific content for it. Hybrid work is specific content about work arrangement. Could map to Schedule? Or maybe we create a section "Hybrid Work" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Hybrid work could go under Schedule? It's about work location/model, not schedule timing. Might be better to put under Schedule? But schedule usually refers to hours. However we have no explicit schedule. Could we omit Schedule? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state hybrid work model, which is about work arrangement, maybe qualifies as Schedule? I'd argue it's about work location, not schedule. Safer to omit Schedule because not explicit schedule. But we could include a short paragraph under About the role? Actually hybrid work is earlier in description, not under About the role. Could we include it as a paragraph before About the role? The instruction: do not repeat job title as heading; we can include paragraphs outside sections? It says output ONLY the HTML fragment; we can include
for prose. Likely we should include hybrid work as a
before About the role heading. Or we could create a section "Schedule" with content about hybrid work. I'd lean to include Schedule section with hybrid work description. Also Skills: not explicitly listed separate; qualifications include skills. Could we create Skills section? Probably not needed; we can put skills under Qualifications. The instruction: prefer few substantive sections over many thin ones. So we can have About the role, Responsibilities, Qualifications (maybe combine Requirements and Qualifications?). The posting has "Qualifications" (required) and "Preferred Qualifications". Could combine into Qualifications section with two sublists? But we need to follow headings: Requirements, Qualifications, Skills. We could put required qualifications under Requirements, preferred under Qualifications? Or combine. Let's map: Requirements = the numbered list (10+ years etc). Qualifications = Preferred Qualifications list. Skills maybe not needed. Thus sections: About the role (heading
About the role
) with prose describing role (the paragraph before responsibilities). Then Responsibilities (Responsibilities
) with- each bullet. Then Requirements (
Requirements
) with- or
- for any list. So use
- . Then Qualifications (
- . Let's extract them:
- Own the target-state architecture for the new platform: a single front door replacing today's separate client-facing and internal portals, balancing scalability, security, reliability, and supportability while setting the patterns others follow.
- Own the canonical work model (client, engagement, project, task, workflow, status) and a composable module architecture in which some modules are built end to end and others orchestrate third-party processing, with every module plugging into one shell that owns identity, tenant context, navigation, and telemetry.
- Design and enforce multi-tenant isolation for external client users, authorizing each request by person, client tenant, engagement permissions, and action, with isolation holding across documents, search, exports, background jobs, and third-party integrations.
- Establish reusable API and integration patterns and build the integration layer to third-party platforms through versioned contracts and anti-corruption adapters, mapping platform identity to the correct downstream account so that clients never hold vendor credentials or see a vendor's interface.
- Keep the platform correct and resilient across systems the firm does not own: idempotent write-back, reconciliation and drift detection, circuit breakers, cached reads, and graceful degradation so that a single vendor outage does not take the front door down.
- Assess and incrementally modernize on-premises and monolithic applications, including older .NET Framework, WCF, and SQL workloads, without disrupting business operations.
- Build cloud-native applications on Azure PaaS, including the application and business-logic layer of a new data and analytics platform, using managed identity, Key Vault, Service Bus, managed databases, App Service, and Container Apps.
- Select appropriate languages and frameworks for each workload and guide team adoption.
- Own application delivery within the platform team's paved path: ship changes through CI/CD, maintain meaningful quality and security gates, and partner with the Staff Azure Cloud Engineer to shape the paved path from the application side.
- Lead application data design and legacy data migration, with strong controls for data quality, auditability, reconciliation, and safe deployment, which matter in a tax and accounting data context.
- Lead application security design, including authentication and authorization, client identity, input validation, encryption, and secrets management through Key Vault and managed identity, ensuring changes pass automated security and policy gates and build for relevant SOC 2 controls from the outset.
- Set engineering standards for coding, testing, quality gates, code review, observability, and incident response, and provide hands-on technical leadership through design decisions, code reviews, mentoring, and architecture decision records as the team grows.
That's 12 bullets.
Requirements: the numbered list after "We expect that our Staff Software Engineer will have the following qualifications:" then 10 items. Let's extract each:
1. 10+ years building and operating production applications and services, including architecture ownership and cross-functional delivery leadership, designing and implementing scalable, secure, reliable, and supportable systems.
2. Demonstrated experience architecting multi-tenant applications serving both internal staff and external customers, with provable data isolation between customers, customer identity such as Entra External ID, Auth0, or Okta alongside workforce identity, fine-grained authorization, and row-level security.
3. Experience building an experience or orchestration layer over third-party systems of record, including API facades, backend-for-frontend, anti-corruption layers, canonical domain models, versioned contracts, event-driven synchronization, idempotent write-back, and resilience against dependencies outside your control.
4. Deep expertise in at least one modern cloud language, with C#/.NET as our largest footprint, and production fluency in others such as Java, Go, Python, or Node.js/TypeScript.
5. Experience incrementally modernizing monolithic, on-premises, or legacy applications to cloud-native patterns without a big-bang rewrite, and consolidating or replacing existing applications with a unified platform.
6. Hands-on Azure PaaS application development using services such as App Service or Container Apps, managed identity, Key Vault, and Service Bus or equivalent messaging.
7. Full-stack capability, including a modern component-based TypeScript web UI, a shared design system, and a plugin or micro-frontend model that lets multiple modules deliver one consistent experience.
8. Strong relational data modeling and migration experience, with attention to data quality, auditability, and reconciliation.
9. Leadership in secure application development, including authentication, authorization, input validation, encryption, secrets management, OWASP practices, and working knowledge of SOC 2 controls.
10. Experience delivering through CI/CD using GitHub Actions, GitHub Enterprise, or equivalent tools, including pull requests, automated testing, and quality and security gates.
11. Demonstrated technical leadership without formal authority, and comfort serving as the first and lead application engineer in a program spanning both greenfield development and legacy modernization.
Actually there are 11 items (I counted). Let's keep as list.
Preferred Qualifications: bullet list after "Preferred Qualifications". Items:
- Experience with plugin-based platform architectures, where capabilities extend the platform through defined interfaces.
- Familiarity with policy engines for fine-grained authorization where enforcement belongs in the services themselves.
- Experience with data-dense client-facing interfaces at scale, including grids, grouping, virtualized rendering, and export.
- Experience integrating professional-services, tax, or accounting platforms, document management systems, and practice-management systems.
- Sound build-versus-buy judgment, including open-source license diligence.
- Hands-on experience with incremental modernization patterns such as strangler fig, anti-corruption layers, and event-driven decomposition.
- Experience operating through an audit cycle in a compliance-driven environment such as SOC 2 or HIPAA.
- Experience in tax, accounting, financial services, or professional services.
- Microsoft AZ-204 and/or AZ-305 certification, or relevant language, framework, or database certifications.
Now Schedule/hybrid work paragraph: "Hybrid Work HCVT currently offers a hybrid work model that allows eligible employees to work both remotely and in the office, based on business needs and team coordination. When working remotely, employees are expected to meet the same performance standards, adhere to the same policies, and maintain the same level of communication, collaboration, and responsiveness as working in the office. Please note that this arrangement is not guaranteed and subject to change at any time. We will strive to provide reasonable notice of any changes to your work location or schedule whenever possible."
We'll put that under
Schedule
as prose. Now ensure we don't include any boilerplate like "Come for the Challenge..." etc. That's marketing fluff but maybe considered substantive? It's not about role specifics; could be considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The opening marketing sentences maybe not required but could be considered fluff. However they are not explicitly listed as boilerplate to remove. But they are not substantive about the role. Safer to omit them? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The marketing fluff might be considered not substantive about the job. I'd keep only the role-specific sections. So we will not include the opening paragraph. Thus final HTML:About the role
We are building a new Azure cloud platform to support a multi-year modernization program. This role will lead application engineering on the program, architecting and coding new solutions while modernizing legacy applications onto the platform. You will set the technical direction, establish reusable patterns, and
Qualifications
) with preferred qualifications list. Then maybe Schedule (Schedule
) with hybrid work paragraph. We must not include boilerplate like EEO etc. Remove duplicated lines. Ensure we preserve all substantive information. Let's extract About the role prose: The paragraph after "About The Role" before responsibilities: "We are building a new Azure cloud platform to support a multi-year modernization program. This role will lead application engineering on the program, architecting and coding new solutions while modernizing legacy applications onto the platform. You will set the technical direction, establish reusable patterns, and raise the engineering bar as the team grows. Our largest application footprint is C#/.NET on Azure, but the role requires sound judgment across modern cloud languages and frameworks. You will partner with the Azure Cloud Engineer and the firm's IT, security, and network teams. The platform team owns the landing zone, guardrails, and infrastructure; you will build and modernize applications on that paved path and turn shared standards into working code, patterns, and documentation." That's the About the role content. Responsibilities: list after "As the Staff Software Engineer, you will be responsible for, but not limited to, the following:" then many bullet points each starting with a bold phrase? We need to capture each bullet as - . Let's extract them:
- Own the target-state architecture for the new platform: a single front door replacing today's separate client-facing and internal portals, balancing scalability, security, reliability, and supportability while setting the patterns others follow.
- Own the canonical work model (client, engagement, project, task, workflow, status) and a composable module architecture in which some modules are built end to end and others orchestrate third-party processing, with every module plugging into one shell that owns identity, tenant context, navigation, and telemetry.
- Design and enforce multi-tenant isolation for external client users, authorizing each request by person, client tenant, engagement permissions, and action, with isolation holding across documents, search, exports, background jobs, and third-party integrations.
- Establish reusable API and integration patterns and build the integration layer to third-party platforms through versioned contracts and anti-corruption adapters, mapping platform identity to the correct downstream account so that clients never hold vendor credentials or see a vendor's interface.
- Keep the platform correct and resilient across systems the firm does not own: idempotent write-back, reconciliation and drift detection, circuit breakers, cached reads, and graceful degradation so that a single vendor outage does not take the front door down.
- Assess and incrementally modernize on-premises and monolithic applications, including older .NET Framework, WCF, and SQL workloads, without disrupting business operations.
- Build cloud-native applications on Azure PaaS, including the application and business-logic layer of a new data and analytics platform, using managed identity, Key Vault, Service Bus, managed databases, App Service, and Container Apps.
- Select appropriate languages and frameworks for each workload and guide team adoption.
- Own application delivery within the platform team's paved path: ship changes through CI/CD, maintain meaningful quality and security gates, and partner with the Staff Azure Cloud Engineer to shape the paved path from the application side.
- Lead application data design and legacy data migration, with strong controls for data quality, auditability, reconciliation, and safe deployment, which matter in a tax and accounting data context.
- Lead application security design, including authentication and authorization, client identity, input validation, encryption, and secrets management through Key Vault and managed identity, ensuring changes pass automated security and policy gates and build for relevant SOC 2 controls from the outset.
- Set engineering standards for coding, testing, quality gates, code review, observability, and incident response, and provide hands-on technical leadership through design decisions, code reviews, mentoring, and architecture decision records as the team grows.
That's 12 bullets.
Requirements: the numbered list after "We expect that our Staff Software Engineer will have the following qualifications:" then 10 items. Let's extract each:
1. 10+ years building and operating production applications and services, including architecture ownership and cross-functional delivery leadership, designing and implementing scalable, secure, reliable, and supportable systems.
2. Demonstrated experience architecting multi-tenant applications serving both internal staff and external customers, with provable data isolation between customers, customer identity such as Entra External ID, Auth0, or Okta alongside workforce identity, fine-grained authorization, and row-level security.
3. Experience building an experience or orchestration layer over third-party systems of record, including API facades, backend-for-frontend, anti-corruption layers, canonical domain models, versioned contracts, event-driven synchronization, idempotent write-back, and resilience against dependencies outside your control.
4. Deep expertise in at least one modern cloud language, with C#/.NET as our largest footprint, and production fluency in others such as Java, Go, Python, or Node.js/TypeScript.
5. Experience incrementally modernizing monolithic, on-premises, or legacy applications to cloud-native patterns without a big-bang rewrite, and consolidating or replacing existing applications with a unified platform.
6. Hands-on Azure PaaS application development using services such as App Service or Container Apps, managed identity, Key Vault, and Service Bus or equivalent messaging.
7. Full-stack capability, including a modern component-based TypeScript web UI, a shared design system, and a plugin or micro-frontend model that lets multiple modules deliver one consistent experience.
8. Strong relational data modeling and migration experience, with attention to data quality, auditability, and reconciliation.
9. Leadership in secure application development, including authentication, authorization, input validation, encryption, secrets management, OWASP practices, and working knowledge of SOC 2 controls.
10. Experience delivering through CI/CD using GitHub Actions, GitHub Enterprise, or equivalent tools, including pull requests, automated testing, and quality and security gates.
11. Demonstrated technical leadership without formal authority, and comfort serving as the first and lead application engineer in a program spanning both greenfield development and legacy modernization.
Actually there are 11 items (I counted). Let's keep as list.
Preferred Qualifications: bullet list after "Preferred Qualifications". Items:
- Experience with plugin-based platform architectures, where capabilities extend the platform through defined interfaces.
- Familiarity with policy engines for fine-grained authorization where enforcement belongs in the services themselves.
- Experience with data-dense client-facing interfaces at scale, including grids, grouping, virtualized rendering, and export.
- Experience integrating professional-services, tax, or accounting platforms, document management systems, and practice-management systems.
- Sound build-versus-buy judgment, including open-source license diligence.
- Hands-on experience with incremental modernization patterns such as strangler fig, anti-corruption layers, and event-driven decomposition.
- Experience operating through an audit cycle in a compliance-driven environment such as SOC 2 or HIPAA.
- Experience in tax, accounting, financial services, or professional services.
- Microsoft AZ-204 and/or AZ-305 certification, or relevant language, framework, or database certifications.
Now Schedule/hybrid work paragraph: "Hybrid Work HCVT currently offers a hybrid work model that allows eligible employees to work both remotely and in the office, based on business needs and team coordination. When working remotely, employees are expected to meet the same performance standards, adhere to the same policies, and maintain the same level of communication, collaboration, and responsiveness as working in the office. Please note that this arrangement is not guaranteed and subject to change at any time. We will strive to provide reasonable notice of any changes to your work location or schedule whenever possible."
We'll put that under
- ? Use
- for any list. So use