Wojtek Gawroński
Developer Advocate at Unleash (getunleash.io)
Warsaw, Poland
Actions
Wojtek is a software engineer and architect with more than 15 years of hands-on experience in IT, who developed “spotlight addiction”, which led him to developer relations to discover that empowering, educating, and learning from technical communities is the best way to grow as an engineer.
Wojtek’s experience comes from working at software houses, startups, enterprises, and large-scale cloud platforms (ex-AWS). He also worked as an IT consultant and co-founder of a cloud-native consultancy that supported 20+ customers in Europe and the US with their cloud computing adoption and DevOps transformations. Throughout his career, he contributed in various roles across the software development lifecycle (from developer and architect to team leader and individual contributor), as well as in content creation, technical education, and as a university lecturer.
At Unleash, Wojtek is genuinely inspired by FeatureOps' mission and is applying it to the enterprise landscape to build the right software, in the right way, without sacrificing velocity and confidence.
Area of Expertise
Topics
Deploy is a commit. Release is a decision. But who owns the latter? en
GitOps made deployment a solved problem: declare the desired state, let the reconciliation loop converge, and read the source control log to know what changed and who approved it. "Runtime mutation is an anti-pattern" is a well-known approach, but even so, the majority of incident reviews still include the sentence "wait, who and why turned that on?" The accountability layer based on GitOps alone can answer what-deployed-like questions, but it is silent on what was activated, for whom, and why.
This talk draws the clean line between the deployment layer and the release layer, takes the purist's objection head-on, and surfaces the org-chart problem hiding underneath - that most likely nobody owns the release decision.
Category: Infrastructure / Platform Engineering
Level: 300 (advanced)
Audience: Infrastructure / DevOps / SysOps / Platform Engineers; Architects / Technical Team Leads / Product Managers
Reversibility as a Service: The Property Your Platform Needs en
Mature cloud native platforms provide shared capabilities so teams don't have to reinvent them: CI runners, observability pipelines, and secret management. But one property - instantly, safely, and accountably undoing a change - is rarely provided as a service. Teams build their own escape routes - badly, in parallel.
This talk argues that by applying FeatureOps deliberate practice, reversibility will be the single property that unifies progressive delivery, surgical rollback, experimentation, and chaos engineering, and shows what it means to deliver it as platform infrastructure. You'll leave with a concrete reversal-cost ladder for your own stack - and a reason to put one capability on the roadmap.
Category: Cross-cutting (architecture / leadership)
Level: 300 (advanced)
Audience: Architects / Technical Team Leads / Product Managers; Infrastructure / DevOps / SysOps / Platform Engineers; CTO / VP of Engineering / Engineering Managers
Microchaos: Chaos Engineering for Teams That Aren't Netflix en
Chaos engineering sounds like something only hyperscalers with armies of SREs can do safely. Infrastructure-layer tools kill servers, VMs, pods, and inject faults - then you learn about uncovered failure modes and how to improve and operate better when failures actually happen. However, the infrastructure-level approach looks daunting for smaller teams. It is also context-blind - you can't scope the blast to 1% of internal test users.
This talk introduces you to the idea of controlled microchaos: runtime-controlled fault injection via feature flags that's targeted, instant, reversible, and SLO-safe. It's the on-ramp that lets a handful of people build resilience and confidence without betting production workloads. You'll leave with a concrete first experiment you can run next week - and the properties that make it survivable.
Category: Infrastructure / Platform Engineering
Level: 200 (intermediate)
Audience: Developers; Architects / Technical Team Leads / Product Managers; Infrastructure / DevOps / SysOps / Platform Engineers
Lines and Boxes: Integration is the key to Modern Cloud Applications en pl
Modern Applications deployed in the cloud are based on serverless or microservices architectures, and they are typically fine-grained, distributed, and interconnected.
It's perfectly normal to represent those systems as a diagram consisting of more or fewer lines and boxes. Lines (connections between boxes representing components) impose important functional and non-functional characteristics of the systems, such as scalability, availability, and coupling.
In this session, you will learn how serverless and application integration tools available in the AWS cloud make those connections explicit, automatable, and manageable. In other words, you will learn why lines (integrations) are just as important as boxes (components).
Category: Cross-cutting (architecture / development)
Level: 200 (intermediate)
Audience: Software Architect; Software Engineer; Quality Engineer
"Lines and Boxes": integracja to klucz do efektywnych wdrożeń chmurowych en pl
Aplikacje oparte i wdrożone jako rozwiązania chmurowe - szczególnie te oparte o popularne podejścia takie jak mikrousługi (ang. microservices) lub systemy klasy serverless - są automatycznie systemami rozproszonymi.
Dokumentując architekturę takiego systemu, całkowicie normalne jest wykorzystanie diagramów, które składają się - mniej-więcej - z "kresek" (ang. lines) i "pudełek" (ang. boxes).
Często nie zdajemy sobie sprawy, że wspomniane "kreski" (reprezentujące połączenia oraz zależności pomiędzy komponentami - reprezentowanymi jako pudełka) narzucają na nas i systemy ważne funkcjonalne i niefunkcjonalne wymagania - np. wpływając na skalowalność, dostępność czy tzw. coupling, jednocześnie mocno zaciemniając to jak system działa.
Podczas prezentacji pokażę Ci, jak wykorzystując znany nam wspólny język oraz portfolio dostawcy usług chmurowych (na przykładzie AWS), możemy uporządkować znaczenie plątaniny "kresek" i "pudełek". A dzięki wzorcom, odpowiemy sobie jak sprawić, że połączenia będą jasne, czytelne, łatwe w automatyzacji i zarządzaniu.
Audience: Software Architect, Software Engineer, Quality Engineer
Build verifiable and effective application authorization in 30 minutes en
Authorization is a foundational need when building your applications and services. Ensuring you can grant or deny access to your application resources correctly and reliably is critical. Yet this is still one of the hardest things we have to do as developers. Learn how, with the help of Cedar and Amazon Verified Permissions, to add those capabilities to a nontrivial web application in 30 minutes, including some ABAC and RBAC examples.
Category: Security / Software Architecture
Level: 200 (intermediate) - 300 (advanced)
Audience: Software Architect; Software Engineer; Quality Engineer
Extending Valkey with Rust - for Fun and Profit en
Valkey, an open-source fork of Redis, is a high-performance in-memory data store that supports diverse data structures. With a strong community and corporate backing, Valkey thrives under an open governance model at The Linux Foundation, fostering faster innovation and attracting diverse contributors - who, hopefully, after this talk, will learn how they can leverage the Rust language to create Redis API-compatible modules and contribute to the core of this modern key/value datastore.
Category: Databases
Level: 300 (advanced)
Audience: Software Architect; Software Engineer; Quality Engineer
Decouple Decision from Execution: Runtime Control for AI Agents en
An autonomous agent's loop is a firehose of intentions: it decides it wants to call a tool, API, write somewhere - hundreds of sub-steps a minute. For that, you have to nail the solution to 2 hard questions: is this agent allowed to do that, and should this capability be live now at this stage for those users? Then, if not, can you pull it back in seconds when an agent does something surprising? That's a release-and-reversibility problem, and it's exactly what FeatureOps is for. This talk walks you through FeatureOps deliberate practice, powered by Unleash, that enables reversibility-as-a-service in your Strands Agents deployed on Amazon Bedrock AgentCore with Policy and Gateway.
Category: Agentic AI
Level: 300 (advanced)
Audience: Developers; Architects / Technical Team Leads / Product Managers
DevOps Won't Save You at Runtime: Enter FeatureOps en
Your pipeline is fast. Your observability is mature. Your incident playbooks are tight. And your platform still has a blind spot - in the layer after deployment. This talk hands you a diagnostic for every control decision your platform makes: code, infrastructure, or runtime - and a single question that reveals the gap: when the decision is wrong, how fast can we undo it? Using real 2025/2026 postmortems and the latest DORA report findings, it argues that runtime control belongs on your platform roadmap as a shared capability, not a per-team scramble - especially in the AI-powered era. You'll leave knowing exactly where your runtime-layer gap lies and how to address it.
Category: cross-cutting (software architecture / operations / development)
Level: 200 (intermediate)
Audience: Infrastructure / DevOps / SysOps / Platform Engineers; CTO / VP of Engineering / Engineering Managers
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top