IOT architect

Hi, greetings of the day.

Please find the below Job description, and let me know your interest

Role: IOT architect

Location: Boston MA Day 1 On-site

Duration: 6 months

Client: Cigniti

Visa: Except OPT, CPT and H1 Transfers any visa is fine

C2C allowed.

• Assessment of AWS platform running IOT based payloads that is supporting 3.3 million users and identify technical debt in the current state.
• Understanding the current stateof the Platform and current Automation
  • Understand and document application architecture, technology landscape, current deployment cycle and activities performed.
  • Understand and document the current tooling set up and integration of various pipelines for in-scope application and publish a report on the same.
  • Review the code for quality, security, scale and stability for the in-scope applications.
  • Evaluate continuous delivery, monitoring, configuration management, security within DevOps pipelines and create a back log to implement continues delivery pipes using DevOps principles.
  • Review existing build and release process and understand the continuous testing set-up for both functional and non-functional testing.
  • Review test data and environment set-up process.
  • Review current tools and infrastructure set-up for DevOps and recommend improvements.
• Identify current Service Level Indicator (SLI) / Service Level Objectives (SLO)and measure the current availability and reliability.
  • Identify the metric to monitor to ensure appropriate reliability.
  • Define how to calculate the SLI for the metrices.
  • Set a target as the SLO to compare against during use.
  • Define steady state as a measurable output for normal behavior of the platform.
  • Build a hypothesis around steady state behavior to scale for supporting 2x growth to around 7.5 million user bases in next 2 years.
  • Need to identify availability 9s for the platform and draw a road map to achieve Shark Ninja target (99.99%)
• Risk Analysis of the current platform to understand the break point.
  • Introduce variables that reflect real world events for identification of risk points, breaking points due to increase load and define the point of failure.
  • Build resilience to scale.