Software engineer · Las Vegas
Simrod Furman
Backend and systems engineer: reliable services, performance when it matters, and delivery teams can run.
MIT CS · backend and systems since the mid-1990s · after a health-related break, back at capacity and looking for a long-term engineering role.
Focus
Backend systems
Services, APIs, data stores, and the glue between them—clear interfaces and code teams can own.
Performance & specialized compute
When throughput matters: GPU-accelerated numerical work, concurrency fixes, and measuring the result.
Cloud delivery & team enablement
Serverless backends, IaC, and CI/CD so shipping is a process—not a one-person fire drill. Same habits at home: private Gitea, runners, Cloudflare deploys.
AI / LLM in the workflow
Models as leverage for coding and tooling, with human review and ownership. More in Writing.
Writing
All posts →Using LLMs as an engineer
How I treat coding assistants and agents: leverage with review, not autopilot—and what “AI familiarity” should mean on a hiring page.
Returning to full-time work
Why I’m re-entering consistent team work, how I’m talking about a health-related gap, and what I’m optimizing for next.
Next step
If we worked together before, or you’re hiring for backend / systems roles where ownership matters—I’d like to hear from you.