Lead Integration Engineer

Role: System Integration Lead

Location: Gurugram, India (In-Office)

About Walker Digital Table Systems (WDTS) Walker Digital Table Systems (WDTS) Headquartered in Las Vegas, with teams across India, Macau, Australia, and the US, WDTS is known for its industry-leading Perfect Pay Baccarat Table Network and proprietary PJM RFID technology — a proven RFID protocol designed for the speed, volume, and complexity of live casino environments.

WDTS builds digital table game technology for the global gaming and casino industry. Our platforms power live and electronic table games at casinos worldwide, combining real-time systems, distributed architecture, and player-facing technology at scale. Our India team in Gurugram is a core engineering hub building the products that run on casino floors globally.

WDTS is a global gaming technology company building intelligent, secure, and high-performance table game solutions for the casino gaming industry.

Website:

LinkedIn Page:

About the Role

We are looking for a Systems Integration Lead to work directly with the CTO and provide a consolidated view across our software, hardware, systems, and customer-delivery activities.

As a systems company, our success depends on more than individual software or hardware teams completing their work. Hardware, software, firmware, infrastructure, manufacturing, testing, deployment, and customer readiness must come together as one functioning system. This role will ensure that these interconnected workstreams remain aligned.

The Systems Integration Lead will serve as the connective layer between the CTO and our technical and operational teams. This person will develop a clear understanding of what is happening across the organization, identify dependencies and readiness gaps, surface risks early, and help drive issues to resolution.

This is not necessarily a deeply hands-on engineering position. The ideal candidate will have enough technical fluency to work credibly with software and hardware teams, ask effective questions, understand dependencies, and translate complex information into a clear, integrated view for the CTO.

Key Responsibilities

Provide an Integrated Systems View

• Maintain a consolidated view of progress across software, hardware, firmware, testing, manufacturing, deployment, and other relevant workstreams.

• Evaluate readiness at the complete-system level—not simply whether an individual team has completed its portion of the work.

• Ensure that hardware availability, software compatibility, configuration, testing, documentation, deployment, and customer readiness remain aligned.

• Develop system-level dashboards, readiness assessments, milestone views, and executive summaries.

Partner Directly With the CTO

• Work closely with the CTO on day-to-day technical, operational, and organizational priorities.

• Provide concise, reliable updates on overall system status, major risks, dependencies, decisions, and areas requiring leadership attention.

• Prepare information and analysis needed for technical reviews, planning discussions, customer commitments, and executive decisions.

• Follow up on CTO priorities and help coordinate their execution across teams.

Coordinate Across Software and Hardware Teams

• Build strong working relationships with software, hardware, firmware, systems, product, manufacturing, quality, deployment, and customer-facing teams.

• Connect plans and milestones across functions so that teams understand how their deliverables affect overall system readiness.

• Identify conflicting assumptions, schedules, requirements, configurations, and priorities.

• Facilitate cross-functional reviews and ensure decisions, owners, and next steps are clearly documented.

• Help teams resolve integration issues and escalate matters that require executive attention.

Manage Dependencies and Risks

• Identify system-level dependencies, blockers, and delivery risks before they affect customer or business commitments.

• Track critical decisions, open issues, integration gaps, and ownership through resolution.

• Challenge isolated declarations of readiness when dependent components or teams are not yet ready.

• Distinguish between component completion and true end-to-end system readiness.

• Create clear escalation paths for issues that cannot be resolved within individual teams.

Improve System Readiness and Operating Processes

• Establish and continuously improve system-level planning, integration, and readiness-review processes.

• Define practical criteria for development readiness, integration readiness, release readiness, shipment readiness, and customer deployment readiness.

• Promote end-to-end thinking and shared accountability across the organization.

• Help improve the quality, consistency, and transparency of information provided to technical leadership.

• Capture lessons learned and ensure they improve future planning and execution.

What Success Looks Like

• The CTO has a clear, current, and trusted view of overall system status.

• Software and hardware plans are coordinated around shared system and customer milestones.

• Dependencies and readiness gaps are identified early rather than during shipment or deployment.

• Teams have clear ownership of cross-functional issues, decisions, and follow-up actions.

• Customer commitments reflect the readiness of the complete solution.

• Leadership spends less time reconstructing status from separate teams and more time making informed decisions.

• The organization increasingly operates as a systems company rather than as disconnected software and hardware functions.

Qualifications

• Experience in systems engineering, technical program management, systems integration, engineering operations, product development, or a similar cross-functional role.

• Demonstrated experience coordinating complex initiatives, preferably involving both software and hardware. However hardware experience is not a blocker.

• Strong understanding of product-development and delivery lifecycles.

• Sufficient technical fluency to engage with engineering teams and understand interfaces, dependencies, constraints, and tradeoffs.

• Strong organizational, analytical, and problem-solving abilities.

• Excellent written and verbal communication skills, including the ability to communicate clearly with both engineers and executives.

• Experience creating executive-level status reports, risk assessments, readiness reviews, and cross-functional plans.

• Ability to operate effectively in an environment with evolving priorities and incomplete information.

• Strong judgment, follow-through, and attention to the details that affect overall system outcomes.

• Ability to influence teams and drive alignment without relying solely on direct authority.

Preferred Qualifications

• Experience in a company that develops and delivers integrated hardware-software systems.

• Familiarity with firmware, embedded systems, cloud services, manufacturing, validation, deployment, or field operations.

• Experience supporting a CTO, VP of Engineering, Chief Engineer, or another senior technical leader.

• Experience with customer deployments and release or shipment-readiness processes.

• Familiarity with technical program-management, systems-engineering, or product-lifecycle tools and methodologies.

Ideal Candidate Profile

The ideal candidate is a systems thinker who naturally connects information across organizational and technical boundaries. They are comfortable moving between executive discussions and detailed conversations with engineering teams.

They do not need to be the deepest technical expert in every discipline. However, they must be curious, technically credible, highly organized, and willing to ask difficult questions. They should recognize when a team’s deliverable is complete but the overall system is not.

This person communicates clearly, follows through consistently, and brings structure to complex situations without creating unnecessary bureaucracy. They are trusted by both leadership and engineering teams and can turn fragmented updates into a coherent picture of system readiness.

Reporting Relationship

This position reports directly to the CTO and works closely with leaders and teams across software, hardware, firmware, systems engineering, product, manufacturing, quality, deployment, and customer operations.

Important Role Distinction

This role is not limited to traditional technical integration or hands-on interface development. Its primary responsibility is to create alignment, visibility, and accountability across all elements required to deliver a complete, functioning system.