OMsignal is made possible by the expertise of Smart Textile experts,
Data/Bio Scientists, Hardware, Firmware and
Software Engineers. Please note that this offer is mostly focused on
Full Stack Engineers, but we are also looking to
hire smart Data Scientists who have an interest in biodata and possibly
people who could help bridging BLE/MSP firmware and driver development.
What we do
==========
OMsignal is an exciting Montreal start-up developing a revolutionary
line of bio-sensing clothes that connect seamlessly
to smartphones. The company is at the intersection of the wearable
technology, well-being and fashion markets.
We are a well-funded startup [1] working to deliver a smart biometric
shirt. You can read more about our mission on [2].
And for those who followed the US Open 2014, we are the technology
behind Ralph Laurent Polo Tech.
We just shipped the product to our first customers.
What we are looking for
=======================
We are looking for Full Stack Software Engineers who can
help us to architect, design and implement a complex system based
on bleeding edge technologies (Scala, Akka, Spray, Reactive Programming [3],
iOS, Swift, Docker...), a modern architectural
style (Micro Services, CQRS, Event Sourcing, Eventual Consistency),
and a clean codebase (Clean Code, Domain Driven Design…) -- emphasis on
the “Engineer” over the “Full Stack” part.
In-depth knowledge of the technologies we use is not required, but
having strong Software Engineering foundations is
(Algorithmics, Design and Architectural Patterns, …).
Understanding that code is read much more often than it is
written is an absolute must.
You should be willing to face the upcoming challenges
(Machine Learning, Predictive algorithms,
Opening the platform/iOS SDK/API, -- who knows the rest?…).
And of course, you need to speak/write english fluently
(we need to understand each other, right ?)
The Technologies we currently use
=================================
- Backend : Scala, Akka, Akka Persistence, Spray, ReactiveMongo, SBT, Kafka, ZooKeeper
- Web : NodeJS, AngularJS
- iOS : Swift, Objective C, ReactiveCocoa, Core Bluetooth, CocoaPods`
- DevOps : Ubuntu, Docker, Ruby, Amazon AWS/EC2
- Project management: git/github
The `iOS` stack is more sophisticated than the average iOS App.
It includes a Pub/Sub system similar
to `Apache Kafka` (that we call iOS Kafka internally),
makes heavy use of
asynchronous programming + `CQRS`/`Event Sourcing` and
computes biometric algorithms and reports.
Our culture
===========
We get some inspiration from the Open Source model to
achieve high-cohesion (within teams) and
low-coupling (between teams) : small, empowered teams,
systematic pull requests, developer autonomy.
Our software engineering practices are also influenced
by Antifragile [4] principles
(Small is Beautiful, Less is more, Hormesis principle,
evolutionary darwinism, over-compensation ...)
And if you are on the Paleo diet, like hiking/camping or
enjoy a good raclette you will certainly find friends here!
Next step
=========
If you are curious about the project and want to explore
opportunities working with us, you can
- reach out to dev@omsignal.com
- come hang out on IRC (irc.freenode.net #omsignal) to ask your questions
If you have a `github`/`bitbucket` account, we would love to take
a look at what you like doing
(even if you feel ashamed of it in retrospective -- explain us
what you would improve now)
OMsignal is made possible by the expertise of Smart Textile experts,
Data/Bio Scientists, Hardware, Firmware and
Software Engineers. Please note that this offer is mostly focused on
Full Stack Engineers, but we are also looking to
hire smart Data Scientists who have an interest in biodata and possibly
people who could help bridging BLE/MSP firmware and driver development.
What we do
==========
OMsignal is an exciting Montreal start-up developing a revolutionary
line of bio-sensing clothes that connect seamlessly
to smartphones. The company is at the intersection of the wearable
technology, well-being and fashion markets.
We are a well-funded startup [1] working to deliver a smart biometric
shirt. You can read more about our mission on [2].
And for those who followed the US Open 2014, we are the technology
behind Ralph Laurent Polo Tech.
We just shipped the product to our first customers.
What we are looking for
=======================
We are looking for Full Stack Software Engineers who can
help us to architect, design and implement a complex system based
on bleeding edge technologies (Scala, Akka, Spray, Reactive Programming [3],
iOS, Swift, Docker...), a modern architectural
style (Micro Services, CQRS, Event Sourcing, Eventual Consistency),
and a clean codebase (Clean Code, Domain Driven Design…) -- emphasis on
the “Engineer” over the “Full Stack” part.
In-depth knowledge of the technologies we use is not required, but
having strong Software Engineering foundations is
(Algorithmics, Design and Architectural Patterns, …).
Understanding that code is read much more often than it is
written is an absolute must.
You should be willing to face the upcoming challenges
(Machine Learning, Predictive algorithms,
Opening the platform/iOS SDK/API, -- who knows the rest?…).
And of course, you need to speak/write english fluently
(we need to understand each other, right ?)
The Technologies we currently use
=================================
- Backend : Scala, Akka, Akka Persistence, Spray, ReactiveMongo, SBT, Kafka, ZooKeeper
- Web : NodeJS, AngularJS
- iOS : Swift, Objective C, ReactiveCocoa, Core Bluetooth, CocoaPods`
- DevOps : Ubuntu, Docker, Ruby, Amazon AWS/EC2
- Project management: git/github
The `iOS` stack is more sophisticated than the average iOS App.
It includes a Pub/Sub system similar
to `Apache Kafka` (that we call iOS Kafka internally),
makes heavy use of
asynchronous programming + `CQRS`/`Event Sourcing` and
computes biometric algorithms and reports.
Our culture
===========
We get some inspiration from the Open Source model to
achieve high-cohesion (within teams) and
low-coupling (between teams) : small, empowered teams,
systematic pull requests, developer autonomy.
Our software engineering practices are also influenced
by Antifragile [4] principles
(Small is Beautiful, Less is more, Hormesis principle,
evolutionary darwinism, over-compensation ...)
And if you are on the Paleo diet, like hiking/camping or
enjoy a good raclette you will certainly find friends here!
Next step
=========
If you are curious about the project and want to explore
opportunities working with us, you can
- reach out to dev@omsignal.com
- come hang out on IRC (irc.freenode.net #omsignal) to ask your questions
If you have a `github`/`bitbucket` account, we would love to take
a look at what you like doing
(even if you feel ashamed of it in retrospective -- explain us
what you would improve now)
We are looking for a Site Reliability Engineer who can
help us operate and scale a reactive, event-driven system based
on bleeding edge technologies (Scala, Akka, Spray, Reactive Programming,
iOS, Swift, Docker...), a modern architectural
style (Micro Services, CQRS, Event Sourcing, Eventual Consistency),
and a clean codebase (Clean Code, Domain Driven Design…).
Do you have specific examples of where things break hard?
We are currently using ES end to end for a distributed application including a wearable device, iOS app and scala backend, and up to now, the things that broke hard in the system are the naive/non ES parts.
For information, on the server-side, we are currently experimenting with GetEventStore (https://geteventstore.com/), which seems to be working well for us.
You basically consider the event log as a big collection,and you "fold over" the events in order to incrementally build your state/projection, the same way you would do with finite collections in a Functional language (scala, haskell, ...).
Narrative I/O | 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.
Here are some examples of projects that we would like some help with:
- Interactive tools to help buyers discover the data they need to accomplish their business objectives.
- Interactive tools to help sellers maximize the yield from the data that they are selling.
- Data analytics pipelines to drive the interactive report UIs. For example: reports for yield forecasting and deal pre-qualification.
- Implementing additional infrastructure to support transactions for more types of data.
- Improving the latency and resource usage of our transaction processes.
Apply at hiring@narrative.io. We are hiring for Backend and Frontend Software Engineering roles and are building the team with a remote-first mindset.
Narrative I/O | 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.
Narrative I/O | 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.
Narrative I/O | 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.
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.
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.
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.
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.
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.
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.
Narrative I/O | Scala/AWS/Spark Backend Engineer, VueJS Frontend Engineer| New York, NY | Full-time | ONSITE, REMOTE | http://narrative.io/
Narrative is building a data streaming marketplace that makes it easy to buy, sell and win.
We do this by creating tools that reduce the friction and increase transparency in the data buying process, creating a win-win relationship between buyers and sellers.
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.
We are building the team with a remote-first mindset, and as a result every team member is expected to have an ability to synthesize business requirements, distill the domain, contribute to high-level design documents, efficiently communicate asynchronously, and more generally work autonomously toward a shared vision.
While the company's headquarter is in NYC, the development team is currently made of engineers working from California (US), Québec (Canada), New Brunswick (Canada) and British Columbia (Canada).
Our technical stack (Scala, AWS, Spark on the backend, VueJS on the frontend) looks like:
- Our webapp frontend projects are written in Vuejs, Sass and Pug. We make use of modern and fuctional JavaScript patterns.
- 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, cats-effect, http4s, doobie, but keep a pragmatic stance on purity and are also exposed to the AWS Java SDK/hadoop/spark ecosystems.
- We are operating in Amazon Web Services. Our long-running services are deployed on EC2, Fargate, and Lambda and provisioned with Terraform. Our scheduled (spark) jobs are mostly executing on EMR and triggered by Jenkins Jobs.
- We also heavily use other AWS technologies such as DynamoDB, S3, RDS, Step Functions and EMR.
- Other services we use include: GitHub, Gitlab, Jenkins, DataDog, Crucible.
- Being a small team, we think twice before rolling out custom infra that we need to monitor and maintain.
Narrative I/O | Scala/AWS/Spark Backend Engineer, VueJS Frontend Engineer| New York, NY | Full-time | ONSITE, REMOTE | http://narrative.io/
Narrative is building a data streaming marketplace that makes it easy to buy, sell and win.
We do this by creating tools that reduce the friction and increase transparency in the data buying process, creating a win-win relationship between buyers and sellers.
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.
We are building the team with a remote-first mindset, and as a result every team member is expected to have an ability to synthesize business requirements, distill the domain, contribute to high-level design documents, efficiently communicate asynchronously, and more generally work autonomously toward a shared vision.
While the company's headquarter is in NYC, the development team is currently made of engineers working from California (US), Québec (Canada), New Brunswick (Canada) and British Columbia (Canada).
Our technical stack (Scala, AWS, Spark on the backend, VueJS on the frontend) looks like:
- Our webapp frontend projects are written in Vuejs, Sass and Pug. We make use of modern and fuctional JavaScript patterns.
- 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, cats-effect, http4s, doobie, but keep a pragmatic stance on purity and are also exposed to the AWS Java SDK/hadoop/spark ecosystems.
- We are operating in Amazon Web Services. Our long-running services are deployed on EC2, Fargate, and Lambda and provisioned with Terraform. Our scheduled (spark) jobs are mostly executing on EMR and triggered by Jenkins Jobs.
- We also heavily use other AWS technologies such as DynamoDB, S3, RDS, Step Functions and EMR.
- Other services we use include: GitHub, Gitlab, Jenkins, DataDog, Crucible.
- Being a small team, we think twice before rolling out custom infra that we need to monitor and maintain.
Narrative I/O | Scala/AWS/Spark Backend Engineer, VueJS Frontend Engineer| New York, NY | Full-time | ONSITE, REMOTE | http://narrative.io/
Narrative is building a data streaming marketplace that makes it easy to buy, sell and win.
We do this by creating tools that reduce the friction and increase transparency in the data buying process, creating a win-win relationship between buyers and sellers.
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.
We are building the team with a remote-first mindset, and as a result every team member is expected to have an ability to synthesize business requirements, distill the domain, contribute to high-level design documents, efficiently communicate asynchronously, and more generally work autonomously toward a shared vision.
While the company's headquarter is in NYC, the development team is currently made of engineers working from California (US), Québec (Canada), New Brunswick (Canada) and British Columbia (Canada).
Our technical stack (Scala, AWS, Spark on the backend, VueJS on the frontend) looks like:
- Our webapp frontend projects are written in Vuejs, Sass and Pug. We make use of modern and fuctional JavaScript patterns.
- 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, cats-effect, http4s, doobie, but keep a pragmatic stance on purity and are also exposed to the AWS Java SDK/hadoop/spark ecosystems.
- We are operating in Amazon Web Services. Our long-running services are deployed on EC2, Fargate, and Lambda and provisioned with Terraform. Our scheduled (spark) jobs are mostly executing on EMR and triggered by Jenkins Jobs.
- We also heavily use other AWS technologies such as DynamoDB, S3, RDS, Step Functions and EMR.
- Other services we use include: GitHub, Gitlab, Jenkins, DataDog, Crucible.
- Being a small team, we think twice before rolling out custom infra that we need to monitor and maintain.
Narrative I/O | Senior Backend Engineer | New York, NY | Full-time | REMOTE | $120k to $200k USD | https://narrative.io/
Narrative has been building a data collaboration platform designed for simplicity and ease of use since being founded in 2016.
Our primary strength is functioning as a data marketplace where we differentiate ourselves by automatically standardizing data across suppliers, making data available via powerful query interfaces (both intuitive UIs and an SQL dialect) instead of via one-size-fits-all pre-packaged datasets, and giving data providers the ability to define row-level access and pricing policies. The same building blocks that power the marketplace enable other data collaboration use cases, like clean room data analysis and the automatic segmentation and delivery of data to other platforms. We're also building towards a future where users can leverage our collaboration tools without needing to push their data to us, instead our query engine will be embeddable where their data is already at rest.
We are a small, remote-first team looking for great developers who want to jump in and take major systems and user-facing features from design to launch. While the company's headquarters are in NYC, the development team currently includes engineers working from the US (California and New York), Canada (Alberta, British Columbia, and Québec), and Poland.
In brief, the technologies we use are:
- Scala, Spark, Apache Iceberg, and Apache Calcite in the backend. We love functional programming and make use of libraries like Cats, Cats-Effect, and FS2, but we keep a pragmatic stance on purity given our exposure to the Spark ecosystem.
- Our services are deployed on AWS and provisioned using Terraform. We leverage the usual suspects: Fargate, EMR, RDS, Lambda, etc. and we're starting to lean into Kubernetes. Being a small team, we think twice before rolling out custom infrastructure that we'll need to monitor and maintain.
- On the frontend, we use Typescript, VueJS, PrimeVue, Nuxt, and Vite.
Job postings and more on information about our team and culture are available at: https://jobs.narrative.io/
Apply by sending your resume to hiring-dev@narrative.io.
Narrative I/O | Senior Backend Engineer | New York, NY | Full-time | REMOTE | $120k to $200k USD | https://narrative.io/
Since being founded in 2016, Narrative has been building a data collaboration platform designed for simplicity and ease-of-use which is trusted by Fortune 500 companies and startups alike.
Our primary strength is functioning as a data marketplace where we differentiate ourselves by automatically standardizing data across suppliers, making data available via powerful query interfaces (both intuitive UIs and an SQL dialect) instead of via one-size-fits-all pre-packaged datasets, and giving data providers the ability to define row-level access and pricing policies. The same building blocks that power the marketplace enable other data collaboration use cases, like clean room data analysis and the automatic segmentation and delivery of data to other platforms. We're also building towards a future where users can leverage our collaboration tools without needing to push their data to us, instead our query engine will be embeddable where their data is already at rest.
We are a small, remote-first team looking for great developers who want to jump in and take major systems and user-facing features from design to launch. While the company's headquarters are in NYC, the development team currently includes engineers working from the US (California and New York), Canada (Alberta, British Columbia, and Québec), and Poland.
In brief, the technologies we use are:
- Scala, Spark, Apache Iceberg, and Apache Calcite in the backend. We love functional programming and make use of libraries like Cats, Cats-Effect, and FS2, but we keep a pragmatic stance on purity given our exposure to the Spark ecosystem.
- Our services are deployed on AWS and provisioned using Terraform. We leverage the usual suspects: Fargate, EMR, RDS, Lambda, etc. and we're starting to lean into Kubernetes. Being a small team, we think twice before rolling out custom infrastructure that we'll need to monitor and maintain.
- On the frontend, we use Typescript, VueJS, PrimeVue, Nuxt, and Vite.
Job postings and more on information about our team and culture are available at: https://jobs.narrative.io/
Apply by sending your resume to hiring-dev@narrative.io.
Headquarters: Montreal | http://www.omsignal.com
Link to Job Offer: https://github.com/OMsignal/omsignal-job-offers/blob/master/...
OMsignal is made possible by the expertise of Smart Textile experts, Data/Bio Scientists, Hardware, Firmware and Software Engineers. Please note that this offer is mostly focused on Full Stack Engineers, but we are also looking to hire smart Data Scientists who have an interest in biodata and possibly people who could help bridging BLE/MSP firmware and driver development.
OMsignal is an exciting Montreal start-up developing a revolutionary line of bio-sensing clothes that connect seamlessly to smartphones. The company is at the intersection of the wearable technology, well-being and fashion markets.We are a well-funded startup [1] working to deliver a smart biometric shirt. You can read more about our mission on [2]. And for those who followed the US Open 2014, we are the technology behind Ralph Laurent Polo Tech.
We just shipped the product to our first customers.
We are looking for Full Stack Software Engineers who can help us to architect, design and implement a complex system based on bleeding edge technologies (Scala, Akka, Spray, Reactive Programming [3], iOS, Swift, Docker...), a modern architectural style (Micro Services, CQRS, Event Sourcing, Eventual Consistency), and a clean codebase (Clean Code, Domain Driven Design…) -- emphasis on the “Engineer” over the “Full Stack” part.In-depth knowledge of the technologies we use is not required, but having strong Software Engineering foundations is (Algorithmics, Design and Architectural Patterns, …). Understanding that code is read much more often than it is written is an absolute must.
You should be willing to face the upcoming challenges (Machine Learning, Predictive algorithms, Opening the platform/iOS SDK/API, -- who knows the rest?…).
And of course, you need to speak/write english fluently (we need to understand each other, right ?)
The `iOS` stack is more sophisticated than the average iOS App. It includes a Pub/Sub system similar to `Apache Kafka` (that we call iOS Kafka internally), makes heavy use of asynchronous programming + `CQRS`/`Event Sourcing` and computes biometric algorithms and reports. We get some inspiration from the Open Source model to achieve high-cohesion (within teams) and low-coupling (between teams) : small, empowered teams, systematic pull requests, developer autonomy.Our software engineering practices are also influenced by Antifragile [4] principles (Small is Beautiful, Less is more, Hormesis principle, evolutionary darwinism, over-compensation ...)
And if you are on the Paleo diet, like hiking/camping or enjoy a good raclette you will certainly find friends here!
If you are curious about the project and want to explore opportunities working with us, you can - reach out to dev@omsignal.com - come hang out on IRC (irc.freenode.net #omsignal) to ask your questionsIf you have a `github`/`bitbucket` account, we would love to take a look at what you like doing (even if you feel ashamed of it in retrospective -- explain us what you would improve now)
[1] http://www.omsignal.com/blogs/omsignal-blog/14669049-omsigna... [2] http://venturebeat.com/2014/04/16/brave-new-wearable-world-c... [3] http://www.reactivemanifesto.org/ [4] http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...