←back to thread

128 points whoishiring | 1 comments | | HN request time: 0.204s | source

Share your information if you are looking for work. Please use this format:

  Location:
  Remote:
  Willing to relocate:
  Technologies:
  Résumé/CV:
  Email:
Please only post if you are personally looking for work. Agencies, recruiters, job boards, and so on, are off topic here.

Readers: please only email these addresses to discuss work opportunities.

There's a site for searching these posts at https://www.wantstobehired.com.

1. tuckerpo ◴[] No.44437585[source]

  Location: Denver, Colorado (CO)
  Remote: Yes, or hybrid, or on-site.
  Willing to relocate: Yes, within Colorado, east coast USA, or EU/UK
  Technologies: C++, C, Python, (Java|Type)Script, assembly (ARM, MIPS, SHARC), Linux (userspace), Linux (kernel), embedded Linux (buildroot, Yocto, OpenWRT, uboot, grub), networking (802.11n,ac,ax,be,k,v,r,s, hostapd, wpa_supplicant, nl80211), FPGA (VHDL, Verilog, Xilinx, Intel), Windows (kernel, C runtime, MFC, WPF, C++, C#), Docker
  Résumé/CV: https://tuckerpo.me/ or curl https://tuckerpo.me/short-resume | jq
  Email: tuckerpolomik[@]gmail.com
Hi, I’m Tucker — a senior systems engineer with 7+ years of experience and the battle scars to prove it. I’ve written firmware for chips that barely boot, kernel modules that talk to hardware no one admits to designing, and userland code that somehow still runs in production. Occasionally I get dragged into front-end work too, usually as penance for something I did in a past life.

Strong C++/C background, systems-level orientation. I’m at home in resource-constrained, real-time, or just-plain-hostile environments. Embedded Linux, networking stacks, wireless protocols, FPGAs, weird bootloaders—if it’s not glamorous and people usually avoid it, there’s a good chance I’ve done it. Currently getting into Rust and Zephyr in my free time. Also very very strong background in networking/Wi-Fi, with several talks, published papers, and patents.

Looking for roles where software is the product, not an afterthought. I’d prefer to avoid places where Jira boards are sacred texts, architecture is decided by slide deck, and everyone’s calendar is 95% “syncs” to discuss work nobody’s doing. If your team measures value in working code and shipped products, and not in "alignment", we’ll probably get along.

Spoken at conferences (NetworkX, prpl Summit, SCTE Expo), given demos to customers, and generally enjoy making things that actually work.

If you’ve got an interesting problem, and you aren’t staffed wall-to-wall with MBAs LARPing as engineers via spreadsheet, shoot me an email.