Jump to content

Engineering & Information Technology: Difference between revisions

From ICANNWiki
Jessica (talk | contribs)
Created page with "* Lead Infrastructure Engineer - DNS * Sr. Lead Infrastructure Engineer - DNS * Sr. Infrastructure Engineer - Network * Technical Engagement Specialist * VP, Technical Engagem..."
 
Dankojev (talk | contribs)
Ash to Andre Abed (no link)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
ICANN's '''Engineering & Information Technology''' ('''E&IT''') department is the foundational "service provider" for ICANN. The E&IT team uses an integrative, collaborative process to gather demands for systems and prioritize work. Twice a year, senior leaders in ICANN org evaluate their respective function's current and future E&IT-related project demands. Projects include optimizing computer, network, and storage infrastructure, custom-coding fit-for-purpose software systems, and optimizing the infrastructure for such systems.<ref>[https://www.icann.org/en/blogs/details/a-peek-into-the-icann-org-engineering-factory-and-an-update-on-czds-5-11-2020-en A peek into ICANN Org's Engineering "Factory," ICANN Blogs]</ref>
==Frozen Delivery Pipeline Process==
The list of IT demands is managed via the following process. Feedback is gathered from each team, project proposals are aligned with ICANN's strategies, and cross-functional dependencies and impacts and community input are considered to prioritize requests. This process leads to a priority list of E&IT demands for each function within ICANN org. The projects are considered in light of community-reviewed and ICANN Board-approved budgets and the E&IT department’s capacity for each upcoming semester (January-June or July-December). The resulting list is called the “Frozen Delivery Pipeline,” which is then reviewed and approved by ICANN Senior Vice Presidents and the ICANN CEO.
==E&IT Workstreams==
The E&IT department has seven workstreams:
# Community Engagement: supporting [[Engagement]] with the ICANN community.
# Community Collaboration: working on tools and websites used by ICANN org, [[SO]]s, and [[AC]]s, such as the [[Information Transparency Initiative]] (ITI).
# Contracted Parties: supporting transactional work with [[registries]] and [[registrars]]
# Technical Services: the systems used by ICANN org and/or community to ensure contracted parties meet contractual obligations, such as [[Service Level Agreement Monitoring]] (SLAM), Zone File Access, and [[CZDS]]
# IANA Services: systems for performing the IANA functions, including root zone management.
# [[:Category:ICANN Staff|Staff]] Services: for the ICANN org, including Enterprise Resource Planning (ERP) functions for [[HR]] and [[Finance]], Intranet, email, and phone systems
# IT Infrastructure: systems and services such as Zoom, data centers, cloud, information security, and ICANN Managed Root Servers ([[IMRS]]).
==E&IT Roles==
* SVP, Engineering and Chief Information Officer (CIO): Andre Abed
* Lead Infrastructure Engineer - DNS
* Lead Infrastructure Engineer - DNS
* Sr. Lead Infrastructure Engineer - DNS
* Sr. Lead Infrastructure Engineer - DNS
* Sr. Infrastructure Engineer - Network
* Sr. Infrastructure Engineer - Network
* Infrastructure Architect
* Sr. Lead Infrastructure Engineer – Architecture
* Senior Infrastructure Engineer 2
* Infrastructure Engineer<br/>
* Technical Engagement Specialist
* Technical Engagement Specialist
* VP, Technical Engagement
* VP, Technical Engagement
* Technical Engagement Manager
* Regional Technical Engagement Manager<br/>
* Technical Services Director
* Technical Services Director
* Director, Technical Services
* Director, Technical Services
* Technical Engagement Manager
* Regional Technical Engagement Manager
* Senior Director, GDS Technical Services
* Senior Director, GDS Technical Services
* Technical Services Senior Manager* Technical Services Senior Manager<br/>
* Sr Technical Lead- Software Engineering
* Sr Technical Lead- Software Engineering
* Technical Services Senior Manager
* Technical Lead, Software Engineering
* Technical Lead, Software Engineering
* Technical Services Senior Manager
* SVP, Engineering and Chief Information Officer (CIO)
* Infrastructure Architect
* Principal Software Architect
* Principal Software Architect
* Sr. Lead Infrastructure Engineer – Architecture
* Senior Infrastructure Engineer 2
* Salesforce Engineer 2- Salesforce
* Software Engineer 2 - Salesforce
* Manager, Salesforce Solutions
* Senior Developer - Python
* Sr. Software Engineer 1
* Sr. Software Engineer 1
* VP, Software Engineering
* VP, Software Engineering
* Staff Software Engineer, QA Automation
* Staff Software Engineer, QA Automation
* Staff Software Engineer - Platforms
* Staff Software Engineer - Platforms
* Software Engineer 2 - Salesforce
* Software Engineer 1, Platform
* Software Engineer 1, Platform
* Sr. Software Engineer 1, QA
* Sr. Software Engineer 1, QA
* Sr. Lead Software Engineer, QA
* Sr. Lead Software Engineer, QA
* Software Engineer 2
* Technical Lead, Software Engineering<br/>
* Salesforce Engineer 2- Salesforce
* Manager, Salesforce Solutions
* Senior Developer - Python
* Senior Localization Program Manager
* Senior Localization Program Manager
* Senior Java Developer
* Senior Java Developer
* Technical Lead, Software Engineering
* VP, Engineering - Stakeholder Community Solutions Delivery
* VP, Engineering - Stakeholder Community Solutions Delivery
* IT Business Analytics and Intranet Services Senior Manager
* IT Business Analytics and Intranet Services Senior Manager
* Protocol Parameters Sr. Manager
* Protocol Parameters Sr. Manager
* Director, IROS Operations
* Director, IROS Operations
* SVP and Chief Technology Officer (CTO)
* Senior Director, Cloud/DC and MTS Operations
* Senior Director, Cloud/DC and MTS Operations
* Software Engineer 2
* Infrastructure Engineer
* IT PMO Associate Project Manager
* IT PMO Associate Project Manager
* Senior Cryptographic Key Manager
* Senior Cryptographic Key Manager
* Cryptographic Key Manager
* Cryptographic Key Manager
==References==
[[Category:ICANN Organization]]

Latest revision as of 16:27, 16 October 2024

ICANN's Engineering & Information Technology (E&IT) department is the foundational "service provider" for ICANN. The E&IT team uses an integrative, collaborative process to gather demands for systems and prioritize work. Twice a year, senior leaders in ICANN org evaluate their respective function's current and future E&IT-related project demands. Projects include optimizing computer, network, and storage infrastructure, custom-coding fit-for-purpose software systems, and optimizing the infrastructure for such systems.[1]

Frozen Delivery Pipeline Process[edit | edit source]

The list of IT demands is managed via the following process. Feedback is gathered from each team, project proposals are aligned with ICANN's strategies, and cross-functional dependencies and impacts and community input are considered to prioritize requests. This process leads to a priority list of E&IT demands for each function within ICANN org. The projects are considered in light of community-reviewed and ICANN Board-approved budgets and the E&IT department’s capacity for each upcoming semester (January-June or July-December). The resulting list is called the “Frozen Delivery Pipeline,” which is then reviewed and approved by ICANN Senior Vice Presidents and the ICANN CEO.

E&IT Workstreams[edit | edit source]

The E&IT department has seven workstreams:

  1. Community Engagement: supporting Engagement with the ICANN community.
  2. Community Collaboration: working on tools and websites used by ICANN org, SOs, and ACs, such as the Information Transparency Initiative (ITI).
  3. Contracted Parties: supporting transactional work with registries and registrars
  4. Technical Services: the systems used by ICANN org and/or community to ensure contracted parties meet contractual obligations, such as Service Level Agreement Monitoring (SLAM), Zone File Access, and CZDS
  5. IANA Services: systems for performing the IANA functions, including root zone management.
  6. Staff Services: for the ICANN org, including Enterprise Resource Planning (ERP) functions for HR and Finance, Intranet, email, and phone systems
  7. IT Infrastructure: systems and services such as Zoom, data centers, cloud, information security, and ICANN Managed Root Servers (IMRS).

E&IT Roles[edit | edit source]

  • SVP, Engineering and Chief Information Officer (CIO): Andre Abed
  • Lead Infrastructure Engineer - DNS
  • Sr. Lead Infrastructure Engineer - DNS
  • Sr. Infrastructure Engineer - Network
  • Infrastructure Architect
  • Sr. Lead Infrastructure Engineer – Architecture
  • Senior Infrastructure Engineer 2
  • Infrastructure Engineer
  • Technical Engagement Specialist
  • VP, Technical Engagement
  • Technical Engagement Manager
  • Regional Technical Engagement Manager
  • Technical Services Director
  • Director, Technical Services
  • Senior Director, GDS Technical Services
  • Technical Services Senior Manager* Technical Services Senior Manager
  • Sr Technical Lead- Software Engineering
  • Technical Lead, Software Engineering
  • Principal Software Architect
  • Sr. Software Engineer 1
  • VP, Software Engineering
  • Staff Software Engineer, QA Automation
  • Staff Software Engineer - Platforms
  • Software Engineer 2 - Salesforce
  • Software Engineer 1, Platform
  • Sr. Software Engineer 1, QA
  • Sr. Lead Software Engineer, QA
  • Software Engineer 2
  • Technical Lead, Software Engineering
  • Salesforce Engineer 2- Salesforce
  • Manager, Salesforce Solutions
  • Senior Developer - Python
  • Senior Localization Program Manager
  • Senior Java Developer
  • VP, Engineering - Stakeholder Community Solutions Delivery
  • IT Business Analytics and Intranet Services Senior Manager
  • Protocol Parameters Sr. Manager
  • Director, IROS Operations
  • Senior Director, Cloud/DC and MTS Operations
  • IT PMO Associate Project Manager
  • Senior Cryptographic Key Manager
  • Cryptographic Key Manager

References[edit | edit source]