[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"job-product-engineer-vivid-en-kz":3},{"id":4,"slug":5,"title":6,"description":7,"company":8,"is_featured":11,"featured_until":7,"is_active":12,"deactivated_at":7,"is_enriched":12,"processed_job_posting_json":13,"processed_latitude":98,"processed_longitude":99,"processed_employment_types":100,"processed_working_hours":101,"processed_working_hours_labels":103,"processed_home_office":104,"processed_salary_min":95,"processed_salary_max":96,"processed_salary_currency":92,"processed_salary_source":105,"processed_benefits":106,"processed_benefits_labels":114,"processed_industry":115,"processed_skills":7,"processed_job_location":116,"processed_full_address_gmaps":122,"processed_street_gmaps":128,"processed_city_gmaps":130,"processed_postal_code_gmaps":131,"processed_country_gmaps":136,"processed_country_iso_code_gmaps":142,"full_description":16,"formatted_description":143,"processed_employment_types_labels":62,"processed_home_office_labels":60,"processed_industry_labels":64,"processed_it_skills":144,"processed_it_skills_labels":148,"processed_soft_skills":149,"processed_soft_skills_labels":150,"processed_job_expertise_skills":151,"processed_job_expertise_skills_labels":152,"processed_language_requirements":153,"processed_total_experience_years":146,"processed_professional_field":160,"processed_professional_field_labels":163,"processed_leadership_role":11,"processed_date_posted":19,"raw_job_url":164,"apply_url":7,"raw_hiringOrganization_logo_url":165,"translations":7,"canonical_industry_key":166,"canonical_industry_label":167,"max_cpc":168,"actual_cpc":7},99817,"product-engineer-vivid","Product Engineer",null,{"name":9,"slug":10,"logo_url":7},"Vivid","vivid",false,true,{"@context":14,"@type":15,"title":6,"description":16,"hiringOrganization":17,"datePosted":19,"validThrough":20,"jobLocation":21,"jobLocationType":60,"employmentType":61,"industry":63,"skills":65,"baseSalary":90},"https:\u002F\u002Fschema.org\u002F","JobPosting","About The Role\nWe’re looking for a \nProduct Engineer\n for \nCustomer Care\n: a product person with real technical depth and an AI-first mindset, who wants to build our customer-facing support systems with us, not just run them. You’ll own all of Customer Care’s conversational systems: the chatbot today and voice\u002Fphone support next.\nYour primary focus is product: identifying problems worth solving, shaping solutions, and driving them from 0 to 1. You understand architecture, you’ve written code, you know how databases work, and you speak engineering fluently. AI is not a feature we’re adding, it’s how we work and how we build. Think 70% product, 30% engineer, 100% accountable for results. You set the direction, you write the spec, and you can also get into the build and ship the fix yourself.\nYour Mission\nOwn 0-to-1 development of Customer Care conversational systems (chat, voice\u002Fphone, knowledge base, tool integrations): decide what to build, why, and how to measure success, from discovery to launch to iteration.\nDesign with engineers how the bot is built: agents, routing, tools, internal-system actions, handoff; understand architectural trade-offs and unblock technical decisions.\nWork independently: research the problem in the data yourself, prototype a fix with AI tools, test it on real conversations, and prove it works, then scale it with engineering or open the PR yourself.\nWrite, test, and iterate prompts, skills, and knowledge so the bot answers correctly, acts safely, and sounds like us; build evals that catch regressions before every release. \nRun A\u002FB tests of models, prompts and flows, define success metrics upfront, and shut down what doesn't work.\nScale self-service via AI and automation, deflection up and cost-to-serve down without hurting CSAT; define “resolved” and “valid handoff” and monitor KPIs (deflection, handoff reasons, resolution quality, CSAT, handling time, cost per conversation).\nWrite product specs and briefs engineers actually want to read: clear, technical, and opinionated.\nChallenge the rules around the bot, not just the bot: when escalation policies, back-office processes or missing tools block resolution, build the case and get them changed.\nPrioritise ruthlessly and collaborate with Engineering, Design, Analytics, QA, Operations, and business owners to ship every release.\nYour Profile\nEssential\n4+ years in product management, product engineering, or a similar role with strong technical involvement, including meaningful hands-on experience applying LLMs \u002F agentic AI to real products.\nProven track record of taking ideas from 0 to a live product with real users.\nAI-native way of working: you use LLMs, vibe coding, and AI agents daily to move faster and validate ideas. This isn’t optional, it’s core to how we expect you to operate.\nYou know at least one programming language well enough to build things yourself (Python or similar), and you’re comfortable with git, databases, and evaluating system architecture.\nStrong analytical skills: comfortable with data, metrics, and decisions under uncertainty.\nClear communicator in English: you explain technical decisions to non-technical stakeholders and write specs engineers respect.\nSelf-directed: you don’t wait for someone to tell you what matters.\nDegree in Computer Science, Software Engineering, or equivalent practical experience.\nDesired\nBackground in customer support, conversation design, product, or prompt engineering. What you’ve built matters more than the title.\nSide projects with LLM APIs, agents, or automation. Show us.\nFintech or banking support: cards, transfers, chargebacks, KYC\u002FAML restrictions, account closure.\nExperience with LLM observability tools (Langfuse or similar) and helpdesk platforms (Kustomer, Zendesk).\nVoice\u002Ftelephony stacks (STT, TTS, turn detection) for phone support.\nWhy Join Vivid?\nWe have a hybrid model in our offices, or fully remote outside office locations. \nWe support relocation to Cyprus (visa, package) when needed.\nAI-first culture – we use it every day, not just talk about it.\nLearning & development budget to support your professional growth. \nFully paid vacation and sick leave. \nSports compensation. \nReal growth prospects, significant responsibility, and the ability to make an immediate impact from day one.\nCompensation range\nFinal compensation is determined individually, based on your experience, skills and the scope of the role, assessed against objective, gender-neutral criteria.\nAbout Vivid\nAt Vivid, we're on a mission to change how businesses and individuals manage their money across Europe. For businesses, we build tools that actually make a difference: multi-IBAN accounts, high-yield savings, business cashback, team cards, and accounting integrations that save real time — all in one place. And for individuals, we offer a simple way to manage and grow your wealth: access to global stocks, ETFs and 150+ cryptocurrencies, cashback, and personalised financial insights.\nOur mission? Your success. Everyone deserves the chance to see their finances flourish, and we're dedicated to empowering our customers to make this a reality.\nFounded in 2019 in Berlin by Alexander Emeshev and Artem Iamanov, Vivid has quickly grown into one of Germany's top financial platforms for SMEs and private accounts. Since then, we've expanded rapidly across Europe, earning the trust of over 500,000 customers — and with over €200 million raised and a valuation of €775 million, we're just getting started.\nWe're building Vivid as an AI-native organization — across every function, from product to compliance to operations. Automation handles a growing share of day-to-day execution. For us, this means our teams can focus on architecture, strategy, and high-impact decision-making. This changes how we work: less manual execution, more ownership in building systems that scale. We want to help define what AI-native looks like in a regulated financial environment — and we're looking for people who want to build that future with us.",{"@type":18,"name":9},"Organization","2026-10-22","2027-10-22",[22,32,39,47,54],{"@type":23,"address":24,"geo":28},"Place",{"@type":25,"addressLocality":26,"addressCountry":27,"addressRegion":26},"PostalAddress","Almaty","KZ",{"@type":29,"latitude":30,"longitude":31},"GeoCoordinates",43.2190777,76.9292402,{"@type":23,"address":33,"geo":36},{"@type":25,"addressLocality":34,"addressCountry":35,"addressRegion":34},"Lemesos","CY",{"@type":29,"latitude":37,"longitude":38},34.6850893,33.0558847,{"@type":23,"address":40,"geo":44},{"@type":25,"addressLocality":41,"addressCountry":42,"addressRegion":43},"Barcelona","ES","Lissabon",{"@type":29,"latitude":45,"longitude":46},41.3896592,2.1769216,{"@type":23,"address":48,"geo":51},{"@type":25,"addressLocality":49,"addressCountry":50},"Belgrad","RS",{"@type":29,"latitude":52,"longitude":53},44.8125449,20.46123,{"@type":23,"address":55,"geo":57},{"@type":25,"addressLocality":43,"addressCountry":56},"PT",{"@type":29,"latitude":58,"longitude":59},38.7346077,-9.149766399999999,"HYBRID",[62],"PERMANENT",[64],"Financial Technology (Fintech)",[66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89],"Python","Git","Databases","System Architecture","LLMs","AI Agents","Prompt Engineering","Vibe Coding","LLM Observability Tools (e.g., Langfuse)","Helpdesk Platforms (e.g., Kustomer, Zendesk)","Voice\u002FTelephony Stacks (STT, TTS, turn detection)","Analytical Skills","Communication","Self-Direction","Collaboration","Prioritization","Product Management","Product Engineering","Conversational AI Design","A\u002FB Testing","Metrics Definition","Customer Support Systems","Fintech\u002FBanking Support","Conversation Design",{"@type":91,"currency":92,"value":93},"MonetaryAmount","EUR",{"@type":94,"minValue":95,"maxValue":96,"unitText":97},"QuantitativeValue",70000,100000,"YEAR",[30,37,45,52,58],[31,38,46,53,59],"permanent",[102],"FULL_TIME",[102],"hybrid","estimated",[107,108,109,110,111,112,113],"Relocation support to Cyprus (visa, package)","Learning & development budget","Fully paid vacation and sick leave","Sports compensation","Hybrid work model or fully remote outside office locations","AI-first culture","Real growth prospects and significant responsibility",[107,108,109,110,111,112,113],"financial technology (fintech)",[117,118,119,120,121],"al-farabi avenue 77\u002F8 77\u002F8, 050060, almaty, kz","amathountos street 5th floor 5, 3105, limassol, cy","ronda de sant pere 52, 08010, barcelona, es","vivid, xxxx, belgrade, rs","vivid, 1050, lisboa, pt",[123,124,125,126,127],"8 floor, Al-Farabi Avenue 77\u002F7, Almaty 050000, Kasachstan","Amathountos, Lemesos 3105, Zypern","Rda. de Sant Pere, 52, Ciutat Vella, 08010 Barcelona, Spanien","Belgrad, Serbien","1050 Lissabon, Portugal",[129],"Al-Farabi Avenue 77\u002F7",[26,34,41,49,43],[132,133,134,135],"050000","3105","08010","1050",[137,138,139,140,141],"Kasachstan","Zypern","Spanien","Serbien","Portugal",[27,35,42,50,56],"## About The Role\n\nWe’re looking for a **Product Engineer** for **Customer Care**: a product person with real technical depth and an AI-first mindset, who wants to build our customer-facing support systems with us, not just run them. You’ll own all of Customer Care’s conversational systems: the chatbot today and voice\u002Fphone support next.\n\nYour primary focus is product: identifying problems worth solving, shaping solutions, and driving them from 0 to 1. You understand architecture, you’ve written code, you know how databases work, and you speak engineering fluently. AI is not a feature we’re adding, it’s how we work and how we build. Think 70% product, 30% engineer, 100% accountable for results. You set the direction, you write the spec, and you can also get into the build and ship the fix yourself.\n\n## Your Mission\n\n- Own 0-to-1 development of Customer Care conversational systems (chat, voice\u002Fphone, knowledge base, tool integrations): decide what to build, why, and how to measure success, from discovery to launch to iteration.\n- Design with engineers how the bot is built: agents, routing, tools, internal-system actions, handoff; understand architectural trade-offs and unblock technical decisions.\n- Work independently: research the problem in the data yourself, prototype a fix with AI tools, test it on real conversations, and prove it works, then scale it with engineering or open the PR yourself.\n- Write, test, and iterate prompts, skills, and knowledge so the bot answers correctly, acts safely, and sounds like us; build evals that catch regressions before every release.\n- Run A\u002FB tests of models, prompts and flows, define success metrics upfront, and shut down what doesn't work.\n- Scale self-service via AI and automation, deflection up and cost-to-serve down without hurting CSAT; define “resolved” and “valid handoff” and monitor KPIs (deflection, handoff reasons, resolution quality, CSAT, handling time, cost per conversation).\n- Write product specs and briefs engineers actually want to read: clear, technical, and opinionated.\n- Challenge the rules around the bot, not just the bot: when escalation policies, back-office processes or missing tools block resolution, build the case and get them changed.\n- Prioritise ruthlessly and collaborate with Engineering, Design, Analytics, QA, Operations, and business owners to ship every release.\n\n## Your Profile\n\n### Essential\n\n- 4+ years in product management, product engineering, or a similar role with strong technical involvement, including meaningful hands-on experience applying LLMs \u002F agentic AI to real products.\n- Proven track record of taking ideas from 0 to a live product with real users.\n- AI-native way of working: you use LLMs, vibe coding, and AI agents daily to move faster and validate ideas. This isn’t optional, it’s core to how we expect you to operate.\n- You know at least one programming language well enough to build things yourself (Python or similar), and you’re comfortable with git, databases, and evaluating system architecture.\n- Strong analytical skills: comfortable with data, metrics, and decisions under uncertainty.\n- Clear communicator in English: you explain technical decisions to non-technical stakeholders and write specs engineers respect.\n- Self-directed: you don’t wait for someone to tell you what matters.\n- Degree in Computer Science, Software Engineering, or equivalent practical experience.\n\n### Desired\n\n- Background in customer support, conversation design, product, or prompt engineering. What you’ve built matters more than the title.\n- Side projects with LLM APIs, agents, or automation. Show us.\n- Fintech or banking support: cards, transfers, chargebacks, KYC\u002FAML restrictions, account closure.\n- Experience with LLM observability tools (Langfuse or similar) and helpdesk platforms (Kustomer, Zendesk).\n- Voice\u002Ftelephony stacks (STT, TTS, turn detection) for phone support.\n\n## Why Join Vivid?\n\n- We have a hybrid model in our offices, or fully remote outside office locations.\n- We support relocation to Cyprus (visa, package) when needed.\n- AI-first culture – we use it every day, not just talk about it.\n- Learning & development budget to support your professional growth.\n- Fully paid vacation and sick leave.\n- Sports compensation.\n- Real growth prospects, significant responsibility, and the ability to make an immediate impact from day one.\n\n## Compensation range\n\nFinal compensation is determined individually, based on your experience, skills and the scope of the role, assessed against objective, gender-neutral criteria.\n\n## About Vivid\n\nAt Vivid, we're on a mission to change how businesses and individuals manage their money across Europe. For businesses, we build tools that actually make a difference: multi-IBAN accounts, high-yield savings, business cashback, team cards, and accounting integrations that save real time — all in one place. And for individuals, we offer a simple way to manage and grow your wealth: access to global stocks, ETFs and 150+ cryptocurrencies, cashback, and personalised financial insights.\n\nOur mission? Your success. Everyone deserves the chance to see their finances flourish, and we're dedicated to empowering our customers to make this a reality.\n\nFounded in 2019 in Berlin by Alexander Emeshev and Artem Iamanov, Vivid has quickly grown into one of Germany's top financial platforms for SMEs and private accounts. Since then, we've expanded rapidly across Europe, earning the trust of over 500,000 customers — and with over €200 million raised and a valuation of €775 million, we're just getting started.\n\nWe're building Vivid as an AI-native organization — across every function, from product to compliance to operations. Automation handles a growing share of day-to-day execution. For us, this means our teams can focus on architecture, strategy, and high-impact decision-making. This changes how we work: less manual execution, more ownership in building systems that scale. We want to help define what AI-native looks like in a regulated financial environment — and we're looking for people who want to build that future with us.",{"git":145,"llms":146,"python":145,"ai agents":146,"databases":145,"vibe coding":145,"prompt engineering":146,"system architecture":145,"llm observability tools (e.g., langfuse)":147,"helpdesk platforms (e.g., kustomer, zendesk)":147,"voice\u002Ftelephony stacks (stt, tts, turn detection)":147},3,4,2,[66,67,68,69,70,71,72,73,74,75,76],{"analytical skills":146,"communication":146,"self-direction":146,"collaboration":146,"prioritization":146},[77,78,79,80,81],{"a\u002Fb testing":145,"metrics definition":146,"product management":146,"conversation design":145,"product engineering":146,"fintech\u002Fbanking support":147,"conversational ai design":146,"customer support systems":145},[82,83,84,85,86,87,88,89],{"detected_language_jobad":154,"required":155},"en",[156],[157],{"language":158,"level":159},"ENGLISH","C1",[161,162],"Software and Applications Development and Analysis","Customer Service",[161,162],"https:\u002F\u002Fvivid.jobs.personio.de\u002Fjob\u002F2856182","https:\u002F\u002Fassets.cdn.personio.de\u002Flogos\u002F257360\u002Fsocial\u002F8a4c167ab5cf2b116eb0452ac9cf77ea.png","financial technology","Financial Technology",1]