Jetbrains plugin tester

We build plugins for JetBrains IDEs that improve the developer experience when working with template languages. We're looking for an experienced web developer to test them feature by feature and deliver a structured report on what does and does not hold up. The plugins: - Liquid — recently released, and our highest priority - Nunjucks — released a few days ago - Svelte — currently in development What we're asking for: This is not a role for building new features or contributing code. Each plugin offers roughly the same core feature set — around 11 key features. For every advertised feature, on every plugin, we want confirmation that it: - Works correctly - Behaves consistently - Matches the official language specification - Performs well on real-world projects You'll need a JetBrains IDE (preferably WebStorm or IntelliJ IDEA) and real projects in at least one of the supported languages — code completion, navigation, diagnostics and formatting only show their edges under actual use. A good part of this is editor-specific rather than language-specific, and we need it tested as such: code folding, the structure view, and associating file types with the syntax plugin all fall in scope, alongside the language features themselves. How to report a problem: Where a feature doesn't work as advertised, we need enough to act on it: - What you expected - What actually happened - Steps to reproduce - Example code, where applicable - Any observation or suggestion that could help us fix it Deliverable: One structured report per plugin, covering bugs, incorrect behaviour, missing features, documentation inconsistencies, usability feedback and suggestions for improvement. We use it to prioritise fixes across all three plugins. Priority order: 1. Liquid — our most mature plugin, with the largest potential audience, particularly within the Shopify ecosystem 2. Nunjucks — shares a lot with Liquid, as both are HTML-based templating languages, so issues found in one often apply to the other 3. Svelte — still under active development, and will benefit from testing once the first two have been evaluated Experience: You should already be at home in a JetBrains IDE and know its functionality well — that familiarity is what lets you tell a plugin bug from normal IDE behaviour. Ideally you have experience with multiple template languages, but specialising in one ecosystem is fine — a Shopify developer with extensive Liquid experience and no Svelte experience works for us. If you're only comfortable evaluating Liquid, or Liquid and Nunjucks, we'll split the work and either do the Svelte testing internally or assign it to a dedicated Svelte developer. How we develop: Our development process is highly AI-assisted. We use AI extensively to implement functionality, after which we verify the results against official language documentation, language-specific edge cases and reference codebases. Systematic, independent validation from an experienced developer is exactly what that process is missing. In your proposal, tell us which JetBrains IDE you use and what your experience is with the different template languages.