🎁 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 →
We are looking for QA Engineer (Application Support) 3+ Years of Experience in manual testing and application support. Experience in Automation is a PLUS!! 9am-6pm Hybrid work (3 days on-site in office at Ploenchit) We are looking for a QA Engineer who combines hands-on functional testing with application support and production issue investigation for our Insurance Core Platform, covering Motor and Property lines across the Quotation, Renewal, and e-Policy modules. The platform is a web application built on Java (Spring Boot and/or Java EE) with an Angular or Vue.js frontend, backed by an Oracle database with substantial business logic in PL/SQL. You will be the person who can take a defect or a production incident — a premium that calculated wrong, a renewal that did not generate, an e-Policy document that failed to issue — and trace it through the application, API logs, batch job output, and the Oracle database to isolate the root cause, then turn it into a clear, evidence-backed ticket for engineering and verify the fix end to end. This is a delivery role in a regulated insurance environment: evidence quality, data handling discipline, and traceability are part of the job, not an afterthought. Responsibilities: Quality Assurance Design and execute functional, regression, and UAT test cases across Quotation, Renewal, and e-Policy flows for Motor and Property products, covering the Angular/Vue web UI and the Java service layer behind it. Perform API-level testing (Postman or equivalent) against backend services, including negative cases, error contracts, and data validationPerform functional, integration, regression, and exploratory testing. Verify data outcomes directly in Oracle with SQL — policy records, transaction statuses, premium components, and document generation states across the policy lifecycle Maintain test documentation aligned to Definition of Ready / Definition of Done, with evidence suitable for audit (screenshots, logs, SQL results) Collaborate with Developers, Business Analysts, and Product Owners to improve product quality Develop and maintain automated test scripts Support release validation and production verification activities Application Support & Issue Investigation Act as third-level support for production and UAT issues: triage, reproduce, and investigate incidents reported by underwriting, operations, agents, or business users. Trace issues across the stack — web UI behaviour, API request/response logs, application server logs, batch job logs, and Oracle data — to isolate root cause vs. symptom. Escalate defects to engineering with reproduction steps, environment details, and impact assessment; verify fixes before closure. Qualifications: Bachelor’s or Master's degree in computer science, software engineering, Information Technology, or a related field. 3+ years of experience in software QA, application support, or a hybrid of both, in insurance, banking, or another regulated domain. Insurance core system experience (policy admin, quotation, or claims) is strongly preferred. Fluent, hands-on Oracle SQL: multi-table JOINs, aggregation, subqueries, date logic, and reading unfamiliar schemas to investigate issues independently. Proven experience investigating production issues using logs and data — not only executing test scripts. Working understanding of REST APIs: request/response structure, HTTP status codes, JSON payloads, and how to test them with Postman or similar tools. Clear written communication in Thai and English — investigation notes and defect reports will be read by engineering, business, and audit. Experience working in Agile/Scrum environments Preferred Qualifications: Test automation experience — e.g. Playwright, Cypress, or Selenium for web UI; REST Assured or Postman collections + Newman for APIs. Willingness to grow into automation is valued even without deep experience. Familiarity with Angular or Vue.js applications from a testing standpoint (browser DevTools, network tab, console/error inspection, SPA state behaviour) Exposure to Java Spring Boot / Java EE server environments (reading application server logs, stack traces, log correlation) Experience with log/observability tooling (Kibana/ELK, Grafana, Splunk, or similar). Knowledge of Motor or Property insurance products: cover types, sum insured, endorsements, no-claim bonus, renewal cycles Location: In Center of Bangkok (Pleonchit Tower, Chitlom BTS station) > ติดตามพวกเราเพิ่มเติมได้ที่: https://soilfish.co - or - https://www.facebook.com/soilfish.co >
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.