Teradata ETL Developer

Must Have Technical/Functional Skills

• 4-8 years hand on Experience on writing Teradata.
• Experience in Teradata Utilities (BTEQ,Fast Load, Multi Load)
• Extensive experience in developing complex SQL code using Teradata stored procedures, macros etc. 
• Should be good in Unix Shell scripting
• Should be able to create Design documents , mapping documents 
• Design and document development standards
• Should have knowledge on ETL and Data warehouse Concepts
• Should have knowledge of SQL Server and Autosys.

Roles & Responsibilities

• Collaborate with stakeholders to understand the current process 
• Collaborate with business to convert the business requirement into Technical requirements.
• Develop Teradata code meeting 100 percent of technical specifications and business requirements according to the established design patterns
• Analyze, design, code, and test highly complex ETL processes, for data warehouses and/or operational data stores
• Understand design for ETL application including data sources, data targets, data definitions, data relationships, and business rules
• Work closely with technical leads, analysts, data modelers and other developers to understand project requirements and contribute to the project solution
• Provide post go-live & application maintenance support
• Provide technical expertise on Database design, Data modeling, Data Warehousing, and Data integration
• Create solutions for large and complex data driven applications
• Reconciliation and test cases of developed solutions
• Design, develop and support application solutions leveraging Teradata and Teradata Tools and Utilities
• Prepare Test cases for Unit Testing/SIT/Regression
• Should be able to take ownership and deliver independently Report out to stakeholders highlighting achievements, risks, and future work. 
• Follow the Agile standard for the development of the requested proposal. 
• Bring best practices, standards, and innovative ideas for architecture, and design.
• Deployment of data ingestion pipelines into dev, pre, and production environments.
• Unit testing, integration testing, functional, and non-functional testing.