🎁 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 →
Parallel Wireless is reimagining mobile networks with innovative, energy-efficient Open RAN solutions. Join us as we lead the future of telecommunications, driving innovation through green and sustainable networks . Learn more about our mission, vision and values . Parallel Wireless is reimagining mobile networks with innovative, energy-efficient Open RAN solutions. We are now embedding agentic AI deep into our engineering lifecycle from feature development to field debugging to accelerate delivery and raise quality across our 4G/5G stack. Role Summary We're looking for a hands-on QA-Dev Engineer / Technical Lead to help redefine how Open RAN software is built and validated by putting agentic AI at the center of our engineering workflow . You'll design and run the agent-driven systems that handle the time-intensive parts of RAN engineering: agents that author test plans and scripts against 3GPP specifications, execute 4G/5G test campaigns and continuously monitor lab setups, triage logs and perform root-cause analysis when failures arise, and generate PRVT builds to validate proposed fixes all at a scale humans alone can't sustain. What you bring is deep RAN expertise protocol stack, call flows, end-to-end systems paired with strong judgment for what AI agents can and cannot be trusted to do. The result: faster fix cycles, broader test coverage, and engineers freed to focus on the hard, novel problems . What you'll do: AI-Augmented Engineering Use agentic AI to author test plans for 4G/5G features aligned with 3GPP specifications , and to generate, refactor, and maintain test scripts in the in-house automation framework Design and build end-to-end test setups , including RF setups, that are agent-observable and agent-controllable Orchestrate agents to execute regression and feature test suites , triage failures, classify them (product bug / setup issue / flake), and file/update tickets in JIRA with full evidence Build agent workflows that continuously monitor test setups (lab health, UE state, simulator status, RF chain), detect anomalies, and self-heal or escalate Drive RCT (Regression / Continuous Testing) automation as an AI-driven pipeline rather than a static script suite Drive AI-assisted log analysis and use agentic workflows to perform root-cause analysis on field and lab issues across simulators, vBBU components, and end-to-end systems tuning prompts, tools, and retrieval pipelines for accuracy on RAN-specific data Use agents to generate candidate fixes , evaluate them against design intent, and gate them through human review Trigger and supervise agent-generated PRVT builds that compile, package, and deploy fix candidates to validation setups automatically Verify Parallel Wireless products for functional, stability, performance, and user-experience aspects, with AI in the loop Review code (human-written and agent-written) for correctness, maintainability, and performance; contribute to design documents and architecture discussions Technical Leadership & Collaboration Mentor the QA-Dev team on agentic patterns, prompt engineering, tool integration, and evaluation of AI workflows for engineering tasks Define guardrails, eval harnesses, and quality metrics for agent outputs (RCA accuracy, fix-validity rate, test-coverage uplift, false-positive rate on monitoring) Collaborate cross-functionally with: FQG and RQG QA teams for feature verification and test planning PHY and Platform teams for integration and performance tuning PLM and System Architecture for product and architectural alignment Support customer deployments with expert-level (AI-assisted) troubleshooting Drive continuous improvement in tools, agent capabilities, and engineering processes What you must have: Experience Bachelor's or Master's (B.E./B.Tech. or M.E./M.Tech.) in Electronics, Communication, Computer Science, Electrical Engineering, or equivalent 8-12+ years in telecom software development and/or QA, with at least 3 years in a technical leadership role Hands-on experience in RAN development and/or testing Core Technical Skills Deep understanding of LTE / LTE-A protocol stack and Open RAN architecture ; strong grasp of 4G/5G call flows Thorough knowledge of 3GPP standards covering PHY, MAC, RLC, PDCP, RRC, S1AP, and X2AP protocols Strong programming in C/C++ and scripting in Python and Bash/Shell Solid working knowledge of LAN/WAN, WLAN, L2/L3 routing, TCP/IP, and QoS Proficiency on Linux/UNIX platforms Experience handling and troubleshooting User Equipment (mobiles) Experience with virtualization and vRAN deployment models Experience with test management and bug-tracking tools (e.g., JIRA ) AI / Agentic Skills (Required for this role) Practical experience using LLM-based coding and reasoning agents (e.g., Claude Code, Cursor, Copilot agents, or .
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.