4+ QML Jobs in Delhi, NCR and Gurgaon | QML Job openings in Delhi, NCR and Gurgaon

The Opportunity: Building the "Eyes" of Industrial Inspection

At Octobotics, we are addressing the challenge of finding the right "Who" to build the next generation of autonomous industrial inspection systems. We aren't just looking for a coder; we are looking for a Strategic Lead Developer—a high-impact individual who can transform high-bandwidth hardware data into life-saving, intuitive user experiences.

This role is the critical link in our mission. Our autonomous platforms—serving the Oil & Gas, Rail, and Chemical sectors—generate massive sensor payloads that must be visualized in real-time to prevent catastrophic infrastructure failure. You will own the bridge between raw physics and the inspector’s fingertips, ensuring that sustained success and exceptional results are built into our interface.

Key Responsibilities: Where Systems Meet Strategy

• High-Throughput Engine-to-UI Integration: Architect and develop robust WPF (C#) and Qt (C++) applications capable of ingesting and processing sustained sensor data streams of 100–200 MBPS.
• Interoperability Bridge Engineering: Design, implement, and optimize the high-speed data layer (via C++/CLI, Shared Memory, or gRPC) that connects low-level C++ sensor drivers to our C#-based visualization tools used across diverse industrial environments.
• Performance Engineering & Hardware Acceleration: Implement advanced rendering techniques (DirectX/OpenGL) to ensure seamless, 60 FPS visualization of dense PAUT (Phased Array Ultrasonic Testing) datasets, eliminating UI jitter even under peak load.
• Cross-Sector Technical Leadership: Collaborate with the Principal Architect to define scalable data structures and communication protocols for inspection bots operating in specialized Oil, Gas, and Chemical facilities.
• Mission-Critical Reliability: Ensure the stabilization of our software culture by building cohesive, high-performing codebases that avoid the "ripple effect" of technical debt and hiring mistakes.

Required Experience: The Technical Blueprint

• WPF & C# Mastery: Extensive professional experience with XAML, MVVM, and sophisticated asynchronous programming. You must be able to handle high-frequency data notifications without overwhelming the UI Dispatcher.
• Qt/QML Proficiency: Proven track record of building modern, responsive, and performance-oriented interfaces in C++ that interface directly with hardware layers.
• High-Bandwidth Data Handling: Demonstrated experience managing massive data pipelines (100MBps+) where memory management and thread priority are the difference between success and system failure.
• Cross-Language Marshalling: Deep understanding of the performance trade-offs involved in moving data between managed (C#) and unmanaged (C++) memory spaces.
• Strategic Engineering Mindset: An innate ability to identify bottlenecks before they derail projects and the "scrappiness" to implement long-term architectural solutions in a lean startup environment.

Why Join Octobotics?

We offer a culture of excellence where roles are filled by high-performing individuals aligned with our goals and values. You will have the autonomy to choose the best tools for the job and the impact of seeing your work directly influence the safety of global energy and chemical infrastructure. We prioritize growth, meaningful work, and a clear sense of purpose.

Senior C++/Qt Backend Engineer

(High-Performance Systems)

Location: Noida (On-site)

Introduction: Who We Are

We are a lean, product-based startup building the next generation of industrial robotics. Our products are deployed in critical, high-stakes environments, including Railways, Oil & Gas, Chemicals & Fertilizers, and Offshore operations.

We are not just writing code; we are building rugged, intelligent machines that operate in the real world.

1. The Mission (Pure Backend Focus)

You will architect the high-performance C++ Backend of our robotics software.

• No UI Work: You will NOT be designing UI pixels or writing QML front-end code.
• The Engine: Your mission is to build the “invisible engine” that processes 50 Mbps of raw scientific data and feeds it efficiently to the UI layer.
• Ownership: You own the threads, the data structures, and the logic.

2. Critical Outcomes (The First 4 Months)

• Architect the Data Ingestion Layer:
• Design a C++ backend capable of ingesting 50 Mbps of live sensor data (from embedded hardware) without dropping packets or consuming excessive CPU.
• Decouple Backend from UI:
• Implement Ring Buffers and Lock-Free Queues to separate high-speed data acquisition threads from the main Qt Event Loop, ensuring the backend never freezes the UI.
• Crash-Proof Concurrency:
• Refactor the threading model to eliminate Race Conditions and Deadlocks using proper synchronization (Mutexes/Semaphores) or lock-free designs.
• Efficient IPC Implementation:
• Establish robust Inter-Process Communication (Shared Memory / Sockets) to allow the C++ backend to exchange data with other Linux processes instantly.

3. Strategic Outcomes (Months 5 Onward)

As the product matures, your focus will shift from “Building the Engine” to “Hardening and Scaling the Ecosystem.”

• Robust OTA & Redundancy:
• Implement Linux A/B Partitioning strategies. You will design the fallback mechanism where the system uses atomic updates to revert to the last known good configuration in case of an update failure, ensuring high availability in remote offshore locations.
• Containerized Deployment:
• Move from manual builds to automated deployment. You will containerize the application (Docker / Podman) and integrate it with Jenkins / GitLab CI to enable seamless remote deployment to the robot fleet.
• Remote Diagnostics Engine:
• Build the internal logic to capture, compress, and transmit critical system logs and core dumps securely to the cloud without saturating the robot’s bandwidth.
• Fleet Monitoring Infrastructure:
• Distinct from simple logging, you will architect the heartbeat and telemetry protocols that allow our central command to monitor the health of robots deployed in railways and chemical plants in real time.

4. Competencies (Must-Haves)

• Qt Core (Backend Only):
• Expert in QObject, QThread, QEventLoop, and Signal/Slot mechanisms. You understand how to push data to QML, but you don’t style it.
• High-Performance C++:
• You handle data at the byte level, preferring Circular Buffers (Ring Buffers) over standard vectors for streams.
• Concurrency Mastery:
• You know when to use Lock-Free programming to avoid thread contention and can manage interactions between Data Acquisition and Processing threads without bottlenecks.
• Design Patterns:
• Competence in Producer-Consumer (for streams), Singleton (hardware managers), and Factory patterns.
• Linux System Programming:
• Comfortable with IPC (Shared Memory, Unix Domain Sockets) and optimizing process priorities.

5. The “Squad” (Your Team)

• Embedded Engineers:
• They push the raw 50 Mbps stream to the OS; you write the drivers to catch it.
• UI / Frontend Developers:
• They handle QML / UX; you provide the data APIs they need.
• Robotics (ROS) Engineers:
• You ensure their heavy algorithms don’t starve your data acquisition threads.
• Testers:
• You ensure your code stands up to their stress testing.

6. Why This Role Defines Your Career

• Deep Backend Engineering:
• Escape the “button styling” trap. This is 100% logic, memory management, and architecture.
• Real Engineering Problems:
• Solve race conditions, memory leaks, and high-velocity data streams.
• Architectural Autonomy:
• You decide how the data moves and choose the patterns. You own the “Engine Room.”

The One-Line Mission

You are the Chief Architect of the Robot’s Brain. You are not just writing a module; you are engineering the Complete Production Application that runs on the robot. You define how the system boots, how it manages state, and how it integrates the Robotics Team's ROS-based logic into your high-performance C++ Core without sacrificing speed or safety.

What You Will Engineer (The Complete System)

1. The "Drishti-OS" Application Framework (Core Architecture)

• The Challenge: This is a mission-critical, real-time application running in an explosive zone.
• Your Job: You design the Main Application Lifecycle.
• State Machine: You define the strict logic for the robot's states (e.g., Booting $\rightarrow$ Self-Check $\rightarrow$ Ready $\rightarrow$ Scanning $\rightarrow$ Emergency Stop).
• The ROS Bridge: The Robotics Team uses ROS Middleware for navigation. You architect the efficient Inter-Process Communication (IPC) bridge that allows their ROS nodes to talk to your Real-Time C++ Core without introducing latency into the critical data path.
• Resource Management: You ensure the CPU/RAM are allocated efficiently so the "Data Pump" never starves, even while ROS is calculating trajectory.

2. The "Data Engine" (Ingestion, Sync & Calculation)

• The Challenge: High-velocity data (730 mm/s) meets precise location tracking.
• Your Job: You build the central engine that:
• Ingests: 128 channels of Ultrasonic data via the AFM API.
• Syncs: Merges this data instantly with the ROS-published coordinates (X, Y, Theta) from the Robotics Team.
• Processes: Runs the C++ "Stitching Algorithm" to map raw signals into a coherent buffer for the UI.

3. Production-Grade Safety & Watchdogs (The "Safety Net")

• The Challenge: We operate in explosive refineries (Zone 1).
• Your Job: You implement the Software Safety Watchdogs required for ATEX certification.
• System Health: Your code monitors the heartbeat of the ROS nodes. If the Robotics logic freezes, your architecture must trigger a safe emergency stop immediately.
• Hardware Safety: You monitor internal pressure and motor temperatures, overriding control loops if physical limits are breached.

4. Data Persistence (The Digital Twin Source)

• Your Job: You own the .DRISHTI binary file format. You ensure that what we write to the disk is a corrupt-free, memory-mapped exact replica of the inspection, ready for the Full Stack Team to ingest.

5. The "Immortal" Deployment Architecture

• Your Job: You define how the code gets to the robot. You architect the OTA (Over-The-Air) System with Atomic Rollbacks. If a new update fails to boot, your architecture ensures the robot automatically reverts to the previous working version.

Who You Will Interact With

You sit at the center of the engineering circle:

1. Robotics Engineers (ROS Team):

• They do: They use ROS (Robot Operating System) middleware to build the robot's kinematics, navigation, and control logic.
• You do: You provide the architectural framework they plug into. You ensure their ROS messages (Pose/Odom) are consumed efficiently by your Core System.

1. UI/UX Developer (Qt/QML):

• They do: They build the visual dashboard.
• You do: You provide the Backend API and Signals to drive their interface.

1. Full Stack Developers (Cloud):

• They do: They build the customer-facing Reporting Platform.
• You do: You define the .DRISHTI File Contract so they can perfectly parse the data you save.

The Tech Stack You Architect

• Core: Modern C++ (17/20) (Smart Pointers, Move Semantics).
• Integration: ROS / ROS2 (Subscribers, Publishers, Custom Messages).
• Framework: Qt 6 Core (Event Loop, State Machine Framework).
• OS Level: Linux System Programming (Systemd, Kernel Tuning, Watchdogs).
• Architecture: Multi-threaded Producer-Consumer, Lock-Free Buffers, Shared Memory.

Enpass Technologies Pvt. Ltd. (Gurugram) is seeking for an experienced Windows C++ GUI software developer. We have a product for securely managing the credentials across platforms through a native productivity app, GUI of which is written in Qt toolkit and we are looking for a talented, enthusiastic developer for the same.

JOB RESPONSIBILITIES:

• Design, build, and maintain efficient, reusable, and reliable Windows Qt/QML/C++ code.

• Implement performance and quality modules.

• Identify bottlenecks and bugs, and devise solutions to these problems.

• Help maintain code quality, organization, and automatization.

• Collaborate with cross- functional teams to define, design, and ship new features.

MUST HAVE SKILLS (Please do not apply if you do not fullfill this criteria):

* Desktop Applications using QT/Qml in Windows Environment

* Minimum 1 Year experience in Windows UWP development

• 4-6 yrs experience in C++11 or C++14 standerd.

• Very good knowlege of STL.

• Experience of Multithreading in ANSI C++

• Practical experience in Win32 apis.

• Basics of socket programming and inter process communication.

• Good understanding of REST apis and internet protocols in general.

• Must be able to write unit test.

GOOD TO HAVE SKILLS

* Experience with development of Qt Quick Controls 2 based applications

* Experience in software development for mobile or tablet devices

• Familiarity with Cryptography basic concepts.

• Familiarity with agile processes and development / SW quality practices such as code reviews.

• Expertise on methods and tools for CI and test automatization.

• Build distributable packages (msi or wix).