TA-10080 REG: Preparing the Pacific Renewable Energy Investment Facility, Phase 3 - Product Leader / Chief Technology Officer (E-049450-038)

The consultant is responsible for technical leadership, hands-on delivery, and cross-team coordination across both platforms, through the beta launch and the post-beta refinement phase: • Hands-on architecture and development across the MRAP and APEDR codebases, including the APEDR mapfirst landing page and the core MRAP map frontend. • Ownership of the API contract, with review and merge authority over all repositories. • System-level integration accountability for the deployed system working end to end. • Ownership of RBAC, security add-ons, and the APEDR data repository structure. • Delivery of beta platform hosting and maintenance. • Coordination of the three separately-contracted team members (University of Edinburgh consultant, Senior Developer, Senior UI/UX Specialist) across staggered, potentially non-overlapping contract windows. • Leadership of the post-beta QA/QC and refinement phase (March–April), integrating user feedback and updates to the underlying model. Reference technology stack: The following baseline is established in the MRAP/APEDR concept work. Well-justified alternatives may be proposed subject to ADB approval, provided they remain open-source-first and integrate cleanly with the shared architecture. Detailed Tasks and/or Expected Output October 2026 – April 2027; beta launch end-February 2027, followed by QA/QC and refinement in March– April; inclusive of an approximately two-week reduction over the December holidays: A1- Solution architecture & API contract: Four-tier MRAP architecture, OpenAPI specification and configversion contract, repository scaffolding (mre-model, mrap-api, mrap-webapp, mrap-pipeline) and IaC skeleton. Establishes the technical foundation both platforms build against. A2- Platform Security: RBAC, security add-ons & data repository structure. Access-control model implemented against the agreed matrix, security hardening, and the APEDR data repository structure. Owned end to end by the Product Leader. A3- APEDR map-first landing + MRAP map frontend: Hands-on coding of the APEDR map-first landing page and the core MRAP map frontend (MapLibre GL JS tile rendering, selection tools, cartographic implementation), the STAC-to-CKAN metadata bridge and the seams between components. A4-Establishes and operates the technical governance of the MRAP and APEDR product family, evidenced by dated artefacts rather than continuous activity. The consultant chairs the weekly technical governance forum and maintains a written decision log; holds review and merge authority across all repositories; delivers hosting and maintenance; and coordinates the University of Edinburgh consultant, the Senior Developer and the Senior UI/UX Specialist across their staggered, potentially non-overlapping contract windows. A5 -System-level acceptance & beta launch: Named end-to-end user journeys completing on the deployed platform, supervised redeployment from IaC into a clean AWS account, documented handover of all accounts and credentials to ADB, and the end-February beta launch. A6-Post-beta QA/QC, model-update integration & refinement: Coordinates and integrates fixes arising from user feedback after the beta launch, absorbs updates to the underlying resource model (including the University of Edinburgh threshold/cost revisions) via the request-time configuration, oversees regression testing and a hardening pass, and signs off the refined platform at end-April. Reporting, coordination and quality assurance: The consultant reports to 3 Energy Specialists and Director, Energy Sector Office (Emerging Areas). The consultant will chair the weekly technical governance forum and coordinates the Senior Developer, the Senior UI/UX Specialist and the University of Edinburgh model/engine consultant on API and integration matters, bridging their staggered contract windows and leading the March–April refinement phase. Every deliverable is reviewed and accepted by ADB before payment. Ownership, intellectual property and open-source release: • All engagements are administered by ADB. ADB owns all outputs — code, deliverables, data and derived assets; the consultant receives access rights, not ownership of the outputs. • Intellectual property is assigned to ADB, and code is additionally released under a named open-source licence (MIT or Apache 2.0 for code; CC BY 4.0 for documentation and derived data). • All work is developed in repositories accessible to ADB at highest privileges from day one • Infrastructure is defined as code and is a named deliverable with acceptance criteria, enabling redeployment into an ADB-designated account. • AI features in MRAP are guided, non-generative product features; there is no public-facing generative AI, consistent with ADB's moratorium and AI-use policy, and any assistant output is clearly labelled as indicative and kept human-in-the-loop. • The API-contract ownership, merge/review authority and system-level integration accountability set out above are explicit terms of this engagement, not implied by seniority. • The final payment tranche is gated on the post-beta refinement sign-off (end-April) and the documented handover of all accounts and credentials to ADB. Minimum Qualification Requirements Essential: • Advanced university degree (Master's or equivalent) in computer science, software engineering, geoinformatics or a related field; a first degree with additional qualifying experience may be considered. • At least 10 years of professional experience delivering production web platforms end to end, including in a lead or CTO-level role. • Hands-on proficiency across backend, frontend and infrastructure; demonstrated API design and ownership; infrastructure-as-code (Terraform or AWS CDK) on AWS. • Demonstrated experience with CKAN (RBAC, extensions, custom templates) and/or comparable open-data catalogue platforms. • Demonstrated experience with cloud-native geospatial web architectures (COG/STAC, tiling, MapLibre GL JS) and secure-by-design practices. • Proven technical leadership and coordination of a small, distributed team on staggered timelines. • Professional working proficiency in English (written and spoken) is required. Desirable: • Experience delivering open-source public-good platforms in a development, government or multilateral context. • Familiarity with the ENERGYDATA.INFO / DCAT ecosystem and inter-institutional data harvesting. • Prior work in the energy sector or with geospatial energy data. Minimum General Experience 10 Years Minimum Specific Experience (relevant to assignment) 8 Years Regional/Country Experience Required Desired Not Required Deliverables Details Name Type Estimated Submission Date Solution architecture & API contract Others 31-Oct-2026 Platform Security Others 30-Nov-2026 APEDR map-first landing + MRAP map frontend Others 31-Dec-2026 Establishment and operation of of technical governance of the MRAP and APEDR product family Others 31-Jan-2027 System-level acceptance & beta launch Others 28-Feb-2027 Post-beta QA/QC Others 30-Apr-2027 Schedule and Places of Assignment (chronological and inclusive of travel) Schedule Type Continuous Intermittent Max. Working Days/Week Home Office 5 Field 6 City and Country Estimated Start Date Estimated End Date Other Details (use if place selected is Others) Home Office, Other Search and Select: Place 01-Oct-2026 30-Apr-2027 Export to PDF Export to PDF Copyright (c) 1998, 2023, Oracle and/or its affiliates. All rights reserved. Copyright (c) 1998, 2023, Oracle and/or its affiliates. All rights reserved. Pick a Date Loading... Loading...