New opportunity

Research Fellow (Computer Science / Software Engineering / Artificial Intelligence)

Nanyang Technological University · Singapore

About this role

Nanyang Technological University seeks a Research Fellow for the Desay SV Transfer Project at its main campus in Singapore. The role advances research and industry translation in software engineering and cybersecurity, particularly the industrialization of open-source component detection and emulation-based fuzz testing for automotive software. The fellow will work with academic researchers and industry engineers to turn research prototypes into deployable, high-performance solutions meeting industrial requirements.

Responsibilities

  • Develop and optimize scalable binary analysis frameworks and automated open-source component detection systems.
  • Design and improve emulation-based fuzz testing frameworks and automated security testing pipelines for embedded MCU and SOC platforms.
  • Apply AI and large language model techniques to program understanding, program analysis and vulnerability assessment.
  • Support system integration, benchmarking, deployment and technical documentation.

Requirements

  • PhD in Computer Science, Software Engineering, Artificial Intelligence or a related discipline.
  • Strong research record in software engineering, AI for code or software security, such as publications in reputable international venues.
  • Experience in program analysis, intelligent software systems or LLM-based code intelligence; strong Python and/or C/C++ programming skills.
  • Ability to work independently and collaboratively on joint academic–industry projects.

This is a full-time position. Only shortlisted candidates will be notified.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

AI for codeLarge language modelsProgram analysisBinary analysisOpen-source component detectionEmulation-based fuzz testingVulnerability assessmentSoftware securityCybersecurityPythonCC++Embedded systemsBenchmarkingSystem integrationTechnical documentation

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Industrialize component detection

    Develop and optimize scalable binary analysis and automated open-source component detection for automotive software; the project explicitly aims to move these technologies toward industrial use.

  • Advance embedded fuzz testing

    Design and enhance emulation-based fuzz testing frameworks and automated security testing pipelines for embedded MCU and SOC platforms.

  • Apply AI to security analysis

    Use AI and LLM-based techniques to improve program understanding, program analysis, and vulnerability assessment.

  • Make research deployable

    Support integration, benchmarking, deployment, and technical documentation so research prototypes become high-performance solutions aligned with industrial requirements.

  • Contribute research across teams

    Bring a strong research track record while working independently and with academic researchers and industry engineers on the joint project.

Likely challenges to think through

  • Detection accuracy versus scale

    A likely difficulty is maintaining useful component-identification accuracy while scaling binary analysis. Prepare to explain how you would benchmark detection quality, runtime, and failure cases before optimizing a prototype.

  • Emulation fidelity versus testing reach

    Embedded MCU and SOC fuzzing may require trade-offs between faithfully modeling an environment and running enough tests to find vulnerabilities. Prepare a reasoned approach to validating emulator behavior and measuring testing coverage; the posting does not specify a particular platform or metric.

  • Research novelty versus industrial readiness

    Turning AI-driven analysis and fuzzing prototypes into deployable systems may expose tension between experimental gains and reproducible performance, integration, and maintainability. Prepare examples of how you would validate results, document limitations, and coordinate decisions with researchers and engineers.

03

Practice your answers

Technical practice

How would you design a scalable binary analysis framework for automotive software?

What to coverThe role calls for developing and optimizing scalable binary analysis. Preparation suggestion: explain how you would structure analysis stages, handle large collections of binaries, and measure throughput against analysis quality.

How would you detect open-source components in a binary when source code is unavailable?

What to coverAutomated open-source component detection is a central project focus. Preparation suggestion: discuss candidate matching signals, how compiler changes could affect them, and how you would assess false matches and missed components.

How would you improve emulation-based fuzz testing for an embedded MCU or SOC?

What to coverThe posting calls for enhancing emulation-based fuzz testing in embedded environments. Preparation suggestion: explain how you would identify emulation gaps, preserve useful device behavior, and balance fidelity against test throughput.

How would you evaluate whether an embedded fuzzing framework is finding useful security issues?

What to coverThe role includes fuzz testing and vulnerability assessment. Preparation suggestion: discuss suitable measures such as execution progress, reproducible failures, and the effort required to distinguish security-relevant findings from noise.

How would you build an automated security testing pipeline around binary analysis and fuzzing?

What to coverAutomated security testing pipelines for MCU and SOC platforms are explicitly part of the role. Preparation suggestion: describe how analysis outputs could feed test selection, how results would be retained for investigation, and where automation needs human review.

Where could AI or LLM techniques improve program understanding and analysis?

What to coverThe posting calls for AI-driven program understanding and LLM-based improvements to program analysis. Preparation suggestion: identify a bounded task, the program evidence a model would use, and how you would compare its output with a non-LLM approach.

How would you use an LLM to assist vulnerability assessment without over-trusting its conclusions?

What to coverLLM-based techniques and vulnerability assessment are both stated responsibilities. Preparation suggestion: distinguish a model-generated lead from a verified finding, and explain how code or binary evidence and reproducible tests could support validation.

How would you benchmark a research prototype before translating it into an industrial solution?

What to coverThe fellow will support benchmarking and turn research prototypes into high-performance solutions aligned with industrial requirements. Preparation suggestion: define representative workloads and baselines, then discuss trade-offs among detection quality, runtime, and resource use.

What would you check when integrating and deploying these research systems?

What to coverSystem integration and deployment are listed responsibilities. Preparation suggestion: discuss interface compatibility, repeatable operation, failure handling, and the technical documentation needed for others to use and maintain a solution.

How would you divide implementation work between Python and C or C++?

What to coverThe requirements name strong Python and/or C/C++ programming skills, and the work includes performance-sensitive analysis systems. Preparation suggestion: explain trade-offs involving iteration speed, runtime performance, and maintainability without assuming a particular language stack is prescribed.

Behavioural practice

Tell me about a time you worked independently on an open-ended research problem.

What to coverThe role requires independent work in a research setting. Preparation suggestion: use a real situation, the decisions and actions you took without close direction, and a concrete result or lesson.

Describe a time you collaborated with researchers and engineers who had different priorities.

What to coverThe posting emphasizes joint academic–industry work. Preparation suggestion: give a real example of the differing priorities, how you resolved or managed them, and what the collaboration produced.

Tell me about a time you moved a research idea or prototype toward practical use.

What to coverTranslating research prototypes into deployable solutions is part of this role. Preparation suggestion: explain the initial limitations, your actions to address practical constraints, and the observed result; do not imply a specific deployment process at NTU.

Describe a time you had to communicate a complex technical result to another team.

What to coverThe role includes technical documentation and collaboration with industry engineers and academic researchers. Preparation suggestion: describe the audience and situation, how you adjusted your explanation or documentation, and the outcome.

Tell me about a time an evaluation challenged your research approach.

What to coverThe posting calls for a strong research track record and support for benchmarking. Preparation suggestion: use a real example that explains the evaluation evidence, how you changed course or defended a trade-off, and the resulting finding.

02

Sharpen your knowledge

Topics to prepare

  • Binary analysis and component detection

    The role calls for scalable binary analysis and automated open-source component detection. Revision exercise: explain how you would identify a component in a binary, validate a match, and account for false positives and scale.

  • Emulation-based fuzz testing

    The posting focuses on fuzz testing automotive software in embedded MCU and SOC environments. Revision exercise: sketch a testing loop from emulated execution through input generation, failure detection, and reproduction; identify likely limits of emulation.

  • AI-assisted program analysis

    The role applies AI and LLM techniques to program understanding, analysis, and vulnerability assessment. Revision exercise: outline one use case and explain how you would check its findings against analysis evidence rather than accept model output uncritically.

  • Research-to-industry translation

    NTU seeks to turn research prototypes into deployable, high-performance solutions with academic and industry collaborators. Revision exercise: frame a research contribution, the evidence supporting it, and the trade-offs you would discuss when adapting it to industrial requirements.

  • Security-system evaluation

    Benchmarking and scalable performance are explicit responsibilities. Revision exercise: propose measures for detection accuracy, fuzz-testing effectiveness, and runtime cost, then explain what comparison would make a reported improvement credible.

Skills to revise

  • Python or C/C++ implementation

    Strong programming skills in Python and/or C/C++ are required. Practice suggestion: implement a small binary-analysis or test-input-processing routine in a language you use, then review its correctness, error handling, and performance.

  • Component-detection prototyping

    The role develops automated open-source component detection systems. Practice suggestion: build a small detector over a controlled set of binary samples, record its matches and mismatches, and explain how you would improve it.

  • Embedded fuzz-test workflow

    The role designs emulation-based fuzz testing and automated security testing pipelines. Practice suggestion: draft or prototype a minimal emulated test workflow that generates inputs, records failures, and preserves inputs needed to reproduce them.

  • Benchmarking and technical documentation

    Integration, benchmarking, deployment, and documentation are stated responsibilities. Practice suggestion: prepare a reproducible benchmark plan and a short integration note covering inputs, outputs, performance results, and known limitations.

04

Your preparation checklist

  • Assemble a research and technical evidence sheet

    The posting asks for a relevant PhD, a strong research record, program-analysis or code-intelligence experience, and Python and/or C/C++ skills. Prepare a one-page index of relevant publications and work, noting your contribution and evidence for each requirement; leave out claims you cannot substantiate.

  • Rehearse a binary-analysis project walkthrough

    Prepare one relevant example, if available, showing the problem, your design decisions, implementation, evaluation and limitations. Relate it to the role’s focus on scalable binary analysis and automated open-source component detection.

  • Sketch an embedded fuzz-testing design

    As a preparation exercise, draw an emulation-based fuzz-testing pipeline for an MCU or SOC target. Be ready to explain input generation, execution feedback, failure triage and what you would need to validate on a real target; this is a proposed design, not a stated NTU architecture.

  • Prepare an AI-for-code evaluation example

    Select a relevant research result or proposed experiment using AI or LLMs for program understanding, analysis or vulnerability assessment. Specify the baseline, evaluation data, error checks and limitations rather than assuming an AI approach will outperform alternatives.

  • Outline a prototype-to-deployment plan

    The role includes integration, benchmarking, deployment and technical documentation with academic and industry collaborators. Draft a short plan covering performance measurements, integration risks, reproducible tests and the documentation needed to hand off a prototype.

  • Write questions for the project team

    Ask which automotive binaries or embedded targets are in scope, how component detection and fuzz testing will be evaluated, and what deployment constraints matter most. These are questions to clarify industrial requirements, not assumptions about the project.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: 4 Nov 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in Singapore. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…