Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Narrative I/O | Scala Backend Engineer| New York, NY | Full-time | ONSITE, REMOTE | http://narrative.io/

Narrative is building the first global data marketplace. It has often been said that data is the new currency. Unfortunately, maximizing the value of data is often easier said than done. On one side, transacting via individual point to point integrations carries a lot of overhead in both business development and technical integration efforts. On the other, going through big aggregators introduces opacity in the pricing and provenance of the data. At Narrative, we help our customers get value from their data by building a central auction platform to reduce the friction and tooling to increase the transparency in this process.

We are a small, early stage team looking for great developers who want to jump in and take major systems and user-facing features from design to launch. Here's where we are now:

- We are operating in Amazon Web Services. Our services are mainly deployed on EC2 provisioned with Terraform.

- We also heavily use other technology on AWS such as DynamoDB, S3, and RDS.

- Our backend includes a data ingestion web service with supporting Kinesis consumers, along with a growing array of Spark projects. It’s written mostly in Scala, with a smattering of Python for lambda functions.

- We sit somewhere in the middle of the “Scala as a worse Haskell” and “Scala as a better Java” spectrum. We love functional programming and we do make use of libraries like cats, but at the same time we heavily favor core language features and have no intention of rewriting everything using Free Monads.

- Our frontend is written in Typescript with Angular2 and a supporting API running on Node, and is deployed and monitored using much the same supporting tech as the backend.

- Other services we use include: GitHub, CircleCI, DataDog.

Apply by sending your resume to hiring@narrative.io.

We are hiring for the backend role and are building the team with a remote-first mindset.

- Scala Backend Engineer: http://transparency.narrative.io/join/backend.html

Some more useful links:

- Find out more about Company Culture: http://transparency.narrative.io/culture.



sort by: page size:

Narrative I/O | Scala Backend Engineer| New York, NY | Full-time | ONSITE, REMOTE | http://narrative.io/

Narrative is building the first global data marketplace. It has often been said that data is the new currency. Unfortunately, maximizing the value of data is often easier said than done. On one side, transacting via individual point to point integrations carries a lot of overhead in both business development and technical integration efforts. On the other, going through big aggregators introduces opacity in the pricing and provenance of the data. At Narrative, we help our customers get value from their data by building a central auction platform to reduce the friction and tooling to increase the transparency in this process.

We are a small, early stage team looking for great developers who want to jump in and take major systems and user-facing features from design to launch. Here's where we are now:

- We are operating in Amazon Web Services. Our services are mainly deployed on EC2 provisioned with Terraform.

- We also heavily use other technology on AWS such as DynamoDB, S3, and RDS.

- Our backend includes a data ingestion web service with supporting Kinesis consumers, along with a growing array of Spark projects. It’s written mostly in Scala, with a smattering of Python for lambda functions.

- We sit somewhere in the middle of the “Scala as a worse Haskell” and “Scala as a better Java” spectrum. We love functional programming and we do make use of libraries like cats, but at the same time we heavily favor core language features and have no intention of rewriting everything using Free Monads.

- Our frontend is written in Typescript with Angular2 and a supporting API running on Node, and is deployed and monitored using much the same supporting tech as the backend.

- Other services we use include: GitHub, CircleCI, DataDog.

Apply at hiring@narrative.io. We are hiring for a Scala Backend Engineering role and are building the team with a remote-first mindset.

- Scala Backend Engineer: http://transparency.narrative.io/join/backend.html

Some more useful links:

- Find out more about Company Culture: http://transparency.narrative.io/culture.html.

- More about the hiring process: http://transparency.narrative.io/join/dev-process.html.

- A day in the life of a dev: http://transparency.narrative.io/culture/dev/day-in-life.htm... of a dev.


Narrative I/O | Scala Backend Engineer, Angular Frontend Engineer| New York, NY | Full-time | ONSITE, REMOTE | http://narrative.io/

Narrative is building the first global data marketplace. It has often been said that data is the new currency. Unfortunately, maximizing the value of data is often easier said than done. On one side, transacting via individual point to point integrations carries a lot of overhead in both business development and technical integration efforts. On the other, going through big aggregators introduces opacity in the pricing and provenance of the data. At Narrative, we help our customers get value from their data by building a central auction platform to reduce the friction and tooling to increase the transparency in this process.

We are a small, early stage team looking for great developers who want to jump in and take major systems and user-facing features from design to launch. Here's where we are now:

- We are operating in Amazon Web Services. Our services are mainly deployed on EC2 provisioned with Terraform.

- We also heavily use other technology on AWS such as DynamoDB, S3, and RDS.

- Our backend includes a data ingestion web service with supporting Kinesis consumers, along with a growing array of Spark projects. It’s written mostly in Scala, with a smattering of Python for lambda functions.

- We sit somewhere in the middle of the “Scala as a worse Haskell” and “Scala as a better Java” spectrum. We love functional programming and we do make use of libraries like cats, but at the same time we heavily favor core language features and have no intention of rewriting everything using Free Monads.

- Our frontend is written in Typescript with Angular2 and a supporting API running on Node, and is deployed and monitored using much the same supporting tech as the backend.

- Other services we use include: GitHub, CircleCI, DataDog.

Apply by sending your resume to hiring@narrative.io.

We are hiring for the following positions and are building the team with a remote-first mindset.

- Scala Backend Engineer: http://transparency.narrative.io/join/backend.html

- Frontend Engineer http://transparency.narrative.io/join/frontend.html

Some more useful links:

- Find out more about Company Culture: http://transparency.narrative.io/culture.


Narrative I/O | Scala Backend Engineer, Angular Frontend Engineer| New York, NY | Full-time | ONSITE, REMOTE | http://narrative.io/

Narrative is building the first global data marketplace. It has often been said that data is the new currency. Unfortunately, maximizing the value of data is often easier said than done. On one side, transacting via individual point to point integrations carries a lot of overhead in both business development and technical integration efforts. On the other, going through big aggregators introduces opacity in the pricing and provenance of the data. At Narrative, we help our customers get value from their data by building a central auction platform to reduce the friction and tooling to increase the transparency in this process.

We are a small, early stage team looking for great developers who want to jump in and take major systems and user-facing features from design to launch. Here's where we are now:

- We are operating in Amazon Web Services. Our services are mainly deployed on EC2 provisioned with Terraform.

- We also heavily use other technology on AWS such as DynamoDB, S3, and RDS.

- Our backend includes a data ingestion web service with supporting Kinesis consumers, along with a growing array of Spark projects. It’s written mostly in Scala, with a smattering of Python for lambda functions.

- We sit somewhere in the middle of the “Scala as a worse Haskell” and “Scala as a better Java” spectrum. We love functional programming and we do make use of libraries like cats, but at the same time we heavily favor core language features and have no intention of rewriting everything using Free Monads.

- Our frontend is written in Typescript with Angular2 and a supporting API running on Node, and is deployed and monitored using much the same supporting tech as the backend.

- Other services we use include: GitHub, CircleCI, DataDog.

Apply by sending your resume to hiring@narrative.io.

We are hiring for a Scala Backend Engineering role and are building the team with a remote-first mindset.

- Scala Backend Engineer: http://transparency.narrative.io/join/backend.html

- Frontend Engineer http://transparency.narrative.io/join/frontend.html

Some more useful links:

- Find out more about Company Culture: http://transparency.narrative.io/culture.html.


Narrative I/O | Scala Backend Engineer, Angular Frontend Engineer| New York, NY | Full-time | ONSITE, REMOTE | http://narrative.io/

Narrative is building the first global data marketplace. It has often been said that data is the new currency. Unfortunately, maximizing the value of data is often easier said than done. On one side, transacting via individual point to point integrations carries a lot of overhead in both business development and technical integration efforts. On the other, going through big aggregators introduces opacity in the pricing and provenance of the data. At Narrative, we help our customers get value from their data by building a central auction platform to reduce the friction and tooling to increase the transparency in this process.

We are a small, early stage team looking for great developers who want to jump in and take major systems and user-facing features from design to launch. Here's where we are now:

- We are operating in Amazon Web Services. Our services are mainly deployed on EC2 provisioned with Terraform.

- We also heavily use other technology on AWS such as DynamoDB, S3, and RDS.

- Our backend includes a data ingestion web service with supporting Kinesis consumers, along with a growing array of Spark projects. It’s written mostly in Scala, with a smattering of Python for lambda functions.

- We sit somewhere in the middle of the “Scala as a worse Haskell” and “Scala as a better Java” spectrum. We love functional programming and we do make use of libraries like cats, but at the same time we heavily favor core language features and have no intention of rewriting everything using Free Monads.

- Our frontend is written in Typescript with Angular2 and a supporting API running on Node, and is deployed and monitored using much the same supporting tech as the backend.

- Other services we use include: GitHub, CircleCI, DataDog.

Apply by sending your resume to hiring@narrative.io.

We are hiring for the backend and frontend roles and are building the team with a remote-first mindset.

- Scala Backend Engineer: http://transparency.narrative.io/join/backend.html

- Frontend Engineer: http://transparency.narrative.io/join/frontend.html

Some more useful links:

- Find out more about Company Culture: http://transparency.narrative.io/culture.


Narrative I/O | Scala Backend Engineer, Angular Frontend Engineer| New York, NY | Full-time | ONSITE, REMOTE (US,Canada) | http://narrative.io/

Narrative is building the first global data marketplace. It has often been said that data is the new currency. Unfortunately, maximizing the value of data is often easier said than done. On one side, transacting via individual point to point integrations carries a lot of overhead in both business development and technical integration efforts. On the other, going through big aggregators introduces opacity in the pricing and provenance of the data. At Narrative, we help our customers get value from their data by building a central auction platform to reduce the friction and tooling to increase the transparency in this process.

We are a small, early stage team looking for great developers who want to jump in and take major systems and user-facing features from design to launch. Here's where we are now:

- We are operating in Amazon Web Services. Our services are mainly deployed on EC2 provisioned with Terraform.

- We also heavily use other technology on AWS such as DynamoDB, S3, and RDS.

- Our backend includes a data ingestion web service with supporting Kinesis consumers, along with a growing array of Spark projects. It’s written mostly in Scala, with a smattering of Python for lambda functions.

- We sit somewhere in the middle of the “Scala as a worse Haskell” and “Scala as a better Java” spectrum. We love functional programming and we do make use of libraries like cats, but at the same time we heavily favor core language features and have no intention of rewriting everything using Free Monads.

- Our frontend is written in Typescript with Angular2 and a supporting API running on Node, and is deployed and monitored using much the same supporting tech as the backend.

- Other services we use include: GitHub, CircleCI, DataDog.

Apply by sending your resume to hiring@narrative.io.

We are hiring for the backend and frontend roles and are building the team with a remote-first mindset.

Some more useful links:

- Find out more about Company Culture: http://transparency.narrative.io/culture.


Agree, I'm a remote Scala engineer.

I work with Scala remotely, and we're hiring! (send me a PM).

Oh man I would love to work with Scala

Just more anecdata; most of the Scala positions I've seen are data engineering roles with Spark. I need to look harder for Scala roles without Spark.

FWIW (and we're hiring) ... several AWS services are already written in Scala.

As a Scala developer at one of the major Scala-using companies, this feels on-the-money.

Bonus points for having a Scala SDK!

Scala.

Scala.

scala.

Scala.

I'm a scala engineer. I also work with elixir a bit but Scala is preferred.

Glad to see another successful startup which uses Scala :) http://engineering.klout.com/

Awesome. We're using Scala and Akka, and are hiring, by the way. http://blog.getgush.com
next

Legal | privacy