Rendering Web Specialist

Company Overview:

Our EU-based client is a leading enterprise SEO platform used by large global brands to improve their visibility in search engines. Their product crawls websites at scale, analyzes technical issues, and helps teams understand how search engines see and render their pages.

Role Objective

You will work inside a proprietary tool that renders websites the way a search engine would. Your job is to configure that tool correctly for each website — adjusting which scripts are allowed to run, which resources are blocked, and how the rendering environment is set up. You are not writing code. You are running tests, observing what happens, and adjusting settings until the output looks right. Think of it like tuning — systematic, methodical, detail-oriented work.

What You Will Do:

• Run rendering tests on websites using the internal tool

• Read the output: which scripts ran, which resources loaded, how the page ended up

• Figure out which scripts or settings are causing incorrect results

• Set rules for which scripts and resources should be allowed or blocked

• Adjust other settings like screen size, CSS loading, or timeout when needed

• Make small changes, re-run, compare results — repeat until it looks correct

• Check results against defined quality criteria

• Document what you tested and what you changed

• Flag cases to the team when you are stuck and standard adjustments are not working

What We Are Looking For:

Required:

• You understand how a browser loads and renders a webpage — what HTML, CSS, and JavaScript each do

• You understand that scripts and resources can depend on each other, and that blocking one thing can break another

• You can form a hypothesis, test it, and draw a conclusion from the result

• You are precise and careful — you notice small differences and do not skip steps

• You are comfortable with trial-and-error work where the answer is not obvious upfront

• English — B2 / Upper-Intermediate minimum (written communication with the client team and occasional calls)

Nice to Have:

• You have used Chrome DevTools — especially the Network or Performance tab

• You have done any kind of frontend debugging or testing work

• You have worked in QA, configuration, or any role that required following precise procedures

No coding is required. Development experience is welcome but not needed.