Job Description

The Innovation team runs several grant- and NRE-funded robotics projects at once. Each has its own partner, milestones, parts list and evidence requirements. Today the schedule, parts and paperwork for each project sit with whoever is closest to it. When something slips, it slips quietly, and claims wait on missing documents.

We are fixing this with Innotracker, our own tracker for schedules, documents, procurement and grant claims across every project. It is still being built. This role runs the team’s operations through it, and owns its scope and schedule until it is done.

Delivery schedule

• Run every active project’s schedule and Gantt in Innotracker, the team’s own tracker: owner, next milestone, date and status
• Do all tracking and ops work through Innotracker, and lead the move of remaining projects across from Notion
• Run the weekly schedule check with project leads; flag any milestone at risk at least two weeks before it is due
• Prepare the project status input for the VP’s monthly review

Innotracker scope and schedule

• Own the scope and build schedule for Innotracker, working with the AI team who build it
• Turn what the team needs into clear requirements, priorities and acceptance tests for each module: schedules and Gantt, document repository, procurement ops and grant claims workflow
• Hold the release schedule and sign off each module once it works for the people using it

Clearing blockers

• Propose ways through blockers from your own experience and knowledge, not just escalate them
• When the situation calls for it, take over execution of the fix yourself, technical work included: integration debugging, part substitution, fixture or wiring rework, test scripts
• Log each blocker, fix and lesson in Innotracker so the team does not hit the same problem twice

Prototype to production, and commercial demand

• Take products past the grant-funded MVP towards production grade: design-for-manufacture changes, target BOM cost, production-grade suppliers, certification and regulatory path, service and maintenance plan
• Run the prototype-to-production gate and prepare products for handover into LionsBot production
• Give sales and prospects the ops support that builds demand: demo units, trial logistics, technical set-up, and cost inputs for quotes

Build and prototype operations

• Turn engineering designs into build plans: BOM, make or buy, lead times and build dates
• Track every prototype build from parts-in to test-complete
• Keep a parts and inventory register for innovation builds, and reuse existing LionsBot parts (R3, R5, S3 platforms) where it saves cost or time

Procurement and suppliers

• Run RFQs, compare quotes, raise POs and chase deliveries for prototype and niche parts, tracked in Innotracker procurement ops
• Work directly with China-based suppliers in Mandarin, and with LionsBot supply chain, warehouse and hardware colleagues on sourcing
• Check every quote against the spec before a PO goes out, so wrong-part or wrong-spec orders are caught early

Internal | LionsBot International | Engineering Operations Lead

• Make sure every innovation invoice, including bulk and warehouse purchases, reaches NetSuite coded to the right project

Grant and claims

• Run the grant claims workflow in Innotracker: collect evidence, verify, compile, send for VP approval, submit
• File evidence as the work happens: quotes, POs, invoices, delivery orders, test records and photos, sorted into each grant’s claim categories
• Apply each agency’s rules: qualifying date (BCA uses delivery date; IMDA and ESG use invoice date) and no double-counting across grants or projects
• Keep supplier and quality records that stand up to partner and grant-body audits

Field and deployment operations

• Plan shipping, site access, permits and on-site set-up for showcases, pilots and deployments
• Work with pre-sales and connectivity colleagues on field testing

Development operations

• Keep version-controlled build records for each prototype in Innotracker: BOM revisions, firmware and software versions, configuration and test logs
• Keep the team off side trackers and chat history: if it is not in Innotracker, it did not happen