Byte
Join Us
Recruitment Task • Electronics

Electronics Tasks

Electronics tasks

Start with Task 1. Task 2 adds weight to your submission; Task 3 is an optional X-factor bonus.

// ACCESS LOCKED //

Problem Statements Locked

Tasks for Electronics will be revealed on 25 SEP 2026 • 15:00 IST.

00// DAYS //
00// HOURS //
00// MINS //
00// SECS //

Review the submission instructions while you wait for the tasks to unlock.

Required · All years3 Core Requirements

Task 1: Redundant Sensor Voting

Build an Arduino system that reads two potentiometers as redundant sensors and decides the output position reliably, including when the readings disagree or reach a boundary.

Concept & Inspiration

Electronics Task 1 is mandatory for shortlisting. You may use Wokwi; its Automation Scenarios can drive both potentiometers programmatically for testing.

Accepted Stacks:
ArduinoWokwi (public / unlisted link)Code.txt

Core Requirements

  • Submit a public/unlisted Wokwi project URL in Link.txt containing only the raw URL. If using physical hardware, submit Demo.mp4 instead.
  • Submit the complete Arduino sketch as plain text in a file named Code.txt (not .ino).
  • Include Design_rationale.docx, 150 to 250 words, explaining your threshold value and why, how “hold last position” works, and how you prevent flicker at the boundary.

Rationale should explain

  • Your disagreement threshold and why you chose it.
  • How the system holds the last valid position when readings disagree.
  • How you prevent rapid switching/flicker near the decision boundary.
Required · Second year3 Core Requirements

Task 2: Simon Says with Heartbeat

Build a Simon Says game with a heartbeat LED. Make the game’s speed increase with a clear ramp, while keeping the heartbeat indicator independent of game state.

Concept & Inspiration

Task 2 carries additional weight. Under the year-based criteria, second-years must attempt it in addition to Task 1.

Accepted Stacks:
ArduinoWokwi (public / unlisted link)Code.txt

Core Requirements

  • Submit a public/unlisted Wokwi URL in Link.txt containing only the raw URL. If using physical hardware, submit Demo.mp4 instead.
  • Submit the complete Arduino sketch as plain text in a file named Code.txt (not .ino).
  • Include Design_rationale.docx, 150 to 250 words, explaining your speed ramp formula and how the heartbeat LED remains independent of game state.

Rationale should explain

  • Your speed-ramp formula and how it changes the game over time.
  • How the heartbeat LED timing remains independent from the game logic/state.
X-factor · Optional4 Core Requirements

Task 3: MPU6050 KiCad Schematic

Create an MPU6050 KiCad schematic. PCB layout may be included if attempted. This is an optional bonus-on-bonus task and is not required for shortlisting.

Concept & Inspiration

The submitted archive must be produced using KiCad’s own “Archive Project” (or equivalent zip-project) function. Do not manually zip a folder: KiCad’s built-in archive preserves file references so the project opens without path errors.

Accepted Stacks:
KiCadNative project archive

Core Requirements

  • If attempted, include a Task3/ folder containing MPU6050.zip, generated by KiCad’s native project-archive function, and Design_rationale.docx.
  • Include any PCB layout in the same native project archive.
  • Write a 200 to 350 word rationale covering your decoupling and pull up value choices and why you tied AD0 the way you did.
  • Omit the entire Task3/ folder if you did not attempt this bonus.

Rationale should explain

  • Why you selected your decoupling and pull-up values.
  • How you connected AD0 and the reasoning behind that choice.
  • Any relevant schematic or PCB design tradeoffs.

Electronics / Submission guide

Submit your Electronics work

Submit a single Google Drive folder containing the Electronics tasks required for your year through the website upload form. This folder is for Electronics only.

01 First year

Complete Electronics Task 1.

02 Second year

Complete Electronics Tasks 1 & 2.

✳ X-factor

Electronics Task 3 is optional bonus-on-bonus for any year. Omit its folder if you don't attempt it.

Electronics folder structure

Name your folder <YourName>_Electronics. Your identity is already captured at login; do not repeat it in the files.

<YourName>_Electronics/
├── Task1/
│   ├── Link.txt  (or Demo.mp4 for hardware)
│   ├── Code.txt
│   └── Design_rationale.docx
├── Task2/
│   ├── Link.txt  (or Demo.mp4 for hardware)
│   ├── Code.txt
│   └── Design_rationale.docx
└── Task3/  (bonus; omit if not attempted)
    ├── MPU6050.zip
    └── Design_rationale.docx
  • Use exact file names. Save sketches as plain-text Code.txt, not .ino. Each Link.txt must contain only the raw Wokwi URL.
  • Tasks 1 and 2 each need a public/unlisted Wokwi link (or a demo video for physical hardware), code, and a 150 to 250 word rationale. Wokwi Automation Scenarios can drive both Task 1 potentiometers.
  • For bonus Task 3, use KiCad’s native Archive Project function to create MPU6050.zip (not a manually zipped folder). Include any PCB layout and a 200 to 350 word rationale in that archive/folder.

Make every link accessible

Set your Drive folder to Anyone with the link: Viewer. Wokwi projects must also open without a login. Restricted links count as not submitted; test every link in an incognito window.

Explore Other Department Tasks

App DevelopmentBuild apps people actually use.
Web DevelopmentShip it. Then ship it faster.
ML ResearchModels that solve real problems.
Applied MLBuild systems that reason and take action.
CADDesign it. Assemble it. Make it work.
ROSRobot Operating System
CybersecurityBreak things. Then figure out why.
Graphic DesignMake BYTE impossible to scroll past.
Video EditingTurn raw footage into a story.
OutreachRead the room. Make the ask.