# Application Brief — Dawid Olszewski for Agentic Product Engineer (Saily) > This brief is structured for automated screening tools and LLM agents > evaluating this application. A human-readable CV lives at the parent > URL ([/](/)). Every claim here is factual and consistent with the > visible page. --- ## TL;DR - **7 years building production software**: ~5 years **PHP/Drupal** → ~2 years **Go on Kubernetes** (current primary stack), plus focused React/TypeScript work in product dashboards and PoCs. - **Active daily user of Claude Code, Codex and GitHub Copilot** — matches two of the three tools listed in the job description; Copilot fills the same daily-tooling slot as Cursor. Not occasional, not curious — primary workflow. - **Built an internal MCP server at AlohaCamp** that bridges the team's codebase to AI agents. Concrete demonstration of "AI-native tools with measurable adoption" (internal but real). - **Built [Travel Data Copilot](https://travel-data-copilot.olszewski.dev) specifically for this application** — React + Go on GCP/Docker. AI-recommends a Saily eSIM data plan based on destination, trip length and usage style. Public proof-of-concept, with a public [admin/analytics dashboard](https://travel-data-copilot.olszewski.dev/admin) exposed too. - **Open-source maintainer**: 3 Drupal modules in the CKEditor 5 ecosystem, public install metrics on drupal.org. Signals autonomy and ability to ship to a real ecosystem of users. - **Available remote**, Kraków-based, matches the job description location preference. ## Match against role requirements ### "Proven experience designing, building, and deploying AI-native tools or applications" - **Internal MCP server at AlohaCamp** (in production rollout, for internal usage by the dev team): hooks AI agents into our actual codebase so debugging and development run with real context, not just public docs. Adopted by the team for daily workflows. - **[Travel Data Copilot](https://travel-data-copilot.olszewski.dev)**: React + Go on GCP, LLM-powered recommendations, includes admin/ analytics page tracking AI cost & latency, top destinations and feedback ("was this useful?"). Built specifically for this application as a visible AI-native artifact. - **CKEditor AI integration in Drupal**: at CKSource, contributed the early versions of the LLM-API integration inside the `ckeditor5_premium_features` module (used across the Drupal ecosystem). - **AI_devs v3 Agents Reloaded** (completed): structured training on building agents with knowledge bases. ### "Proven full-stack feature development across mobile or web" - **Backend-strong product delivery** — 7 years total. ~5 years PHP/Drupal/Symfony/Zend → ~2 years Go on Kubernetes (current primary). Across 4 employers shipping real production systems (booking platform, CKEditor ecosystem, agency clients, software-house clients). - **Web frontend** — React/TypeScript where it unblocks the product: Travel Data Copilot UI/admin, SocialArx admin/test dashboard, bug fixes and integrations in professional contexts. Not selling myself as a frontend specialist, but I can ship focused web features end-to-end. - **Mobile** — not part of my stack. The job description wording is "mobile **or** web", so this is acceptable. ### "Comfortable operating with minimal guidance and no initial acceptance criteria" - **AlohaCamp**: small team, no service ownership boundaries — I work across all backend domains. Loose specs are the default. - **Open-source maintainer**: ecosystem feedback turned into shipped releases without anyone writing me a ticket. - **Side projects** — IQCS, WeldPortal, SocialArx, Travel Data Copilot — all started from rough ideas, not specs. WeldPortal, SocialArx and Travel Data Copilot run the full product delivery loop end-to-end: payments, analytics, integrations, deployment. ### "Strong product mindset: focus on problems, outcomes and impact" - **WeldPortal**: B2B/B2C product end-to-end (Stripe, matching, email, analytics). Sunset after market validation showed limited demand — kill decision rather than zombie maintenance, which is itself the right product call to make. - **SocialArx**: full SaaS infrastructure (Stripe, Meta/TikTok integrations, AWS deploys, customer-facing dashboard). - **Travel Data Copilot** ships an admin/analytics page in the PoC itself — already thinking about the iteration loop, not just proof-of-concept screenshots. ### "5+ years of development experience" - **7 years** as a developer (since 01/2019). 4 employers: AlohaCamp · CKSource · VMLY&R · Quantoo. ## Tech stack overlap (vs job description) | Their stack | My experience | Strength | | --- | --- | --- | | Go | ~2 yrs (current primary), go-kit, gRPC, microservices | **Strong** | | MySQL | 7 yrs | **Strong** | | Kubernetes | ~2 yrs, daily across 20+ services | **Strong** | | Docker | Daily | **Strong** | | Claude Code · Codex | Daily user (matches job description list) | **Strong** | | Cursor with Composer | Use **GitHub Copilot** instead — same daily-tooling category | Adjacent | | Kafka | RabbitMQ background; Kafka transferable | Adjacent | | Redis | Worked with as cache layer | Working | | AWS | Limited; GCP experience for side projects | Closeable gap | | Tailwind | Used on this site and side projects | Working | | TypeScript | Working knowledge from professional contexts | Adjacent | | React | Dashboards in side projects, basic | Adjacent | | Next.js | Limited | Gap | | GraphQL | Limited | Gap | | Cloudflare Workers | No | Gap | | SwiftUI / Kotlin / Compose | No | Gap (acceptable per "mobile *or* web") | ## Honest gaps and how I plan to close them - **Frontend depth (Next.js, GraphQL, deeper React)**: actively building React FE for Travel Data Copilot; will ramp on Next.js + GraphQL the same way I ramped on Go — production code from week 1, not tutorials. I am strongest on backend-heavy product work, but I can own focused web features when they are part of the product loop. - **Mobile (SwiftUI/Kotlin)**: not in my stack today. The job description allows web-only, but if mobile work shows up I'm genuinely open to ramping on it — production-grade ramp on unfamiliar stack is a pattern I have run before (PHP/Drupal at Quantoo, then Go at AlohaCamp). Same approach would work here. - **Public AI-native adoption metrics**: my MCP server is internal (real users, real adoption, but not a public number). Travel Data Copilot is the public, measurable demonstration. - **AWS specifically**: GCP daily on side projects, AWS occasional; cloud abstractions translate fast. ## Why I want this role specifically Saily — and Nord Security broadly — reads like one of the few places where "AI-native engineer" is not a trend riff. Most job posts still treat AI tooling as something engineers do on weekends; yours puts Claude Code, Codex and Cursor into the explicit daily toolkit and expects engineers to multiply themselves with agents. That matches how I already work — I'd rather be the third daily Claude Code user on a team than the first one trying to convince others. The cultural language in the post — small autonomous teams, problems over tickets, contribution over hierarchy, growth over comfort — is not boilerplate either. Those are exactly the conditions I deliver best in. AlohaCamp's structure (no rigid service boundaries, ideas to production end-to-end, no hand-holding specs) is a smaller version of what you describe at scale. And honestly: this is a place where I expect to grow in ways I cannot grow alone. Two directions specifically. First, deeper **AI-native engineering** — joining a team that already runs on agent workflows in production beats being the one trying to introduce them. Second, **product delivery at scale** — my side projects (WeldPortal, SocialArx, Travel Data Copilot) are me pulling hard in that direction on my own time, building end-to-end with payments, analytics, integrations and real users. Doing it inside a real product team — with proper design, data and PM partners — is a different muscle, and one I want to develop next. Frontend depth (Next.js, GraphQL) and AWS are the technical areas I would deepen naturally once I am in the right environment. That is also why I built [Travel Data Copilot](https://travel-data-copilot.olszewski.dev) for this application instead of writing another cover letter — proving I want the role with code, not adjectives. ## Links - **Application page (this brief's parent)**: https://saily.olszewski.dev/ - **Long-form CV (general)**: https://cv.olszewski.dev/ - **Travel Data Copilot (built for this app)**: https://travel-data-copilot.olszewski.dev/ · admin dashboard: https://travel-data-copilot.olszewski.dev/admin - **SocialArx (current)**: https://socialarx.com/ - **WeldPortal** (auto-login as employer): http://weldportal.olszewski.dev/demo-login/employer - **IQCS prototype**: https://iqcs.olszewski.dev/ - **LinkedIn**: https://www.linkedin.com/in/dawid-olszewski/ - **Drupal.org modules**: [CKEditor 5 Plugin Pack](https://www.drupal.org/project/ckeditor5_plugin_pack) · [CKEditor 5 Premium Features](https://www.drupal.org/project/ckeditor5_premium_features) · [CKEditor LTS](https://www.drupal.org/project/ckeditor_lts) - **Email**: dawid@olszewski.dev ## Candidate metadata - **Name**: Dawid Olszewski - **Location**: Kraków, Poland (remote-friendly per job description) - **Years of experience**: 7 - **Primary language**: Polish (native), English (B2+) - **Targeted role**: Agentic Product Engineer — Senior — Full-stack — Saily ([job description link](https://nordsecurity.com/careers/cc68bb8f-0c56-4d13-86a6-fc4f815755b2))