Spice Data, a Y Combinator-backed startup, is seeking a software engineer to build their AI-powered contract analysis platform. The ideal candidate is proficient in Python and JavaScript, comfortable working in a fast-paced startup environment, and passionate about leveraging large language models (LLMs) to extract insights from complex legal documents. Experience with natural language processing (NLP), information retrieval, or machine learning is a plus. This role offers the opportunity to significantly impact the product's direction and contribute to a rapidly growing company transforming how businesses understand and manage contracts.
Hightouch, a Y Combinator-backed startup (S19), is seeking a Distributed Systems Engineer to work on their Reverse ETL (extract, transform, load) platform. They're building a system to sync data from data warehouses to SaaS tools, addressing the challenges of scale and real-time data synchronization. The ideal candidate will have experience with distributed systems, databases, and cloud infrastructure, and be comfortable working in a fast-paced startup environment. Hightouch offers a remote-first work culture with competitive compensation and benefits.
The Hacker News comments on the Hightouch (YC S19) job posting are sparse and mostly pertain to the interview process. One commenter asks about the technical interview process and expresses concern about "LeetCode-style" questions. Another shares their negative experience interviewing with Hightouch, citing a focus on system design questions they felt were irrelevant for a mid-level engineer role and a lack of feedback. A third commenter briefly mentions enjoying working at Hightouch. Overall, the comments offer limited insight beyond a few individual experiences with the company's interview process.
Summary of Comments ( 0 )
https://news.ycombinator.com/item?id=43525636
HN commenters discuss the unusual job posting from Spice Data (YC S19). Several find the required skill of "writing C code like it's 1974" intriguing, debating whether this implies foregoing modern C practices or simply emphasizes a focus on efficiency and close-to-the-metal programming. Some question the practicality and long-term maintainability of such an approach. Others express skepticism about the company's claim of requiring "PhD-level CS knowledge" for seemingly standard software engineering tasks. The compensation, while unspecified, is a point of speculation, with commenters hoping it justifies the apparently demanding requirements. Finally, the company's unusual name and purported focus on satellite data also draw some lighthearted remarks.
The Hacker News post discussing the Spice Data (YC S19) Software Engineer job posting has a modest number of comments, focusing primarily on the perceived difficulty of the technical challenge presented in the application process.
Several commenters found the coding challenge, which involves implementing a simplified version of Git, to be excessively complex and potentially a poor indicator of a candidate's actual on-the-job skills. They argue that requiring applicants to build a core piece of functionality of a complex version control system in a short timeframe is unrealistic and may discourage otherwise qualified candidates. This sentiment is echoed across multiple comments, with some suggesting that such challenges might favor those who have already tackled similar problems, potentially overlooking candidates with strong general software engineering abilities but less specific experience.
One commenter suggests that the complexity of the challenge might be a reflection of the company's actual work, implying that day-to-day tasks at Spice Data could involve similarly intricate problems. They posit that this might be a deliberate filtering mechanism to attract engineers who enjoy and excel at this type of low-level, systems-oriented programming.
Another commenter expresses skepticism about the challenge, questioning whether implementing such a simplified Git clone would truly offer valuable insight into a candidate's abilities, and suggesting alternative, potentially more effective evaluation methods.
There's also a brief exchange regarding the use of Rust as a requirement for the role. One commenter questions its necessity, while another responds, clarifying that the challenge can be completed in any language, although Rust is preferred.
The overall tone of the comments suggests a critical view of the application process, particularly the coding challenge, with concerns raised about its difficulty, relevance, and potential to deter qualified applicants. However, there is also acknowledgment that this approach might be intentional, reflecting the nature of the work at Spice Data.