Processor Architecture Trainee
DECCANX
This job at a glance
- Who can apply
- Freshers and up to 1 year
- Must know
- PythonC++ExcelGit
- Work
- On-site in Bengaluru
- Pay
- Not stated by the employer.
- Skill demand
- Python34%C++16%Git14%Excel3%of 99 similar fresher jobs posted in India this week
- Listed
- 1 Nov 2026 · still open
Sign in free to see which of these skills your resume already shows.
About the Role
This role is for graduates who are fascinated by how processors are organised: pipelines, caches, branch prediction, and the way a many-core design shares memory. You will study the microarchitecture behind DECCANX designs, including the 13-stage RISC-V core and the N1X-TITAN GEN1 architecture target, and test ideas through small simulation experiments.
Key Responsibilities
- Study pipeline stages, hazards, forwarding, and branch prediction in DECCANX processor designs.
- Build simple cycle-level models in C++ or Python to test architectural ideas.
- Compare design options and write up trade-offs for review.
- Check architecture documents for consistency and flag contradictions.
- Support RTL engineers by clarifying intended behaviour from the specification.
- Summarise findings as short, evidence-based design notes.
Requirements & Tech Stack
- C++
- Python
- RISC-V toolchain
- Spreadsheets and plotting
- Git
Qualifications
- Computer architecture fundamentals: Strong Pipelining, caches, memory hierarchy, and ISA concepts are the daily vocabulary.
- Digital logic: Working knowledge. You need to reason about what hardware can do in a cycle.
- C++ or Python for modelling: Working knowledge. Experiments are written as small simulators and analysis scripts.
- RISC-V instruction set basics: Working knowledge. DECCANX cores are RISC-V based.
- Analytical reasoning with numbers: Strong. Trade-offs are argued with calculations, not opinions.
Nice to have:
- Familiarity with a cycle-accurate simulator.
- Exposure to parallel computing concepts.
- Reading research papers on microarchitecture.
What you will learn
- Out-of-order execution concepts: rename, issue, wakeup, retirement.
- How parallelism is exploited at instruction, thread, and data level.
- Writing architecture decision records.
Your first 90 days
- First 30 days: Read the architecture specs and reproduce one pipeline diagram from first principles.
- Days 31 to 60: Build a small model that answers one architectural question.
- Days 61 to 90: Write and present a design note with recommendations.
Who fits: You enjoy asking why a design is shaped the way it is and can defend a conclusion with numbers.