Sr. Devops Engineer | Berkeley heights, NJ - 5 days onsite | Contract W2
- for any list of duties/requirements/benefits. So we can flatten? Probably we should keep each bullet as
- . The headings within responsibilities could be omitted? But we need to preserve all substantive information; we could keep the headings as plain text inside
- or as . The instruction didn't forbid using inside li. We'll just include the bullet text as is.
- Required Qualifications: list of items (bullet points). We'll output as
- .
- Preferred Experience Areas: list.
- Behavioral Skills: list.
- About Next Gen Software Solutions: company description (two paragraphs duplicated). We'll keep one substantive paragraph (maybe combine). We'll remove duplicate and EEO.
Thus sections:
About the role: the Job Description paragraph.
Responsibilities: the Key Responsibilities content.
Requirements: maybe combine Required Qualifications + Preferred Experience Areas + Behavioral Skills? But we need to follow headings list. Could have Requirements (mandatory), Qualifications (preferred), Skills (behavioral). That seems reasonable.
Thus:
About the role
...
Responsibilities
- ...
Requirements
- ... (Required Qualifications)
Qualifications
- ... (Preferred Experience Areas)
Skills
- ... (Behavioral Skills)
Experience: 10+ years
inside Requirements section before the list. Also location, duration, type: "Location: Berkeley heights, NJ - 5 days onsite Duration: long term Type: Contract W2 only". This is metadata; we should preserve. Could put in a short p under About the role or a separate section? There's no heading for metadata. We could add aLocation: Berkeley heights, NJ - 5 days onsite | Duration: long term | Type: Contract W2 only
maybe under About the role after the description. Or we could create a small section like "Job Details" but not in allowed headings. Better to fold into About the role paragraph or a p after. We must not invent sections like "Job Details". So we can add aafter the About the role description: "Location: Berkeley heights, NJ - 5 days onsite | Duration: long term | Type: Contract W2 only". That preserves info. Also we need to ensure we don't repeat the job title as heading. Now let's extract the exact text. Job Description paragraph: We'll copy exactly as given, maybe trim. "We are seeking a highly skilled DevOps Engineer to design, implement, automate, and support enterprise-scale infrastructure and platform solutions across hybrid cloud and on-premises environments. The ideal candidate will have deep expertise in Linux systems administration, container orchestration, CI/CD automation, big data platforms, observability, and distributed data processing technologies. This role requires strong experience with OpenShift, Kubernetes, MongoDB, Kafka, Flink, Spark/Cloudera ecosystems, virtualization platforms, and infrastructure automation using Ansible. The engineer will collaborate closely with development, architecture, security, and operations teams to build highly available, scalable, secure, and automated platforms supporting mission-critical enterprise applications." Now Responsibilities: We need to list each bullet. From the posting: Key Responsibilities Infrastructure & Platform Engineering - Design, deploy, configure, and maintain enterprise Linux-based infrastructure environments. - Administer and optimize Red Hat/OpenShift and Kubernetes container platforms. - Manage Linux virtual machine environments across VMware, KVM, or cloud-based virtualization platforms. - Implement highly available, fault-tolerant, and scalable infrastructure architectures. - Perform capacity planning, performance tuning, and infrastructure optimization. Kubernetes & OpenShift Administration - Build and maintain Kubernetes/OpenShift clusters for production and non-production environments. - Configure ingress controllers, networking, storage classes, service mesh, operators, and cluster security. - Automate deployment pipelines and container lifecycle management. - Implement GitOps and Infrastructure-as-Code practices. - Troubleshoot cluster performance, node failures, networking issues, and container runtime problems. Automation & DevOps - Develop automation solutions using Ansible for provisioning, patching, configuration management, and application deployment. - Build and maintain CI/CD pipelines supporting microservices and distributed platforms. - Standardize deployment and operational processes through scripting and automation. - Integrate security, compliance, and operational controls into deployment workflows. Data & Streaming Platform Support - Administer and support Apache Kafka clusters including brokers, topics, partitions, replication, and security. - Support Apache Flink streaming data platforms and real-time processing pipelines. - Manage Cloudera/Spark ecosystems for distributed data processing workloads. - Optimize distributed compute and data platforms for performance and resiliency. - Support data ingestion, streaming, and large-scale analytics environments. Monitoring & Observability - Implement enterprise monitoring, logging, and observability solutions using Splunk and related tooling. - Develop dashboards, alerts, and operational metrics for infrastructure and application monitoring. - Conduct root cause analysis and incident troubleshooting across distributed systems. - Support production operations, incident response, and problem management activities. Security & Compliance - Implement infrastructure hardening, RBAC, secrets management, and container security best practices. - Support enterprise security standards, vulnerability remediation, and compliance initiatives. - Ensure operational reliability, backup strategies, and disaster recovery readiness. We'll output each bullet as
- . We could keep the heading lines (like Infrastructure & Platform Engineering) as plain text maybe inside
- or as . To preserve, we could make them
- Infrastructure & Platform Engineering
then sub-items. But that would treat heading as a list item; maybe better to keep them as plain text outside- ? But instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid other text outside lists. So we could keep the headings as
or outside the list. However to keep it simple, we could just list all bullets ignoring headings; but we would lose the heading text (substantive). The headings are substantive categorization. We should preserve them. Perhaps we can wrap each heading in a
then the sublist. Thus:
Responsibilities
Infrastructure & Platform Engineering
- Design, deploy, configure, and maintain enterprise Linux-based infrastructure environments. ...
Kubernetes & OpenShift Administration
- ...
- . Also we need to include the experience line "Expereince : 10+Yrs". We'll add a
Experience: 10+ years
maybe. Now Preferred Experience Areas list: Preferred Experience Areas Enterprise-scale distributed systems Financial services or high-availability environments Real-time data streaming platforms Large-scale containerized environments We
- .
- Preferred Experience Areas: list.
- Behavioral Skills: list.
- About Next Gen Software Solutions: company description (two paragraphs duplicated). We'll keep one substantive paragraph (maybe combine). We'll remove duplicate and EEO.
Thus sections:
About the role: the Job Description paragraph.
Responsibilities: the Key Responsibilities content.
Requirements: maybe combine Required Qualifications + Preferred Experience Areas + Behavioral Skills? But we need to follow headings list. Could have Requirements (mandatory), Qualifications (preferred), Skills (behavioral). That seems reasonable.
Thus: