Openlayer, a YC S21 startup building a collaborative spatial data platform, is seeking a senior backend engineer. This role involves designing, developing, and maintaining core backend services and APIs for their platform, working with technologies like Python, Django, and PostgreSQL. The ideal candidate possesses strong backend development experience, a solid understanding of geospatial concepts and databases (PostGIS), and excellent communication skills. Experience with cloud infrastructure (AWS, GCP) and containerization (Docker, Kubernetes) is also desired.
Directus is an open-source, instant headless CMS and API platform that connects directly to any new or existing SQL database. It provides an intuitive administrative app for managing content and users, along with automatically generated REST and GraphQL APIs for accessing that data from any application. Directus offers features like granular permissions, flexible data modeling, custom extensions, webhooks, and a modular architecture designed for extensibility. It empowers developers to build digital experiences on top of their preferred database without tedious API development or vendor lock-in.
Hacker News users discussed Directus's potential, particularly its ability to quickly create APIs for existing SQL databases. Some praised its open-source nature and ease of use, suggesting it's a good alternative to writing custom APIs. Others questioned its performance and scalability compared to purpose-built APIs, especially for complex or high-traffic applications. A few users mentioned potential security concerns and the importance of proper database configuration. Some brought up past experiences with Directus, citing both positive and negative aspects. The discussion also touched upon alternatives like PostgREST and Hasura, comparing their features and use cases.
Summary of Comments ( 0 )
https://news.ycombinator.com/item?id=43204682
The Hacker News comments are sparse and mostly logistical. One commenter asks about the tech stack, to which an Openlayer representative replies that they use Python, Django, Postgres, and Redis, hosted on AWS. Another commenter inquires about remote work options, and Openlayer confirms they are a remote-first company. The remaining comments briefly touch upon the interview process and company culture. No particularly compelling or in-depth discussions emerge.
The Hacker News post titled "Openlayer (YC S21) is hiring a senior back end engineer" linking to a Y Combinator job posting has generated a modest discussion with a few noteworthy comments.
One commenter questions the high salary range ($170k - $230k) offered for a "Senior" Backend Engineer, expressing skepticism about the actual seniority expected given the advertised responsibilities, which they perceive as more aligned with a mid-level role. They also point out the seeming disconnect between requiring AWS experience while simultaneously mentioning the use of Google Cloud Platform (GCP). This commenter suggests the high salary might be a tactic to attract a broader range of applicants.
Another commenter echoes this sentiment, finding the listed requirements quite basic for a senior role commanding such a high salary. They also criticize the ambiguity in the job description, particularly regarding the mention of both AWS and GCP without clarifying the primary cloud platform used. This ambiguity, they argue, raises questions about the company's technical direction.
A separate commenter expresses interest in the position and inquires about the specific technologies used for the backend, highlighting the lack of such details in the original job posting. This emphasizes the need for more clarity in job descriptions to attract suitable candidates.
Finally, there's a brief exchange where a commenter asks about the company's tech stack and receives a response from someone claiming to be a founder, stating they primarily use Python, Go, and Node.js. This interaction provides some valuable information, although its veracity isn't independently verifiable.
In summary, the comments largely revolve around the perceived mismatch between the advertised seniority, salary, and listed requirements. Commenters also express concern about the ambiguity surrounding the cloud infrastructure used and the overall lack of detail regarding the tech stack in the initial job posting. While a purported founder chimed in to address some of these questions, the discussion highlights the importance of clear and comprehensive job descriptions, especially for attracting experienced technical talent.