The client has transitioned to the AWS Cloud. As a result, the data generated by various teams now lands in different AWS services like S3 Buckets, EC2 Instances, Redshift, etc., rather than legacy environments.
This shift has impacted how end users access and interact with data. The selected individual will play a key role in helping end users retrieve and interact with their data, ensuring a seamless, user-friendly experience.
Act as a technical enabler for end users, supporting data access and environment navigation within AWS.
Build user-friendly interfaces and workflows that simplify data access from sources such as S3, EC2, and Redshift.
Design and implement automated solutions to:
Provide secure access to environments and data
Move and transform data as needed
Automate post-processing tasks triggered by incoming data
Collaborate with Data Analysts, Data Scientists, and other stakeholders to understand their workflows and provide customized solutions.
Enhance overall environment usability with a focus on efficiency, automation, and reliability.
Provide support in reporting and data visualization needs as required by end users.
Strong hands-on experience in Python development (mandatory).
Deep expertise in AWS Data Services, including but not limited to:
S3, EC2, Lambda, EMR, Redshift, ECS
Familiarity with tools and platforms such as:
SageMaker
Jupyter Notebook
Domino
SQL
Experience building automation pipelines and improving post-processing workflows in a cloud environment.
Proven ability to create end-user-centric solutions in a cloud-first ecosystem.
Excellent problem-solving skills with a consultative and solutions-driven approach.
Familiarity with the R programming language
This is a client-facing position. Strong communication and collaboration skills are essential.
Candidate must be currently local to the DC/VA area and comfortable working 4 days onsite.
This is a long-term opportunity with potential for extension.
Senior and Not Actually a Developer or Tester –
The client has moved to AWS Cloud, and now, their end users (the Data Analysts and Data Scientists, etc.) have their output landing in different places than they are used to — i.e., S3 Buckets, EC2, etc.
So this has changed how the end users need to work – they now have to go to S3 Buckets to get their data or perhaps EC2 machines, etc., as this is where the data now “lands.”
This role is to help these end users “get to the data” – and/or into the environment so they can access their own data
Any Gradute