Excellent Role for AWS Data Engineer @ Hanover NJ (Onsite Role)

0 views
Skip to first unread message

Divyansh Srivastava

unread,
Jul 15, 2026, 9:50:41 AM (8 days ago) Jul 15
to divy...@net2source.com

Title: AWS Data Engineer

Location: Hanover NJ

Duration: 12+ Months

Rate: $70/hr on c2c

 

Note: Don’t share any profile without Passport number.

 

Design and implement scalable data architectures using AWS services (S3, Redshift, Glue, Athena, EMR, DynamoDB).
Build, optimize, and maintain ETL/ELT pipelines for structured and unstructured data.
Develop real‑time and batch ingestion pipelines using AWS Glue, Lambda, Kinesis, or Kafka.
Data Processing & Transformation
Utilize Spark (AWS EMR/Glue), Python, or Scala to build transformation workflows.
Implement data quality checks, validation rules, and automated error‑handling mechanisms.
Ensure data is optimized for analytics, BI, and ML use cases.
Data Warehouse & Lakehouse Management
Build and maintain data lakes on Amazon S3 and data warehouses on Redshift/Snowflake.
Create and optimize database schemas, partitioning, compression, and performance tuning.
Manage metadata, cataloging, and data lineage via AWS Glue Data Catalog or similar tools.
DevOps & Automation
Implement CI/CD pipelines for data workflows using CodePipeline, CodeBuild, GitHub Actions, or Jenkins.
Use Infrastructure‑as‑Code (IaC) tools like CloudFormation or Terraform to automate provisioning.
Monitor pipelines and infrastructure using CloudWatch, CloudTrail, and AWS Config.
Security, Compliance & Governance
Apply AWS security best practices including IAM roles, KMS encryption, VPC networking, and Secrets Manager.
Maintain compliance with organizational data governance and regulatory standards.
Ensure data privacy, retention policies, and audit requirements are met.
Collaboration & Stakeholder Management
Partner with data scientists, analysts, and business teams to understand data requirements.
Provide technical guidance on AWS data capabilities and architectural best practices.
Troubleshoot pipeline failures, performance bottlenecks, and data quality issues.

 

Regards

Divyansh 

Reply all
Reply to author
Forward
0 new messages