‹ BackHN Continuity

Thread

Ask HN: Who wants to be hired? (August 2026)

156 points · 477 comments · whoishiring

  1. codeprimate · · focus · HN ↗
    Location: Bellingham, WA

    Remote: Yes

    Willing to relocate: No

    Technologies: Ruby, Rails, PostgreSQL, Sidekiq, Hotwire, JavaScript, Python, AWS, Docker, MCP, LLMs, RSpec

    Résumé&#x2F;CV: <a href="https:&#x2F;&#x2F;www.linkedin.com&#x2F;in&#x2F;patrick-morgan&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.linkedin.com&#x2F;in&#x2F;patrick-morgan&#x2F;

    GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;codeprimate" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;codeprimate

    Email: contact at bellingham.dev

    I have been shipping software for twenty years, most of it Rails, and what I own has always run wider than the code I write. The work starts in a room where most of the people are not engineers and the problem has not been named yet, and it carries through the data model, the API contract, the authorization boundary, the background queues, the deploy, and whoever holds the pager afterward. Being accountable across that whole span is a broader claim than full stack, and a harder one to fake.

    The depth sits in Rails and Postgres, where I have built async pipelines that had to survive real traffic, payments and third-party integrations that could not quietly drop money, and authorization models that grew more intricate every quarter as the business kept inventing new kinds of users. I reach for Hotwire when the product needs a face, run Docker daily, and treat application security as ordinary hygiene rather than a phase, which means reading the CVEs that touch my stack, running Brakeman and bundler-audit, and reviewing changes against OWASP before they land.

    I work with agents every day and skeptically, on the same practice I was using before the tooling existed: discovery before implementation, verification before reference, scope control before anything ships.

    Two of the more interesting systems I built are ones I argued to shut down, once the numbers showed they cost more than they were worth, and I wrote up the reasoning both times so the decision outlived the project. That judgment matters more to me than shipping volume, because I would rather be right in month three than committed in month nine.

    I am looking for senior IC, staff, or principal work on a team with clear direction and problems worth the depth, whether that runs toward Rails and backend architecture, greenfield systems design, or LLM work that has to earn its place in the product. Available now.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.