NoRedInk | Full-Stack, Site Reliability Engineers, and Engineering Managers| San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk |Full-Stack Engineers,Site Reliability Engineers, and Engineering Managers | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk | Engineering Manager/Developer, Full-Stack, and Site Reliability Engineers | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk |Engineering Manager/Developer, Full-Stack, and Site Reliability Engineers | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk | Full-Stack Engineers, Site Reliability Engineers, and Engineering Managers | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk | Director of Engineering, Full-Stack Engineers, Site Reliability Engineers, and Engineering Managers | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
For our Director of Engineering role, we're seeking an experienced engineering leader who’s operated and scaled a high-performing team, cares about tackling complex technical challenges, and maintains a high bar for talent and engineering practices.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk | Director of Engineering, Site Reliability Engineers, Engineering Managers | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
For our Director of Engineering role, we're seeking an experienced engineering leader who’s operated and scaled a high-performing team, cares about tackling complex technical challenges, and maintains a high bar for talent and engineering practices.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk | Back-End, Front-End, Full-Stack, and Site Reliability Engineers | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk | Back-End, Front-End, Full-Stack, and Site Reliability Engineers | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk | Back-End, Front-End, Full-Stack, and Site Reliability Engineers | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 2 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
NoRedInk | Engineering Manager, Back-end, Front-end, Full-stack, SRE | San Francisco, CA | REMOTE Pacific Time (PST) to Central European Time (CET)
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 2 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
We’re an ed-tech company on a mission to help all students become strong writers! Our team may be small, but NoRedInk is used by 1 in 2 school districts in the US, and students have answered over 5 billion questions on our platform.
We’re a group of friendly people who listen to and learn from each other. We discuss past mistakes openly so we can adapt our processes to the challenges that come with progress. Puns flow freely across our San Francisco office as well as on Slack, and we have remote engineers spanning six different time zones.
Our engineering team [1] prides itself on code quality and innovation. We use the cutting-edge Elm programming language for all our new front-end code, and have been migrating legacy React code to Elm as well. Our back-end is primarily Ruby on Rails, although we are working to split off smaller services as we scale to keep up with our traffic. You can read about our experiences with these technologies on our team blog! [2]
In addition to spending work hours open-sourcing useful libraries we develop [3], we also invest financially in open source. We hired the creator of Elm, Evan Czaplicki, to develop Elm full time. [4] Evan discusses his plans for the language with the team every week, periodically pairs with other engineers on Elm, and cracks up members of the sales team with his lunchtime jokes.
We use Amazon AWS for our infrastructure and automate all of our deployments using Chef and OpsWorks. We write a lot of tests, and use Jenkins for continuous integration. Our process for new features begins with our product team and in-house visual designer, continues with a GitHub pull request from a feature branch into master, and ends with our in-house QA specialist trying to break it before it reaches production.
We’re looking for engineers who want to work on a mission that makes a difference and who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
You can learn more about what to expect through blog posts about our interview process [5] and on-boarding experience [6].
If you’re interested, please apply through our jobs page! https://www.noredink.com/jobs
[1] https://www.noredink.com/about/team
[2] http://tech.noredink.com/
[3] https://github.com/NoRedInk/
[4] http://tech.noredink.com/post/136615783598/welcome-evan
[5] http://tech.noredink.com/post/145260396603/our-engineering-h...
[6] http://tech.noredink.com/post/143787279069/on-boarding-as-a-...