Ruby Chef Developer
About the role
- Deploying applications globally, coordinating in controlled environments using Chef.
- Configuring SVN distributed platform for multiple applications and automating builds using Jenkins or other tools.
- Define a process for regulated SVN code control and builds.
- Creating branches to support parallel development.
- Responsible for Code control and resolving merge conflicts.
- Creating branches to support parallel development.
- Responsible for Code control and resolving merge conflicts.
- Develop all necessary Unix/build scripts required for deployment automation etc. Engage and schedule functional resources in support of deployment, implementation and verification.
- Acquire final approvals from QA and the LOB for application deployments.
- Responsible for SIT, UAT, Prod & COB environments.
- Coordinate overall deployments, create deployment documents, release plans and run books
- Troubleshooting application/middleware applications.
- -Requires 7-8 years of related experience in one or more of the following areas
- Release engineer role
- Test environment support
- Knowledge of SVN/sub version or other SCM tools
- Unix/shell/Perl/Phython scripting
- Middleware support [Web Sphere (preferably), web logic etc].Application build tools like ANT/Maven/Jenkins
- Relational databases like SQL/Oracle(preferred)
- Knowledge of file transfer mechanism (ConnectDirect, SCP, SFTP, etc..)Strong and proven ability to analyze and troubleshoot databases
- Good knowledge on issue/problem reporting or managing systems like JIRA etc. Advanced troubleshooting and deductive reasoning skillsAbility to converse in both technical and non-technical terms
- Ability to show experience managing multiple tasks simultaneously and successfully
- Experience working with geographically distributed and culturally diverse work-groups
- Excellent written and verbal communication skillsAbility to develop strong client relationships
- -Financial industry knowledge is plus.
- Experience with an Enterprise Batch Scheduling tool (Autosys)
- Good understanding on Site Minder/SSO/BIGIP/DNS/3DNS is plus
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
