Skip to main content

Big Data Engineer

Posted yesterday

next level business servicesPhoenix (AZ)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Implementation of various solutions arising out of the large data processing (GB's/ PB's) over various NoSQL, Hadoop, and MPP-based products Expertise on Java/ J2EE and should still be hands on Implemented and in-depth knowledge of various Java/ J2EE/ EAI patterns by using Open Source products Should have experience/knowledge on working with batch processing/ real-time systems using various Open Source technologies like Solr, Hadoop, NoSQL DB's, Storm, Kafka, etc. Active participation in the various Architecture and design calls with Big Data customers Working with Sr. Architects and providing implementation details to offshore Conducting sessions/ writing whitepapers/ Case Studies pertaining to Big Data Responsible for timely and quality deliveries Fulfill organization responsibilities – Sharing knowledge and experience within the other groups in the organization, conducting various technical sessions and trainings Additional Information All your information will be kept confidential according to EEO guidelines.

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.

More like this