kjbekkelund's comments

kjbekkelund | 5 years ago | on: Ask HN: Who is hiring? (March 2021)

Cognite | Oslo, Norway | ONSITE (we help relocate) | https://www.cognite.com/en/careers

At Cognite we provide contextualized data as a service, and through that enable full-scale digital transformation of heavy-asset industries.

We are growing rapidly in the application teams, and we're hiring for several roles:

- Engineering Manager - Applications (https://apply.workable.com/cognite/j/8DF2965370/)

- Principal Front-end Engineer (https://apply.workable.com/cognite/j/DF3106FCD0/)

- Full-stack engineer (https://apply.workable.com/cognite/j/CAC593E8EA/)

There's quite a bit of 3D, visualizations and, genenrally, trying to help users make sense of data that goes into our apps.

https://www.cognite.com/en/careers

kjbekkelund | 9 years ago | on: Ask HN: Who is hiring? (April 2017)

Elastic | Senior JavaScript Engineer | Anywhere | REMOTE (or ONSITE, if you want to)

Elastic is the company behind the open source projects Elasticsearch, Kibana, Logstash and Beats. We're a truly distributed company with many teams that span the globe (the engineering organization is spread across 30+ countries). We're actively looking for people _anywhere_ (so this is not a position limited to just US time zones).

(If you prefer working in an office, you can work out of any of our offices around the world. If you prefer nomading, you can do that too. I've travelled the world for >7 months in this position.)

We're looking for experienced JavaScript developers to work on several of our UIs, for example on Kibana and on our Cloud product.

Many know Kibana as a visualization platform on top of Elasticsearch, but it has now grown into our application platform that hosts all our open source apps in addition to our X-Pack commercial apps (and plugins that users write). Some of the things our apps cover are visualizations, time series analysis, machine learning, graph exploration, alerting, developer tools, security UI, data ingestion UIs, PDF reporting and so on. Kibana is today "the Window into the Elastic Stack".

Because of our distributed nature we're currently only looking for senior engineers with a strong self-drive. We're looking for someone with extensive knowledge of JavaScript and one or more reasonably popular frameworks. You should also have at least 5 to 7 years of web application development experience.

We're especially interested in people that also have a deep passion for a JS related topic, e.g. visualizations, security, performance, architecture or something entirely different, but this is definitely not a requirement.

Some SEO for the ctrl+f people: Angular, React, Redux, Jest, Webpack, Node.js, D3.js, RxJS

If you have any questions, don't hesitate to contact me at [email protected]

All our job descriptions: https://www.elastic.co/about/careers/

kjbekkelund | 9 years ago | on: Ask HN: Who is hiring? (January 2017)

Elastic (http://elastic.co) • ONSITE & REMOTE (Anywhere) • Front-end Developer • Full-time

Elastic, the company behind Elasticsearch and Kibana, is hiring.

We're looking for front-end developers to work on Cloud, our Elasticsearch-as-a-service product offering. Today, Cloud runs primarily in public cloud environments like AWS, allowing customers to provision and scale Elastic clusters in a turnkey fashion. We also plan to bring this same simplicity of deployment and automation to customers who want to run and manage multiple Elastic clusters on-premise (in their own data centers). You will be contributing significantly to both initiatives.

To get there we need more developers with strong JavaScript skills, but we definitely prefer developers who also have other strong front-end development skills. Maybe security, design, UX, CSS, functional programming, testing, or something else?

We need someone to help innovate, lead and contribute to the front-end and user experience of our Elasticsearch-as-a-Service offering. You will also be integral in shaping the products we build, not just implementing specs.

Most of the work we do today is with React and Redux.

Check out https://www.elastic.co/about/careers/engineering/jobs/czg_ky... for more info.

We're a very remote team with developers in Australia, Poland, Norway, Denmark, Argentina, Panama, the US and several other places (and a couple of us are currently travelling around the world while working).

If you're interested, don't hesitate in contacting me at [email protected]

We're also hiring for several other positions: https://www.elastic.co/about/careers/

kjbekkelund | 10 years ago | on: Ask HN: Who is hiring? (January 2016)

Elastic (http://elastic.co) • ONSITE & REMOTE (Anywhere) • Front-end Developer • Full-time

Elastic, the company behind Elasticsearch and Kibana, is hiring.

We're looking for front-end developers to work on Found, our Elasticsearch-as-a-service product offering. Today, Found runs primarily in public cloud environments like AWS, allowing customers to provision and scale Elastic clusters in a turnkey fashion. We also plan to bring this same simplicity of deployment and automation to customers who want to run and manage multiple Elastic clusters on-premise (in their own data centers). You will be contributing significantly to both initiatives.

To get there we need more developers with strong JavaScript skills, but we definitely prefer developers who also have other strong front-end development skills. Maybe security, design, UX, CSS, functional programming, testing, or something else?

This is an early role on a fast-growing team, so you'll have a lot of impact from day 1. We're a very remote team with developers in Australia, Poland, Norway, Denmark, Panama and several locations in the US.

We need someone to help innovate, lead and contribute to the front-end and user experience of our Elasticsearch-as-a-Service offering. You will also be integral in shaping the products we build, not just implementing specs.

Check out https://www.elastic.co/about/careers/engineering/javascript-... for more info.

Additional information

- Extremely competitive pay

- Stock options

- An environment in which you can balance great work with a great life

- Passionate people building great products

- Employees with a wide variety of interests

- Your age is only a number. It doesn't matter if you're just out of college or your children are; we need you for what you can do.

- Distributed-first company with employees in over 23 countries, spread across 18 time zones, and speaking over 30 languages! Some even fly south for the winter :)

We're also hiring several other positions: https://www.elastic.co/about/careers/

kjbekkelund | 13 years ago | on: Patterns for Managing Large Scale Backbone Applications

I wasn't commenting on Backbone itself, I was commenting on getting started with Backbone. I've held 15+ workshops and presentations on Backbone and helped a lot of people getting started. These are the issues I have most often heard from them.

kjbekkelund | 13 years ago | on: Patterns for Managing Large Scale Backbone Applications

Jeremy, what I've seen most people struggle with (including myself in the beginning) is those first couple of hundred lines of code. How does everything fit together? How should I handle templates? How to I create nested models? How do I stop thinking "in jQuery" and start thinking "in Backbone"?

I guess the thing is that the current documentation works really well when you understand Backbone. Before you understand it, getting started is really difficult. That's why we see so many getting started guides all around — the problem of course being that most of them are barely just ok. Backbone should have a really, really good getting started guide, which (I think) should be more opinionated than Backbone itself — i.e. it shows one (really good) way of doing things (that works well when you scale up your application). Or at least link to one.

I've heard many say "look at the todo example", but I think that it's so far away from a real app that it's difficult to use as a starting point. It doesn't use ajax, it relies heavily on global state, it puts templates in the HTML, lots of global `$` stuff, no routing, etcetc. Ok-ish choices, but not a great example for those getting started. E.g. having templates in the DOM is ok when you have 5 views. When you have more it's problematic, especially for testing and for precompiling templates.

Backbone is great when you grok it, but it takes a lot of time to find your own patterns that works really well. (Marionette and Chaplin are awesome, but still, first when you have some basic understanding of Backbone itself)

page 1