Mohit Dilawari is the Senior Engineering Director at Localytics, a leading mobile engagement platform based in Boston. Localytics gives companies the insights and tools they need to grow and engage with their customer base. Approaching 200 employees, Localytics serves such companies at The Wall Street Journal, The New York Times, and Hulu.
Localytics’ buzzwords include analytics, big data, and marketing automation. Essentially, their business takes in a lot of data from mobile apps and gives it to their clients. This gives them insight into their customer base with predictive analytics and allows their clients to market directly to their customers via in-app messaging and push messaging. Localytics entire company is born out of mobile and cloud technologies.
Mohit’s role is to manage and run a portion of the engineering team, specifically those that work on their product’s backend and platform. When he first started with Localytics five years ago, the entire company comprised of about 10 employees. Now, he has 3 managers reporting into him, with 4-5 direct reports each. The entirety of the Localytics engineering team is made up of about 45 people, 50 including management.
By and large, he delegates most of the engineering work to his team. However, because he does have the technical know-how and the experience, he tries to be as hands-on as possible. He still “hacks on stuff” in his spare time.
He prides the company on having hard working, talented engineers, and in his words, “no jerks!”
Localytics + TeamPassword
For Localytics, TeamPassword solved the problem he had with databases that only allow one single data admin. Because Localytics is a Software as a Service company, some of the products they use are not password controlled and have just one password account. TeamPassword is also helpful when teams change hands – this way when someone leaves, they can change the accessibility that person has to any account.
Though Mohit was the person to initially sign up for TeamPassword, choosing us over CommonKey, he admits that he doesn’t use it every day, but his team does.
Mohit would love to see a Google Apps integration for TeamPassword. This way, when someone signs into Google Apps, which they use for other things within their daily workflow, they can SSO into TeamPassword. If he needs to kill someone’s account, he can do it from the Google level. He’d also love to see a forced password setting, making it mandatory for his team to change their passwords once every 6 months or so.
Follow @TeamPassword on Twitter for more tips
If you’re convinced, you should give TeamPassword a whirl.