QA Engineer/JR Developer

About Us We are a rapidly growing telecommunications technology company building APIs and cloud-based communications solutions for businesses around the world. Our platform includes multiple products, applications, APIs, and customer-facing tools, and we're looking for someone who is passionate about quality and enjoys solving technical problems. Position Overview We're looking for a QA Engineer / Junior Software Developer to help ensure our products are reliable, stable, and ready for production. This is more than a traditional QA position. We're looking for someone who enjoys digging into problems, understanding how systems work, and helping engineers identify the root cause of issues rather than simply reporting that something is broken. You'll work across multiple products, APIs, web applications, and internal systems. The ideal candidate is detail-oriented, technically curious, and comfortable working closely with developers to investigate bugs, validate new features, and improve the overall quality of the platform. This is an excellent opportunity for someone who wants to grow into a software engineering role while gaining hands-on experience working with APIs, cloud infrastructure, and modern SaaS applications. Responsibilities Perform quality assurance across multiple products and business units. Test new features before release and perform regression testing on existing functionality. Validate REST APIs using tools such as Postman, Insomnia, cURL, or similar. Test API requests, authentication, JSON payloads, webhooks, error handling, and edge cases. Verify functionality across web applications, customer portals, dashboards, and backend services. Reproduce customer-reported issues and document clear reproduction steps. Investigate bugs to determine whether they originate from the frontend, backend, API layer, third-party integrations, configuration, or data. Create detailed bug reports with screenshots, logs, request payloads, and supporting information. Verify bug fixes after deployment. Assist with release testing and production validation. Maintain QA documentation, test plans, and regression checklists. Work closely with engineering and product teams throughout the development lifecycle. Assist with light development work, scripting, or internal tooling as your technical skills grow. Required Qualifications 1+ years of experience in QA, software development, technical support, or another technical role. Experience testing REST APIs. Familiarity with Postman, Insomnia, cURL, or similar API testing tools. Understanding of HTTP methods, JSON, authentication, headers, status codes, and webhooks. Strong analytical and troubleshooting skills. Excellent attention to detail. Ability to clearly document technical issues. Comfortable learning new technologies in a fast-paced environment. Preferred Qualifications Experience with JavaScript, TypeScript, Python, PHP, or another programming language. Familiarity with Git. Basic SQL knowledge. Experience with SaaS platforms. Experience testing APIs and cloud applications. Experience reading logs and debugging distributed systems. Familiarity with monitoring tools such as Datadog, Grafana, CloudWatch, or similar. Experience with automated testing frameworks is a plus. Experience in telecommunications, messaging, voice, or API platforms is a plus. What Makes Someone Successful in This Role We're looking for someone who naturally asks "why?" When something doesn't work, you don't stop after identifying the bug. You want to understand why it happened, how to reproduce it consistently, and what information the engineering team needs to resolve it quickly. You enjoy testing edge cases, thinking like an end user, and finding issues before customers do. You're organized, detail-oriented, and take pride in delivering high-quality software. Example If a customer reports that an API request failed, we don't expect a bug report that simply says: "The API isn't working." Instead, we want someone who investigates questions like: Was the request formed correctly? Did authentication succeed? What HTTP status code was returned? What does the response body indicate? Can the issue be reproduced consistently? Is the problem isolated to one endpoint, one customer, or one environment? Is it an application issue, infrastructure issue, or third-party dependency? The more information you can gather before involving engineering, the faster problems get solved.