Chapter Lead – UI & Access Management Solutions

📍 Job Overview

Job Title: Chapter Lead – UI & Access Management Solutions Company: ING Hubs Romania Location: CDR (Amsterdam - Cedar), Netherlands Job Type: Other Category: Engineering Management / Data & Analytics Operations Date Posted: 2026-01-29 Experience Level: Mid-Senior Level (2-5 years) Remote Status: Hybrid

🚀 Role Summary

• This role focuses on leading a chapter of Experience Engineers, specializing in User Interface (UI) and Access Management Solutions within Data & Analytics.
• It involves a dual responsibility: approximately 50% leadership and coaching, and 50% hands-on contribution to delivering technical solutions.
• The chapter will be part of the Resource & Access Management (RaAM) squad, developing and maintaining front-end (React) and back-end (Go) solutions on microservices/API architecture running on Kubernetes.
• Key aspects include fostering continuous learning, promoting technical excellence, and driving innovation in UI and access control for data analytics platforms.
• This hybrid role requires strong technical acumen in modern development stacks and excellent interpersonal skills for team leadership and stakeholder engagement in an international environment.

📝 Enhancement Note: This role is classified under "Other" employment type but clearly aligns with Engineering Management and Data & Analytics Operations due to its focus on leading a technical chapter, managing engineers, and overseeing critical UI/Access Management solutions for data platforms. The hybrid nature suggests a blend of remote and in-office work, with specific days likely determined by team and project needs. The "Chapter Lead" title is a common structure in agile, product-aligned organizations, emphasizing functional expertise and people development.

📈 Primary Responsibilities

• Chapter Leadership & Coaching: Guide, coach, and inspire a team of Big Data Cloud engineers, fostering a culture of continuous learning, experimentation, and innovation.
• Talent Development: Conduct regular one-on-one meetings, performance reviews, and support chapter members in their career growth and professional development plans.
• Technical Excellence & Standards: Set and uphold standards for best practices, tools, and methodologies within the Experience Chapter, driving initiatives to enhance technical quality, scalability, and maintainability.
• Hands-on Development: Contribute directly to the development and maintenance of front-end solutions using React and back-end solutions using Go, within a microservices/API architecture on Kubernetes.
• Community Building & Knowledge Sharing: Organize knowledge-sharing sessions, workshops, and other professional development opportunities to foster a strong sense of community within the chapter.
• Stakeholder Engagement: Collaborate with stakeholders across engineering, product, and business functions to ensure alignment between product goals, priorities, and the chapter's strategic objectives.
• Environment Shaping: Create a safe, empathetic, and approachable environment that encourages constructive challenges and open communication within and outside the chapter.
• Technology Adoption: Stay updated with the latest technological developments and introduce relevant innovations to the team and projects.
• Communication: Clearly explain complex technical subjects to diverse audiences, ensuring understanding and alignment.

📝 Enhancement Note: The 50/50 split between leadership and hands-on contribution is a critical element. Candidates must demonstrate both strong technical proficiency in the specified stack (React, Go, Kubernetes, Microservices) and effective people management/coaching skills. The emphasis on "compliance & experience IT," "User Interface," and "Access Management" highlights the critical nature of these solutions for data security and user adoption within ING's data analytics platforms.

🎓 Skills & Qualifications

Education:

• Bachelor’s degree in Computer Science or a related technical field (HBO/bachelor's level or equivalent).

Experience:

• Minimum of 3 years of experience in IT within a corporate environment.
• Proven experience in building distributed, reactive applications.
• Experience in front-end development with React or similar frameworks.
• Experience with back-end development, specifically with Go.
• Demonstrated experience in building and managing CI/CD pipelines, preferably using Azure DevOps.
• Good understanding of databases, particularly Relational Database Management Systems (RDBMS).
• Good understanding of Kubernetes and microservices/API development.

Required Skills:

• Chapter Leadership: Ability to guide, coach, and develop a team of engineers.
• Technical Proficiency: Strong skills in React for front-end development and Go for back-end development.
• Cloud & Containerization: Good understanding of Kubernetes and microservices architecture.
• DevOps & CI/CD: Competence in building CI/CD pipelines, ideally with Azure DevOps experience.
• Databases: Solid understanding of RDBMS principles and usage.
• Communication: Excellent ability to explain complex technical subjects clearly to varied audiences.
• Empathy & Interpersonal Skills: Ability to create a safe and inclusive team environment, fostering collaboration and respect.
• Problem-Solving: Aptitude for identifying and resolving technical challenges.

Preferred Skills:

• Experience with the ELK stack (Elasticsearch, Logstash, Kibana) for logging and monitoring.
• Experience with message-oriented middleware, such as Kafka.
• Familiarity with User Interface (UI) and Access Management best practices and solutions.
• Experience in data-driven software solutions and their development lifecycle.

📝 Enhancement Note: The "HBO/bachelor's degree" requirement is specific to the Dutch educational system, indicating a strong preference for candidates with at least a 4-year technical degree. The blend of front-end (React), back-end (Go), and infrastructure (Kubernetes, CI/CD) skills points towards a full-stack engineering leadership role. The "nice-to-have" skills in ELK and Kafka suggest areas where additional expertise would be highly valued for monitoring and event-driven architectures.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Code Samples: Demonstrable examples of front-end (React) and back-end (Go) code, showcasing clean architecture, best practices, and effective problem-solving.
• System Design: Case studies or descriptions of distributed systems, microservices, and API designs you have contributed to or led.
• CI/CD Pipeline Examples: Documentation or descriptions of CI/CD pipelines you have built or managed, highlighting automation and efficiency gains.
• Database Design & Management: Evidence of experience with RDBMS, potentially including schema design, query optimization, or data governance aspects.

Process Documentation:

• Agile/Scrum Methodologies: Experience working within Agile frameworks, demonstrating understanding of sprint planning, daily stand-ups, and retrospectives, particularly within a squad structure.
• Best Practice Implementation: Documentation of how you have established and enforced technical best practices, coding standards, and quality assurance processes within an engineering team.
• Continuous Improvement: Examples of process improvements you have implemented to enhance team efficiency, code quality, or delivery speed.
• Stakeholder Communication Protocols: Documented approaches to engaging with and reporting to various stakeholders (e.g., Product Owners, other Engineering Leads, business units) on project status, risks, and successes.

📝 Enhancement Note: While not explicitly stated as a "portfolio required" role, candidates are expected to demonstrate their technical and leadership capabilities. This section infers the types of evidence that would be most impactful in an interview. For a Chapter Lead role, showcasing not just individual technical contributions but also the ability to guide a team in process implementation and adherence to standards is crucial.

💵 Compensation & Benefits

Salary Range:

• Based on the location (Amsterdam, Netherlands), experience level (2-5 years), and the hybrid nature of the role, the estimated annual gross salary for a Chapter Lead/Engineering Manager with this profile in the Netherlands typically ranges from €65,000 to €95,000. This estimate is derived from industry benchmarks for similar technical leadership roles in the Dutch IT market, considering ING's standing as a major financial institution.

Benefits:

• Vacation Days: 25-28 vacation days per year, depending on the contract.
• Pension Scheme: Comprehensive pension plan.
• 13th Month Salary: An additional month's salary paid annually.
• Holiday Payment: 8% holiday allowance.
• Hybrid Working: Flexible work arrangement combining remote and office-based work.
• Personal Growth: Opportunities for continuous learning and professional development.
• Challenging Work: Engaging projects with significant impact and opportunities for skill enhancement.
• Innovative Environment: Work with a team of innovative colleagues in an informal setting.

Working Hours:

• Standard full-time working hours are assumed to be around 40 hours per week, with flexibility offered through the hybrid working model.

📝 Enhancement Note: Salary estimates are based on available data for similar roles in Amsterdam, Netherlands, considering the specified experience level and the responsibilities of a Chapter Lead. The provided benefits are directly listed in the job description and are typical for large organizations in the Netherlands. The "OTHER" employment type might mean specific contract terms, but the benefits suggest a standard employment package.

🎯 Team & Company Context

🏢 Company Culture

Industry: Banking & Financial Services Technology Company Size: Large Enterprise (ING is a global financial institution with tens of thousands of employees worldwide). Founded: 1991 (through merger of ING Bank and NMB Postbank Groep).

Team Structure:

• Chapter-Based Agile Model: The role operates within a "Chapter" structure, a common practice in agile organizations where individuals with similar skills (e.g., Experience Engineers) are grouped together under a Chapter Lead for functional guidance and development.
• Squad Integration: Chapter members are assigned to cross-functional "Squads" to deliver specific product or platform features. This role is part of the Resource & Access Management (RaAM) squad.
• Department: Operates within the Enterprise Data Foundation & Compliance department, part of the broader Data & Analytics organization.
• Global Collaboration: Works with teams across multiple countries (Netherlands, Poland, Romania, India), necessitating strong cross-cultural communication and remote collaboration skills.

Methodology:

• Data-Driven: The department's mission is to make ING banking data-driven, leveraging UX research, engineering, and data science.
• Agile & DevOps: Implied by the squad structure, microservices, Kubernetes, and CI/CD focus, suggesting an agile development environment with strong DevOps principles.
• Hybrid Cloud Environment: Utilizes both on-premise and public cloud technologies.
• User-Centric Design: Focus on delivering great user experiences through UI and access management solutions.

Company Website: https://www.ing.com/

📝 Enhancement Note: ING is a well-established global bank with a significant investment in technology and data. The "Chapter Lead" and "Squad" model indicates a mature agile transformation. The "Compliance & Experience IT" and "Data & Analytics" focus means this role is central to how ING manages data security, user access, and the overall user experience of its data platforms, which are critical for compliance and business decision-making.

📈 Career & Growth Analysis

Operations Career Level: This role sits at the intersection of technical leadership and people management. It's a mid-to-senior level position, often considered an entry point into formal engineering management or a senior individual contributor track with leadership responsibilities. It's a step beyond a senior engineer role, involving direct people management and strategic input for a technical domain.

Reporting Structure:

• The Chapter Lead will likely report to a higher-level manager within the Data & Analytics organization, possibly a Head of Engineering, Director of Data Platforms, or similar.
• They will directly manage and mentor the Experience Engineers within their chapter.
• They will collaborate closely with Product Owners and other Chapter Leads/Squad members.

Operations Impact:

• This role significantly impacts the efficiency, security, and user adoption of ING's data analytics platforms by ensuring robust and user-friendly UI and access management solutions.
• By fostering a high-performing engineering team, the Chapter Lead contributes to the overall data-driven mission of the department, enabling better insights and compliance across the organization.
• Effective access management is crucial for regulatory compliance and data security, directly mitigating risks for the bank.

Growth Opportunities:

• Technical Specialization: Deepen expertise in UI/UX, access management technologies, cloud-native development (Kubernetes, Go), or data engineering.
• Leadership Progression: Transition into roles with broader management scope, such as Head of Engineering, Engineering Manager for multiple chapters, or a Product Management role focused on data platforms.
• Cross-Functional Movement: Opportunities to move into roles within different squads or departments within ING's Data & Analytics organization or other technology divisions.
• Continuous Learning: Access to training, workshops, conferences, and certifications to stay current with emerging technologies and leadership best practices.

📝 Enhancement Note: The "Chapter Lead" position is designed to provide a structured career path for senior engineers who want to develop leadership skills without necessarily moving away from technical work. It emphasizes developing people and fostering technical excellence, which are foundational for future leadership roles within ING's technology organization.

🌐 Work Environment

Office Type: Hybrid working model. This implies a mix of remote work and in-office presence at the Amsterdam - Cedar location. The office environment is likely modern, designed for collaboration, and equipped with necessary technology for hybrid teams.

Office Location(s):

• Primary office: CDR (Amsterdam - Cedar), Netherlands.
• Other ING Hubs locations mentioned: Poland, Romania, India, indicating a globally distributed team structure.

Workspace Context:

• Collaborative Spaces: Offices are expected to have meeting rooms, project spaces, and potentially quiet zones to support diverse work needs.
• Technology Infrastructure: Access to standard office technology, high-speed internet, and potentially specialized hardware or software for development and data analysis.
• Team Interaction: Opportunities for informal and formal interactions with chapter members, squad colleagues, and other technical professionals within ING. The hybrid nature means balancing in-person collaboration with effective virtual communication tools.

Work Schedule:

• Standard full-time hours (approx. 40 hours/week) with the flexibility afforded by the hybrid working arrangement. This allows for personal scheduling adjustments while ensuring team alignment and project delivery.

📝 Enhancement Note: The "CDR (Amsterdam - Cedar)" suggests a specific, modern office location within Amsterdam, likely designed with collaborative workspaces to support hybrid teams. The emphasis on working in an "informal working environment with innovative colleagues" points to a culture that values open communication and idea sharing.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A recruiter or HR representative will likely review applications and conduct an initial screening call to assess basic qualifications and cultural fit.
• Hiring Manager Interview: A conversation with the direct hiring manager (likely the Head of Engineering or similar) to delve deeper into leadership experience, technical background, and understanding of the role's responsibilities.
• Technical/Chapter Interview: This will likely involve discussions with senior engineers from the chapter or related teams. It may include technical deep dives into React, Go, Kubernetes, CI/CD, and system design. Candidates may be asked to walk through past projects or solutions.
• Peer/Squad Interview: Meetings with potential peers or members of the RaAM squad to assess collaboration style, communication skills, and cultural fit.
• Case Study/Challenge (Potential): Candidates might be given a small technical challenge or asked to present a hypothetical solution to a problem related to UI/Access Management or system design.
• Final Interview: A concluding discussion, possibly with a senior leader, to finalize the decision and discuss offer details.

Portfolio Review Tips:

• Showcase Leadership: Highlight instances where you mentored junior engineers, established best practices, or led technical initiatives.
• Code Quality: If sharing code samples, ensure they are well-documented, follow clean architecture principles, and demonstrate efficient problem-solving.
• System Design: Prepare to discuss the architecture of systems you've worked on, focusing on scalability, maintainability, and the trade-offs made.
• CI/CD & Automation: Be ready to explain your approach to CI/CD, including tools used, pipeline stages, and benefits achieved (e.g., faster deployment, fewer errors).
• Impact & Metrics: Quantify achievements whenever possible. For example, "Reduced deployment time by X%" or "Improved system uptime to Y%."

Challenge Preparation:

• Technical Depth: Brush up on React, Go, microservices architecture, Kubernetes concepts, and common database patterns.
• Problem Decomposition: Practice breaking down complex problems into smaller, manageable parts.
• Communication Clarity: Prepare to articulate your thought process clearly and concisely, especially when explaining technical decisions.
• Understanding ING's Context: Research ING's data analytics strategy, compliance requirements, and typical challenges in a large financial institution.

📝 Enhancement Note: Given the 50% hands-on component, expect a rigorous technical assessment. The "Chapter Lead" aspect means the interview will also heavily focus on leadership, coaching, and team development. Candidates should be prepared to discuss their management philosophy and how they foster growth and collaboration.

🛠 Tools & Technology Stack

Primary Tools:

• Front-end: React (required)
• Back-end: Go (required)
• Container Orchestration: Kubernetes (required)
• Microservices & APIs: Development and architecture (required)
• CI/CD: Azure DevOps (competency required), other tools are also common.

Analytics & Reporting:

• ELK Stack (Elasticsearch, Logstash, Kibana): Preferred for logging, monitoring, and analysis.
• Data Analytics Platforms: Underlying platforms that the UI and access management solutions serve.

CRM & Automation:

• Message-Oriented Middleware: Kafka (preferred) for asynchronous communication and event streaming.
• Databases: RDBMS (required), potentially NoSQL databases as well.

Other Relevant Technologies:

• Cloud Platforms: On-premise and public cloud environments.
• Version Control: Git (standard, assumed).

📝 Enhancement Note: The core technology stack is clearly defined: React, Go, Kubernetes, Microservices/APIs, and Azure DevOps. Expertise in these areas is essential. The preferred skills in ELK and Kafka indicate a leaning towards robust observability and event-driven architectures, which are common in modern, large-scale systems.

👥 Team Culture & Values

Operations Values:

• Curiosity & Continuous Learning: A strong emphasis on staying updated with technology and introducing new ideas.
• Data-Driven Decision Making: Utilizing data and analytics to inform solutions and processes.
• Collaboration & Community: Fostering a supportive environment where team members help each other succeed.
• Technical Excellence & Quality: Commitment to building scalable, maintainable, and high-quality software solutions.
• Empathy & Respect: Creating a safe space for open communication, feedback, and constructive challenges.
• Innovation: Encouraging experimentation and the adoption of modern technologies.

Collaboration Style:

• Agile Squad-Based: Work within cross-functional squads, collaborating closely with Product Owners, engineers, and other IT specialists.
• Chapter Model: Regular interaction with members of the same discipline (Experience Engineers) for functional guidance, knowledge sharing, and process alignment.
• International & Hybrid: Requires effective collaboration across different time zones and working models, relying on digital tools and clear communication protocols.
• Open Feedback Culture: Encouragement of constructive feedback to drive continuous improvement and personal/team growth.

📝 Enhancement Note: ING, as a large financial institution, likely values reliability, security, and compliance, alongside innovation and agility. The emphasis on empathy and creating a safe environment suggests a modern, people-centric approach to management within a technically demanding domain.

⚡ Challenges & Growth Opportunities

Challenges:

• Balancing Leadership and Hands-on Work: Effectively managing time and priorities between coaching, mentoring, and direct technical contributions.
• Technical Debt Management: Addressing and mitigating technical debt in existing UI and access management solutions while delivering new features.
• Cross-Cultural & Distributed Teams: Navigating communication and collaboration challenges across different time zones, cultures, and working styles in a hybrid environment.
• Evolving Technology Landscape: Keeping pace with rapid advancements in UI frameworks, backend languages, and cloud-native technologies.
• Security & Compliance Demands: Ensuring that UI and access management solutions meet stringent financial industry security and compliance standards.

Learning & Development Opportunities:

• Leadership Training: Formal programs or mentorship focused on engineering management, coaching, and team building.
• Technical Skill Enhancement: Opportunities to deepen expertise in React, Go, Kubernetes, cloud technologies, and potentially specialized areas like security or UX design.
• Industry Conferences & Certifications: Support for attending relevant industry events and obtaining certifications.
• Mentorship Programs: Access to senior leaders within ING for guidance and career advice.
• Exposure to Large-Scale Systems: Gaining experience with complex, mission-critical systems in a global financial institution.

📝 Enhancement Note: The challenges highlight the complexity of managing technical teams and solutions in a regulated industry, especially within a distributed, hybrid model. The growth opportunities are well-aligned with career paths in tech leadership and specialized engineering.

💡 Interview Preparation

Strategy Questions:

• Leadership Philosophy: "Describe your approach to coaching and developing engineers. How do you foster a culture of continuous learning and psychological safety within your team?" (Prepare specific examples of mentoring, performance feedback, and team-building activities).
• Technical Vision: "How would you approach setting technical standards for UI and Access Management solutions? What are the key considerations for building scalable and maintainable microservices?" (Be ready to discuss your preferred architecture patterns, testing strategies, and quality assurance processes).
• Problem-Solving & Conflict Resolution: "Describe a time you faced a significant technical challenge or interpersonal conflict within your team. How did you address it?" (Focus on your analytical skills, decision-making process, and collaborative approach).

Company & Culture Questions:

• ING's Data Strategy: "What do you understand about ING's mission to be data-driven? How do you see the role of UI and Access Management in supporting this mission?" (Research ING's public statements on data, digital transformation, and compliance).
• Hybrid Team Dynamics: "How do you ensure effective collaboration and communication within a hybrid, globally distributed team?" (Discuss tools, strategies, and best practices for remote and cross-cultural collaboration).
• Balancing Priorities: "This role involves 50% leadership and 50% hands-on work. How do you plan to balance these demands effectively?" (Prepare a strategy for time management and prioritization).

Portfolio Presentation Strategy:

• Case Study Selection: Choose 1-2 projects that best demonstrate your technical leadership, problem-solving skills, and contributions to UI/Access Management or distributed systems.
• Structure: For each case study, clearly outline:
  1. The problem/challenge.
  2. Your role and responsibilities.
  3. The solution designed and implemented (highlighting technical stack and design decisions).
  4. The impact/results (quantify with metrics if possible).
  5. Lessons learned and future improvements.
• Technical Details: Be prepared to discuss the architecture, specific code snippets (if applicable), challenges encountered, and trade-offs made.
• Leadership Aspect: For each case, also highlight how you guided or influenced team members, established standards, or fostered collaboration.

📝 Enhancement Note: Candidates should prepare to discuss both their technical expertise (React, Go, Kubernetes, Microservices) and their leadership capabilities. The interview will likely assess their ability to manage people, drive technical excellence, and contribute hands-on to the development lifecycle. Demonstrating an understanding of the financial services context, particularly around security and compliance, will be advantageous.

📌 Application Steps

To apply for this operations position:

• Submit your application through the provided link on the ING careers portal.
• Resume Optimization: Tailor your resume to highlight experience in UI development, access management solutions, back-end development with Go, microservices, Kubernetes, and CI/CD (especially Azure DevOps). Quantify achievements wherever possible to showcase impact.
• Portfolio Preparation: Compile relevant code samples, project descriptions, or case studies that demonstrate your technical skills and leadership experience. Focus on projects involving distributed systems, front-end/back-end development, and process improvements.
• Interview Practice: Prepare for behavioral questions related to leadership, coaching, and problem-solving, as well as technical questions covering the core technologies. Practice articulating your contributions and impact.
• Company Research: Familiarize yourself with ING's mission, values, and its approach to data and technology. Understand the significance of compliance and user experience in the financial sector.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.