11+ Postfix Jobs in Chennai | Postfix Job openings in Chennai

About us:

HappyFox is a software-as-a-service (SaaS) support platform. We offer an enterprise-grade help desk ticketing system and intuitively designed live chat software.

We serve over 12,000 companies in 70+ countries. HappyFox is used by companies that span across education, media, e-commerce, retail, information technology, manufacturing, non-profit, government and many other verticals that have an internal or external support function.

To know more, Visit! - https://www.happyfox.com/

Responsibilities

• Build and scale production infrastructure in AWS for the HappyFox platform and its products.
• Research, Build/Implement systems, services and tooling to improve uptime, reliability and maintainability of our backend infrastructure. And to meet our internal SLOs and customer-facing SLAs.
• Implement consistent observability, deployment and IaC setups
• Lead incident management and actively respond to escalations/incidents in the production environment from customers and the support team.
• Hire/Mentor other Infrastructure engineers and review their work to continuously ship improvements to production infrastructure and its tooling.
• Build and manage development infrastructure, and CI/CD pipelines for our teams to ship & test code faster.
• Lead infrastructure security audits

Requirements

• At least 7 years of experience in handling/building Production environments in AWS.
• At least 3 years of programming experience in building API/backend services for customer-facing applications in production.
• Proficient in managing/patching servers with Unix-based operating systems like Ubuntu Linux.
• Proficient in writing automation scripts or building infrastructure tools using Python/Ruby/Bash/Golang
• Experience in deploying and managing production Python/NodeJS/Golang applications to AWS EC2, ECS or EKS.
• Experience in security hardening of infrastructure, systems and services.
• Proficient in containerised environments such as Docker, Docker Compose, Kubernetes
• Experience in setting up and managing test/staging environments, and CI/CD pipelines.
• Experience in IaC tools such as Terraform or AWS CDK
• Exposure/Experience in setting up or managing Cloudflare, Qualys and other related tools
• Passion for making systems reliable, maintainable, scalable and secure.
• Excellent verbal and written communication skills to address, escalate and express technical ideas clearly
• Bonus points – Hands-on experience with Nginx, Postgres, Postfix, Redis or Mongo systems.

JOB DETAILS:

* Job Title: Specialist I - DevOps Engineering

* Industry: Global Digital Transformation Solutions Provider

* Salary: Best in Industry

* Experience: 7-10 years

* Location: Bengaluru (Bangalore), Chennai, Hyderabad, Kochi (Cochin), Noida, Pune, Thiruvananthapuram

Job Description

Job Summary:

As a DevOps Engineer focused on Perforce to GitHub migration, you will be responsible for executing seamless and large-scale source control migrations. You must be proficient with GitHub Enterprise and Perforce, possess strong scripting skills (Python/Shell), and have a deep understanding of version control concepts.

The ideal candidate is a self-starter, a problem-solver, and thrives on challenges while ensuring smooth transitions with minimal disruption to development workflows.

Key Responsibilities:

• Analyze and prepare Perforce repositories — clean workspaces, merge streams, and remove unnecessary files.
• Handle large files efficiently using Git Large File Storage (LFS) for files exceeding GitHub’s 100MB size limit.
• Use git-p4 fusion (Python-based tool) to clone and migrate Perforce repositories incrementally, ensuring data integrity.
• Define migration scope — determine how much history to migrate and plan the repository structure.
• Manage branch renaming and repository organization for optimized post-migration workflows.
• Collaborate with development teams to determine migration points and finalize migration strategies.
• Troubleshoot issues related to file sizes, Python compatibility, network connectivity, or permissions during migration.

Required Qualifications:

• Strong knowledge of Git/GitHub and preferably Perforce (Helix Core) — understanding of differences, workflows, and integrations.
• Hands-on experience with P4-Fusion.
• Familiarity with cloud platforms (AWS, Azure) and containerization technologies (Docker, Kubernetes).
• Proficiency in migration tools such as git-p4 fusion — installation, configuration, and troubleshooting.
• Ability to identify and manage large files using Git LFS to meet GitHub repository size limits.
• Strong scripting skills in Python and Shell for automating migration and restructuring tasks.
• Experience in planning and executing source control migrations — defining scope, branch mapping, history retention, and permission translation.
• Familiarity with CI/CD pipeline integration to validate workflows post-migration.
• Understanding of source code management (SCM) best practices, including version history and repository organization in GitHub.
• Excellent communication and collaboration skills for cross-team coordination and migration planning.
• Proven practical experience in repository migration, large file management, and history preservation during Perforce to GitHub transitions.

Skills: Github, Kubernetes, Perforce, Perforce (Helix Core), Devops Tools

Must-Haves

Git/GitHub (advanced), Perforce (Helix Core) (advanced), Python/Shell scripting (strong), P4-Fusion (hands-on experience), Git LFS (proficient)

Why this role exists

Our infrastructure footprint is growing faster than our headcount, and we believe most of that

gap should be closed by automation and AI agents — not by hiring more humans to do toil. We

need someone early in their career who treats manual work as a bug, ships scripts and agents

instead of tickets, and wants to grow into deeper ownership over the next two years.

You will not be the most senior person on the team. You will be the one who multiplies the team.

What you'll own

In your first 1 months

• Take ownership of one slice of our CI/CD pipeline and make it measurably

faster, more reliable, or cheaper. We expect a number on a dashboard to move.

• Build at least three internal automations that replace manual ops toil —

using AI agents (Claude Code, agentic CLIs, scripted LLM workflows) as your force

multiplier.

• Be the first responder for a defined set of alerts. Write the runbooks. Drive

the alert volume down.

• Support senior engineers on AI/ML infrastructure (GPU nodes, inference

services, model deployment) — observe, document, and gradually take on contained

changes under review.

By 3 months you should be

• The go-to person for at least two production systems.

• Shipping routine infrastructure changes without needing senior review.

• Treating "manual" as a code smell.

Required (we will reject without these)

• 0–3 years hands-on experience with one major cloud (AWS, GCP, or

Azure — one is fine, depth beats breadth).

• Fluent in Linux command line, bash, and at least one scripting language

(Python or Go preferred).

• Have shipped something to production that real users hit. A side project

counts; a graded coursework lab does not.

• Comfortable with Docker — you can explain what an image vs. a

container is and why it matters.

• Working knowledge of networking fundamentals: DNS, HTTP/HTTPS,

TLS, ports, basic subnets — enough to debug "it works on my machine."

• Git fluency: branches, merges, rebases, conflict resolution.

• CI/CD pipelines — you have authored or substantially modified pipelines

in GitHub Actions, GitLab CI, ArgoCD, Jenkins, or similar. Not just "I clicked Re-run."

• Kubernetes basics — kubectl for real work, can read pod logs,

understand deployments and services, can debug a CrashLoopBackOff without

panicking. You do not need to have run a cluster; you do need to have lived inside one.

• Active user of AI coding agents (Claude Code, Cursor, Copilot, agentic

CLIs, etc.). You should be able to walk us through specific tasks where they made you

faster, and specific tasks where they failed you and how you noticed. "I have tried it" is

not enough.

Bonus (real plus, not required)

• Infrastructure as Code: Terraform, Pulumi, or Ansible.

• Observability: Prometheus/Grafana, Datadog, OpenTelemetry, any APM.

• Have built or extended an LLM-based agent — a custom MCP server, a

scripted multi-step workflow, an internal tool that calls models in a loop. Anything beyond

chat-with-Claude.

• Exposure to GPU workloads, model serving (vLLM, Triton, TGI, etc.), or

ML pipelines.

What we don't care about

• Whether your degree is in CS — or whether you have a degree at all.

• Brand-name companies on your resume.

• Certifications. They are fine. They do not substitute for having shipped.

How we work

• We default to automation. If you do something manually twice, the third

time you script it or hand it to an agent.

• AI agents are part of the workflow, not a novelty. Expect interview

questions about exactly how you use them — and where you have caught them being

wrong.

• Small, reversible changes beat big-bang rollouts.

• Postmortems are blameless and written down.

• We push back on each other. If you only execute, you will be unhappy

here.

How to apply

Send:

• Your resume.

• A short note (≤200 words) describing one infra or automation problem you

solved, and how AI agents factored in — or did not, and why. We read these. Generic

notes get rejected.

Internal note — delete before posting externally

• Comp band, location policy, team name, and reporting line marked

[CONFIRM] need to be filled in before this goes external.

• The Required list is intentionally tight: CI/CD and Kubernetes basics

promoted from bonus. Expect this to filter ~80% of typical junior DevOps applicants. The

remaining pool will skew toward people who have actually shipped infra at a startup, not

bootcamp grads or pure cloud-cert holders.

• IaC, observability, agent-building, and GPU/ML serving stay as bonus.

Promoting any of these to required at 0–3 yrs collapses the pool to near-zero or forces

hiring senior people at junior comp. If you want IaC required, re-level this to mid (3–5

yrs) and raise the band.

• Screening implication: the resume screen should explicitly check for

CI/CD pipeline authorship and any K8s-touching production work. If neither is on the

resume, reject at screen. Do not waste interview slots.

• Pipeline watch: if fewer than ~15 qualified resumes after 2 weeks of

active sourcing, the first thing to relax is the AI-agent-fluency bar (move to bonus and

screen for it in interview instead). Do not relax the "shipped to production" requirement

— that is the load-bearing filter.

Wissen Technology is hiring for Devops engineer

Required:

-4 to 10 years of relevant experience in Devops

-Must have hands on experience on AWS, Kubernetes, CI/CD pipeline

-Good to have exposure on Github or Gitlab

-Open to work from hashtag Chennai

-Work mode will be Hybrid

Company profile:

Company Name : Wissen Technology

Group of companies in India : Wissen Technology & Wissen Infotech

Work Location - Chennai

Website : www.wissen.com

Wissen Thought leadership : https://lnkd.in/gvH6VBaU

LinkedIn: https://lnkd.in/gnK-vXjF

Hiring for the below position with one of our premium client

Role: Senior DevOps Engineer

Exp:7+ years

Location: Chennai

Key skills: DevOps, Cloud, Python scripting

Description:

 Strong analytical and problem-solving skills 

Ability to work independently, learn quickly and be proactive

 7-9 years overall and at least 3-4 years of hands-on experience in designing and managing DevOps Cloud infrastructure

 Experience must include a combination of:

o Experience working with configuration management tools – Ansible, Chef, Puppet, SaltStack (expertise in at least one tool is a must)

o Ability to write and maintain code in at least one scripting language (Python preferred)

o Practical knowledge of shell scripting

o Cloud knowledge – AWS, VMware vSphere

o Good understanding and familiarity with Linux o Networking knowledge – Firewalls, VPNs, Load Balancers o Web/Application servers, Nginx, JVM environments

o Virtualization and containers - Xen, KVM, Qemu, Docker, Kubernetes, etc.

o Familiarity with logging systems - Logstash, Elasticsearch, Kibana o Git, Jenkins, Jira 

If interested kindly apply!

DevOps Lead Engineer

We are seeking a skilled DevOps Lead Engineer with 8 to 10 yrs. of experience who handles the entire DevOps lifecycle and is accountable for the implementation of the process. A DevOps Lead Engineer is liable for automating all the manual tasks for developing and deploying code and data to implement continuous deployment and continuous integration frameworks. They are also held responsible for maintaining high availability of production and non-production work environments.

Essential Requirements (must have):

• Bachelor's degree preferable in Engineering.

• Solid 5+ experience with AWS, DevOps, and related technologies

Skills Required:

Cloud Performance Engineering

• Performance scaling in a Micro-Services environment

• Horizontal scaling architecture

• Containerization (such as Dockers) & Deployment

• Container Orchestration (such as Kubernetes) & Scaling

DevOps Automation

• End to end release automation.

• Solid Experience in DevOps tools like GIT, Jenkins, Docker, Kubernetes, Terraform, Ansible, CFN etc.

• Solid experience in Infra Automation (Infrastructure as Code), Deployment, and Implementation.

• Candidates must possess experience in using Linux, Jenkins, and ample experience in Configuring and automating the monitoring tools.

• Strong scripting knowledge

• Strong analytical and problem-solving skills.

• Cloud and On-prem deployments

Infrastructure Design & Provisioning

• Infra provisioning.

• Infrastructure Sizing

• Infra Cost Optimization

• Infra security

• Infra monitoring & site reliability.

Job Responsibilities:

• Responsible for creating software deployment strategies that are essential for the successful

deployment of software in the work environment and provide stable environment for delivery of

quality.

• The DevOps Lead Engineer is accountable for designing, building, configuring, and optimizing

automation systems that help to execute business web and data infrastructure platforms.

• The DevOps Lead Engineer is involved in creating technology infrastructure, automation tools,

and maintaining configuration management.

• The Lead DevOps Engineer oversees and leads the activities of the DevOps team. They are

accountable for conducting training sessions for the juniors in the team, mentoring, career

support. They are also answerable for the architecture and technical leadership of the complete

DevOps infrastructure.

Experience: 3+ years of experience in Cloud Architecture

About Company:

Cloud Architect / Lead

• Role Overview

• Senior Engineer with a strong background and experience in cloud related technologies and architectures. Can design target cloud architectures to transform existing architectures together with the in-house team. Can actively hands-on configure and build cloud architectures and guide others.

• Key Knowledge

• 3-5+ years of experience in AWS/GCP or Azure technologies
• Is likely certified on one or more of the major cloud platforms
• Strong experience from hands-on work with technologies such as Terraform, K8S, Docker and orchestration of containers.
• Ability to guide and lead internal agile teams on cloud technology
• Background from the financial services industry or similar critical operational experience

DevOps Engineer

Job Description:

The position requires a broad set of technical and interpersonal skills that includes deployment technologies, monitoring and scripting from networking to infrastructure. Well versed in troubleshooting Prod issues and should be able to drive till the RCA.

Skills:

• Manage VMs across multiple datacenters and AWS to support dev/test and production workloads.
• Strong hands-on over Ansible is preferred
• Strong knowledge and hands-on experience in Kubernetes Architecture and administration.
• Should have core knowledge in Linux and System operations.
• Proactively and reactively resolve incidents as escalated from monitoring solutions and end users.
• Conduct and automate audits for network and systems infrastructure.
• Do software deployments, per documented processes, with no impact to customers.
• Follow existing devops processes while having flexibility to create and tweak processes to gain efficiency.
• Troubleshoot connectivity problems across network, systems or applications.
• Follow security guidelines, both policy and technical to protect our customers.
• Ability to automate recurring tasks to increase velocity and quality.
• Should have worked on any one of the Database (Postgres/Mongo/Cockroach/Cassandra)
• Should have knowledge and hands-on experience in managing ELK clusters.
• Scripting Knowledge in Shell/Python is added advantage.
• Hands-on Experience over K8s based Microservice Architecture is added advantage.

Job Dsecription:

○ Develop best practices for team and also responsible for the architecture

○ solutions and documentation operations in order to meet the engineering departments quality and standards

○ Participate in production outage and handle complex issues and works towards Resolution

○ Develop custom tools and integration with existing tools to increase engineering Productivity

Required Experience and Expertise

○ Having a good knowledge of Terraform + someone who has worked on large TF code bases.

○ Deep understanding of Terraform with best practices & writing TF modules.

○ Hands-on experience of GCP  and AWS and knowledge on AWS Services like VPC and VPC related services like (route tables, vpc endpoints, privatelinks) EKS, S3, IAM. Cost aware mindset towards Cloud services.

○ Deep understanding of Kernel, Networking and OS fundamentals

NOTICE PERIOD - Max - 30 days