SDET

Ovii's Interpretation of the Role

The SDET will design and own automation frameworks, build AI‑enhanced validation systems, and ensure release confidence for Composio's integration platform. The role blends test engineering, CI/CD quality gates, and deep knowledge of distributed, API‑centric systems.

Role Snapshot

• Automation framework owner
• AI‑augmented testing specialist
• Integration & API test engineer
• Quality‑gate and release confidence advocate

Must-Have Requirements

• Automation framework development
• Test automation
• CI/CD quality gates
• API testing
• Integration testing
• Contract testing
• End‑to‑end testing
• AI‑powered validation
• Distributed systems debugging
• Logs/metrics analysis
• Product risk assessment
• Ownership & collaboration

Work Setup

• Location: Bangalore, India
• Work mode: ONSITE
• Employment type: Full-Time

Not Specified in JD

• Salary range
• Visa sponsorship
• Remote eligibility
• Education requirement
• Certifications

What You'll Likely Work On

• Design, develop, and maintain reusable automation frameworks and quality tooling for integration workflows
• Create and run comprehensive test scenarios covering APIs, authentication, retries, idempotency, and asynchronous flows
• Build automated test suites, quality gates, and CI/CD checks to provide release confidence and prevent regressions
• Develop AI‑driven validation agents that detect regressions, investigate failures, and scale quality across evolving products
• Improve testing strategy, coverage, and patterns across API, contract, and end‑to‑end layers
• Establish reliability practices for AI‑native workflows, measuring quality and addressing non‑deterministic behavior
• Investigate production incidents, enhance test observability, and implement preventive improvements for platform stability
• Partner with engineers to improve testability, influence design decisions, and raise overall engineering quality

Good Fit If You Have

• Enjoys tackling complex integration scenarios with multiple external dependencies
• Comfortable using logs, traces, and metrics to diagnose failures
• Proactive communicator who can explain technical trade‑offs across teams