Ashby, a Y Combinator-backed recruiting platform, is seeking Principal Product Engineers to join their growing team. They're looking for experienced engineers with strong product sense and a passion for building impactful software to improve the hiring process. Responsibilities include leading the design and development of core product features, mentoring other engineers, and contributing to the overall technical strategy. The ideal candidate possesses expertise in full-stack development, preferably with experience in Ruby on Rails and React. Ashby offers competitive compensation, benefits, and the opportunity to work on a product used by leading companies.
James Shore envisions the ideal product engineering organization as a collaborative, learning-focused environment prioritizing customer value. Small, cross-functional teams with full ownership over their products would operate with minimal process, empowered to make independent decisions. A culture of continuous learning and improvement, fueled by frequent experimentation and reflection, would drive innovation. Technical excellence wouldn't be a goal in itself, but a necessary means to rapidly and reliably deliver value. This organization would excel at adaptable planning, embracing change and prioritizing outcomes over rigid roadmaps. Ultimately, it would be a fulfilling and joyful place to work, attracting and retaining top talent.
HN commenters largely agree with James Shore's vision of a strong product engineering organization, emphasizing small, empowered teams, a focus on learning and improvement, and minimal process overhead. Several express skepticism about achieving this ideal in larger organizations due to ingrained hierarchies and the perceived need for control. Some suggest that Shore's model might be better suited for smaller companies or specific teams within larger ones. The most compelling comments highlight the tension between autonomy and standardization, particularly regarding tools and technologies, and the importance of trust and psychological safety for truly effective teamwork. A few commenters also point out the critical role of product vision and leadership in guiding these empowered teams, lest they become fragmented and inefficient.
Summary of Comments ( 0 )
https://news.ycombinator.com/item?id=43161876
Several commenters on Hacker News expressed skepticism about Ashby's "Principal" Product Engineer role, pointing out what they perceived as a relatively junior-level description of responsibilities and questioning the title's appropriateness. Some suggested the listing was targeted towards less experienced engineers who might be drawn to the "Principal" title, while others wondered if it reflected a broader trend of title inflation in the tech industry. There was also discussion about Ashby's use of an Applicant Tracking System (ATS), with commenters debating the merits of such systems and their impact on the hiring process. A few commenters expressed interest in the company and its product, while others shared anecdotes about their own experiences with similar job titles and company cultures.
The Hacker News post titled "Ashby (YC W19) Is Hiring Principal Product Engineers," linking to an Ashby job posting, generated a small number of comments, primarily focused on the salary range offered and the remote work policy.
One commenter questioned the listed salary range of $170k-$280k, pointing out the large difference between the low and high ends. They speculated whether the high end was genuinely attainable or merely a tactic to attract more applicants. This commenter also inquired about the criteria used to differentiate between candidates offered the lower and higher ends of the range.
Another commenter expressed specific interest in the remote work policy, inquiring about Ashby's stance on international remote employees. They explicitly asked whether Ashby hires from countries outside the US, indicating a personal interest in potentially applying.
A third commenter echoed the concern about the broad salary range, suggesting it might be too wide. They proposed that providing more context or a midpoint within the range could offer potential applicants a clearer picture of the compensation they could realistically expect. This commenter also brought up the importance of transparency in salary discussions, especially in the current job market.
Finally, a commenter mentioned the potential for confusion between Ashby, the company in the job posting, and Hashby, a seemingly unrelated company with a similar name. They suggested this similarity could negatively impact Ashby's search engine optimization (SEO) and brand recognition.
In summary, the comments mainly revolved around the advertised salary range and the remote work policy. The broadness of the salary range drew particular attention, with commenters advocating for greater clarity and transparency. The possibility of international remote work was also raised, and one commenter noted a potential branding issue due to a similarly named company. There was no significant discussion of the role itself or the company's technology beyond these points.