Dev Lead — eCommerce Platforms | Warsaw, Poland

O projekcie: Preferred (strong signals, not hard requirements): - Experience in the gaming industry — game key distribution, virtual currency marketplaces, or gaming services platforms. - Familiarity with PrestaShop 8/9 architecture, module development, and the PrestaShop ecosystem. - Experience scaling engineering teams from 5 to 15+ people. - Background in B2B platform development (supplier APIs, automated procurement, pricing algorithms). - Contributions to open source, technical blog posts, or conference talks. - Working knowledge of DevOps practices — Docker, CI/CD pipelines, cloud infrastructure (AWS/GCP). - Polish language proficiency (not required, but helpful for local team interactions). Wymagania: - 7+ years of professional software development with at least 2 years in a technical leadership capacity (lead developer, tech lead, or engineering manager with hands-on coding). - Hands-on project management experience — you've owned sprint planning, backlog grooming, task estimation, and delivery commitments. You know how to run a dev team's weekly cadence, not just participate in it. Experience with tools like Jira, TeamWork, Linear, or equivalent is expected. - People management track record — you've directly managed, mentored, or technically led at least 3–5 developers. This means: conducting 1:1s, giving performance feedback, participating in hiring decisions, onboarding new developers, and resolving interpersonal or workload conflicts within the team. If you've scaled a team (hired, onboarded, retained), that's a strong signa - Strong PHP experience — ideally with Symfony, PrestaShop, or equivalent MVC framework. You understand the PrestaShop module architecture and can work within (and improve) it. - Production React/TypeScript experience — React 18, modern hooks patterns, TypeScript in a real frontend codebase (not toy projects). - Working Python proficiency — enough to build, maintain, and extend Python services (data processing, integrations, automation). - PostgreSQL fluency — query optimization, schema design, understanding of performance at scale. - Demonstrable, hands-on experience using Claude in your actual development workflow. We will ask you to demonstrate this in the interview. Specifically: prompt engineering for code generation, using AI for spec-to-implementation workflows, AI-assisted testing, and AI-augmented code review. If you haven't actively integrated LLMs into how you write code, this role is not the right fit. - eCommerce or marketplace platform experience — you've built or significantly contributed to a transactional platform handling payments, inventory, multi-vendor/supplier logic, or order management. - Comfortable working in-office in Warsaw — we have an office and we use it. Hybrid flexibility exists, but this is an office-first role. - Strong English communication — our team is international. Daily communication, specs, and documentation are in English. Codzienne zadania: - Lead development delivery across platforms. Own the sprint cycle end-to-end — planning, estimation, task assignment, daily coordination, and retrospectives. You're accountable for what the dev team delivers each week. - Write production code daily and improve overall company dev framework. - Manage and grow the development team. Run regular 1:1s, provide direct performance feedback, resolve blockers, and create an environment where developers improve. As we scale, you'll own hiring — writing role specs, running technical interviews, onboarding new hires, and building the team culture. - Own technical architecture decisions. Lead system design for new modules, evaluate technical debt, and drive the modernisation roadmap. You'll make the call on how things get built — stack choices, patterns, data models — and defend those decisions with clear reasoning. - Drive AI-augmented development as a team standard. Use Claude Enterprise and LLM tools as core parts of your workflow — spec-to-code generation, test scaffolding, code review augmentation, documentation. Then make it the team's standard: build prompt libraries, run workshops, and track adoption. This isn't experimental — it's how we work. - Run the spec-to-deployment pipeline. Translate product requirements into technical specs, get them through the CEO sign-off gate, break them into sprint tasks, and ensure clean handoff from spec → development → QA → deployment. You own the throughput of this pipeline.