Location: Portland, Oregon
Remote: Yes
Willing to relocate: No
Technologies:
- Most specialized in backend engineering - APIs, databases (worked with Postgres and MongoDB), making complex systems work together.
- Full-stack enough (with React) that I was building personal web apps for myself and my partner before coding agents got good.
- Now I have like five of them, and they do a lot more; it's been a very interesting way to explore the strengths and limitations of agents.
- I'm expert in Typescript / Javascript (and Node.js), conversant in Ruby and Python, and happy to learn other languages.
Resume: https://www.dropbox.com/scl/fi/3y2tf55v4zopivr4xze8w/Sam-Lie...
Email: samliebow [at] gmail [dot] com
I'm a primarily-backend engineer with ~7 years of experience, most recently in the Risk division at Stripe for 3.5 years, and at a Series C startup before that. On my teams I've been known for good product sense, for improving efficiency (e.g. taking the team's core cron job's runtime from 8 hours to 15 minutes), for making myself an expert on complex code and data, and for being an excellent debugger, reviewer, and incident-responder.
Remote: Yes
Willing to relocate: No
Technologies:
- Most specialized in backend engineering - APIs, databases (worked with Postgres and MongoDB), making complex systems work together.
- Full-stack enough (with React) that I was building personal web apps for myself and my partner before coding agents got good.
- Now I have like five of them, and they do a lot more; it's been a very interesting way to explore the strengths and limitations of agents.
- I'm expert in Typescript / Javascript (and Node.js), conversant in Ruby and Python, and happy to learn other languages.
Resume: https://www.dropbox.com/scl/fi/3y2tf55v4zopivr4xze8w/Sam-Lie...
Email: samliebow [at] gmail [dot] com
I'm a primarily-backend engineer with ~7 years of experience, most recently in the Risk division at Stripe for 3.5 years, and at a Series C startup before that. On my teams I've been known for good product sense, for improving efficiency (e.g. taking the team's core cron job's runtime from 8 hours to 15 minutes), for making myself an expert on complex code and data, and for being an excellent debugger, reviewer, and incident-responder.