Weaveworks, a Kubernetes tooling company, writes about GitOps, Flux, Kubernetes operations, and related open-source projects.
HN commenters link it for GitOps and Flux, credit it for open-sourcing Cortex, and one team says it uses Weave and likes the git-stored state.
Core Engineer at VC-funded open-source project, Weaveworks, London
Weaveworks is a start-up founded by the team that created RabbitMQ and backed by one of the world’s leading tech investors. Headquartered in London, we are hiring engineers to work on our open source software product, Weave.
The purpose of Weave is to enable all developers, no matter what their background, to take advantage of container technologies such as Docker and build better software applications. We believe that containers will lead to much more software being built at greater speed and scale than ever before, so much so that many existing approaches will need to be reimagined.
We have an experienced team and welcome newcomers who want to progress fast, as well as domain experts in relevant technologies. Currently Weave is a set of network services written in Go, packaged to make distributed Docker applications much easier to construct. But we have considerable ambitions, and the space is evolving rapidly, so we especially seek developers with the right outlook and ability to adapt.
Ideally you have real world experience of building and running systems with a focus on resilience and uptime. You are as comfortable designing or debugging a distributed protocol as you are talking to customers building a web app or scaling a data service.
We hope to meet developers who share our values:
- Complete focus on the simplest possible user experience
- A real desire to innovate, and then measure success by…
Weaveworks | Senior Backend Developer | San Francisco, London, Berlin, Madrid | ONSITE, Full-time, https://www.weave.works
* Senior backend dev: develop microservices (primarily in Go) and container tools
* Senior frontend dev: write reactive and snappy web UIs that show complex data and are easy to navigate (Berlin only)
* Developer experience/evangelist: spread the word in meetups/conferences, develop integrations for our tools
Come help us build OSS tools that other developers use to tame their containerized applications. Projects like Weave Scope observe containers/pods/services and their interactions to provide visibility and insights. Developers can quickly see the state of the resulting systems and validate their assumptions.
We offer family-friendly hours (some of us have kids, too) and encourage a good work-life balance. Feel free to work from home on certain weekdays, or combine work and travel for a month. It's no big deal if you're not a Go expert, we trust that you can learn on the job. Also, all our tools are open source: https://github.com/weaveworks Browse our PRs to see how we work as a team!
The hiring process: Checking your CV/GH/SO (if not enough signal: small coding challenge), 45 mins hangout, afternoon take-home coding/design challenge, in person interview with future colleagues
If you’re interested please drop us a line with your desired location at jobs (at) weave.works
Note: Weaveworks will consider visa sponsorship on case-by-case basis,…
Weaveworks | Senior Backend Engineer, Senior Frontend Engineer | San Francisco, London, Berlin, Madrid | ONSITE, Full-time, https://www.weave.works
- Senior backend engineer: develop microservices (primarily in Go) and container tools
- Senior frontend engineer: Design and implement reactive web UIs that visualize complex data using state-of-the-industry tools, like React and D3
Come help us build OSS tools that other developers use to tame their containerized applications. Projects like Weave Scope observe containers/pods/services and their interactions to provide visibility and insights. Developers can quickly see the state of the resulting systems and validate their assumptions.
We offer family-friendly hours (some of us have kids, too) and encourage a good work-life balance. Feel free to work from home on certain weekdays, or combine work and travel for a month. It's no big deal if you're not a Go expert, we trust that you can learn on the job. Also, all our tools are open source: https://github.com/weaveworks Browse our PRs to see how we work as a team!
The hiring process: Checking your CV/GH/SO (if not enough signal: small coding challenge), 45 mins hangout, afternoon take-home coding/design challenge, in person interview with future colleagues
If you’re interested please drop us a line with your desired location at jobs (at) weave.works
Note: Weaveworks is not set up to sponsor visas at this point.
This seems especially important if you want to offer Prometheus as SaaS.
Your customers won't want to run their own Prometheus installs (that's what they pay you for, after all),
and asking customers to open their firewalls so that your Prometheus can discover and scrape their
infrastructure is probably a non-starter.
At Weaveworks we provide Prometheus as a SaaS using Cortex, which is how the project was started. For our service we have an agent that installs a Prometheus agent (and some other ones) on the customers K8s cluster.
The upsides of running the agent on their side is that they benefit from Prometheus' automatic service discovery. They can also use standard Prometheus configuration and scrapers to get the full capabilities for their environment.
There are also situations where the user wants to continue to run their own Prometheus, but down sample and send a limited number of metrics for long-term storage in the Weave Cloud SaaS. This can be done with one line in a standard Prometheus.
It's true that running the agent takes resources, I think the benefits are worth it. For most people the key question is getting the full value from their metrics data to enable better development and operations.
[NOTE]: Full Disclosure I work at Weaveworks where we provide Prometheus-as-a-Service (https://www.weave.works/features/prometheus-monitoring/)
I know a bit of the history with this one.
Back in the day there was a smaller consultancy with awesome developers called LShift (mentioned here https://en.wikipedia.org/wiki/East_London_Tech_City). They worked out that an open source messaging thing would be useful, and created RabbitMQ (there were details about who, how it was funded internally, etc). That got sold to VMWare, and a bunch of people went with it, but LShift went on as before, happy, but always looking for another Rabbit. Didn't find one, was aquihired in the end.
Meanwhile, some of the Rabbit people formed Weave, looking for the killer business around the early container ecosystem (https://www.weave.works/oss/net/ was interesting, eksctl, flux, CNCF, lots of good things). But I guess they took a bite of the VC apple and sustainable technical contributions was no longer the goal.
I've huge respect for everyone I knew from Weave. Great people all. Best wishes and I know you'll land on your feet.
Weaveworks | Software Engineer, Backend | ONSITE(London)/REMOTE (prefereably EU/US TZs) | https://www.weave.works | Full time
Weaveworks aims to empower developers, no matter their background, to take advantage of container technology such as Docker to build faster and more scalable applications. We believe that container software will change the way developers create applications, so much so that many approaches are yet to be imagined. Help us build open source software tools that other developers use to tame their containerized applications.
We are looking for experienced software engineers with background in kubernetes, go and AWS. Experience in open source software development practices highly appreciated. The job is with a remote, global team, ability to work unsupervised and coordinate with others on daily basis. Devops experience with one or more public cloud providers.
Apply here: https://boards.greenhouse.io/weaveworks/jobs/1829839