I’m glad to see new tooling targeting developers and the local development loop which was neglected because historically was hard to monetize. As an consultant involved in cloud migrations and CI/CD I do see the value of a common language for build/test/deploy, it’s a mess in the enterprises nowadays. I’m curious to learn what is Hashicorp’s opinion about CNAB (which somehow tries to solve the same problem). As Waypoint is complementary to CI tools, do you see this also complementary for the GitOps tooling which is gaining traction in the Kubernetes world?
We help clients build confidence with cloud technologies and transition to microservices. We work with cloud native vendors on next-generation open-source tools. We're growing our Amsterdam (HQ) and Zurich offices and creating new engineering teams in Berlin and London. We are hiring for potential, not for skills.
We are looking currently for:
Cloud Native engineers (all offices)
Background in development or operations with some experience in microservices, CI/CD, technologies like Docker, Kubernetes, Mesos, cloud (AWS, Google, Azure), cloud automation and provisioning (Terraform, Ansible, Cloud Formation etc). We value consultancy skills and community work (open-source projects, meetups and conference talks, blogging).
Expect mainly short-term projects (2-4 months) mostly delivered from our offices. We automate the infrastructure of our customers and deploy on top of it orchestration layers for running apps and data. We work in small self-managed teams that take full responsibility for the projects. We're not tech/cloud service resellers, we mix the best open-source tools and services that make sense for the project.
All our engineers are encouraged to share their knowledge at conferences and within the company. We consider ourselves a continuous learning company. Switching between projects/roles/offices is possible and quite common.
Front-End Developer (Amsterdam)
Create beautiful and usable interfaces and are especially interested in building GUIs for distributed systems. Should have an affinity with design thinking and from the beginning, are expected to lead ideation sessions and have interest in backend development.
I'm a prime member for nautilus for 2 years now. I can't support all the good journalism sites I visit. But that doesn't mean I (or you) shouldn't support any. Just pick one.
Hi, for remote candidates, we are looking for proofs of remote capabilities. Open source projects, conference talks, any type of visibility. As we're based in Europe we prefer candidates in our own timezones, because we do collaborate on a daily basis.
Or somebody we already know and trust (did business somehow together).
Go and Java are the main languages used by us. We don't want to pass great engineers because they may not have experience with a specific language. We expect them to be willing to learn it if required (same for other technologies).
We're open to experiment with remote candidates. We have 2 guys working outside the office locations I listed, but they are still in UK (Leeds, Edinburgh), where we have an office.
We are looking for engineers who want to join a supportive, relaxed and experimental environment where they can express their skills. Container Solutions is a premium software consultancy & research company that focuses on programmable infrastructure. We encourage entrepreneurial people; in the last year several projects that started in Container Solutions grew as independent companies.
We are looking currently for:
Systems Developers - Implement immutable infrastructure architecture & write code for leading open source projects: Hashicorp tools, Mesos (frameworks), K8s and own projects.
Application Developers - Write applications for drones, e-commerce, big data and data science as well as for IoT devices
Support Engineers - Provide support for the systems we have built and installed. These systems include DC/OS, Mesos and K8s.
UI/UX Developers - Create beautiful and usable interfaces and are especially interested in building GUIs for distributed systems. Should have an affinity with design thinking and from the beginning, are expected to lead ideation sessions.
All our engineers are expected to share their knowledge at conferences and within the company. Switching between projects/roles is common, people can choose the project they’re most interested in.
Nice concept. Indeed for remote working teams (read asynchronous working team) slack is not enough. We experiment now with basecamp+slack for the reasons you mentioned: measure work progress, milestones, announcements.