Now that we have you interested, here is what we’re looking for:
· A passion for technology and solving interesting challenges.
· Proven problem solver and pragmatic thinker.
· Current knowledge of industry best practices
· At least 10 years of experience in a lead development or architecture role(s).
· At least 3 years of experience with public and/or private cloud
· Highly Skilled in one or more of the following (Java, NodeJS, Python, Bash)
· Experience with Terraform, Cloud-formation or Troposphere
· You consider yourself or have been told you are a T shaped for E shaped individual
· Have the ability to translate business requirements to end-to-end solutions.
· Collaborative mind, able to work with a team to delivery the strongest solution.
· Self-starter and takes ownership in the quality of work being delivered.
· Proven track record of High-Profile communication written and verbal
You have at least 5 years lead experience in 2 or more of the following areas:
· Data & Analytics – Industry expert in modern analytics practices and emerging technologies. Leveraging Spark, Hadoop, Airflow, Informatica, Map/Reduce, Algorithmia, MS/SQL, MySQL, NoSQL databases.
· Cloud Infrastructure – Deep understanding of cloud infrastructure and application architecture including but not limited to VPC, Networking, Security and isolation, routing, micro services, scalability, and cloud native architecture.
· Continuous Delivery & DevOps – experience in DevOps practices including infrastructure as code, configuration as code, release pipeline definition and deployment leveraging terraform, puppet, ansible, XL Release, git and artifactory.
· Web Applications
· Mobile Applications
· Integration – Integration patterns including SOA, message bus, web hooks, long and short-lived subscriptions. Leveraging technologies including SQS, SNS, Oracle Fusion, API Gateway and various file transfer protocols. Experience defining interfaces for software to hardware devices, integrating with hardware based protocols.
Principal Reference Architect – Day to Day Responsibilities:
The Principal Reference Architect will typically split their day to day responsibilities between four main areas: influencing, solutioning, coding and innovating. Below we have listed details about each area and roughly the percentage of time expected to be allocated to each area.
Influencing (20%): Working alongside other architects, lead engineers and delivery leaders to ensure they understand what the work is and how it needs to be developed. In this role you will often need to rely on your influence to get the work done as you defined, because it is often different from how individual teams would complete the same work.
· Assume a lead role in the Reference Architecture function in defining the technology standards and practices for global client use in the areas of Data Analytics, Integration and Web Application Architecture.
· Works closely with other Reference Architects, Domain & Solution Architects, and Platform Engineering to ensure strategy and execution alignment.
Solutioning (30%): Once you define the overall reference architecture you must often dive deep into the specifics of the solution being built to support the customer. By digging deep into the overall solution you will often uncover shortcomings of the reference architecture that should be updated and changed.
· Develop vision, strategy and execution in alignment with Domain roadmap demand plans for technology. Translating cross organizational demand into consistent and unified architectures delivered through reference architectures and reference implementations.
· Delivers technology solutions inclusive of on-premise through cloud and COTS to custom developed solutions and all combinations. Analyzing solution implications from multiple vectors including but limited to: cloud native design, resource planning, financial cost optimization, performance optimization, disaster recovery, high availability, global network performance and location impact.
· Creation and maintenance of Reference Architectures as required by business Domains and Platform teams.
· Review and access solution approach documents created by Domain and Solution architects ensuring best practices are followed.
Coding (30%): Many of our engineering teams are learning about our new reference architectures and implementations. The ability to work alongside other teams and help code solutions is important to our success and ability to influence those teams on the art of possible.
Innovating (20%): Keep in touch with the direction of architecture in the industry and a good pulse on what the enterprise is working on. Understanding that sometimes we need to drive a proof of concept to understand the art of what is possible.
· Ensures Client Technology keeps up with latest technology industry trends, product and solutions through research, meeting with industry partners.
· Create proofs of concept with new and disruptive technologies.
· Provide architectural guidance and direction for Technology Innovation Initiatives.
· Create Reference Architectures and Reference Implementations from proven disruptive technologies for scaled innovation.