Senior Microservices Developer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract substantive content: About TEGNA (company description) maybe as "About the role"? Actually "About TEGNA" is company overview; we could put under
About the role
or maybe "About TEGNA". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have sections: About TEGNA (company description) could go under About the role. Responsibilities list. Requirements list. Benefits list. Possibly Qualifications? The posting includes Requirements and also mentions "Why Join TEGNA" which is like benefits/culture. Also "Benefits" section present. Also "Why Join TEGNA" includes some description; could be part of Benefits or maybe separate but we can incorporate into Benefits or maybe a "Why Join TEGNA" not a standard heading; we could treat as part of Benefits or maybe as a separate section like "About the team"? But instruction says only use those headings if content exists. We could create a section "About the role" for the company overview and why join. Then Responsibilities, Requirements, Benefits.
We must not include EEO statement, recruiting fraud alert, privacy notice. Also remove duplicated lines.
We need to preserve all substantive information: So include details about TEGNA, the role, responsibilities, requirements, benefits (including medical plans, 401k, Teladoc, therapy, PTO, holidays). Also mention "Why Join TEGNA" details: senior technical voice, Azure/AWS hybrid, AI-assisted development, etc. That could be part of About the role or Benefits.
We must not invent or summarize away detail. So we need to keep specifics: e.g., "64 television stations in 51 U.S. markets, reaches more than 100 million people monthly across the web, mobile apps, streaming, and linear television." etc.
We need to format as HTML fragment: no or . Use for headings,
for prose,
- for lists.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Let's extract content:
About TEGNA paragraph: "TEGNA Inc. helps people thrive in their local communities by providing the trusted local news and services that matter most. With 64 television stations in 51 U.S. markets, TEGNA reaches more than 100 million people monthly across the web, mobile apps, streaming, and linear television. Together, we are building a sustainable future for local news."
Then role description: "We are looking for a Senior Developer to help build and evolve the microservices behind TEGNA's Content Management platform — the systems that ingest, manage, and deliver content to millions of users. Our content management side runs on Azure; C#/.NET Function Apps with a Service Bus event backbone, fronted by Akamai. You'll be a technical anchor on the team: designing and implementing services, setting the bar for code quality and structure, and mentoring mid-level and offshore engineers. You'll take the tech briefs and epics that come from the CMS Solutions Architect and shape them into well-structured services, partnering with the Cloud Architect on how those designs are realized in infrastructure."
That could be part of About the role.
Responsibilities list: bullet points:
- Design, build, and operate C#/.NET microservices, primarily as Azure Function Apps, that power content management workflows.
- Own event-driven service design using Azure Service Bus — modeling messages and handling idempotency, ordering, retries, and failure gracefully.
- Lead technical design for meaningful features and services, and set standards for code quality, testing, and observability across the team.
- Mentor mid-level and offshore developers, raising the overall technical maturity of the team.
- Help convert epics into actionable, well-architected stories alongside the team lead.
- Drive the modernization of legacy content systems into scalable, maintainable, event-driven services.
- Partner with the CMS Solutions Architect and the Cloud Architect and cloud team (who own infrastructure realization, CI/CD, and standards).
- Work cloud-native in an Agile/Scrum team with disciplined source control.
Requirements list:
- 5+ years of professional software engineering experience building production backend services.
- Strong hands-on expertise in C#/.NET, including serverless/Azure Functions and RESTful API design.
- Solid experience with event-driven and messaging architectures (Azure Service Bus, queues, or equivalent pub/sub systems).
- Strong understanding of distributed-systems fundamentals: reliability, idempotency, concurrency, and observability, and a genuine concern for code structure and design.
- Production experience running cloud-native services in Azure and/or AWS.
- A track record of mentoring engineers and elevating team practices.
- Fluent in Agile/Scrum delivery and Git-based source control; exposure to Docker, Kubernetes, and Terraform is a plus.
- Media, streaming, high-traffic content platforms, or Graph-RAG content systems experience is a plus.
Benefits list: from Benefits section:
- TEGNA offers comprehensive benefits designed to safeguard the physical, mental and financial health of our employees and their families.
- TEGNA offers two medical plan options for full and part-time employees through Blue Cross Blue Shield of Texas, as well as access to dental and eye care coverage; fertility, surrogacy and adoption assistance; disability and life insurance.
- Our 401(k) program offers full, part-time and temporary employees the opportunity to contribute 1% - 80% of their pay on a pre-tax basis to TEGNA’s 401(k). Contributions made up to the first 4% of pay are eligible for a 100% match from the company and are 100% vested from day one.
- Regardless of participation in TEGNA medical plans, ALL employees and their eligible family members receive nine free virtual doctor’s appointments with a physician through Teladoc, and 12 free annual therapy sessions with a licensed clinician through Spring Health.
- TEGNA offers a generous Paid Time Off (PTO) benefit as well as nine paid holidays per year.
- Some jobs are covered by a collective bargaining agreement and thus some or all of the benefits described herein may not apply. For example, some newsroom bargaining unit employees receive health and retirement benefits under plans administered by the union.
We should keep that as prose or list? The instruction: Use
- for any list of duties/requirements/benefits. So we can turn each benefit into list items. However some sentences are long; we can split.
We also have "Why Join TEGNA" paragraph: "You'll be a senior technical voice on the team building TEGNA's content management platform at scale, in a modern Azure/AWS hybrid environment. This is an opportunity to shape the services and the engineering practices that power content across all of TEGNA's media properties. We are investing heavily in AI-assisted development, modern cloud-native services, and flexible architecture patterns that let our teams innovate quickly while delivering high-quality, high-impact products."
We could incorporate that into About the role or maybe a separate section like "About the team". Since we only have headings list, we could put it under About the role as additional prose.
We must not include EEO statement, recruiting fraud alert, privacy notice.
Now produce HTML:
About the role
TEGNA Inc. helps people thrive in their local communities by providing the trusted local news and services that matter most. With 64 television stations in 51 U.S. markets, TEGNA reaches more than 100 million people monthly across the web, mobile apps, streaming, and linear television. Together, we are building a sustainable future for local news. We are looking for a Senior Developer to help build and evolve the microservices behind TEGNA's Content Management platform — the systems that ingest, manage, and deliver content to millions of users. Our content management side runs on Azure; C#/.NET Function Apps with a Service Bus event backbone, fronted by Akamai. You'll be a technical anchor on the team: designing and implementing services, setting the bar for code quality and structure, and mentoring mid-level and offshore engineers. You'll take the tech briefs and epics that come from the CMS Solutions Architect and shape them into well-structured services, partnering with the Cloud Architect on how those designs are realized in infrastructure. You'll be a senior technical voice on the team building TEGNA's content management platform at scale, in a modern Azure/AWS hybrid environment. This is an opportunity to shape the services and the engineering practices that power content across all of TEGNA's media properties. We are investing heavily in AI-assisted development, modern cloud-native services, and flexible architecture patterns that let our teams innovate quickly while delivering high-quality, high-impact products.
Responsibilities
- Design, build, and operate C#/.NET microservices, primarily as Azure Function Apps, that power content management workflows.
- Own event-driven service design using Azure Service Bus — modeling messages and handling idempotency, ordering, retries, and failure gracefully.
- Lead technical design for meaningful features and services, and set standards for code quality, testing, and observability across the team.
- Mentor mid-level and offshore developers, raising the overall technical maturity of the team.
- Help convert epics into actionable, well-architected stories alongside the team lead.
- Drive the modernization of legacy content systems into scalable, maintainable, event-driven services.
- Partner with the CMS Solutions Architect and the Cloud Architect and cloud team (who own infrastructure realization, CI/CD, and standards).
- Work cloud-native in an Agile/Scrum team with disciplined source control.
Requirements
- 5+ years of professional software engineering experience building production backend services.
- Strong hands-on expertise in C#/.NET, including serverless/Azure Functions and RESTful API design.
- Solid experience with event-driven and messaging architectures (Azure Service Bus, queues, or equivalent pub/sub systems).
- Strong understanding of distributed-systems fundamentals: reliability, idempotency, concurrency, and observability, and a genuine concern for code structure and design.
- Production experience running cloud-native services in Azure and/or AWS.
- A track record of mentoring engineers and elevating team practices.
- Fluent in Agile/Scrum delivery and Git-based source control; exposure to Docker, Kubernetes, and Terraform is a plus.
- Media, streaming, high-traffic content platforms, or Graph-RAG content systems experience is a plus.
Benefits
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: About TEGNA (company description) maybe as "About the role"? Actually "About TEGNA" is company overview; we could put under
About the role
or maybe "About TEGNA". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have sections: About TEGNA (company description) could go under About the role. Responsibilities list. Requirements list. Benefits list. Possibly Qualifications? The posting includes Requirements and also mentions "Why Join TEGNA" which is like benefits/culture. Also "Benefits" section present. Also "Why Join TEGNA" includes some description; could be part of Benefits or maybe separate but we can incorporate into Benefits or maybe a "Why Join TEGNA" not a standard heading; we could treat as part of Benefits or maybe as a separate section like "About the team"? But instruction says only use those headings if content exists. We could create a section "About the role" for the company overview and why join. Then Responsibilities, Requirements, Benefits. We must not include EEO statement, recruiting fraud alert, privacy notice. Also remove duplicated lines. We need to preserve all substantive information: So include details about TEGNA, the role, responsibilities, requirements, benefits (including medical plans, 401k, Teladoc, therapy, PTO, holidays). Also mention "Why Join TEGNA" details: senior technical voice, Azure/AWS hybrid, AI-assisted development, etc. That could be part of About the role or Benefits. We must not invent or summarize away detail. So we need to keep specifics: e.g., "64 television stations in 51 U.S. markets, reaches more than 100 million people monthly across the web, mobile apps, streaming, and linear television." etc. We need to format as HTML fragment: no or . Usefor headings,
for prose,
- for lists.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Let's extract content:
About TEGNA paragraph: "TEGNA Inc. helps people thrive in their local communities by providing the trusted local news and services that matter most. With 64 television stations in 51 U.S. markets, TEGNA reaches more than 100 million people monthly across the web, mobile apps, streaming, and linear television. Together, we are building a sustainable future for local news."
Then role description: "We are looking for a Senior Developer to help build and evolve the microservices behind TEGNA's Content Management platform — the systems that ingest, manage, and deliver content to millions of users. Our content management side runs on Azure; C#/.NET Function Apps with a Service Bus event backbone, fronted by Akamai. You'll be a technical anchor on the team: designing and implementing services, setting the bar for code quality and structure, and mentoring mid-level and offshore engineers. You'll take the tech briefs and epics that come from the CMS Solutions Architect and shape them into well-structured services, partnering with the Cloud Architect on how those designs are realized in infrastructure."
That could be part of About the role.
Responsibilities list: bullet points:
- Design, build, and operate C#/.NET microservices, primarily as Azure Function Apps, that power content management workflows.
- Own event-driven service design using Azure Service Bus — modeling messages and handling idempotency, ordering, retries, and failure gracefully.
- Lead technical design for meaningful features and services, and set standards for code quality, testing, and observability across the team.
- Mentor mid-level and offshore developers, raising the overall technical maturity of the team.
- Help convert epics into actionable, well-architected stories alongside the team lead.
- Drive the modernization of legacy content systems into scalable, maintainable, event-driven services.
- Partner with the CMS Solutions Architect and the Cloud Architect and cloud team (who own infrastructure realization, CI/CD, and standards).
- Work cloud-native in an Agile/Scrum team with disciplined source control.
Requirements list:
- 5+ years of professional software engineering experience building production backend services.
- Strong hands-on expertise in C#/.NET, including serverless/Azure Functions and RESTful API design.
- Solid experience with event-driven and messaging architectures (Azure Service Bus, queues, or equivalent pub/sub systems).
- Strong understanding of distributed-systems fundamentals: reliability, idempotency, concurrency, and observability, and a genuine concern for code structure and design.
- Production experience running cloud-native services in Azure and/or AWS.
- A track record of mentoring engineers and elevating team practices.
- Fluent in Agile/Scrum delivery and Git-based source control; exposure to Docker, Kubernetes, and Terraform is a plus.
- Media, streaming, high-traffic content platforms, or Graph-RAG content systems experience is a plus.
Benefits list: from Benefits section:
- TEGNA offers comprehensive benefits designed to safeguard the physical, mental and financial health of our employees and their families.
- TEGNA offers two medical plan options for full and part-time employees through Blue Cross Blue Shield of Texas, as well as access to dental and eye care coverage; fertility, surrogacy and adoption assistance; disability and life insurance.
- Our 401(k) program offers full, part-time and temporary employees the opportunity to contribute 1% - 80% of their pay on a pre-tax basis to TEGNA’s 401(k). Contributions made up to the first 4% of pay are eligible for a 100% match from the company and are 100% vested from day one.
- Regardless of participation in TEGNA medical plans, ALL employees and their eligible family members receive nine free virtual doctor’s appointments with a physician through Teladoc, and 12 free annual therapy sessions with a licensed clinician through Spring Health.
- TEGNA offers a generous Paid Time Off (PTO) benefit as well as nine paid holidays per year.
- Some jobs are covered by a collective bargaining agreement and thus some or all of the benefits described herein may not apply. For example, some newsroom bargaining unit employees receive health and retirement benefits under plans administered by the union.
We should keep that as prose or list? The instruction: Use
- for any list of duties/requirements/benefits. So we can turn each benefit into list items. However some sentences are long; we can split.
We also have "Why Join TEGNA" paragraph: "You'll be a senior technical voice on the team building TEGNA's content management platform at scale, in a modern Azure/AWS hybrid environment. This is an opportunity to shape the services and the engineering practices that power content across all of TEGNA's media properties. We are investing heavily in AI-assisted development, modern cloud-native services, and flexible architecture patterns that let our teams innovate quickly while delivering high-quality, high-impact products."
We could incorporate that into About the role or maybe a separate section like "About the team". Since we only have headings list, we could put it under About the role as additional prose.
We must not include EEO statement, recruiting fraud alert, privacy notice.
Now produce HTML:
About the role
TEGNA Inc. helps people thrive in their local communities by providing the trusted local news and services that matter most. With 64 television stations in 51 U.S. markets, TEGNA reaches more than 100 million people monthly across the web, mobile apps, streaming, and linear television. Together, we are building a sustainable future for local news. We are looking for a Senior Developer to help build and evolve the microservices behind TEGNA's Content Management platform — the systems that ingest, manage, and deliver content to millions of users. Our content management side runs on Azure; C#/.NET Function Apps with a Service Bus event backbone, fronted by Akamai. You'll be a technical anchor on the team: designing and implementing services, setting the bar for code quality and structure, and mentoring mid-level and offshore engineers. You'll take the tech briefs and epics that come from the CMS Solutions Architect and shape them into well-structured services, partnering with the Cloud Architect on how those designs are realized in infrastructure. You'll be a senior technical voice on the team building TEGNA's content management platform at scale, in a modern Azure/AWS hybrid environment. This is an opportunity to shape the services and the engineering practices that power content across all of TEGNA's media properties. We are investing heavily in AI-assisted development, modern cloud-native services, and flexible architecture patterns that let our teams innovate quickly while delivering high-quality, high-impact products.
Responsibilities
- Design, build, and operate C#/.NET microservices, primarily as Azure Function Apps, that power content management workflows.
- Own event-driven service design using Azure Service Bus — modeling messages and handling idempotency, ordering, retries, and failure gracefully.
- Lead technical design for meaningful features and services, and set standards for code quality, testing, and observability across the team.
- Mentor mid-level and offshore developers, raising the overall technical maturity of the team.
- Help convert epics into actionable, well-architected stories alongside the team lead.
- Drive the modernization of legacy content systems into scalable, maintainable, event-driven services.
- Partner with the CMS Solutions Architect and the Cloud Architect and cloud team (who own infrastructure realization, CI/CD, and standards).
- Work cloud-native in an Agile/Scrum team with disciplined source control.
Requirements
- 5+ years of professional software engineering experience building production backend services.
- Strong hands-on expertise in C#/.NET, including serverless/Azure Functions and RESTful API design.
- Solid experience with event-driven and messaging architectures (Azure Service Bus, queues, or equivalent pub/sub systems).
- Strong understanding of distributed-systems fundamentals: reliability, idempotency, concurrency, and observability, and a genuine concern for code structure and design.
- Production experience running cloud-native services in Azure and/or AWS.
- A track record of mentoring engineers and elevating team practices.
- Fluent in Agile/Scrum delivery and Git-based source control; exposure to Docker, Kubernetes, and Terraform is a plus.
- Media, streaming, high-traffic content platforms, or Graph-RAG content systems experience is a plus.
Benefits
- for any list of duties/requirements/benefits. So we can turn each benefit into list items. However some sentences are long; we can split.
We also have "Why Join TEGNA" paragraph: "You'll be a senior technical voice on the team building TEGNA's content management platform at scale, in a modern Azure/AWS hybrid environment. This is an opportunity to shape the services and the engineering practices that power content across all of TEGNA's media properties. We are investing heavily in AI-assisted development, modern cloud-native services, and flexible architecture patterns that let our teams innovate quickly while delivering high-quality, high-impact products."
We could incorporate that into About the role or maybe a separate section like "About the team". Since we only have headings list, we could put it under About the role as additional prose.
We must not include EEO statement, recruiting fraud alert, privacy notice.
Now produce HTML: