Cloud Data Developer
united itIselin (NJ)
About the role
Cloud Data Developer
Location: Iselin, NJ (Hybrid)
Key Responsibilities:
Design and implement scalable data pipelines using Azure Databricks and Scala.
Develop and optimize queries and data models in PostgreSQL and Elasticsearch.
Collaborate with DevOps teams to build and maintain CI/CD pipelines for data applications.
Monitor and troubleshoot data workflows and cloud infrastructure.
Work closely with data scientists, analysts, and other developers to deliver high-quality data solutions.
Ensure data security, compliance, and best practices in cloud environments.
Monitor and optimize application performance, reliability, and cost.
Write clean, maintainable, and well-tested code following best practices.
Troubleshoot and resolve issues across development, test, and production environments.
Participate in agile ceremonies such as sprint planning, stand-ups, and retrospectives.
Contribute to code reviews, knowledge sharing, and mentoring of junior developers.
Communicate effectively across teams to align on project goals, timelines, and deliverables.
Foster a collaborative team environment by promoting open communication and continuous improvement.
Required
Skills & Qualifications:
Strong experience with Microsoft Azure services (e.g., Data Lake, Azure Functions, Azure DevOps).Proficiency in Databricks and Apache Spark.
Solid understanding of Elasticsearch for search and analytics.
Experience with PostgreSQL database design and optimization.
Proficient in Scala programming language.
Hands-on experience with CI/CD tools (e.g., Azure DevOps, GitLab, GitHub).Experience with containerization tools like Docker and orchestration with Kubernetes.
Familiarity with Agile development methodologies.
Excellent communication and teamwork skills.
Preferred Qualifications:
Knowledge of data governance and security best practices.
Certifications in Azure or related technologies. Experience in designing data models and managing data pipelines at scale.
Exposure to machine learning pipelines or data science workflows.
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.