🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Job Description As a Senior Web Stack Engineer, you will play a key role in delivering high-quality frontend solutions across diverse headless architectures. This role requires both technical expertise and a strong focus on performance, accessibility, usability, and security, ensuring consistent quality, maintainability, and scalability. You will work on a Nuxt / Vue headless tool. Communication skills are key in your role: you will partner with a distributed team in the Philippines and Denmark, ensuring smooth collaboration, knowledge sharing, and reliable delivery. Responsibilities Take ownership of complex frontend features, ensuring timely and high-quality delivery. Develop and optimize performant, headless frontend applications using modern frameworks. Collaborate closely with frontend engineers, backend engineers, project managers, design, and UX teams. Ensure accessibility, security, and SEO best practices are embedded in development workflows. Apply performance optimization techniques across frontend projects. Mentor developers and contribute to knowledge sharing within the team. Use AI-assisted development tools to improve coding, testing, and documentation efficiency. Identify and drive improvements in development, testing, and release processes. Understand client needs and business context to recommend improvements and ensure solutions support long-term goals. Experience Minimum 5 years of full-time professional experience in frontend development. Several years of experience with headless frontend architectures. Demonstrated success delivering performance-focused web applications. Background working in agile (SCRUM) environments. Experience collaborating in distributed and cross-cultural teams. Mandatory Skills Strong communication skills in English. Vue and Nuxt. TypeScript and SCSS. Headless development principles. Performance optimization for modern web applications. Accessibility guidelines (WCAG). Security best practices (OWASP). SEO optimization techniques. Automated testing and modern frontend tooling. AI-assisted coding workflows. Bonus Skills Storybook or similar component libraries. Experience integrating with Umbraco Content API Experience integrating with SAP products Personal Traits Self-driven and proactive, with a strong sense of ownership and accountability. Able to work independently while keeping a holistic project perspective. Detail-oriented with a passion for performance and code quality. Comfortable working in distributed teams and managing asynchronous communication. Enthusiastic about learning and adopting new technologies and tools. Location DGS India - Pune - Kharadi EON Free Zone Brand: Merkle Time Type: Full time Contract Type: Permanent .
Here's where they are and how to stand out in your next interview.
24.795Jobs
9.577IN
74%EN
That number includes positions in India (9,577), Poland (3,429), the United States (1,753), Singapore (787), and Brazil (779). If you're looking to move or work remotely, check which countries match your goals — then filter WorkMundi by location to see what's actually hiring near you.
Most developer ads you'll see are written in English: 18,397 of the 24,795. That doesn't tell you whether the job itself requires you to speak English or work in English daily, so read each posting carefully. Don't assume the language of the ad matches the language of the team.
The employers posting the most developer roles are Link Group (369 jobs), Upvanta (257), jobgether (226), and OfferZen (212). If you're applying to any of these, research their hiring patterns. They move fast and post often, which means they're either scaling hard or replacing people who didn't fit.
In your interview, expect this: 'Walk me through the last time you had to debug something that took you more than an hour. What was it, what did you try first, and what would you do differently?' Hiring managers ask this to see if you think systematically or just try random fixes. Have a real example ready with specifics.