1

Pulumi Jobs in Indiana (NOW HIRING)

Pulumi information

What Python jobs are in demand?

Python developers are in high demand across various industries, including web development, data science, machine learning, and automation. Skills in frameworks like Django or Flask, along with knowledge of cloud platforms and version control, enhance job prospects. Many roles require proficiency in Python scripting, problem-solving, and sometimes experience with related tools like Docker or Kubernetes.

Which companies use Pulumi?

Many organizations across various industries use Pulumi for infrastructure as code, including companies like Microsoft, Capital One, and Snowflake. These companies leverage Pulumi's support for multiple cloud providers and programming languages to automate and manage their cloud infrastructure effectively.

What are the key skills and qualifications needed to thrive as a Pulumi Engineer, and why are they important?

To thrive as a Pulumi Engineer, you need a solid background in cloud infrastructure, infrastructure as code (IaC), and programming languages such as Python, TypeScript, or Go, often backed by relevant cloud certifications. Familiarity with Pulumi's CLI, SDKs, and cloud provider platforms like AWS, Azure, or GCP is typically required. Strong problem-solving, collaboration, and communication skills help you efficiently design, deploy, and manage scalable cloud solutions. These capabilities ensure secure, maintainable, and efficient infrastructure deployments in dynamic cloud environments.

How does Pulumi work?

Pulumi is an infrastructure as code tool that allows developers to define cloud resources using familiar programming languages like JavaScript, TypeScript, Python, Go, or C#. It translates these code definitions into cloud provider-specific configurations and manages resource provisioning, updates, and deletions. Pulumi integrates with cloud platforms such as AWS, Azure, and Google Cloud, enabling automation and version control of infrastructure deployments.

What is the difference between Pulumi vs Cloud Engineer?

AspectPulumiCloud Engineer
Primary RoleInfrastructure as Code tool for managing cloud resourcesDesigning, implementing, and maintaining cloud infrastructure and solutions
Required SkillsProgramming, cloud platforms, IaC toolsCloud platforms, scripting, networking, security
Work EnvironmentDevOps teams, cloud development projectsIT departments, cloud service providers
CertificationsCloud certifications, IaC knowledgeCloud certifications, networking, security

While Pulumi is a tool used by Cloud Engineers to automate and manage cloud infrastructure, Cloud Engineers are professionals responsible for designing and maintaining cloud solutions. Pulumi helps Cloud Engineers implement infrastructure as code efficiently, making it a key part of their toolkit.

What jobs pay $500,000 a year in the US?

High-paying roles related to Pulumi, such as senior cloud engineers, solutions architects, or DevOps directors, can reach or exceed $500,000 annually, especially with experience, certifications, and leadership responsibilities. These positions often require expertise in cloud infrastructure, automation tools, and programming skills, and may include bonuses or stock options that contribute to total compensation.

What are some common challenges faced by engineers working with Pulumi for infrastructure as code, and how can they be addressed?

Engineers using Pulumi often encounter challenges such as managing complex infrastructure dependencies, keeping codebases organized as projects scale, and ensuring seamless collaboration across teams. Addressing these challenges typically involves adopting best practices like modularizing code with reusable components, leveraging Pulumi's stack and configuration management features, and integrating with version control systems for collaborative workflows. Regular code reviews and clear documentation also play key roles in maintaining code quality and team alignment when working with Pulumi.

What is Pulumi?

Pulumi is an open-source infrastructure as code (IaC) platform that allows developers and DevOps teams to define, deploy, and manage cloud infrastructure using familiar programming languages such as JavaScript, TypeScript, Python, Go, and C#. Unlike traditional IaC tools that use domain-specific languages, Pulumi lets you use real code to model and provision resources across cloud providers like AWS, Azure, Google Cloud, and Kubernetes. This approach enables better testing, reusability, and integration with existing development workflows. Pulumi also provides a cloud service for state management, collaboration, and policy enforcement.
What are popular job titles related to Pulumi jobs in Indiana? For Pulumi jobs in Indiana, the most frequently searched job titles are:
What job categories do people searching Pulumi jobs in Indiana look for? The top searched job categories for Pulumi jobs in Indiana are:
Infographic showing various Pulumi job openings in Indiana as of June 2026, with employment types broken down into 94% Full Time, 4% Part Time, and 2% Contract. Highlights an 81% Physical, 2% Hybrid, and 17% Remote job distribution.

Senior Network Reliability Engineer

Group 1001

Indianapolis, IN • On-site

Full-time

Re-posted 16 days ago


Group1001 rating

9.5

Company rating: 9.5 out of 10

Based on 8 frontline employees who took The Breakroom Quiz

8th of 299 rated insurance


Job description

Job Summary:
Group 1001 is a consumer-centric, technology-driven family of insurance companies focused on delivering outstanding value and operational performance. They are seeking a Senior Network Reliability Engineer to build and implement Site Reliability Engineering practices, applying SRE principles to enhance the firm's network platform and ensure reliability across multi-cloud environments.
Responsibilities:
• Treat reliability as an engineered property. Define SLOs and error budgets for the network platform — DNS resolution, edge availability, mesh ingress success, cross-region path health — and use them to gate changes, not just to color dashboards. Lead postmortems with a focus on permanent remediation, not pattern-recognition. Alert on symptoms users feel, not on causes that may or may not produce impact.
• Move network state into code. Use Terraform (or Pulumi), Ansible, and Python to replace CLI-driven configuration with declarative, version-controlled, peer-reviewed change running through Infra CI/CD. This applies equally to the edge tier (Cloudflare), security platforms (Zscaler ZIA/ZPA, ZTNA policies, next-gen firewalls), the cloud network fabric (Transit Gateway, Cloud WAN, VPCs, Route53, IPAM), and increasingly the Kubernetes and service-mesh layer.
• Build network policy as intent, not rule lists. Express what flows are permitted, what segments are isolated, what egress is inspected, what zones share DNS — and engineer the compilers that turn that intent into per-vendor configuration. Use Policy as Code (OPA/Rego, Sentinel, Cilium NetworkPolicy) to catch invariant violations at plan time, not apply time.
• Infrastructure as Code (IaC): Design, deploy, and manage network infrastructure using Terraform or Ansible, moving the firm away from manual configuration to a code-first approach.
• Engineer the cloud network platform. Operate and extend our multi-account AWS Landing Zone — Cloud WAN segmentation, Transit Gateway peering, IPAM-driven CIDR allocation, shared private DNS, cross-account telemetry pipelines. Build the platform abstractions that make a new account or service land correctly with policy and connectivity composed from declarative inputs.
• Extend platform thinking into the container tier. Kubernetes networking, service mesh (Istio, Linkerd, Consul Connect), eBPF-based observability and policy (Cilium, Hubble), and the integration points where mesh-level authz meets cloud-tier identity. Recognize that an "internal" service is one logical hop on a chain of policy enforcement points and engineer for that explicitly.
• Improve telemetry and observability with intent. Build alerts as structured payloads with runbook links, suspected blast radius, and dependency-aware suppression. Author both system-health dashboards for operators and end-user monitoring dashboards that reflect actual user experience. Use Grafana, Elastic, Open Telemetry where each fits.
• Mentor and grow the team. Provide technical guidance to junior engineers, foster a culture of learning, and work out loud across Platform Engineering so the patterns you build cross-pollinate to adjacent domains.
• Handle hardware when required. Provide maintenance and configuration support for routers, switches, and firewalls at data centers and offices when needed — bringing code-first practices to physical hardware where possible (templating, change validation, zero-touch provisioning) and direct hands-on competence where it isn't.
• Incident Response: Serve as an escalation point for network issues, some complex and some basic but not yet covered by runbooks. Troubleshooting with a focus on root cause analysis and permanent remediation with a documentation-first mindset.
• Reduce toil and hand off cleanly. Repetitive operational tasks are scoped engineering problems with measurable payoff. Author runbooks and SOPs that the NOC can execute confidently; package routine work for L1/L2 handoff so engineering interrupt drops over time. Coordinate across Data Platforms, NOC/SOC, and Cyber Security so reliability practices spread instead of staying siloed.
Qualifications:
Required:
• Deep understanding of TCP/IP, BGP, OSPF, VPNs, and SD-WAN architecture.
• Proven experience with Terraform (state management, modules) and Ansible (playbooks, roles) – or similar – in a production environment.
• Proficiency in Python for automation and API interaction, or similar.
• Hands-on experience with Cloudflare, zScaler, and/or enterprise firewalls.
• Experience configuring monitoring tools (e.g., Datadog, Prometheus, Grafana) to create meaningful alerts and dashboards.
Preferred:
• Service mesh experience (Istio, Linkerd, Consul Connect, Cilium).
• eBPF-based observability (Hubble, Pixie).
• AWS Multi-account landing zone tooling experience (AFT, Control Tower, or equivalent).
• Policy as Code experience (OPA/Rego, Sentinel, Cilium NetworkPolicy).
• Documentation First: A strong belief that a job isn't done until the documentation in written.
• Toil Reduction: A mindset that actively seeks to automate repetitive tasks.
• Hybrid Capability: Willingness to handle physical hardware tasks when required while maintaining a software-centric engineering mindset.
Company:
Group 1001 is a collective that empowers companies to create positive growth. Our insurance and annuities are easy to understand and accessible to all. Founded in 2013, the company is headquartered in Zionsville, USA, with a team of 1001-5000 employees. The company is currently Late Stage.

What Group1001 employees say

Pay

Benefits

Hours and flexibility

Workplace

Get the full story on Breakroom