Attingal, Kerala Software test engineer Jobs – 85 Open Jobs Today

Other jobs to consider

Find your next job by exploring related positions.

Lead II - Software Testing (playwright, automation testing, api testing,gitlab)
UST —Thiruvananthapuram, Kerala
Ability to work in an Agile development environment. Strong experience in designing and implementing automated test frameworks.
Quality Analyst
ECS Fin —Thiruvananthapuram, Kerala
Test Design and Execution: Ability to design effective test cases, scenarios, and test scripts based on functional requirements and user stories.

By signing in to your account, you agree to SimplyHired's Terms of Service and consent to our Cookie and Privacy Policy.

Responsibilities :

Take untapped RCM opportunities, design full-stack solutions that solve real problems and ship them to production, and iterate on real-world feedback.
Select and justify the best tools / frameworks per project; implement PoCs when needed.
Build and maintain secure, scalable APIs, UIs, automations, and data pipelines.
Integrate third-party systems (EHR, CRM, payment gateways, RPA bots).
Uphold code quality with reviews, automated tests, CI/CD, and cloud-native best practices.
Mentor junior engineers in problem-solving and tech-agnostic thinking.
Work closely with the RCM operations team to understand pain points and identify high-impact automation opportunities.
Focus on measurable business outcomes rather than processes, with emphasis on RCM performance metrics improvement.

Must-Have Skills & Mindset :

3 – 6 years designing, coding, testing, and running production software end‑to‑end.
Proven ability to learn new stacks fast and pick “best‑fit” tech (language, framework, cloud, DB) per use case.
Deep grasp of computer‑science fundamentals, distributed systems, and REST/gRPC/GraphQL API design.
Solid understanding of front‑end back‑end integration patterns (contract design, API gateways, auth flows) and real‑time communication (WebSockets, SSE, pub‑sub, event streams).
Hands‑on cloud (AWS / GCP / Azure) with container orchestration and observability.
Strong unit / integration testing discipline; Git & trunk‑based workflows.
Bias for metrics‑driven decisions and rapid experimentation.
Outcome-focused approach that prioritizes solving real business problems over following rigid processes.
Excellent written & verbal communication with non‑technical stakeholders.