1 pointby philhow2 hours ago2 comments
  • philhow2 hours ago
    We run a residential construction company on top of a custom internal system built over ~30 years.

    It handles estimating, scheduling, accounting, contracts, and day-to-day operations. It’s lightly documented, actively used, and largely shaped around how one person (the company owner) actually works.

    It works. But we don’t fully understand what we have.

    We’re not looking for someone to start coding.

    We’re looking for someone to step in, understand the system as it exists today (workflows, data, dependencies), and help us answer a more fundamental question:

    What should this become?

    That could mean: • evolving what exists • breaking it into services • or rebuilding parts of it

    We don’t have a predetermined answer.

    This is not a clean greenfield problem. It’s a real system, used every day, with real constraints.

    If you’ve worked with legacy systems, untangled messy workflows, or helped something move from “it works” to “it scales,” we’d be interested in talking.

    This starts as an exploratory role. Remote is fine.

    If this sounds interesting, send a few lines about your background or relevant work.

    Email: tec@pacificwestcompanies.com

  • toomuchtodo2 hours ago
    These usually belong in the whoishiring threads:

    https://news.ycombinator.com/submitted?id=whoishiring