Data Architect Lead

Role: Data Architect Lead

Duration: 12 months

Location: All 5 Tech Hubs
Pittsburgh, PA.
Cleveland, OH.
Dallas, TX.
Birmingham, AL.
Phoenix, AZ.

Summary: The main function is to set standards and coordinate changes to computer databases, test, and implement the database applying knowledge of database management systems. The typical database architect is involved in both improving the reliability and performance of a database along with planning and implementing future improvements to database architecture.

Job Responsibilities:
Test programs or databases, correct errors and make necessary modifications
Write technical documentation of improvements made to system technologies
Troubleshoot various database system errors
Implement new database technologies and security solutions

Responsible for building a highly available and scalable database model that will service as the backend to payment processing as well as refactoring.

Level 4: 6 years

Must Have Technical Skills:
MySQL
Oracle Database
Erwin Data Model Software
Data design for scale
Understand databases and how they interact and their capabilities

Flex Skills/Nice to Have:
N/A

Soft Skills:
Strong emphasis on extroverted personality - looking for an individual who wants to be involved in meetings, events, not afraid to speak up, drive down to the answers, needs an individual to participate
Communication
Organization
Driving out requirements - work with other team members
Education/Certifications:
Relevant work experience in lieu of education
Any Oracle Certs - not required, but nice to have

Database refactoring for enterprise scale
o Must be able to model the database effectively.
o Must be able to refactor the database without affecting current exposed processes (including implementing the data
model)
o Refactor for consistency and resiliency.
o Create and implement indexing, partitioning, and purge strategies.

Experience with Oracle Exadata is a plus.
o Including transaction guard

Experience with Golden Gate replication is a plus.

Feedback from interviews was that candidates were either heavily focused on reporting and less on the data modeling, focused on cloud work and seemed to only want to do designs and not the coding needed.