Mission: Our mantra is: It's not just business, it's personal!
Nulogy is a Canadian success story. Our story started 15 years ago when four engineering grads from the University of Waterloo worked on a design project that grew to become Nulogy. We are now a world-leading provider of specialized solutions for complex supply-chain challenges.
As a company founded by friends wanting to make a difference, the close relationship between our founders influenced the family-like culture that exists at Nulogy! This informs our mantra, “It’s not just business, it’s personal”.
Quality and collaboration are at the core of Nulogy’s engineering culture. We build teams that can level-up together, diffuse their knowledge, and build their experiences into a stronger product. That means using modern agile practices to guide our work.
We are looking for developers that love solving difficult domain problems. If pair programming, TDD, continuous integration, story walls, and retrospectives are your thing, then you’re halfway there. Couple that with a sense of humour, humility, and strong work ethic and we’re intrigued. Studied DDD or GOOS? We should definitely talk!
Je travaille chez Nulogy à plein temps (Plus de 3 ans)
Some company leaders claim that they care about their employees but when you need them the most they are nowhere to be found. This is not the case at Nulogy. Everyone who works here genuinely cares about not just the work they are doing, but they people they are working with. The leaders here deeply care about their employees, that is undeniable.
I haven't had any profound negative experiences at Nulogy. Any company has some drama or frustrating experiences. Such is life.
J'ai postulé en ligne. J'ai passé une entrevue à Nulogy (Toronto, ON) en avril 2017.
Super slow. And unresponsive.
So slow that I ended up taking a role with Facebook in the process of this application because Facebook was way more organised in scheduling interviews and was actually looking for an engineer and no a comments formatter.
First call was great and was handled by an actual engineer. It was helpful to jump right to the tech talk.
Assignment was super easy, however it was rejected due to flood of personal and styling preferences of the reviewers.
I even got a comment about using `class << self` questioning what it does and wether it's needed at all in a module. Yes it could be `extend Namespace` or it could be a `class` even. Point is it's a personal or a style matter. Candidates have no idea about your internal style-guides.
Statement about the use of blocks just killed the last bits of my interest in this company. Assignment review speaks for the level of knowledge and type of environment.
Funny, some failed to even bring the environment without dependencies locally. Literally all you need is: irb and a bash.
I am glad the interview process is over with just an assignment and I haven't wasted more of my time.
Good luck with your business guys.
Questions d'entretien d'embauche