Solutions Engineer

Role purpose

Be the technical authority in front of the customer. This role converts user-force operational problems into a defensible V-BAT-based solution architecture, payload and communications configuration, CONOPS and integration path and carries that solution credibly through briefings, demonstrations, trials and evaluations. It is equally the channel that carries validated customer requirements back into the product roadmap.

Key responsibilities

Pre-sales technical authority

• Own technical engagement with Army, Navy, Air Force, Coast Guard, paramilitary and central armed police forces, plus MoD testing and evaluation establishments.
• Build and deliver capability briefs, technical presentations and CONOPS packages tailored to each user's mission set — ISR, targeting, artillery observation, maritime domain awareness, border and coastal surveillance, counter-insurgency.
• Handle technical objections and comparative questions; establish JSW's position against competing Group 2/3 and VTOL offerings on measurable parameters.
• Plan and technically lead demonstrations, captive trials and user evaluations jointly with Flight Operations.

Solution architecture and integration

• Define mission architectures: airframe configuration, EO/IR and signals payload selection, LOS and SATCOM/BLOS communication paths, ground control station and C2 integration, data links, and interoperability with customer BMS/C4I and imagery exploitation chains.
• Assess and specify third-party sensors, payloads and ground segment elements; run trade studies on endurance, range, payload weight, resolution, latency and link budgets.
• Produce solution documentation: system block diagrams, interface definitions, integration plans, environmental and EMI/EMC considerations, and deployment footprint (crew, GSE, transport, launch/recovery).
• Support technical inputs to bids and tenders: GSQR/QR compliance matrices, technical bid documents, deviation statements and clarification responses aligned to DAP/DPP procedure.

Requirement capture and product feedback

• Systematically capture user requirements, field observations and trial findings; maintain a structured requirements register mapped to platform capability.
• Translate captured requirements into product roadmap inputs, variant definitions and indigenisation/localisation priorities; work with Engineering and the OEM partner on feasibility, cost and schedule.
• Advise on bid scope — spares provisioning, maintenance concept, training load, AMC/CMC and lifecycle cost — so commercial proposals are technically grounded.

Market and programme intelligence

• Track user-force procurement documents, RFIs, EOIs and emergency/fast-track procurement routes relevant to UAS; assess technical fit and shape early requirements where permissible.
• Maintain a competitive technical database of Indian and international Group 2/3 UAS offerings.

Eligibility and experience

• Mandatory: Armed Forces Techincal Officer (Preferred - Flight Test Engineer) with 10+ years of service from a technical branch (EME/Signals/Army Aviation technical, Naval Air Technical/Electrical, IAF Engineering — Aeronautical Mechanical/Electrical, or equivalent).
• Direct exposure to UAS, aviation, avionics, EW/SIGINT, communications or sensor systems in service — operations, maintenance, trials, or QA/inspection.
• Demonstrated ability to write and defend technical documents — trial reports, QRs/GSQRs, evaluation inputs, staff papers.
• Comfort engaging Service HQ directorates, Commands and testing establishments; understanding of the Indian procurement lifecycle (DAP 2020, trial directives, staff evaluation, TEC/CNC stages).
• Preferred: Post-service experience in a defence OEM, systems integrator or pre-sales/solutions role; familiarity with SATCOM/BLOS architectures, mission planning software, or ISR data exploitation workflows.
• Preferred: Engineering masters degree; exposure to systems engineering practice (requirements management, V-model, interface control).

Competencies

Deep technical fluency paired with commercial instinct • ability to simplify a complex architecture for a decision-maker in ten minutes • disciplined documentation • credibility with serving officers • collaborative posture with engineering rather than adversarial • high ownership in a lean team.

Success measures (first 12 months)

Requirements register operational and feeding roadmap decisions; technical compliance achieved on all bids submitted; successful technical clearance through demonstrations and trials pursued; defined and validated at least two customer-specific solution configurations; competitive technical positioning pack maintained and used across the BD team.