[SOUND] So you've heard Leo talk about the importance, of both technical skills and soft skills, in interviewing for and succeeding in a software engineering and development position. Now, there's lots of roots, to developing these skills, and to a software, engineering, and development career. And so, we've been thrilled to have, a group of engineers working with us, and some of them have agreed to share their stories, of their career path to where, where they are now. And I'll hand it over to them. >> Okay hi, I'm Roshni. I'm a software engineer on identity and authentication at Google, and I've been here about two and a half years. So, my dad is a total nerd. He hasn't actually studied Computer Science. But, because of him, I had a really great interest in computer science because he brought us a computer when I was ten years old. And since then I've been taking computer science classes and I took a class or two in graphics but I was actually more interested in systems. So now I am a software engineer with a couple of degrees in computer science [LAUGH]. >> My name is Shane Brennan, and I am a software engineer. I knew form an early point, even as early as high school, that I was passionate about the act of coding. I really like that deep state of focus that people sometimes called the zone. And for a while, I guess, I thought this may be something of a software engineer It wasn't until I graduated and started working a real job that I understood I really don't know what the heck it means to be a software engineer. And so in order to not look like a total in front of my coworkers I started spending a lot of time trying to build up skills around good code health, good testability, having a clean consistent style, making it easy for someone to come in and understand what the heck I'm working on. In building these skills, I came to realize that this is what people mean by software engineering. It's not the code you write or knowing all the algorithms and when to apply them to different situations, but it's the processes and practices that we develop in order to build software together, collaboratively, more efficiently and after all that, I really cared about these practices. It mattered to me whether my team had a principle set of skills we would apply in developing code, or if we were just hacking things together. >> My name's Howard, now I'm a software engineer at Google. But I think long-term as is many of the folks within my industry, you want to kind of have your own company. You want to build a product that really focuses on solving a niche problem, or providing a niche service in a very technical fashion. That's many years from now, but that's definitely something that is a career aspiration for something else I'm very passionate about is just outreach in the nonprofit and educational space. I try to make myself available as a mentor to any and all who have aspirations in being a software engineer in the financial technology industry.