Junior / Mid Web Developer

• Shipping real client work from your first weeks. Webflow, Astro builds that go out on Vercel, content models in Sanity or Payload. If you're new, you start with sections and pages. If you've already shipped, you take the build. Either way it's live client work, not sandbox exercises
• Taking our designers' Figma files and making them behave in a browser exactly the way they were meant to, down to the spacing, the motion and the small details nobody writes down in the ticket. This is where most of the craft in this job lives. If you already know when a file will break in production, you say so before it ships
• Moving across the stack on purpose. One day you're in Webflow, the next you're fixing an animation in Astro, the day after you're wiring up analytics or cleaning up a content migration. Some of it is unglamorous. If you're junior, this is how you find your strengths. If you're mid, you use them, and you pick up the rest of our stack without being walked through it
• Working with Claude Code, Codex and Cursor every day, and reviewing and correcting what they produce instead of trusting it. The AI shift is still unfolding and our processes are taking shape around it, which means what you notice and say actually counts
• Pairing with senior devs. If you're junior, you grow from pages to whole builds, and we'd rather that happened fast. If you're mid, you own the build, sit on client calls in English, and review work that isn't yours
• Holding your work to the same bar as everyone else's: responsive, accessible, fast, SEO-sane, and checked before anyone has to ask

• Genuinely strong HTML and CSS. Flexbox, grid, responsive layouts, and the ability to explain why something breaks instead of patching it at random. This is the one thing we won't teach from zero
• JavaScript: enough to write and debug a small script on your own. If you already think in components and can debug other people's code, even better
• Real fluency with AI dev tools. You know which tool fits which job, how to prompt it, and how to spot when it's confidently wrong
• Something you've actually built and shipped. A side project, a portfolio, a landing page, a tool you vibe-coded over a weekend, or a full production site you owned. Send the URL. This matters far more than your diploma, and far more than how many years the calendar says. We'll know from the work whether this is a junior conversation or a mid one
• Taste. Technical skills get you in the door, but taste is how you stay. This is not a designer-only thing here. You won't be the one designing, but you'll be the one who makes a design come alive, and that only works if you can see why it works. Noticing that a spacing is off by 4px, that an animation is 200ms too slow, that a hover state feels cheap
• SEO, accessibility and web performance: you understand why they matter to a client's business. If you already own them on the builds you ship, we'll see that
• We'll happily teach you the rest of the stack. Wanting to get better has to come from you
• Git: a GitHub account with something in it is enough to start. Branches, pull requests and merge conflicts you can learn as you go. If that's already daily practice, perfect
• English at a communicative level. It doesn't have to be polished, but it has to be enough to read documentation, sit in on a client call and write a message nobody has to decode. We speak mostly Polish internally, though not everyone on the team does, and everything client-facing happens in English
• Nice to have: any hands-on time with the tools we live in. Webflow, Astro, React or Next.js, Sanity or Payload, Vercel. Having one or two of these is a head start, having none of them is fine if everything above is there. If you've already shipped in them, say so
• Warsaw-based, full-time. For the first 6 to 12 months, three or four days a week in our Krucza office and the rest remote, more flexible after that. If you're not in Warsaw, this isn't the role
• This is a full-time role. If you're only partially available right now but you've read the list above and think you're a perfect fit, send it anyway and we'll figure it out together

• A senior team that reviews your work. If you're new, you get pairing and a mentor, not a vague “ask someone if you get stuck”. If you're further along, they expect you to review theirs
• Client work that ships. Funded B2B SaaS companies, real deadlines, your code in production, not internal filler tasks
• A written path with expectations you can read instead of vibes you have to guess. Junior to mid, or mid to senior, depending on where you start
• A flexible learning budget for courses, books and workshops. If something will genuinely move you forward, we don't look for reasons to say no
• Paid access to whatever tools you need to do the job well. No asking permission every month
• Conferences and events with the team
• Flexible working hours. Most of the work happens between 9:00 and 17:00
• 21 days paid time off and sick leave
• No mandatory overtime, but paid extra if you volunteer
• LuxMED + Multisport
• Dinners, retreats, and workations

1. Application - CV welcome if you have it, we'll open it. Still: tell us about yourself in your own words, and show us what you've built. GitHub, a Webflow project, a Vercel deployment, a half-finished experiment, or a live production URL you owned. All of it counts. Add two or three websites you find genuinely beautiful, with a line each on what you like about them. We ask because developers here need taste, not just designers. And if there's something we haven't asked about that you think we should know, tell us anyway
2. Initial call - 30-minute video chat with our developers about what you've built and how you work with AI tools. If you're new, we talk about what you want to learn next. If you've already shipped, we talk about a build you owned
3. Ship something - A short build task we'll send you after the call. One evening, three hours tops. The brief meets you where you are. And yes, you're expected to use AI

Final step - Meet the team at Krucza, wrap up the details, then welcome aboard. We're hiring one person for this role, with a start date from September