S Liborem Častulíkem o transformaci, integracích a realitě jeho BDO týmu

Business context & team role (ČSOB Pojišťovna)

• The interview is about a Business DevOps (BDO) organization inside ČSOB Pojišťovna’s Product division, led by Libor Častulík (one of three BDO managers).
• BDO covers end-to-end product/IT delivery roles: business analysts, IT analysts, developers, and operations specialists.
• Core responsibility: connect technical solutions to business product tasks—understand business intent, propose alternative approaches, and ensure implementation supports product strategy.

Operating model

• 6 teams within Libor’s area
• Each team is ~7–10 people
• Teams are organized by product area and by frontend/backend domains
• Teams aim to be “full-stack” enough to analyze + develop + handle operations/incidents
  • Some shared roles across teams
  • External suppliers in some places

Geography / coverage

• Mostly in Pardubice
• About ~10 people in Prague
• Mentions a new office building in Pardubice (candidate attraction + location strategy)

---

Concrete product examples & operational needs

• Frontend application for merchants to negotiate insurance (life & non-life)
  • Example goal for car insurance: reduce friction so that entering a license plate number minimizes other inputs
  • Outcome: faster quote/offers so salespeople focus on client conversations rather than system usage
  • Digital negotiation workflow: digital signature or email draft contract + payment confirmation
• Shift in partner behavior:
  • Partner networks increasingly prefer their own environment and connect via web services
  • They compare offers across insurers, then negotiate with the selected insurer
  • This drives focus on non-life insurance web-service integration
• Transformation program context:
  • Modernization priority is corporate insurance (not optimal with legacy setup)
  • Builds on earlier retail modernization that introduced modern systems + process coverage + digital signatures
  • The team works on:
    • Changes to current systems
    • Integration/implementation of systems tied to a new core system (e.g., frontend)

---

Operating cadence & flexibility policy

• Remote work policy within the ČSOB group:
  • 3 days in office / 2 days at home
• Workforce flexibility:
  • Mentions multiple mothers with shortened contracts (last ~2 years)
  • A part-time colleague (~4 months) used as staffing complement to meet team needs

---

Transformation program: what BDO is doing

Libor’s team focuses on:

• Modifications to existing systems
• Implementation of components linked to the new core system
• Integrations into current ecosystems, including:
  • Some changes that are temporary (legacy parts disappear after full core replacement)
  • Some changes that are permanent (new core still requires integrations with other systems)

Release readiness

• They are close to deploying into production / pilot for at least part of the work
• They frame it as “big project” reality: hiccups are expected

---

Integration challenges & scale (operational pain points)

• The key challenge is not “technology” itself, but coordination across teams and alignment on interfaces/data contracts
• They integrate a backend boxed solution into existing systems:
  • The new system expects returned data with specific response speed
  • The source system needs to provide data according to assigned requirements
  • Therefore, multiple teams must agree on interfaces and exchanged data
• Common failure modes:
  • Missing information
  • Unclear assumptions
  • Need for clarification
• Integration volume:
  • The team handled 150+ integrations (used as an indicator of coordination complexity and misunderstanding/clarification load)

---

Technology stack (execution layer)

• Backend: Java
• Database: Oracle
• Frontend: Angular or React

---

Quality & “Shift Left” approach (organizational playbook)

QA structure

• Testing is handled by a central test team (“one large unit”)
• During transformation, testing was moved/organized at the central level to support a large program

Planned future state

• Over the long term, they want testers closer to product teams to:
  • share more context
  • collaborate more easily

Shift Left alignment

• No explicit named framework/metric targets were given, but they discuss evolution aligned with:
  • Shift Left concepts (testing closer to development/teams)
  • CI/test automation efforts (referenced under AI section)

---

AI integration strategy (POC + testing automation)

• AI is approached pragmatically because transformation is already underway:
  • In some areas AI integration is feasible
  • In others, it’s not—so they may defer or revisit
• Specific AI POC:
  • Use AI to automate tests more effectively
• Bottleneck addressed:
  • Automated tests exist, but extending/maintaining them is hard because maintaining automated tests is painful
  • When the system changes during development, unmaintained tests break quickly (“automated test is gone”)
• Target outcome of the POC:
  • Validate that AI can create and maintain automated tests reliably as systems evolve

---

Metrics / KPIs / targets

• No explicit numeric KPIs were stated (e.g., no revenue/CAC/LTV targets)
• Concrete operational “scale” metrics mentioned:
  • 150+ integrations handled by the team
  • Team size 6 teams, ~7–10 people per team
  • Remote work policy: 3 days in office / 2 days at home
  • Testing and AI: POC status (no timeline numbers provided)

---

6–12 month / near-term milestones (business execution)

Alongside the transformation program, the team must:

• Continuously modify and improve current products based on client/merchant requests
• Run two workstreams simultaneously:
  • Daily product improvements
  • Transformation-related integration/system work

Product delivery expectations:

• Two “large” work-in-progress product efforts are expected to be delivered to retailers, who then serve end clients
• The interview emphasizes the operational complexity of keeping both transformation and ongoing product iteration running optimally

---

Leadership, hiring & culture (management tactics)

• What he’s most proud of:
  • Recruitment of new capable people
  • Ensuring team collaboration works well
• Culture priorities:
  • Everyone should be a team player
  • Encourage a “work like you own it” mindset
  • Build resilience through mutual support when difficult sections appear
• Diversity:
  • Notes broader diversity than earlier IT culture (more women, various ages/genders)

---

Recruiting pitch (how he positions BDO team)

• They position themselves as a corporation with process discipline, but not:
  • a “huge bank-like company”
  • a startup
• Candidate value propositions:
  • Pardubice headquarters presence and future focus (new building)
  • Show systems/working environment during recruitment (office walkthrough + systems/agendas)

---

Presenters / sources

• Libor Častulík — BDO manager, ČSOB Pojišťovna (interviewee)
• Smithy Talk — interview/podcast host and channel (interviewer mentioned only as “welcome to another Smithy Talk interview”; no individual name provided in the subtitles)