Rangle.io Reviews

Updated Apr 18, 2021

To filter reviews, or .
3.1
59%
Recommend to a Friend
46%
Approve of CEO
Rangle.io Chief Executive Officer Nick Van Weerdenburg
Nick Van Weerdenburg
45 Ratings
Pros
  • "Rangle has a genuine commitment to diversity and tries to be as inclusive as possible(in 17 reviews)

  • "It used to be a fun place to work, good work life balance(in 7 reviews)

  • Cons
  • "Was employed as a part of my university's student-work program and saw two layoffs in my short time at Rangle(in 12 reviews)

  • "The project I got are no longer interesting and there are way too many middle management who are good with talking(in 4 reviews)

  • More Pros and Cons
    Pros & Cons are excerpts from user reviews. They are not authored by Glassdoor.
    1. 5.0
      Former Employee, more than 1 year

      Family like culture and strong learning culture

      Mar 7, 2021 - Software Developer in Toronto, ON
      Recommend
      CEO Approval
      Business Outlook

      Pros

      - Surreal level of mentorship and talented senior engineers / solutions architects to help guide junior members of the team to correctly solve technical problems. The technical leaders I worked with weren’t only exceptionally experienced, they were all kind individuals who encouraged and sought to bring out the best in all of us. This, in turn, inspired us to mentor new junior developers when we graduated from that junior level and assumed more responsibility, especially as we stayed longer on projects. - I was fortunate enough to have served on one of the most difficult and technically demanding projects at Rangle. While this may only be anecdotal evidence, there was consensus among more senior developers and our solutions architects that this was easily one of the most difficult projects they managed in their careers, which meant that for us junior developers who were on the project, we were able to absorb some of the best practices for React, TypeScript and Node, as the project unfolded. Because of the complexity of the project, we often had to create custom solutions, and had a very strong TypeScript discipline to reinforce good architectural patterns, which left a profound impression on me as I continued to advocate and promote the same architectural rigour and best practices as I had learned from my mentors. - Outside of technical roles, we had some of the best Product Owners, Scrum Masters, who, combined with our engineering leads and managers who interfaced with clients, effectively shielded us from confrontation, angry clients (at times), unreasonable requests, communicating task details, producing progress reports - developers were able to do what they did best - develop. After moving to a new job, where it isn’t the case, I have a whole new level of appreciation for the amazing job our teammates did to protect us from all of this noise. - Outside of project responsibilities, I was pleasantly surprised by the number of learning opportunities there were in the company. There were lunch and learns (anywhere from Deno, design systems, project retrospectives), guilds where folks would gather together and talk about a specialized subject (e.g. Scrum, accessibility, React, TypeScript, etc.), mentorship opportunities to learn from incredible experts in the company. I was fortunate enough that my manager at that time paired me up with an amazing mentor, from whom I was able to ask and get clarity on a variety of questions regarding RxJS, as well as TypeScript, and to whom I remain grateful till this day. - There’s a learning budget where you can spend on buying books (although most folks chose to spend it on going to conferences overseas or locally) to help you learn. It’s not about the amount or this being a perk - the culture of learning, or better ourselves really encouraged us to seek out these opportunities to learn new ways of doing this - this atmosphere of learning was really encouraging to me. - On the subject of conferences, Rangle is probably best known for sponsoring various major conferences in its early days - that’s how it established its expertise, and one of the reasons, I believe, why so many expert level developers were attracted to Rangle. You are encouraged to participate and present (if interested) in these conferences - this allows you to gain experience in public speaking, and was deemed on of the key criteria for a promotion to a more senior level developer.

      Cons

      - The spark that attracted a lot of people (including myself), I believe, was the fact that Rangle was a front end consultancy - it prided itself in having unrivaled JavaScript expertise, and after having worked at Rangle for almost two years, I can agree with that. Unfortunately, this seemed to be becoming less and less the case as we tried to diversify into different areas - with machine learning, backend, DevOps, design systems. As time passed, I felt that we were trying to expand too quickly, too fast, which resulted in diluting the core strengths with which Rangle was founded in the first place. - No CTO after the previous CTO, who was also one of the co-founders, left. This created a technological vacuum where an ambitious vision to expand into more technical diversity and offerings, I felt, began to fall apart. For a consultancy whose strengths and daily work depends on the technical strength of developers, this did not instill confidence amongst us. - Your experience could be really good, or really bad depending on the project. The definition of “good” and “bad” can also vary among people. For example, the first project I served on was amazing in terms of its technical learnings, freedom of choice in terms of tech stack, and the sheer integrity and talent in that team (especially the original team). However, for my second project, I was sent to work with a client with an old tech stack, client-sanctioned hardware equipment, developers on the client side who were backend developers writing front end code the way they would write C# (in all fairness, not their fault - and they were nice, easy-to-work-with developers), some proprietary versioning system which was difficult to use, and had to support IE. Needless to say, that was not a pleasant experience, but as a consultancy, I understood that they only had so many projects they could distribute between developers, and had to do so keeping everyone’s strengths and preferences in mind. But that was not a project I could learn from, and one of the reasons I left. - I had a few occasions to interact with Nick, the CEO - I really liked him as a person and felt he had a compelling vision for leading Rangle to become a great consultancy to expand its offerings beyond its front end roots. However, and I hate to say this, I simply could not agree with some of the choice of senior leaders we had in the company at that time. Alongside some of the most responsible, smart and dedicated teammates I worked with, there were managers and leaders who literally did nothing except to answer a few emails and phone calls. They made no attempt to solve problems, nor to liaise between clients and the team. Initiatives started under their watch in the company had either poor results or minimal traction by any reasonable standard - they were a far cry from the inspiration and exciting vision I heard our CEO share in numerous town halls and talks. - In a similar vein that some leaders didn’t do much, there were also people at certain roles who did very little, which represented an extreme minority of teammates I worked with, or those who were rumored in general to have a subpar work ethic, and a commensurately bad reputation. What added salt to the wound was that a lot of these people who contributed little value were promoted over their hard working, capable peers, much to the chagrin of those who were glossed over and others around them. - At the time, we were a 290-person company, and outside of roles like developers, Scrum Masters, QAs, Solutions Architect, Technical Directors, there were over 130 distinct job titles.

      Continue reading
      5 people found this review helpful
    2. 1.0
      Former Employee

      Worst professional experience of my life.

      Apr 14, 2021 - Anonymous Employee 
      Recommend
      CEO Approval
      Business Outlook

      Pros

      Free drinks and snacks, and the people at the bottom of the pyramid are generally very smart and good at their jobs.

      Cons

      Duplicitous and weak leadership. My bosses seemed susceptible to favouritism and brown-nosing individuals who would just agree with them to get ahead. I never even received a general job description, all my performance feedback (that I sought out proactively from them) was positive, and then i was abruptly let go. Previous to my dismissal I also watched several other people seemingly randomly get let go just based on trivial political motives.

      Continue reading
      3 people found this review helpful
    3. 4.0
      Current Employee

      Optimistic outlook

      Apr 18, 2021 - Software Developer in Toronto, ON
      Recommend
      CEO Approval
      Business Outlook

      Pros

      Good company culture, you work with and learn from a team of skilled developers.

      Cons

      Recovering from a period of instability due to COVID.

      1 person found this review helpful
    4. 4.0
      Former Employee, more than 3 years

      good experience overall

      Mar 25, 2021 - Solutions Architect in Toronto, ON
      Recommend
      CEO Approval
      Business Outlook

      Pros

      Good culture while I was there.

      Cons

      I wish they would focus on promoting from within. There's plenty of talent.

      Be the first to find this review helpful
    5. 3.0
      Former Employee, less than 1 year

      Great Company, Not Great Hiring Experience

      Mar 22, 2021 - Scrum Master in Toronto, ON
      Recommend
      CEO Approval
      Business Outlook

      Pros

      Really smart people working on really cool work You will learn a lot Agile work environment Relaxed west-coast vibe

      Cons

      Hired and soon after was told was making too much and asked to leave

      Continue reading
      1 person found this review helpful
    6. 5.0
      Former Employee

      Pmo

      Mar 6, 2021 - PMO Manager 
      Recommend
      CEO Approval
      Business Outlook

      Pros

      The pay was not bad

      Cons

      More diversity needed here asap

      Be the first to find this review helpful
    7. 1.0
      Former Employee, less than 1 year

      Poor leadership all around.

      Dec 10, 2020 - Full Time in Toronto, ON
      Recommend
      CEO Approval
      Business Outlook

      Pros

      Standard perks like free snacks & swag, joining wellness committees, lunch & learns, monthly spending account, and office location right in Downtown Toronto inside the PATH. Great if you're only starting out in your career, but doesn't mean much once you've gone up the ladder. A pro that no one has talked about is because of the layoffs, I am still in touch with many talented people I am connected with in my network for any future opportunities elsewhere in Toronto.

      Cons

      Was employed as a part of my university's student-work program and saw two layoffs in my short time at Rangle. After the first layoff, management & leadership was very poor and lacked serious decision-making as to why these layoffs needed to be done. Did not learn any technical skills at all as a result, which is very unfortunate. If anything, I learned more interpersonal skills that I can now apply to other workplaces. This negative experience has actually made me switch career paths, which I am grateful of from Rangle.

      Continue reading
      6 people found this review helpful
    8. 5.0
      Current Employee, more than 1 year

      Great Place for Growth

      Feb 1, 2021 - Agile Delivery Manager 
      Recommend
      CEO Approval
      Business Outlook

      Pros

      Despite challenging times, Rangle has AMAZING people and supportive management to allow for growth and ongoing learning.

      Cons

      Some accounts and clients can be challenging

      Continue reading
      Be the first to find this review helpful
    9. 4.0
      Former Employee

      Great place to grow

      Jan 30, 2021 - Design Director in Toronto, ON
      Recommend
      CEO Approval
      Business Outlook

      Pros

      Work with highly talented, driven, and nice people

      Cons

      Opportunity for better operations and process

      Be the first to find this review helpful
    10. 4.0
      Former Employee

      It was good while it lasted, got in at the tail end of it's hay-day

      Sep 28, 2020 - Senior Software Developer in Brampton, ON
      Recommend
      CEO Approval
      Business Outlook

      Pros

      Brilliant developers and designers work here. Back in 2018, we had the education budget, culture hours, regular workshops, cool projects, fun social events, etc. It'll be what you make of it.

      Cons

      Management needs some work, or to have their hands untied. Little room for advancement, managers don't seem invested in your career.

      Continue reading
      2 people found this review helpful
    Viewing 1 - 10 of 80 Reviews

    Popular Careers with Rangle.io Job Seekers

    Software Developer
    Learn About the Job
    JobsSalariesInterviews
    Quality Assurance (QA) Analyst
    Learn About the Job
    Director of Digital Innovation
    Learn About the Job
    Quality Assurance Specialist
    Learn About the Job

    Work at Rangle.io? Share Your Experiences

    Rangle.io logo
    or