DevOps Architect

Job Title: Lead Associate Principal, Software Engineering: DevOps Location: Chicago, IL (Onsite – Hybrid - 3 days in a week) [Required] Understanding of Kanban and/or Agile methodologies[Required] Familiarity with SRE principles as defined by Google SRE practices (error budgets, toil elimination, reliability hierarchy)[Required] Able to succeed in a fast-paced environment with frequent changes[Required] Comfortable communicating with both technical and non-technical audiences[Required] Self-starter — takes initiative to research, learn, and deliver; anticipates the play[Required] Team player — humble, collaborative, and focused on making the entire team succeed [Required] AWS EC2, Kubernetes, Kafka, Jenkins, Terraform, Ansible, Hashicorp Vault[Required] Observability tooling such as Prometheus, Grafana, OpenTelemetry, Datadog, or equivalent[Required] Incident management platforms and on-call tooling (e.g., PagerDuty, OpsGenie)[Required] Microservices and streaming data-intensive application architecture[Required] Application architecture, networking, and security in the cloud[Required] Setting up platforms in AWS for high-performance requirements[Required] Broad experience in API-based development[Required] Git and Artifactory for sourcing artifacts[Required] Multi-AZ, multi-region failover architecture[Required] Chaos engineering principles and tooling (e.g., Chaos Monkey, Gremlin, LitmusChaos)[Required] Fluent with different data formats and structures: JSON, Protobuf, Avro[Required] SQL and NoSQL databases, in-memory data stores[Required] Java/Python/Scala/Golang software development[Required] Two or more of the following: web/mobile application development, Unix/Linux environments, event-driven systems, transaction processing systems, distributed and parallel systems, large software system development, security software development, public-cloud platforms[Required] Fluent in industry best practices, software patterns, and architecture principles[Required] Enterprise architecture frameworks such as TOGAF[Required] Ability to define and document architecture strategies, designs, and requirements across all enterprise architecture domains[Required] Ability to define service-based, component architectures and demonstrate visualization of enterprise architecture concepts To perform this job successfully, an individual must be able to perform each primary duty satisfactorily.Guides the implementation using CI/CD pipelines in Kubernetes environmentDirects review, configuration, and execution of Terraform and Ansible automation pipelines delivered by product teamsGuides the setup of common infrastructure platforms like multi-region Kubernetes and Kafka clustersElicits requirements for application deployment and sizing to manage expected workloadsDefines and enforces Service Level Objectives (SLOs), Service Level Indicators (SLIs), and Error Budgets in collaboration with product teamsLeads blameless post-mortems and drives resolution of action items to reduce repeat incidentsDesigns and implements observability frameworks covering metrics, logs, and distributed tracing across all platform servicesDrives toil reduction initiatives by identifying and automating repetitive operational workPartners with product teams to embed reliability requirements and non-functional requirements (NFRs) early in the software development lifecycleMonitors application performance and tunes systems working with product teamsConfers with product team leads and practitioners to create deployment and reliability plansConfers with Enterprise Architecture and Renaissance architecture teams to devise implementation architecturePromotes standards across application configuration towards the highest security postureCollaborates with access management and security teams on setting up roles and permissions using least privilege strategiesCollaborates with integration/performance testing teams to leverage integrated release testing in the Release Acceptance environmentCollaborates with production controls teams on monitoring, failover, logging, and alerting strategiesOwns and continuously improves incident response runbooks, on-call rotations, and escalation proceduresConducts capacity planning and load forecasting to proactively address scalability needsImplements and validates infrastructure failover scenariosConfers with Network team on all connectivity plans and issue resolution (including between on-premises and AWS)Follows and enables program-level agile practices for efficient collaboration and deliveryDevelops documentation for ORT technical infrastructure, architecture, and reliability support

Create an account to see the full posting, access our search engine, and more.