Hacker Newsnew | past | comments | ask | show | jobs | submit | manish_gill's commentslogin

ClickHouse | Senior Software Engineer - Distributed Systems / Cloud Data Infrastructure / Kubernetes | Remote

US remote preferred right now, EU is technically fine but I'm looking to ramp up in US atm

ClickHouse is a popular, Open-Source OLAP Database. We are ClickHouse Inc, the company behind the database aiming to build the best in class real time data warehouse.

What we are looking for:

Distributed Systems / Cloud Engineers to build the AutoScaling Systems for a Cloud Database.

We also maintain our own ClickHouse-based Data Infrastructure. Bonus points if you've worked on auto-scaling or other data-driven forecasting challenges in the past.

    Can work in an early stage startup environment. Proactive and hands on.

    You must be independent and self-organised.

    Good at Go, Kubernetes (Understanding how to manage stateful services in a multi-cloud environment)

    We have a Python service in our Recommendation pipeline, so some ML/Data Science knowledge would be good.

    SQL / ClickHouse SQL (goes without saying)

    You'll need to be able to do On-Call - debugging production infra or db issues

    If you can do low-level database programming (C++, ClickHouse) that's added bonus.
If you want to work on operating production critical databases in the cloud on k8s + write data-driven algorithms for autoscaling, consider applying!

Send me an email: manish.gill [at] clickhouse [dot] com

[0] https://www.youtube.com/watch?v=AFoMsLMZKik

[1] https://www.youtube.com/watch?v=ufY_JFPpzRI

PS: If you're a pure DevOps person or a pure Data Engineer who wrangles data tools, please read the above requirements carefully before firing off an email. This role is an intersection of a lot of sub-roles, not a particular specialization.


> Clickhouse is not good for joins

This is less and less true as time goes on tbh. 25.9 introduced Join Reordering as well - https://clickhouse.com/blog/clickhouse-release-25-09


ClickHouse | Senior Software Engineer - Distributed Systems / Cloud Data Infrastructure / Kubernetes | Remote

(US preferred right now, EU is technically fine but I'm looking to ramp up in US atm)

ClickHouse is a popular, Open-Source OLAP Database. We are ClickHouse Inc, the company behind the database aiming to build the best in class real time data warehouse.

What we are looking for:

Distributed Systems / Cloud Engineers to build the AutoScaling Systems for a Cloud Database.

We also maintain our own ClickHouse-based Data Infrastructure. Bonus points if you've worked on auto-scaling or other data-driven forecasting challenges in the past.

    Can work in an early stage startup environment. Proactive and hands on.

    You must be independent and self-organised.

    Good at Go, Kubernetes (Understanding how to manage stateful services in a multi-cloud environment)

    We have a Python service in our Recommendation pipeline, so some ML/Data Science knowledge would be good.

    SQL / ClickHouse SQL (goes without saying)

    You'll need to be able to do On-Call - debugging production infra or db issues

    If you can do low-level database programming (C++, ClickHouse) that's added bonus.
If you want to work on operating production critical databases in the cloud on k8s + write data-driven algorithms for autoscaling, consider applying!

Send me an email: manish.gill [at] clickhouse [dot] com

[0] https://www.youtube.com/watch?v=AFoMsLMZKik [1] https://www.youtube.com/watch?v=ufY_JFPpzRI

PS: If you're a pure DevOps person or a pure Data Engineer who wrangles data tools, please consider the above requirements before firing off an email. This role is an intersection of a lot of sub-roles, not a particular specialization.


ClickHouse | Senior Software Engineer - Cloud Infrastructure / Kubernetes | Remote (US / EU preferred)

ClickHouse is a popular, Open-Source OLAP Database. We are ClickHouse Inc, the company behind the database aiming to build the best in class real time data warehouse.

What we are looking for:

Cloud / Kubernetes Operator engineers to build the AutoScaling infrastructure. We also maintain our own ClickHouse-based Data Infrastructure. Bonus points if you've worked on autoscaling or other data-driven forecasting challenges in the past.

    Can work in an early stage startup environment. Proactive and hands on.

    Senior/Staff+ Engineer. You must be independent and self-organized.

    Good at Go, Kubernetes (Understanding how to manage stateful services in a multi-cloud environment)

    We have a Python service in our Recommendation pipeline, so some ML/Data Science knowledge would be good.

    SQL / ClickHouse SQL (goes without saying)

    You'll need to be able to do On-Call - debugging production infra or db issues

    If you can do low-level database programming (C++, ClickHouse) that's added bonus.
If you want to work on operating production critical databases in the cloud on k8s + write data-driven algorithms for autoscaling, consider applying! Send me an email: manish.gill [at] clickhouse [dot] com [0] https://www.youtube.com/watch?v=AFoMsLMZKik

[1] https://www.youtube.com/watch?v=ufY_JFPpzRI


Okta / Lumos are the biggest offenders of this.


I suspect in that case it's to get their name in front of people's faces for marketing purposes. If things are actually seamless enough that you don't need to re-auth, you won't be reminded that their company exists.


Co-incidentally, saw this video on Microsoft's VSCode Youtube channel yesterday - the Engineer in question was born without a right hand and shows her workflow with accessibility tools: https://www.youtube.com/watch?v=pUPqKm5wVhw

Hope this helps your relative. Good luck.


They tried running minecraft, but I wonder if a similar (or better) cloning is possible for a mission critical workload - like a database consuming a huge amount of memory. Neon uses QEMU to achieve this for example: https://neon.tech/docs/reference/glossary#live-migration but is that the only way?


If people are still coming up with you for questions that the docs answer, then the docs are not discoverable. Nobody is going to sit through hours of docs to find that one small thing they are interested in knowing the answer to _right now_.

LLMs can solve this to some extend now tbh.


As I said, people doing this aren't interested in looking for an answer. They're interested in making their problem someone else's problem. An AI agent doesn't solve this.


Insofar as "the problem" is sifting through pages and pages of documentation to find the relevant information for an answer, I think that current-day LLMs are actually quite capable at this.


Before needing an LLM for it, they might want to ensure their doc system is using a search system that actually works. There's too many doc-focused templates / apps that have the worst search possible.


I think I qualify for EB-1C, but does one need to be present and already living in the US to apply for it, or can that happen from the current country of residence?

Or is the general path: L1 -> Move -> Apply for EB-1C once migrated.


Most people go the EB1C green card route after they are in the U.S. in L-1A status but that's not required; the entire green card process can be done while the applicant is outside the U.S. and not yet employed by the U.S. company.


Is it recommended or not? I've heard anecdotally that going through the Consular services to obtain EB1C is not recommended - because you can get denied easily without any protections you might get from being in the US.


You don't have protections in the US per se. If you are on a visa, your visa will remain valid and continue on its own terms. Your GC application is orthogonal.


If there are any of these hacker spaces that are friendly for English speakers (my German is only A2.1 sadly), I would love to join one of them :)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: