Security Engineer Intern (Firmware)

Learn firmware security, check what our engine finds in real device firmware, then improve the engine's code. A remote internship in India for freshers.

Engineering

Employment
Internship, 6 months, full-time
Location
Remote, based in India
Experience
Freshers welcome
Equipment
Your own laptop (BYOD)
After the internship
Full-time role for interns who do well
Posted

About the role

About MAGDOX

MAGDOX Private Limited is an early-stage cybersecurity startup based in India. We build FDIE (Firmware Delta Intelligence Engine), a platform that checks the firmware inside connected devices such as cameras, routers and IoT products for security problems. It helps device makers find and fix issues before a security test lab, a tender or a customer finds them, and prepare the evidence those reviews ask for.

We serve device makers in India, Europe, the UK and the US. FDIE runs in three regions, India, the EU and the US, and each customer chooses where its data is kept.

The role

We are looking for a Security Engineer Intern (Firmware). FDIE reports the components inside a firmware image and the public vulnerabilities that may affect them. You will check those results against the evidence in the image's own files, find out why the engine gets some of them wrong, and then fix those causes in the engine's code, so it improves for every customer. This is a full-time, remote internship based in India for freshers; you do not need a degree. You do not need to know security yet either: we teach it in a structured two-week programme, and a supervisor works with you every day. We are hiring for the long term: interns who do well are offered a full-time role at the end of the internship.

What you will do

  • Learn how device firmware is put together: the bootloader, the Linux kernel, file systems, BusyBox and the libraries devices ship
  • Read public vulnerability records (CVE, CVSS, CWE) and work out what each one needs: which component, which versions, which code
  • Check, from the files in a firmware image, whether a reported vulnerability really applies, using Linux tools such as strings, grep, readelf and find
  • Write down your evidence clearly, so anyone on the team can check your conclusion in two minutes
  • Find the patterns behind wrong results and fix them in our firmware engine, written in Python, with tests that prove the fix
  • Work alongside a second person on the same results, then compare and discuss your conclusions

What we are looking for

  • Programming in Python: you can write a script that reads files, searches them and prints a clear result
  • Reading C: you can follow what a short C function does
  • Comfort with the Linux command line: moving around files and folders, reading and searching text
  • Git basics: cloning, committing and opening a pull request
  • Care and patience: you check before you conclude, and you say so when you are not sure
  • Clear written English: you can explain in a few sentences how you reached a conclusion
  • Your own laptop for work (Bring Your Own Device) that meets the security requirements under Work setup

Good to have

  • A degree or studies in electronics and communication engineering (ECE), computer science (CSE) or information technology (IT)
  • Cybersecurity knowledge from coursework, certifications, capture-the-flag competitions or your own projects
  • Embedded or microcontroller projects, for example with ARM, ESP32, STM32 or a Raspberry Pi, and hardware interfaces such as UART or JTAG
  • Reverse engineering with open-source tools such as Ghidra
  • Knowing software bill of materials formats such as CycloneDX or SPDX, and how CVSS scores and VEX statements work
  • A vulnerability you reported responsibly, or a credit in a security advisory
  • Networking basics: TCP/IP, DNS, DHCP and HTTP

How you will learn

  • A structured two-week onboarding with written lessons, worked examples and practice tasks with answers
  • A supervisor who answers your questions every day and reviews your work every week
  • Every change you make is reviewed before it is merged, so you learn from each review

Work setup

  • This is a Bring Your Own Device (BYOD) role: we do not provide a laptop
  • Your own laptop (Windows, macOS or Linux) that can run a modern browser and video calls, and a reliable internet connection
  • On that laptop: a supported operating system with updates switched on, full-disk encryption, a screen lock, antivirus switched on, and a separate user account for work that only you use
  • A smartphone for two-step sign-in
  • We provide your company email and access to the systems you need. You work on firmware and code inside our secure work environment: nothing is copied to your laptop or personal storage, and you sign a confidentiality agreement before you start

Why join us

  • Learn firmware security, a specialist skill few freshers get to practise, on the software of real devices
  • Your analysis and your code directly improve a product that device makers use
  • Work closely with a small, supportive team where your work is visible
  • Interns who do well are offered a full-time role at the end of the internship

We value care, curiosity and clear thinking over degrees and marks. If you are a fresher who likes taking things apart to see how they work, we would like to hear from you.