AI-First Frontend Developer

27 Марта

Партнерские Вакансии

Компания "aqua cloud GmbH"

This is not a traditional frontend developer role. We’re looking for someone who has fundamentally understood that AI-assisted development isn’t a productivity boost – it’s a paradigm shift. Someone who uses Claude Code, Cursor, or similar tools as the primary engine of their work. Someone who knows that the right prompt and the right validation is worth more than ten years of memorizing API docs.

The One Thing That Matters Most

You are an AI-native developer.

That’s it. That’s the job requirement that towers above everything else. Specific frameworks, languages, libraries – all of that is secondary. A developer who truly masters AI-assisted coding can pick up any technology in days, not months. We’ve seen it. We believe it. We’re hiring for it.

If you still believe you can consistently write better code than Claude Code with the right human guiding it – this role isn’t for you. If you understand that your real value lies in knowing what to build, how to architect it, how to prompt for it, and how to validate the result – read on.

What AI-Native means to us

This isn’t about using Copilot for autocomplete. This is about a fundamentally different way of building software:

• AI is your primary coding instrument. You don’t write boilerplate. You don’t manually refactor. You don’t Google syntax. You prompt, you iterate, you ship.
• You are the architect and validator, not the typist. Your job is to define the right abstractions, set the right constraints, and ruthlessly validate what AI produces. You catch the subtle bugs, the leaky abstractions, the solutions that look clean but won’t scale.
• You learn new technologies in days. Because with AI tools and solid engineering fundamentals, the barrier to picking up a new framework, language, or library has collapsed. You don’t need three years of React experience – you need the judgment to know when React is the right choice and the AI fluency to be productive in it immediately.
• You evolve constantly. If a better AI tool drops tomorrow, you’re the first to try it. You don’t defend your current workflow – you upgrade it.

What we’re building

aqua-cloud.io is an enterprise ALM platform used by companies worldwide for test management, defect tracking, and quality assurance. Our mission: to build the future of agentic work – a platform where AI agents and human testers collaborate seamlessly, where intelligent automation amplifies human capabilities by orders of magnitude.

Where we’re heading:

• Micro-frontend architecture: We’re breaking out of the monolithic SPA. You’ll help design and implement a micro-frontend strategy that allows teams to independently deploy, choose their own tech stacks, and iterate fast.
• Technology-agnostic: Our current stack includes Vue 3, TypeScript, Tailwind, Shadcn, Chart.js, Node.js, and more. But we’re not loyal to any framework. The right tool for the right job – and you’ll help decide what that is.
• Agentic interfaces: We’re building UIs where AI agents are first-class citizens. Human-AI collaboration surfaces, agent orchestration dashboards, real-time feedback loops – the kind of interfaces that barely еxistyet.

This is a 100+ component, enterprise-grade system with real-time communication, multi-tenancy, and complex permissions. It’s not a toy. But with the right AI workflow, even this complexity becomes manageable.

What we expect – in order of priority

#1 AI-First Development

This is the filter. Everything else is secondary.

• Daily, productive use of Claude Code, Cursor, or equivalent AI coding tools as your primary development method.
• The ability to prompt effectively: you know how to break down complex problems into prompts that produce high-quality, maintainable code.
• The judgment to validate: you catch when AI output is plausible but wrong, when it introduces subtle bugs, picks the wrong abstraction, or ignores edge cases.
• Zero ego about “hand-crafted code.” You measure yourself by outcomes – not by how many lines you typed manually.

#2 Engineering judgment

AI generates code. You decide if it’s good.

• Enough experience to tell the difference between code that works and code that’s production-ready. Scalability, maintainability, security – you see the bigger picture.
• Architectural thinking: you can evaluate micro-frontend strategies, state management approaches, and component design patterns on their merits.
• Pragmatism. You ship, iterate, and improve. You don’t spend three weeks debating the perfect folder structure.

#3 Openness & adaptability

The tech landscape changes fast. So should you.

• Willingness to work with any modern frontend technology – Vue, React, Svelte, Solid, or whatever emerges next.
• Curiosity to explore unfamiliar tools, patterns, and architectures without fear.
• Comfort with ambiguity: we’re building things that don’t have established playbooks yet.

#4 Technical skills

Helpful, but AI compensates. This is explicitly the lowest priority on this list.

• Experience with any modern SPA framework and component-based architecture.
• Familiarity with CSS utility frameworks (Tailwind), component libraries (Shadcn), charting (Chart.js, ECharts).
• Understanding of build tools (Vite, Webpack), Node.js, and REST APIs.
• Bonus: micro-frontend experience, C#/.NET familiarity, real-time systems (SignalR), feature flags (LaunchDarkly).

#5 Your location and language skills

We are willing to hire a person with Georgian residence or Private Entrepreneurship with advanced conversational English for communication within the team.

Your application

We don’t want a cover letter. We want proof of how you work:

Show us your AI workflow. Record a short video, write a walkthrough, or share screenshots of a real project where you used Claude Code, Cursor, or similar tools to build something non-trivial. This is the most important part of your application. We will weigh it more heavily than your CV.

Your CV with relevant experience. We’ll look at it, but see point 1.

3–5 sentences: How will AI change the way frontends are built in the next two years?

Optional: GitHub, portfolio, open-source work.