Devops engineer AWS
Budget: ₹37,500 – ₹75,000 INR
Must be available US timing
This is for an internal AWS cloud security tool
If someone creates a resource in an AWS account it will react
They need to make sure that all of their AWS assets are tagged with the proper naming convention
This helps them with security & with costs
They need to be extremely strong with Python
Must have AWS development experience
The application is serverless & uses Lambdas
AWS events is key to know, tagging assets
They use Docker containers so Jenkins is important for them to know as well
If they have a security background it is a plus but not a must
They must have REST API experience either consuming or building
GitHub experience is a must & critical
They have a small team & will be working with 1-2 Engineers
The resource will be working very independently
They need to be autonomous & there will not be any hand holding
They need someone with 5+ years of Python, & 3+years of AWS development experience
Having experience doing unit or integration testing
Experience with creating AWS assets or deleting
The environment is Agile so experience working in that type of environment is a plus
There is no front end experience required at all
CI/CD, Jenkins Files, Terraform (used to provision AWS environment) experience is a must
Daily team meetings that they will attend & contribute to
The code already exists & there is architecture in place already so they will be fitting all times into the current model
Remote is fine for the resource
Strong documentation is an absolute must
They will document how the code looks & is structure Data Engineer AWS
3 months could go longer
This is for an internal AWS cloud security tool
If someone creates a resource in an AWS account it will react
They need to make sure that all of their AWS assets are tagged with the proper naming convention
This helps them with security & with costs
They need to be extremely strong with Python
Must have AWS development experience
The application is serverless & uses Lambdas
AWS events is key to know, tagging assets
They use Docker containers so Jenkins is important for them to know as well
If they have a security background it is a plus but not a must
They must have REST API experience either consuming or building
GitHub experience is a must & critical
They have a small team & will be working with 1-2 Engineers
The resource will be working very independently
They need to be autonomous & there will not be any hand holding
They need someone with 5+ years of Python, & 3+years of AWS development experience
Having experience doing unit or integration testing
Experience with creating AWS assets or deleting
The environment is Agile so experience working in that type of environment is a plus
There is no front end experience required at all
CI/CD, Jenkins Files, Terraform (used to provision AWS environment) experience is a must
Daily team meetings that they will attend & contribute to
The code already exists & there is architecture in place already so they will be fitting all times into the current model
Remote is fine for the resource
Strong documentation is an absolute must
They will document how the code looks & is structure
This is for an internal AWS cloud security tool
If someone creates a resource in an AWS account it will react
They need to make sure that all of their AWS assets are tagged with the proper naming convention
This helps them with security & with costs
They need to be extremely strong with Python
Must have AWS development experience
The application is serverless & uses Lambdas
AWS events is key to know, tagging assets
They use Docker containers so Jenkins is important for them to know as well
If they have a security background it is a plus but not a must
They must have REST API experience either consuming or building
GitHub experience is a must & critical
They have a small team & will be working with 1-2 Engineers
The resource will be working very independently
They need to be autonomous & there will not be any hand holding
They need someone with 5+ years of Python, & 3+years of AWS development experience
Having experience doing unit or integration testing
Experience with creating AWS assets or deleting
The environment is Agile so experience working in that type of environment is a plus
There is no front end experience required at all
CI/CD, Jenkins Files, Terraform (used to provision AWS environment) experience is a must
Daily team meetings that they will attend & contribute to
The code already exists & there is architecture in place already so they will be fitting all times into the current model
Remote is fine for the resource
Strong documentation is an absolute must
They will document how the code looks & is structure Data Engineer AWS
3 months could go longer
This is for an internal AWS cloud security tool
If someone creates a resource in an AWS account it will react
They need to make sure that all of their AWS assets are tagged with the proper naming convention
This helps them with security & with costs
They need to be extremely strong with Python
Must have AWS development experience
The application is serverless & uses Lambdas
AWS events is key to know, tagging assets
They use Docker containers so Jenkins is important for them to know as well
If they have a security background it is a plus but not a must
They must have REST API experience either consuming or building
GitHub experience is a must & critical
They have a small team & will be working with 1-2 Engineers
The resource will be working very independently
They need to be autonomous & there will not be any hand holding
They need someone with 5+ years of Python, & 3+years of AWS development experience
Having experience doing unit or integration testing
Experience with creating AWS assets or deleting
The environment is Agile so experience working in that type of environment is a plus
There is no front end experience required at all
CI/CD, Jenkins Files, Terraform (used to provision AWS environment) experience is a must
Daily team meetings that they will attend & contribute to
The code already exists & there is architecture in place already so they will be fitting all times into the current model
Remote is fine for the resource
Strong documentation is an absolute must
They will document how the code looks & is structure