Laminar is a problem-driven company with the sole focus on solving the Traffic Problem we have with the mindset of whatever it takes to solve it. As a result, you will find things that are unusual for technology but are driven by the need for the complex problem we are trying to solve. We are starting our beta development in Delhi NCR with expected results of up to 80% reduction in time taken on specific routes with an average reduction of 40% time taken overall and a 30% reduction in pollution emitted by motor vehicles. We are well aware of the complexities we will face in the journey and what kind of resources will be required to solve them; with the support of the government and the blessing of investors, we are confident that we will reach our milestones.
Having a real impact of your work on the ground, where people who know you are part of the team who are solving this complex problem not just thank you but appreciate your effort while you are getting well compensated for your efforts; a place where your team not just care about you but everybody they interact, with unprecedented company culture where we ensure you can perform your best without worries of redundant office politics (like somebody else taking the credit of work you have done). If you also care about people as much as we do, become a jewel of our team, and feel the freedom and autonomy in work at our rapidly growing company, which also takes care of employees’ personal and professional development, then Laminar is place for you!
Looking for a veteran with decades of experience who feels how code will run on the processor level and execute throughout the system. With the knowledge and understanding of all the existing and upcoming technologies to know which will be the best for a particular problem.
The initial team also has a technical background, but recently when we were scaling one of our solutions, it was showing anomalistic behavior. We knew it was because of how OS did the scheduling, but we also understood what it would require fixing those variables and there is no documentation available to solve it in timely fashion. With a vast array of components involved in the solution and how different components will behave with each other would result in a lot of trial and error, which can only be skipped with the addition of experience. With rapid expansion, having somebody who can create and manage large pipelines efficiently is the outlook.
The development of KPIs, tracking them for reliability, efficiency, scalability, and other similar things like management, are implicit and are expected by default.