Job Description
Project Notes:
(streaming, ingestion, ETL/ELT, API connections, testing).
Cloud Developer Experience 1. In-depth knowledge of AWS IaaS and PaaS services2. Well versed with Cloud design patterns 3. Designing and developing automation tools and infrastructure to run service-oriented Stacks on an internal data center, Public & Private clouds4. Experience in a large scale Cloud (Private and or Public) environments and SaaS, PaaS, IaaS, pattern development by using AWS5. Well versed in leveraging following some or more AWS services: Amazon EC2, Amazon S3, Kinesis, Lambda, Aurora, Dynamo DB, API Gateway, SQS, CloudFormation6. AWS network EXperience, VPN and Express Route, DNS and Load Balancers7. Strong Experience in developing Terraform templates and Modules8. Responsible for systems and application performance monitoring9. Ability to design data storage, movement, orchestration solutions on AWS10. Design, co-ordinate and execute proof of concepts, guidance on business scenarios and deployment guidance11.Knowledge in infrastructure automation, build automation and deployment automation12.Experience in SCRUM Methodology for Agile DevelopmentThese three initiatives will be completed in unison to take a proof of concept to a full AWS Serverless pipeline product
1. High Availability for Ordering and Activation
· Records come in different files. Deliver by wireless carriers. Have to process files as soon as possible. Count them, push calls from London to the US, etc. Doing this with systems. BASH processing, not scaling.
· Receiving data every 5-15 mins. Speed is not the issue but when they receive data. Mostly about the volume, have 15-20 mins to process this volume of data.
· Requires AWS using Kinesis streaming, AWS Dynamo & Aurora database, CloudFormation w/ MySQL, be able to build lambda functions (causes processes to happen).
· Not complicated project. There\'s a proof of concept. Need to take this and build a product, can be configurable and deployed easily.
2. Usage Processing Platform
· Everything said above applies.
· One project to create the \"provisioning gateway\"—where applications connect to the AWS data pipeline-- have version 2 already in place. Has some shortcomings in the best use of AWS services and architecture. Lots of lambda, projects, services working together to achieve an objective. Not properly deployed. Lots of architecture there.
· Candidates with stronger experience API Gateway & Lambda experience will fit well here.
3. Load Test Environment & Automation Tools
· Developer will be tasked with building this a production breaker/fix environment with direction from the Test Lead & Architect. This is becoming an industry “best practice” in order to scale products for multi-customer use. Take the two initiatives above & what they’re building, build a clone of that for internal use and testing. They can spin up the environment no problem. But want to copy data from production to this environment and mask it. Goal- to build an environment where very quickly they can run a script and have data reset to a known state. Then they can run their system.
· Leveraging following some or more AWS Services: Amazon EC2, Amazon S3, Kinesis, Lambda, Aurora, Dynamo DB, API Gateway, SQS, CloudFormation
· Candidates that have partnered closely with a testing team before will have an edge.