At Coalesce, we are building a data transformation platform for large enterprises. While there are other DAG-based tools in this market such as Matillion, Alteryx, DBT, Airflow, etc, our architecture has been built from the beginning to scale to the needs of large enterprises.
We recently raised a $26M Series A and are looking to grow our engineering team. Our customer list and feature requests keep growing and we need engineers to help us build!
We've got the foundations of our product in place and we have many customers that are already using it in production. This year, we've invested a lot in our tooling and codebase, and because of this as well as the swelling customer demand I think we are setup to be truly crushing it in 2023.
To give you an idea of what our team works on:
* Our team develops algorithms for managing data warehouses at scale
* Our UI is a fully interactive Directed Acyclic Graph editor that supports interactions at up to 50,000+ objects
* Our CLI and API's are used by Fortune 500's to manage and run data analytics processes
We've recently brought on many hires from Snowflake and FiveTran as well.
I've done multiple successful startups now, and I truly think that now is an amazing time to join our team at Coalesce and be a part of something truly special.
Full Stack Software Engineer - https://jobs.lever.co/coalesce.io/ae173d8b-6ada-456c-aef4-ae...
Staff Software Engineer - https://jobs.lever.co/coalesce.io/bfdeb358-ecba-4e88-b32f-44...
If you think you are a really great fit, please email me at michael.xu<AT>coalesce.io and I'll reach out to you.
At Coalesce, we are building a data transformation platform for large enterprises. While there are other DAG-based tools in this market such as Matillion, Alteryx, DBT, Airflow, etc, our architecture has been built from the beginning to scale to the needs of large enterprises.
We recently raised a $26M Series A and are looking to grow our engineering team. Our customer list and feature requests keep growing and we need engineers to help us build!
We've got the foundations of our product in place and we have many customers that are already using it in production. This year, we've invested a lot in our tooling and codebase, and because of this as well as the swelling customer demand I think we are setup to be truly crushing it in 2023.
To give you an idea of what our team works on:
* Our team develops algorithms for managing data warehouses at scale
* Our UI is a fully interactive Directed Acyclic Graph editor that supports interactions at up to 50,000+ objects
* Our CLI and API's are used by Fortune 500's to manage and run data analytics processes
We've recently brought on many hires from Snowflake and FiveTran as well.
I've done multiple successful startups now, and I truly think that now is an amazing time to join our team at Coalesce and be a part of something truly special.
Full Stack Software Engineer - https://jobs.lever.co/coalesce.io/ae173d8b-6ada-456c-aef4-ae...
Staff Software Engineer - https://jobs.lever.co/coalesce.io/bfdeb358-ecba-4e88-b32f-44...
If you think you are a really great fit, please email me at michael.xu<AT>coalesce.io and I'll reach out to you.
not sure what's 'fucking stupid' about that.
it might be harder to grok at first - but that's the reality of tools - by nature, they get more complex but more elegant, i think it's fucking stupid to want to go back to componentDidMount()componentDidUpdate, componentWillReceiveProps, componentWillUnmount, getDerivedStateFromProps and UNSAFE_componentWillUpdate. like... really?
hey everyone one of the things that annoys me about REST APIs is the integration of them. everyone integrates with the same APIs over and over again, rediscovering what the endpoints are, how the parameters work, guessing what the return fields are, writing the pagination code, figuring out how to get a token, etc. even amongst the most popular APIs, openAPI adherence is poor.I'm thinking about...
i think theres still a use for surveillance. just my opinion.
then again. im paranoid. i want the fort knox of data.
they are constantly SSH'd running jobs on the data, using different tools to understand their data.
i think SSH will always exist going forward, and we won't be able to automate everything.
any other thoughts on how to prevent data leaks?
You bring up remote desktop environments... its actually a good point... similar to what VM's on AWS are.
If the access point (SSH) is locked down and recorded, doesn't that pretty much remove any possibility of employees leaking stuff?
knowing that they are being recorded is a pretty big deterrent to leaking data right?
this is something that i've been pondering for awhile.at pretty much every job i've been at, we've had Linux Servers that we ssh into.these linux servers have customer data on them, builds, code, business critical shit.if i were a malicious individual, i could easily just rm -rf important files, scp important customer data out to my home computer. or use dropbox to sync some critical business...
simply put, you are thinking it wrong.
in particular, if you are appending to a file.
especially with ext4, consider calling fallocate() to preallocate the size of the file you are appending to and keeping track of the offset yourself, i've seen that help performance immensely.
they have daily blog posts from excellent game developers.
although i'm not a c++ game developer, i do use c++ and i take a lot of inspiration from the techniques that they talk about on that site.
read it when you start c++, then read it 6 months later. it will feel like you are reading a completely different book :)
but... what happens if i want to read, process and write a log message....? thats three different bloom blocks that require 2 partial orderings.
instead of totally unordering everything, id rather have the ability to declaratively order functions for a request, where a function is a typical sequenced set of operations.
their examples arent particularly helpful, looks like most of these bloom blocks are single lines...
hi everyone.does anyone have tips for a software engineer on how to do good UI web design?It's not as simple as it appears, I know, and doing stuff like drop-shadows. matching colors. layouts. having a toolkit of UI tools like different brushes, gradients, etc.basically, resources on ui design for the software engineer would be very helpful...where do i about learning about professional front...
does anyone have any emacs productivity tips?is there anything that you've done to your emacs to make it work really well?im using gdb inside of emacs, i type M-x compile to make, i only use emacs -nw inside of terminal because the regular X version is too slow, stuff like that...i've never used buffer rings, or customized keyboard shortcuts to automatically macro-out if statements and...
all of the things you are talking about requires hardware + software. which is more expensive, slower and more dangerous than building web 2.0 sites that are easily patchable.
that's actually a very prohibitive point, as most startups we hear about nowadays use software because of its low bootstrap cost and economies of scale