#TBT: From Predicting to Propelling the Industrial IoT Reply

If you missed it, you should check out the recent press release about RTI’s growth in the Industrial Internet of Things (IIoT). It’s really a great time to be RTI! Sure, from a business perspective all the vectors point the right way. But for me, the most exciting things in that press release aren’t numbers.  I’m more amazed that we get to play with so many futuristic applications. Carbots? Renewable energy? Smart healthcare? Hyperloop? Flying cars? Wind turbines? CT scanners? We got ‘em all. And new things show up all the time.

How can a small company like RTI play in so many areas? It’s Thursday, so in honor of #TBT, I thought I’d take a look back and see how we got here.

For those of you RTI history buffs, we sold our tools business to Wind River in 2005. It was 80% of our revenues at the time. So, in 2006, we had some money and great people, but not much in the way of products. So, we started looking for new trends. What did we find? Here’s an excerpt from our 2006 vision paper called “The Data-Centric Future”:

Truly profound technologies become part of everyday life. Motors, plastics, computers, and now networking have made this transition in the last 100 years. These technologies are embedded in billions of devices; they have melted into the assumed background of the modern world.

Another step is emerging in this progression: pervasive, real-time data. This differs from the Internet in that this pervasive information infrastructure will connect devices, not people. Just as the “web” connected people and fundamentally changed how we all interact; pervasive data will connect devices and change how they interact.

Today’s network makes it easy to connect nodes, but not easy to find and access the information resident in networks of connected nodes. This is changing; we will soon assume the ability to pool information from many distributed sources, and access it at rates meaningful to physical processes.  Many label this new capability the “network-centric” architecture. We prefer the term “data centric” because the change, fundamentally, is driven by a fast and easy availability of information, not the connectivity of the network itself. Whatever the name, it will drive the development of vast, distributed, information-critical applications.

If you change “pervasive information infrastructure” to “Industrial IoT,” that was a pretty good prediction. Too bad the name didn’t stick, but I suppose “PII” sounds more like the second act of a play or a stuttering math teacher than a technology revolution. Anyway, we thought it was coming soon, but 6 years later, we were still predicting. An RTI handbook entry from 2012 (still before the IoT and before the IIC launched the Industrial IoT in 2014) expanded on this a bit:

There is amazing value in distributed information. Connecting people to information transforms society – news feeds, weather satellites, and the Internet are only a few examples – timely information flow drives value in every industry and every endeavor.

However, current technologies only connect people at human speeds. There’s an entirely new opportunity to connect machines at physics speeds. Just as the Internet connected people and fundamentally changed how we all interact, a new “pervasive information infrastructure” will connect devices at speeds fast enough to drive distributed applications. RTI’s people and technology are the best in the world at delivering that data to the right place at the right time. We fundamentally connect complex systems at extreme speeds better than any organization on the planet.

Our technology enables tens, or hundreds, or thousands, or (soon) millions of processors to work together as a single application. Why does that matter? Because intimately-connected systems can do things that weakly-connected systems cannot. They can request and access data from far-flung reaches fast enough to react intelligently. They can read deeply-embedded sensors, use that data to control high-speed machines, and feed the results to the enterprise for monitoring and optimization. This powerful connectivity is a fundamental transformation that will make currently difficult things commonplace and currently impossible things possible. We are already working on many of these applications. Our work will help astronomers probe the deepest reaches of space, protect passengers from injury on tomorrow’s roads, make our nation more secure from attack, and improve the efficiency of renewable energy generation. RTI is leading the new wave of large connected systems, systems that work together as one.

So how can we play in so many futuristic areas? Call us lucky or call us prescient, but the IIoT has been our target for over a decade. RTI is influential in the IIoT because we got a head start. We’re no longer predicting. We’re now realizing the future.

So, what’s next? Our new tagline is “RTI lives at the intersection of functional artificial intelligence and pervasive networking.” Think about that one for a while. AI and connectivity are perhaps the most important trends for the next 40 years. They will combine to bring new wonders to light in every industry on the planet. The IIoT is much more than a name or a connectivity technology; it’s a new infrastructure for, well, everything. Connecting things together is powerful. Connecting those things to smarts is a whole new game. Carbots will improve transportation, autonomous hospital devices will take better care of patients and smart networks will make green energy practical. But, these are just the ENIACs of the IIoT. It won’t be long until every device on the planet is part of a connected, intelligent infrastructure. That infrastructure will make everything more efficient, more useful and friendlier.  These are exciting times indeed!

In any case, it’s an honor to be a leader in the “new” IIoT revolution. It’s even more of an honor to be associated with the technical visionaries at RTI that put us there.

My Internship Ride at RTI Reply

-Where talent meets innovation.

FRIDAY! It’s the first thing that comes to mind when I think about RTI. To almost everyone, Friday means the end of the week, the beginning of the weekend, late night parties and, of course, catching up on sleep. But for me, Friday and RTI have an entirely different connection, and I will explain why.

It starts with a cold, snowy Friday in February 2016. I was looking forward to the upcoming weekend – needed a break from the stressful set of assignments and projects for my courses at Penn – when I got an email from RTI saying that the HR department would like to schedule a call.

Immediately, my excitement started to build, since prior to this I had gone through a couple of interviews with RTI, including a coding round for the role of a Software Engineer Intern. I hoped this call would give me a reason to go out and celebrate on Friday. Hope turned into reality when I got the call saying that I was being offered an Internship role at RTI for the summer. Though they proceeded to tell me about the compensation, benefits, etc., all those words only passed tangentially over me. The only information I was excited about was the part that I got the internship I had been hoping for. The call ended at 6 pm that Friday, and yes, as I said before: a reason to go out and celebrate!

After gladly accepting the offer, I communicated with Jan, the VP of Engineering (and the Head of Research) over emails to deepen my learning about RTI and to keep in touch before my start date. We discussed the project and skills to deploy. It was supportive of them to answer my queries and encourage discussions.

Fast forward three months, and it was the end of my 2nd semester. I flew to Sunnyvale, California and prepared myself for the first day at RTI. Starting on a sunny day on May 11th, an initial welcome by HR set the ball rolling for the internship that was to go on for the next 15 weeks.

Fig 1: The first view of my cubicle.

After the initial formalities of joining, I was soon greeted by the VP of Engineering, having already spoken over emails with him, I could now link a face to the name. Furthermore, I was introduced to my mentor for the internship project. After a quick tour of the RTI office, I was soon taken for a welcome lunch by my mentor to a delicious place where we discussed a little bit of the project as well as more about RTI.

The very next day was exciting since all of us were going for a toast at the nearby ToGo’s to celebrate a recent product release. How awesome is it that you get to attend a toast party the very next day after joining? I was sinking into the moment. I imagined what would be in store for me the next day since it was a Friday, and Fridays meant the start of a lovely weekend. RTI didn’t fail to impress me on my first Friday as well since I was told that the company provides lunches every Friday. Yummy delicious food from the best restaurants around the Bay Area. WOW!

Soon enough, there was RTI Corporate training scheduled at HQ, and I was auto-enrolled to join. The training christened appropriately as “QuickStart,” was true to its title in getting me on track with RTI products quickly! The training focused on the products we offer and what they do and how. In addition, the hands-on exercises were truly a bonus. Receiving a training completion certificate from the presenting Principal Solution Architect was truly icing on the cake. Time started to roll by, I started to work on my project, and planned and chalked out a schedule of how and when things were to be done.

My project was to develop an Eclipse plugin from scratch. The project entailed completely encompassing the steps that a user of RTI Connext® DDS would go through in generating code from an IDL, bringing the project to Eclipse, modifying the IDL and regeneration of support code and finally building and executing the code without leaving Eclipse or using any other tool/software.

It was very exciting for various reasons. Firstly, I was to develop this from scratch, which became a true learning experience since I could research the various ways to go about this and choose the best one that would suit our requirements. Secondly, the complete code base was to be done in Java, a language with which I’m comfortable and had a quest to learn in-depth. Developing this plugin resulted in a fantastic learning experience with Eclipse and Java. I also ensured that I followed industry standard coding practices and guidelines along with appropriate documentation and comments in the code base.

Carrying on further, I started developing prototypes and very proactively communicating all of the developments and progress on my project to my mentor and the VP of Engineering on a regular basis. This communication was well appreciated and helped them to track progress without any follow up from their end.

One thing I’m particularly fond of is RTI’s daily lunch time. All of us gather around and go to the food options located in the adjacent building; we buy ourselves food and get back to the office kitchen to eat. This culture undoubtedly creates one of the best times of the day since you get to sit and talk to everyone about various topics ranging from sports to technology to personal favorites (in my case, cars! 😊 ). I was pleasantly surprised and happy to understand that the regular corporate hierarchy and designation-based differences are non-existent at RTI and everyone is extremely friendly and amiable. How cool is it that our CEO plays ping pong with you and joins you at the lunch table for interesting conversations? Another fun thing to add here is the after-hours get-togethers. One such shown below:

Fig 2b: After hours at Eureka.

After successfully achieving the first milestone in my project schedule, additional milestones and tasks were added. Thinking from the perspective of the end-user, I started to analyze various other requirements and added them to the list of tasks for the next milestone, giving me a sense of accomplishment and satisfactory progression on a task to complete.

Soon enough, I showcased my work to our CTO, who patiently sat with me, went through every step of the project and appreciated me for things I did intuitively. He also provided suggestions that could improve the quality of the plugin being developed. Incorporating the suggestions as I progressed, I was beginning to feel a sense of fulfillment to the project towards the end of July.

Fig. 3: Figurative form of thoughts in my head 😝

Towards the end, when I had achieved something substantial, I was then given a slot at the weekly R&D meeting to show a demo of the Eclipse Plugin to my colleagues at HQ as well as to my colleagues in our Spain office via a video call. I received valuable input after the demo which helped me shape my project appropriately.

Two months had passed by and it was the end of July. One fine day, the VP of Engineering walked up to my desk and asked me to join him for a short walk around the building, wherein details of my plan to complete my courses for graduation and timeline were discussed.

A few days later, a meeting with HR provided a little more information which gave me a deeper hope about returning to RTI as a full-time employee. I was thrilled. I was waiting. At the end of July on a Friday morning, I was as usual busy with my semi-colons and code, when The VP of Engineering walked up to me with a paper in hand, and said, “Let’s discuss a few things.” I tried to keep my excitement from appearing on my face, as he revealed that RTI was making me an offer to return as a full-time employee and went over the details about the compensation and benefits.

That moment, just like the moment many, many Fridays ago in February, had a deja-vu effect, as everything spoken that day was only remotely and softly heard by me as I was too excited to receive an offer from RTI. I love RTI, love the Bay Area for numerous reasons, and being able to come back was something I always hoped for. I quickly gathered my thoughts together, thanked Jan and RTI, and continued my work until the end of the day.

There were about three weeks left, and I completed all the tasks and milestones by the first week of August, leaving me with two weeks to complete all the testing and documentation. This Eclipse plugin was to be deployed and tested on three different platforms mainly Windows, Linux, and Mac. Hence, I had all three machines on my desk, and my desk looked like this. 😝

Fig 4: My lovely desk with my toys.

On the final day of my internship, having completed the exit formalities, I was pleasantly surprised to receive a box full of my favorite brownie bites from one of the friends I had made at RTI. Another lunch from RTI, on my last Friday of the internship, completed the schedule. I was all set to fly out of the Bay Area that evening, and onward to India for a short vacation. Appreciating the help and support from many of my newfound colleagues, I bid goodbye to everyone at RTI and the Bay Area with one thought; I’ll be back!

Fig 5: Me with the RTI banner at the entrance

Mission: ace the initial screening call and get asked back for in-depth interviews Reply

 

Congratulations! Hopefully the tips from Mission: score an interview with a Silicon Valley company were helpful, and you have been contacted to talk to the hiring manager. Here are a few tips on how to ace the initial call.

Before the interview

  • Test your system. We often use a video call to interview candidates: Skype or Google Hangouts. Make sure your camera and microphone work. Do not use a phone for video conferencing. Sometimes we do hands-on exercises. Have a working IDE, editor and compiler installed. Lastly, take a few moments to clean up your computer background and desktop files.
  • Be professional. Dress appropriately in a shirt or blouse. A suit or tie is overkill. Also, pay attention to your environment and background. Clean up the room. Coordinate with your family or roommates that you will be in an important interview call.
  • Prepare by exploring the company website. Read about the products, download the evaluation software, check out the videos, or forums. Learn as much as you can about the company. Look up the interviewer on LinkedIn. You have to learn about a common passion.

During the interview

  • Be friendly and personable. Smile. Show a spark.
  • Be confident, but don’t oversell. And no BS.
  • Ask clarifying questions, especially if your English is not that great.
  • Be sincere if you do not know something but try to answer anyway. For example, “I am not a Java expert, though if it works similar to C#, then …”
  • Don’t give up. Brainstorm. An interview is not a pass/fail test. One candidate felt he should have been asked back for an in-depth interview because he answered six of the ten questions correctly; in his eyes, he had passed the interview. Unfortunately, for the four questions he missed, he didn’t even try to answer them. Being able to figure out things you don’t know is one of the most important skills of an engineer.
  • Don’t play hard to get or show you are disinterested. Don’t act selectively.
  • Think of some questions to ask about the company, job, customers, etc.

Good luck getting to the in-depth interview mission. Apply now to start the process!