Every engineer here passed a scored technical interview in their specialization. You read the category breakdown before you talk to anyone.
Free to browse. Verification is one 30-minute interview, and engineers keep 100% of their billings.
Hiring and want to post first?
A fixed-scope review by a senior FPGA engineer. Your timing, CDC, reset, and datapath are examined against the claim your product makes, and you receive a prioritized findings report. No open-ended consulting.
Every posting is reviewed before publication and states its vacancy status. Verified engineers are matched first: get verified to be considered.
Loading open roles…
ShawSilicon is run by a working FPGA engineer, not a recruiter. One scoring scale for everyone, and a verified pool that's live today — engineers you can browse now, not a sign-up list.
The same engineer who designs the structured technical interview ships timing-closed RTL. His public benchmarks include a GNSS spoof/jam detector at 488.76 MHz, with flashattn-softmax and kvcache-compress both closed at 400 MHz. The bar on ShawSilicon is the bar he holds himself to.
One structured technical interview in your specialization — about 30 minutes, scored stage by stage on the same scale for everyone.
Real items from the FPGA / RTL Design track — the kind each engineer answers before any grade is shown. No multiple choice, no LeetCode.
You have 1,000 18-bit coefficients for a filter and need to store them on a Xilinx UltraScale FPGA. Walk through your decision process for choosing between BRAM, URAM, distributed RAM, and ROM inference — including resource cost, latency, and read port requirements.
Your 50 MHz write domain updates a 32-bit configuration register and signals a 200 MHz read domain to latch it. In lab, the read domain occasionally reads a mix of old and new bits — simulation was clean. Diagnose why the 2-FF synchronizer approach fails for multi-bit buses, design a correct toggle-handshake CDC scheme in RTL, and list the FPGA synthesis attributes your design requires.
You run timing analysis on a Xilinx UltraScale design and see this path report: setup slack = -0.3ns, data path delay = 4.8ns (3.1ns logic, 1.7ns route), clock path skew = +0.15ns, clock uncertainty = 0.035ns. Walk through where the slack is being lost and propose three concrete fixes, ranked by effort.
Each engineer is scored on one scale. You see it; they see it. No black box.
Letter grades are independent of the gate. Verified at 51 and up. 51–59 shows as Credible, verified but below a B. Every verified engineer is company-facing; the browse set is ranked by score, not gated a second time.
Live verified engineers you can browse today, with new tracks opening.
Prove it once on a test built by an engineer who holds the same bar. Get matched only to roles that fit your specialization, and keep 100% of your billings.
One structured interview — about 30 min — free — keep 100% of your billings.