Manager, Technical Operations
Pay
with that info in. Also maybe "Benefits" not present, so omit. "Schedule" not present. "Qualifications" maybe same as Requirements? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "About InvoiceCloud" which is about company, not role. Could map to "About the role"? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. The posting has "About InvoiceCloud" (company overview). Could map to "About the role"? Not exactly but we could use "About the role" heading and put the company description there? Might be okay. However they said do NOT repeat the job title as a heading. They didn't forbid using About the role for company overview. Probably better to use "About the role" for the Position Overview? Actually "Position Overview" is about role. So we could use "About the role" heading for Position Overview. Then "About InvoiceCloud" could be omitted? But we need to preserve ALL substantive information; we cannot drop company description. Could we put it under "About the role"? Might be mixing. Perhaps better to create a custom heading? But instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings where applicable. We have content that fits:
- About the role: Position Overview (description of role)
- Responsibilities: maybe the Success Profile sections (Results Driven, Takes Ownership, Drives Efficiency, Innovative) could be considered responsibilities. Could map each bullet under Responsibilities as list items? But they are detailed. Could create a - for each responsibility. However the Success Profile includes many bullet points under each competency. Could combine them into a single list of responsibilities. Might be lengthy but okay.
- Requirements: the "Requirements" section includes Experience & Education, Core Technical Expertise, etc. That's clearly requirements.
- Qualifications: maybe we could split out Preferred Certifications? But they are under Requirements as "Preferred Certifications". Could treat as Qualifications.
- Skills: maybe we could extract technical skills from Core Technical Expertise etc. But that might be duplication.
- Pay: base compensation range.
- Benefits: not present.
- Schedule: not present.
We need to preserve all substantive information. If we compress too much we might lose detail. Better to keep sections as they appear: About InvoiceCloud (maybe as a paragraph), Position Overview, Success Profile (with subheadings?), Requirements (with subheadings). But the instruction says use those specific headings for section headings. It might be okay to also include other headings like "About InvoiceCloud" as a
? The examples are not exhaustive; they say e.g. About the role, Responsibilities, etc. So we could still use other headings if needed. But to be safe, we can map:
- About the role
: Position Overview paragraph.
- Responsibilities
: combine the Success Profile bullet points (maybe each competency as a subheading? but we cannot add extra headings beyond those? Not prohibited). Could just list responsibilities as - each bullet from Success Profile.
-
Requirements
: the Requirements section (Experience & Education, Core Technical Expertise, etc.) as - each bullet.
-
Qualifications
: Preferred Certifications.
- Pay
: Base Compensation Range.
We must not repeat job title as heading. Not needed.
We must remove boilerplate: EEO, accommodation, privacy policy, recruitment agency note. Remove those.
We must not include application instructions.
We must preserve all substantive information: company description, position overview, success profile details, requirements details, preferred certifications, base compensation range.
Let's extract content.
Company description: "About InvoiceCloud InvoiceCloud is a fast-growing fintech leader recognized with 20 major awards in 2025, including USA TODAY and Boston Globe Top Workplaces, multiple SaaS Awards wins for Best Solution for Finance and FinTech, and national customer service honors from Stevie and the Business Intelligence Group. Judges also highlighted our mission to reduce digital exclusion and restore simplicity and dignity to how people pay for essential services, as well as our leadership in AI maturity and responsible innovation. It’s an award-winning, purpose-driven environment where top talent thrives. To learn more, visit InvoiceCloud.com."
We can put that under maybe About the company
but not in list. Could put under About the role
? Might be odd. Better to add a About InvoiceCloud
as a heading, though not in the examples but likely acceptable. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, just gives examples. So we can use About InvoiceCloud.
Thus sections:
- About InvoiceCloud (company overview)
- About the role (Position Overview)
- Responsibilities (Success Profile)
- Requirements (Experience & Education, Core Technical Expertise, etc.)
- Qualifications (Preferred Certifications)
- Pay (Base Compensation Range)
We need to ensure we don't create empty sections.
Now format.
We'll output HTML fragment only.
Let's craft.
First, About InvoiceCloud: put in
.
Then About the role: Position Overview paragraph.
Then Responsibilities: we need to list each bullet from Success Profile. Let's extract them.
Success Profile sections:
Results Driven:
- Deliver a transparent, predictable Infrastructure Service Request intake and prioritization process that aligns work to business urgency, risk, and impact.
- Ensure timely triage, assignment, and resolution of infrastructure requests with clear SLAs, communication, and stakeholder visibility.
- Coordinate and execute maintenance windows—including patching, security updates, and operational upgrades—in partnership with Cloud Platform Engineers, ensuring minimal disruption and validated outcomes.
- Facilitate Infrastructure Board Review sessions that drive clarity on priorities, decision-making, and execution readiness.
- Maintain operational rigor by ensuring all changes adhere to established change-management processes, approvals, and audit requirements.
Takes Ownership:
- Own the Infrastructure Service Request JIRA board, including intake quality, prioritization discipline, backlog health, and workflow governance.
- Lead, coach, and develop a team of Cloud Platform Engineers, setting clear goals, conducting regular 1:1s and performance reviews, and building individual growth and career development plans.
- Anticipate and escalate infrastructure risks related to capacity, obsolescence, performance degradation, security exposure, or operational bottlenecks.
- Maintain accountability for communicating maintenance plans, change impacts, and risk considerations to stakeholders and leadership.
- Manage team capacity and staffing needs for Cloud Platform Engineers, balancing workload, skill development, and hiring to meet operational demand.
- Manage the backlog of infrastructure initiatives and ensure large-scale requests are decomposed, scoped, and routed into platform sprint cycles.
- Provide regular updates, insights, and risk assessments to the VP of Platform Engineering, demonstrating operational command and strategic awareness.
- Partner with InfoSec to coordinate security hardening initiatives and support PCI and SOC 2 audit readiness across infrastructure and platform environments.
Drives Efficiency:
- Streamline the end-to-end request workflow by defining intake standards, triage guidelines, prioritization rubrics, and repeatable processes.
- Improve throughput and cycle time by removing operational bottlenecks, optimizing workflows, and ensuring clean handoffs between Infrastructure and Cloud Platform Engineering teams.
- Enhance efficiency of patching and maintenance operations through structured scheduling, automation opportunities, and consistent communication practices.
- Leverage metrics—such as cycle time, board aging, change success rates, and ticket throughput—to identify trends and continuously refine processes.
- Standardize documentation, templates, and communication mechanisms to reduce ambiguity and accelerate execution.
- Reduce manual toil by applying AI-assisted tooling to ticket triage, request classification, and routine operational tasks, freeing capacity for higher-value platform work.
Innovative:
- Identify and implement improvements to the infrastructure request intake and prioritization model, leveraging automation, workflow tooling, and data-driven insights.
- Explore enhancements to maintenance and patching strategies, including phased rollouts, automated validation, and modernized operational patterns.
- Partner with Cloud Platform Engineers to adopt new technologies, practices, and governance models that increase reliability and reduce operational overhead.
- Introduce new methods for operational transparency—such as dashboarding, reporting automation, or trend analysis—to improve decision-making and stakeholder alignment.
- Drive continuous improvement in change-management practices by evaluating emerging tooling, compliance frameworks, and risk-reduction strategies.
- Evaluate and pilot AI-driven automation—such as intelligent alerting, anomaly detection, and self-service remediation—to reduce operational toil and improve overall platform efficiency.
We'll put each as
- under a
.
Requirements: we have sub-sections: Experience & Education, Core Technical Expertise (with many bullet points). We'll flatten into list items.
Experience & Education:
- Bachelor’s degree and minimum 5 years of experience in Infrastructure, Platform Engineering, Site Reliability Engineering, or related technical operational roles.
- Demonstrated experience managing technical work intake processes and backlogs using JIRA or similar tools.
- Experience coordinating maintenance windows, patch cycles, or operational readiness activities.
- Strong understanding of change-management frameworks and operational governance best practices.
- Excellent communication skills and experience engaging with senior technical and business stakeholders.
- Strong analytical capabilities for assessing technical risk, complexity, and business impact.
Core Technical Expertise: many bullet points. We'll list each.
- Cloud & Kubernetes Expertise supporting and troubleshooting Microsoft Azure, including AKS, VNets, NSGs, Load Balancers, VPN/ExpressRoute, managed identities, and Azure Policy/RBAC.
- Expertise supporting and troubleshooting Kubernetes experience: cluster operations, scaling, upgrades, workload security, and troubleshooting.
- Expertise supporting and troubleshooting Cloudflare DNS, CDN, WAF, and Zero Trust configurations.
- Infrastructure as Code & Automation Experience with Terraform for modular, reusable cloud provisioning.
- Experience with Ansible for system configuration and application deployment.
- Automation skills using PowerShell, Bash, and/or Python.
- Applications Experience supporting and troubleshooting Windows Server, IIS, and .NET Framework/Core application environments.
- Experience supporting and troubleshooting Ubuntu Server, Nginx, and Python Django applications, including containerization and integration with Azure services.
- Experience containerizing both .NET and Python/Django applications and operating them in AKS with proper health probes, scaling, and observability.
- Network Security & Access Control Experience designing and managing firewall rules, NSGs, ACLs, and network segmentation strategies in both cloud and on-prem environments.
- Ability to analyze traffic flows, identify misconfigurations, resolve blocked flows, and enforce least-privilege access patterns.
- Experience managing distributed firewall policies across Azure, Cloudflare, and virtualization platforms (e.g., Proxmox).
- CI/CD & Observability Experience with GitHub Actions or Azure DevOps for automated builds, tests, deployments, and environment promotions.
- Strong monitoring, logging, and performance troubleshooting skills using Azure Monitor,
? The examples are not exhaustive; they say e.g. About the role, Responsibilities, etc. So we could still use other headings if needed. But to be safe, we can map:
- About the role
: Position Overview paragraph.
- Responsibilities
: combine the Success Profile bullet points (maybe each competency as a subheading? but we cannot add extra headings beyond those? Not prohibited). Could just list responsibilities as - each bullet from Success Profile.
-
Requirements
: the Requirements section (Experience & Education, Core Technical Expertise, etc.) as - each bullet.
-
Qualifications
: Preferred Certifications.
- Pay
: Base Compensation Range.
We must not repeat job title as heading. Not needed.
We must remove boilerplate: EEO, accommodation, privacy policy, recruitment agency note. Remove those.
We must not include application instructions.
We must preserve all substantive information: company description, position overview, success profile details, requirements details, preferred certifications, base compensation range.
Let's extract content.
Company description: "About InvoiceCloud InvoiceCloud is a fast-growing fintech leader recognized with 20 major awards in 2025, including USA TODAY and Boston Globe Top Workplaces, multiple SaaS Awards wins for Best Solution for Finance and FinTech, and national customer service honors from Stevie and the Business Intelligence Group. Judges also highlighted our mission to reduce digital exclusion and restore simplicity and dignity to how people pay for essential services, as well as our leadership in AI maturity and responsible innovation. It’s an award-winning, purpose-driven environment where top talent thrives. To learn more, visit InvoiceCloud.com."
We can put that under maybe About the company
but not in list. Could put under About the role
? Might be odd. Better to add a About InvoiceCloud
as a heading, though not in the examples but likely acceptable. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, just gives examples. So we can use About InvoiceCloud.
Thus sections:
- About InvoiceCloud (company overview)
- About the role (Position Overview)
- Responsibilities (Success Profile)
- Requirements (Experience & Education, Core Technical Expertise, etc.)
- Qualifications (Preferred Certifications)
- Pay (Base Compensation Range)
We need to ensure we don't create empty sections.
Now format.
We'll output HTML fragment only.
Let's craft.
First, About InvoiceCloud: put in
.
Then About the role: Position Overview paragraph.
Then Responsibilities: we need to list each bullet from Success Profile. Let's extract them.
Success Profile sections:
Results Driven:
- Deliver a transparent, predictable Infrastructure Service Request intake and prioritization process that aligns work to business urgency, risk, and impact.
- Ensure timely triage, assignment, and resolution of infrastructure requests with clear SLAs, communication, and stakeholder visibility.
- Coordinate and execute maintenance windows—including patching, security updates, and operational upgrades—in partnership with Cloud Platform Engineers, ensuring minimal disruption and validated outcomes.
- Facilitate Infrastructure Board Review sessions that drive clarity on priorities, decision-making, and execution readiness.
- Maintain operational rigor by ensuring all changes adhere to established change-management processes, approvals, and audit requirements.
Takes Ownership:
- Own the Infrastructure Service Request JIRA board, including intake quality, prioritization discipline, backlog health, and workflow governance.
- Lead, coach, and develop a team of Cloud Platform Engineers, setting clear goals, conducting regular 1:1s and performance reviews, and building individual growth and career development plans.
- Anticipate and escalate infrastructure risks related to capacity, obsolescence, performance degradation, security exposure, or operational bottlenecks.
- Maintain accountability for communicating maintenance plans, change impacts, and risk considerations to stakeholders and leadership.
- Manage team capacity and staffing needs for Cloud Platform Engineers, balancing workload, skill development, and hiring to meet operational demand.
- Manage the backlog of infrastructure initiatives and ensure large-scale requests are decomposed, scoped, and routed into platform sprint cycles.
- Provide regular updates, insights, and risk assessments to the VP of Platform Engineering, demonstrating operational command and strategic awareness.
- Partner with InfoSec to coordinate security hardening initiatives and support PCI and SOC 2 audit readiness across infrastructure and platform environments.
Drives Efficiency:
- Streamline the end-to-end request workflow by defining intake standards, triage guidelines, prioritization rubrics, and repeatable processes.
- Improve throughput and cycle time by removing operational bottlenecks, optimizing workflows, and ensuring clean handoffs between Infrastructure and Cloud Platform Engineering teams.
- Enhance efficiency of patching and maintenance operations through structured scheduling, automation opportunities, and consistent communication practices.
- Leverage metrics—such as cycle time, board aging, change success rates, and ticket throughput—to identify trends and continuously refine processes.
- Standardize documentation, templates, and communication mechanisms to reduce ambiguity and accelerate execution.
- Reduce manual toil by applying AI-assisted tooling to ticket triage, request classification, and routine operational tasks, freeing capacity for higher-value platform work.
Innovative:
- Identify and implement improvements to the infrastructure request intake and prioritization model, leveraging automation, workflow tooling, and data-driven insights.
- Explore enhancements to maintenance and patching strategies, including phased rollouts, automated validation, and modernized operational patterns.
- Partner with Cloud Platform Engineers to adopt new technologies, practices, and governance models that increase reliability and reduce operational overhead.
- Introduce new methods for operational transparency—such as dashboarding, reporting automation, or trend analysis—to improve decision-making and stakeholder alignment.
- Drive continuous improvement in change-management practices by evaluating emerging tooling, compliance frameworks, and risk-reduction strategies.
- Evaluate and pilot AI-driven automation—such as intelligent alerting, anomaly detection, and self-service remediation—to reduce operational toil and improve overall platform efficiency.
We'll put each as
- under a
.
Requirements: we have sub-sections: Experience & Education, Core Technical Expertise (with many bullet points). We'll flatten into list items.
Experience & Education:
- Bachelor’s degree and minimum 5 years of experience in Infrastructure, Platform Engineering, Site Reliability Engineering, or related technical operational roles.
- Demonstrated experience managing technical work intake processes and backlogs using JIRA or similar tools.
- Experience coordinating maintenance windows, patch cycles, or operational readiness activities.
- Strong understanding of change-management frameworks and operational governance best practices.
- Excellent communication skills and experience engaging with senior technical and business stakeholders.
- Strong analytical capabilities for assessing technical risk, complexity, and business impact.
Core Technical Expertise: many bullet points. We'll list each.
- Cloud & Kubernetes Expertise supporting and troubleshooting Microsoft Azure, including AKS, VNets, NSGs, Load Balancers, VPN/ExpressRoute, managed identities, and Azure Policy/RBAC.
- Expertise supporting and troubleshooting Kubernetes experience: cluster operations, scaling, upgrades, workload security, and troubleshooting.
- Expertise supporting and troubleshooting Cloudflare DNS, CDN, WAF, and Zero Trust configurations.
- Infrastructure as Code & Automation Experience with Terraform for modular, reusable cloud provisioning.
- Experience with Ansible for system configuration and application deployment.
- Automation skills using PowerShell, Bash, and/or Python.
- Applications Experience supporting and troubleshooting Windows Server, IIS, and .NET Framework/Core application environments.
- Experience supporting and troubleshooting Ubuntu Server, Nginx, and Python Django applications, including containerization and integration with Azure services.
- Experience containerizing both .NET and Python/Django applications and operating them in AKS with proper health probes, scaling, and observability.
- Network Security & Access Control Experience designing and managing firewall rules, NSGs, ACLs, and network segmentation strategies in both cloud and on-prem environments.
- Ability to analyze traffic flows, identify misconfigurations, resolve blocked flows, and enforce least-privilege access patterns.
- Experience managing distributed firewall policies across Azure, Cloudflare, and virtualization platforms (e.g., Proxmox).
- CI/CD & Observability Experience with GitHub Actions or Azure DevOps for automated builds, tests, deployments, and environment promotions.
- Strong monitoring, logging, and performance troubleshooting skills using Azure Monitor,
Requirements
: the Requirements section (Experience & Education, Core Technical Expertise, etc.) as- each bullet.
-
Qualifications
: Preferred Certifications. -Pay
: Base Compensation Range. We must not repeat job title as heading. Not needed. We must remove boilerplate: EEO, accommodation, privacy policy, recruitment agency note. Remove those. We must not include application instructions. We must preserve all substantive information: company description, position overview, success profile details, requirements details, preferred certifications, base compensation range. Let's extract content. Company description: "About InvoiceCloud InvoiceCloud is a fast-growing fintech leader recognized with 20 major awards in 2025, including USA TODAY and Boston Globe Top Workplaces, multiple SaaS Awards wins for Best Solution for Finance and FinTech, and national customer service honors from Stevie and the Business Intelligence Group. Judges also highlighted our mission to reduce digital exclusion and restore simplicity and dignity to how people pay for essential services, as well as our leadership in AI maturity and responsible innovation. It’s an award-winning, purpose-driven environment where top talent thrives. To learn more, visit InvoiceCloud.com." We can put that under maybeAbout the company
but not in list. Could put underAbout the role
? Might be odd. Better to add aAbout InvoiceCloud
as a heading, though not in the examples but likely acceptable. The instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, just gives examples. So we can use About InvoiceCloud. Thus sections: - About InvoiceCloud (company overview) - About the role (Position Overview) - Responsibilities (Success Profile) - Requirements (Experience & Education, Core Technical Expertise, etc.) - Qualifications (Preferred Certifications) - Pay (Base Compensation Range) We need to ensure we don't create empty sections. Now format. We'll output HTML fragment only. Let's craft. First, About InvoiceCloud: put in
. Then About the role: Position Overview paragraph. Then Responsibilities: we need to list each bullet from Success Profile. Let's extract them. Success Profile sections: Results Driven: - Deliver a transparent, predictable Infrastructure Service Request intake and prioritization process that aligns work to business urgency, risk, and impact. - Ensure timely triage, assignment, and resolution of infrastructure requests with clear SLAs, communication, and stakeholder visibility. - Coordinate and execute maintenance windows—including patching, security updates, and operational upgrades—in partnership with Cloud Platform Engineers, ensuring minimal disruption and validated outcomes. - Facilitate Infrastructure Board Review sessions that drive clarity on priorities, decision-making, and execution readiness. - Maintain operational rigor by ensuring all changes adhere to established change-management processes, approvals, and audit requirements. Takes Ownership: - Own the Infrastructure Service Request JIRA board, including intake quality, prioritization discipline, backlog health, and workflow governance. - Lead, coach, and develop a team of Cloud Platform Engineers, setting clear goals, conducting regular 1:1s and performance reviews, and building individual growth and career development plans. - Anticipate and escalate infrastructure risks related to capacity, obsolescence, performance degradation, security exposure, or operational bottlenecks. - Maintain accountability for communicating maintenance plans, change impacts, and risk considerations to stakeholders and leadership. - Manage team capacity and staffing needs for Cloud Platform Engineers, balancing workload, skill development, and hiring to meet operational demand. - Manage the backlog of infrastructure initiatives and ensure large-scale requests are decomposed, scoped, and routed into platform sprint cycles. - Provide regular updates, insights, and risk assessments to the VP of Platform Engineering, demonstrating operational command and strategic awareness. - Partner with InfoSec to coordinate security hardening initiatives and support PCI and SOC 2 audit readiness across infrastructure and platform environments. Drives Efficiency: - Streamline the end-to-end request workflow by defining intake standards, triage guidelines, prioritization rubrics, and repeatable processes. - Improve throughput and cycle time by removing operational bottlenecks, optimizing workflows, and ensuring clean handoffs between Infrastructure and Cloud Platform Engineering teams. - Enhance efficiency of patching and maintenance operations through structured scheduling, automation opportunities, and consistent communication practices. - Leverage metrics—such as cycle time, board aging, change success rates, and ticket throughput—to identify trends and continuously refine processes. - Standardize documentation, templates, and communication mechanisms to reduce ambiguity and accelerate execution. - Reduce manual toil by applying AI-assisted tooling to ticket triage, request classification, and routine operational tasks, freeing capacity for higher-value platform work. Innovative: - Identify and implement improvements to the infrastructure request intake and prioritization model, leveraging automation, workflow tooling, and data-driven insights. - Explore enhancements to maintenance and patching strategies, including phased rollouts, automated validation, and modernized operational patterns. - Partner with Cloud Platform Engineers to adopt new technologies, practices, and governance models that increase reliability and reduce operational overhead. - Introduce new methods for operational transparency—such as dashboarding, reporting automation, or trend analysis—to improve decision-making and stakeholder alignment. - Drive continuous improvement in change-management practices by evaluating emerging tooling, compliance frameworks, and risk-reduction strategies. - Evaluate and pilot AI-driven automation—such as intelligent alerting, anomaly detection, and self-service remediation—to reduce operational toil and improve overall platform efficiency. We'll put each as
- under a
- .
Requirements: we have sub-sections: Experience & Education, Core Technical Expertise (with many bullet points). We'll flatten into list items.
Experience & Education:
- Bachelor’s degree and minimum 5 years of experience in Infrastructure, Platform Engineering, Site Reliability Engineering, or related technical operational roles.
- Demonstrated experience managing technical work intake processes and backlogs using JIRA or similar tools.
- Experience coordinating maintenance windows, patch cycles, or operational readiness activities.
- Strong understanding of change-management frameworks and operational governance best practices.
- Excellent communication skills and experience engaging with senior technical and business stakeholders.
- Strong analytical capabilities for assessing technical risk, complexity, and business impact.
Core Technical Expertise: many bullet points. We'll list each.
- Cloud & Kubernetes Expertise supporting and troubleshooting Microsoft Azure, including AKS, VNets, NSGs, Load Balancers, VPN/ExpressRoute, managed identities, and Azure Policy/RBAC.
- Expertise supporting and troubleshooting Kubernetes experience: cluster operations, scaling, upgrades, workload security, and troubleshooting.
- Expertise supporting and troubleshooting Cloudflare DNS, CDN, WAF, and Zero Trust configurations.
- Infrastructure as Code & Automation Experience with Terraform for modular, reusable cloud provisioning.
- Experience with Ansible for system configuration and application deployment.
- Automation skills using PowerShell, Bash, and/or Python.
- Applications Experience supporting and troubleshooting Windows Server, IIS, and .NET Framework/Core application environments.
- Experience supporting and troubleshooting Ubuntu Server, Nginx, and Python Django applications, including containerization and integration with Azure services.
- Experience containerizing both .NET and Python/Django applications and operating them in AKS with proper health probes, scaling, and observability.
- Network Security & Access Control Experience designing and managing firewall rules, NSGs, ACLs, and network segmentation strategies in both cloud and on-prem environments.
- Ability to analyze traffic flows, identify misconfigurations, resolve blocked flows, and enforce least-privilege access patterns.
- Experience managing distributed firewall policies across Azure, Cloudflare, and virtualization platforms (e.g., Proxmox).
- CI/CD & Observability Experience with GitHub Actions or Azure DevOps for automated builds, tests, deployments, and environment promotions.
- Strong monitoring, logging, and performance troubleshooting skills using Azure Monitor,