Empirical Health, a YC-backed startup focused on reinventing primary care, is hiring design engineers. They're seeking engineers with a passion for healthcare and experience building user-friendly interfaces for complex systems. These engineers will play a crucial role in designing and developing the company's core product, a technology platform aiming to streamline and improve the patient and physician experience within primary care. The ideal candidate is comfortable working in a fast-paced startup environment and eager to contribute to a mission-driven company.
This blog post by David Weisberg traces the evolution of Computer-Aided Design (CAD). Beginning with early sketchpad systems in the 1960s like Sutherland's Sketchpad, it highlights the development of foundational geometric modeling techniques and the emergence of companies like Dassault Systèmes (CATIA) and SDRC (IDEAS). The post then follows CAD's progression through the rise of parametric and solid modeling in the 1980s and 90s, facilitated by companies like Autodesk (AutoCAD) and PTC (Pro/ENGINEER). Finally, it touches on more recent advancements like direct modeling, cloud-based CAD, and the increasing accessibility of CAD software, culminating in modern tools like Shapr3D.
Hacker News users discussed the surprising longevity of some early CAD systems, with one commenter pointing out that CATIA, dating back to the late 1970s, is still heavily used in aerospace and automotive design. Others shared anecdotal experiences and historical details, including the evolution of CAD software interfaces (from text-based to graphical), the influence of different hardware platforms, and the challenges of data exchange between systems. Several commenters also mentioned open-source CAD alternatives like FreeCAD and OpenSCAD, noting their growing capabilities but acknowledging their limitations compared to established commercial products. The overall sentiment reflects an appreciation for the progress of CAD technology while recognizing the enduring relevance of some older systems.
Empirical Health, a YC S23 startup building AI-powered tools for faster medical diagnoses, is hiring Design Engineers in NYC. They're looking for experienced engineers proficient in frontend development (React, Typescript) and familiar with design tools like Figma, with a passion for improving healthcare. Successful candidates will contribute to building intuitive interfaces for complex medical data, collaborating closely with clinicians and researchers to translate research into user-friendly products.
Hacker News users discussed the high salary ($200k-$250k) offered by Empirical Health for a Design Engineer, questioning its justification. Some argued the role seemed more like a traditional mechanical or manufacturing engineer focused on medical devices, not warranting the "Design Engineer" title often associated with software. Others pointed out the increasing prevalence of high salaries in the medical device field due to its demanding nature and regulatory hurdles. Several commenters debated the value of a Master's degree for the position, some suggesting experience might be more valuable, while others emphasized the importance of a strong theoretical foundation for medical device design. A few comments also mentioned the potential impact of YC funding on inflated salaries. Finally, some users highlighted the overall growth and opportunity within the medical device sector.
Summary of Comments ( 0 )
https://news.ycombinator.com/item?id=43279220
Hacker News users discussed the Empirical Health job posting, focusing on the disconnect between the advertised "Design Engineer" role and the seemingly pure software engineering requirements listed. Several commenters questioned the use of "design" in the title, suspecting it was simply a trendy buzzword to attract talent. Others debated the actual meaning of "Design Engineer" in different contexts, with some suggesting it implied a focus on user experience and product design while others interpreted it as a more systems-oriented role involving architecture and implementation. Some users expressed skepticism about the company's approach to healthcare, while others were more optimistic. A few commenters also discussed the compensation and benefits offered.
The Hacker News post discussing Empirical Health's hiring of design engineers generated several comments, mostly focusing on the ambiguity of the "Design Engineer" role and the company's approach to healthcare.
Several commenters questioned the specific responsibilities of a "Design Engineer" at Empirical Health. They expressed confusion about whether the role leaned more towards software engineering, hardware design, or a hybrid of both, with some speculating it might involve designing physical spaces for healthcare delivery. This lack of clarity prompted calls for a more detailed job description.
One commenter highlighted the potential for mismatched expectations, suggesting that applicants with strong software backgrounds might be disappointed if the role heavily involved hardware or other non-software tasks. This concern underscores the importance of a precise job description to attract the right talent.
Another commenter, seemingly familiar with Empirical Health's work, offered insight into their approach. They described the company as aiming to automate routine primary care tasks using technology and suggested the "Design Engineer" role likely involves developing the hardware and software to achieve this automation. This comment provides valuable context for understanding the company's goals and the potential nature of the advertised role.
Several users discussed the broader challenges and opportunities within the healthcare industry. One commenter expressed skepticism about the feasibility of fully automating healthcare, emphasizing the importance of human interaction and empathy in patient care. This sparked a brief discussion about the potential role of technology in augmenting, rather than replacing, human healthcare providers.
Finally, one commenter mentioned the substantial funding secured by Empirical Health, suggesting this might be a factor influencing their approach to scaling and automating primary care services. This comment hints at the financial resources the company has at its disposal to pursue its ambitious goals.
In summary, the comments primarily revolve around the unclear nature of the "Design Engineer" role and the broader implications of Empirical Health's technology-driven approach to healthcare. The discussion highlights the need for clearer communication regarding job responsibilities and the ongoing debate about the appropriate balance between technology and human interaction in healthcare.