AB-00PUBLIC / EVIDENCE-CONTROLLEDREV 2026.08.24
SSAbout

ABOUT / CONSTRUCTION RECORD

I design and define hardware.

I work at the architectural layer of silicon: specification definition, subsystem structure, interconnect and integration interfaces, and accelerator datapath organisation.

Professional position

I am Sundaram S S, a VLSI design and hardware architecture engineer based in Coimbatore, India, working as Deputy Head – Design Process at Zepto Logic Technologies Private Limited.

My public portfolio is intentionally narrower than my internal work. Current-employer programme names, architecture, collaborators, funding information, patent candidates and internal measurements are not published here.

FORMATION

Engineering education

M.E. VLSI Design

PSG College of Technology, Coimbatore · Anna University

CGPA 8.2Thesis record W-01 →

B.E. Electrical & Electronics Engineering

Kumaraguru College of Technology, Coimbatore

CGPA 8.5

Diploma · Electrical & Electronics Engineering

Kongu Polytechnic College, Perundurai

87%
CAPABILITY TAXONOMY

Hardware-first vocabulary

A / ARCHITECTURE

System and subsystem architecture definition · hardware specification authoring · design partitioning · architectural trade-off analysis · power/performance/area targeting.

B / INTERCONNECT

Network-on-Chip architecture · AMBA AXI4 / AXI4-Lite / AXI-Stream · bus and interconnect topology · integration interfaces · ready/valid boundaries · CDC structure.

C / DATAPATH

Modular arithmetic structures · transform engines · elliptic-curve arithmetic hardware · multiply-accumulate organisation · pipeline depth and resource sharing.

D / SECURITY

Hardware network security · root-of-trust concepts · post-quantum accelerator architecture · security-domain-bound execution · side-channel-resistant architecture as research direction.

E / VERIFICATION

Verilog RTL · UVM environment structure · Vivado · Cadence Genus synthesis · FPGA prototyping · resource and timing characterisation.

METHOD

Three operating principles

01

Architecture before implementation.

A programme is cheapest to correct while its interfaces and contracts are still definitions.

02

Evidence before claim.

A capability statement is only as strong as the artifact that can defend it.

03

Reuse with explicit boundaries.

Shared resources are valuable when arbitration, ownership and verification remain visible.