SDET- API/Middleware
Free to start · No card · 5 credits the moment you sign up
Job description
Job Overview
Welo Global is hiring an SDET (Software Development Engineer in Test) to bring deep technical rigor to middleware-layer testing. This role requires strong technical expertise across gRPC-Web, Proto3, HTTP/2, JSON-RPC/REST, proxy-based traffic inspection, and API scripting. The primary responsibility is to observe and reconstruct the network interactions generated by the onboarding UI, including request/response structures, schemas, headers, identifiers, Enums, and client-injected parameters. This is primarily an API/network analysis and evidence-generation role rather than a conventional UI automation or regression-testing role. The resource will produce sanitized network evidence and controlled, benign tracer replay scripts for downstream backend validation.
Project Details
Title: SDET - API/Middleware
Rate: $9.50/hr
Start Date: 19th October
Duration: 5 Weeks
Commitment: 35 Hours per Week
Location: India (Remote)
Job Type: Freelance
Responsibilities
- Design, build, and maintain automated API test suites covering gRPC-Web, Proto3, HTTP/2, and JSON-RPC/REST based services
- Export clean, sanitized HAR/network evidence while maintaining traceability between UI actions and corresponding network requests.
- Map relevant schemas, headers, identifiers, routing information, and client-injected parameters.
- Use proxy tools such as Mitmproxy, Charles Proxy, and browser DevTools to inspect, intercept, and validate network traffic between client and server
- Develop and maintain API automation scripts using Python, Postman, and cURL for functional and regression testing
- Analyze protocol-level request/response behavior to identify defects related to serialization, encoding, and transport
- Inspect and validate request payload structure, including system-level headers (e.g., auth tokens, routing identifiers) and internal/hidden parameters, ensuring correct handling under both valid and malformed conditions
- Collaborate with backend and middleware engineers to define testable contracts and edge-case scenarios
- Continuously improve test automation frameworks for reliability, speed, and maintainability
- Document technical findings, automation coverage, and known protocol-level limitations
Required Qualifications
- Strong hands-on expertise of 3-5+ years with gRPC-Web, Proto3, HTTP/2, and JSON-RPC/REST protocols
- Proficiency with proxy/traffic inspection tools including Mitmproxy, Charles Proxy, and browser DevTools
- Solid scripting/programming skills in Python, with practical use of Postman and cURL for API automation
- Experience designing and maintaining automated test suites for middleware or API-layer services
- Working understanding of API request structure, including headers, auth tokens, and internal/system parameters, and how to test for their correct handling
- Understanding of software engineering practices as applied to test automation (version control, CI integration, code review)
- Strong debugging skills at the network/protocol level
- Experience analysing browser-generated network traffic and reconstructing API behaviour is strongly preferred.
- Experience with HAR analysis, API schema reconstruction, or controlled API replay is strongly preferred.
- Ability to work within approved staging/test environments and follow defined data-handling and test-authorization requirements is required.
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for Welocalize. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.