First of all, I'm really sorry you had a bad candidate experience when interviewing for Private Internet Access in the past.
Although I wasn't involved in your hiring at the time, I'd love for you to reach out to us at recruiting@londontrustmedia.com and provide any feedback about ways in which we could improve our candidate experience. Of course we shouldn't be "ghosting" any candidates and won't do it again but I'd be happy to hear any other ways in which you think our candidate experience has been disrespectful.
About your friend, it's hard for me to tell which candidate it is from this conversation, but if it's recent than it's likely that I was (or should have) been involved. If you can please tell him to contact me with his feedback, I'll be sure to address it the best way I can and ensure it doesn't happen to other candidates in the future.
NoRedInk | Front-end, Backend, Infrastructure Engineer | 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 3 school districts in the US, and students have answered over 1 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. We started with Ruby on Rails on our backend, and have lately been working to introduce Elixir to our stack. 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 OpsWorks and Chef. 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 hiring both engineers who have been around the block many times, as well as those who started their careers just a couple years ago. 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.
After having hired 4 junior engineers in the past quarter, we are currently only hiring engineers with professional programming experience in order to better provide mentorship to our current junior engineers. If you'd like to be considered for this position once it reopened please let us know at jr-engineer-job@noredink.com and we'll reach out to you once the position is available again.
NoRedInk | San Francisco, CA or REMOTE for Senior, 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 3 school districts in the US, and students have answered over 1 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. We started with Ruby on Rails on our backend, and have lately been working to introduce Elixir to our stack. 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 OpsWorks and Chef. 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 hiring both engineers who have been around the block many times, as well as those who started their careers just a couple years ago. 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.
After having hired 4 junior engineers in the past quarter, we are currently only hiring engineers with professional programming experience in order to better provide mentorship to our current junior engineers. If you'd like to be considered for this position once it reopened please let us know at jr-engineer-job@noredink.com and we'll reach out to you once the position is available again.
NoRedInk | San Francisco, CA or REMOTE for Senior, 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 3 school districts in the US, and students have answered over 1 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. We started with Ruby on Rails on our backend, and have lately been working to introduce Elixir to our stack. 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 OpsWorks and Chef. 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 hiring both Senior Engineers who have been around the block many times, as well as Junior Engineers who are just getting started. We’re looking for Junior Engineers who are eager to learn, who thrive on great mentorship, and who want to work on a mission that makes a difference. We’re looking for Senior Engineers who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
NoRedInk | San Francisco, CA or REMOTE for Senior, 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 3 school districts in the US, and students have answered over 1 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. We started with Ruby on Rails on our backend, and have lately been working to introduce Elixir to our stack. 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 OpsWorks and Chef. 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 hiring both Senior Engineers who have been around the block many times, as well as Junior Engineers who are just getting started. We’re looking for Junior Engineers who are eager to learn, who thrive on great mentorship, and who want to work on a mission that makes a difference. We’re looking for Senior Engineers who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
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 3 school districts in the US, and students have answered over 1 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. We started with Ruby on Rails on our backend, and have lately been working to introduce Elixir to our stack. 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 OpsWorks and Chef. 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 hiring both Senior Engineers who have been around the block many times, as well as Junior Engineers who are just getting started. We’re looking for Junior Engineers who are eager to learn, who thrive on great mentorship, and who want to work on a mission that makes a difference. We’re looking for Senior Engineers who are the type of collaborators that value kindness and open-mindedness, over convincing the group they’re right.
NoRedInk | San Francisco, CA (or REMOTE for Sr., up to 6h difference from Pacific)
Full stack rails engineer, backend / infrastructure engineers and frontend engineers wanted to make sure that grammer is taught good. Every one's revolutioneyesing educaton but while some student's cant even right the write words.
Then there was NoRedInk.
NoRedInk helps students quickly improve their grammar and writing skills. We've got a small, technically excellent engineering team.
We're gradually porting all of our React.js and Flux code to Elm, and are really active on the Elm community.
On the backend, we use Rails and MySQL, and manage our AWS deployments using Chef / Opsworks.
NoRedInk | San Francisco, CA (or REMOTE for Sr., up to 6h difference from Pacific)
Full stack rails engineer, backend / infrastructure engineers and frontend engineers wanted to make sure that grammer is taught good. Every one's revolutioneyesing educaton but while some student's cant even right the write words.
Then there was NoRedInk.
NoRedInk helps students quickly improve their grammar and writing skills. We've got a small, technically excellent engineering team.
We're gradually porting all of our React.js and Flux code to Elm, and are really active in the Elm community.
On the backend, we use Rails and MySQL, and manage our AWS deployments using Chef / Opsworks.
NoRedInk | San Francisco, CA (or REMOTE for Sr., up to 6h difference from Pacific)
Full stack rails engineer, backend / infrastructure engineers and frontend engineers wanted to make sure that grammer is taught good. Every one's revolutioneyesing educaton but while some student's cant even right the write words.
Then there was NoRedInk.
NoRedInk helps students quickly improve their grammar and writing skills. We've got a small, technically excellent engineering team.
We're gradually porting all of our React.js and Flux code to Elm, and are really active on the Elm community.
On the backend, we use Rails and MySQL, and manage our AWS deployments using Chef / Opsworks.
NoRedInk in San Francisco (or remote for Sr., up to 6h time zone difference from Pacific)
Full stack rails engineer, backend / infrastructure engineers and frontend engineers wanted to make sure that grammer is taught good. Every one's revolutioneyesing educaton but while some student's cant even right the write words.
Then there was NoRedInk.
NoRedInk helps students quickly improve their grammar and writing skills. We've got a small, technically excellent engineering team.
We're gradually porting all of our React.js and Flux code to Elm, and are really active on the Elm community.
On the backend, we use Rails and MySQL, and manage our AWS deployments using Chef / Opsworks.
First of all, I'm really sorry you had a bad candidate experience when interviewing for Private Internet Access in the past.
Although I wasn't involved in your hiring at the time, I'd love for you to reach out to us at recruiting@londontrustmedia.com and provide any feedback about ways in which we could improve our candidate experience. Of course we shouldn't be "ghosting" any candidates and won't do it again but I'd be happy to hear any other ways in which you think our candidate experience has been disrespectful.
About your friend, it's hard for me to tell which candidate it is from this conversation, but if it's recent than it's likely that I was (or should have) been involved. If you can please tell him to contact me with his feedback, I'll be sure to address it the best way I can and ensure it doesn't happen to other candidates in the future.