SheCanCode's Spilling The T

Foundry Beginnings: A conversation with inspiring women in tech

March 18, 2024 SheCanCode Season 10 Episode 10
Foundry Beginnings: A conversation with inspiring women in tech
SheCanCode's Spilling The T
More Info
SheCanCode's Spilling The T
Foundry Beginnings: A conversation with inspiring women in tech
Mar 18, 2024 Season 10 Episode 10
SheCanCode

Join us as we sit down with two remarkable women from Foundry to delve into their fascinating journeys during their first six months at the company. From their diverse backgrounds to the unique paths that led them to Foundry, Subin Jeong and Gabriela Almeida share their personal stories and experiences.

Discover their onboarding process and gain a glimpse into their day-to-day activities within Foundry. As women in the industry, they open up about the challenges they've faced, offering valuable perspectives and advice about overcoming obstacles and thriving at work. 

SheCanCode is a collaborative community of women in tech working together to tackle the tech gender gap.

Join our community to find a supportive network, opportunities, guidance and jobs, so you can excel in your tech career.

Show Notes Transcript Chapter Markers

Join us as we sit down with two remarkable women from Foundry to delve into their fascinating journeys during their first six months at the company. From their diverse backgrounds to the unique paths that led them to Foundry, Subin Jeong and Gabriela Almeida share their personal stories and experiences.

Discover their onboarding process and gain a glimpse into their day-to-day activities within Foundry. As women in the industry, they open up about the challenges they've faced, offering valuable perspectives and advice about overcoming obstacles and thriving at work. 

SheCanCode is a collaborative community of women in tech working together to tackle the tech gender gap.

Join our community to find a supportive network, opportunities, guidance and jobs, so you can excel in your tech career.

Speaker 1:

Hello everyone. Thank you for tuning in again. I am Kayli Batesman, content director at she Can Code. Today we are discussing Foundry Beginnings, a conversation with inspiring women in tech. I've got two incredible women from Foundry with me today and we're going to delve into their fascinating journeys during their first six months at the company. I have Subin and Gabby who are here to give us a glimpse into their onboarding day-to-day and their advice for other females in the tech industry. Welcome, ladies, thank you for joining.

Speaker 2:

Thank you for having us.

Speaker 1:

It's a pleasure to have you both with us today. Can we kick off with a bit of context and a bit of background about you both to set the scene for our audience? If that's okay, gabby, should we start with you?

Speaker 2:

Sure, I'm Gabby, I'm a software engineer at Foundry and I'm happy to be here.

Speaker 1:

Amazing Gabby, can I ask you a little bit about your education? Did you study computer science? Did you have a traditional background? What was your route in?

Speaker 2:

I have a traditional background. I did my undergrad in computer engineering. I studied in Brazil the undergrad there is five years, so I've long years but I was able to learn everything from software to hardware. I decided I loved software more so I went through the path of web developing. I worked in a bank, but then I realized I really did not want to work in a bank. During the pandemic I was like okay, so what type of industry do I like? What are my hobbies? Something that I can combine with my work life? I realized that I really liked and was interested about computer animation and visual effects and it could be something related to my degree. I decided to shift industries, but I really wanted a better base to be able to do that. So I did a master's degree in computer animation and visual effects and after the master's I got the job in the VFX company.

Speaker 1:

That's an impressive background. It's so far new, only very new in work, so Sooping yourself, welcome. What is your background, what does your background look like and what do you do at Foundry?

Speaker 3:

Hello, so I'm Sooping. I'm also a software developer at Foundry. I have a not very traditional background. I had a really unrelated undergraduate back in Korea. I did politics and economics and then after that I did a bit of tutoring for math and English for high school students for a few years, figuring out what I wanted to do in life. I'm very undefeatable about what to do because I wanted to do everything at once. And then I remembered I really like video games and computer. I was a lifelong gamer.

Speaker 3:

So I decided to go to UK to do a course in video game arts where I learned how to use game engines, which was a bit more technical than I expected. And I was always doing a bit of scripting for myself since young modding for games, making small websites. So I decided, ok, maybe I can do something related to computer tech and creative industry. So it was either gaming or VFX. I was a technical junior technical director at a few studios before I joined Foundry only a couple years of experience there. I did mostly debugging, then looking at what's wrong with the VFX pipelines, fixing stuff, which gave me more understanding about the VFX industry, because it turns out gaming VFX is similar but very different. So I learned about VFX there and I joined Foundry and now I'm working here, as a software developer.

Speaker 1:

Nice and you are both perfect examples of having completely different backgrounds, which is something that we love to advocate. She can code that. Gabby, you have a more traditional computer science based background and, subin, you come from a very different path. You started in politics and economics and then moved into tech and that's something that we love to hear here and that you can come into tech at any time and you can have that fall to any time and train and end up in a really good job at a really good company. So perfect, perfect start. So what I wanted to ask you next was so you've landed yourself now great roles at Foundry, so what attracted you to Foundry in the first place? Was it something about the company? And how did you find your way in there, subin, should we go to you first on that?

Speaker 3:

Yeah, so when I was working as a TD in the studios, I was exposed to founder products at least two of them is Nuke and Katana, where I would look up the file and try to see what's plugging the pipeline, et cetera. So I really knew Foundry and what they do and what they make. So I exposed their software. And then, luckily, chloe a different Chloe, so in-house recruiter she reached out to me on LinkedIn and then I was ecstatic. So I really knew that I really wanted to work for a software company. Studio is nice, but I wanted to go more into technical role. So I did interview and joined the team. What attracted me the most is that the first thing was that they are a software company. So as a developer, the experience of writing code and developing products was more seamless. So that was my favorite thing about Foundry when I joined.

Speaker 1:

Yeah, I think it's nice to hear, as though, that when you were contacted by them, you were so excited by that because they're quite a creative company as well, and that's not always something that we think of in tech, is it that you don't always think your role is going to be that creative? But, as a company, when you look at them, I mean I'm not technically minded, but they're quite creative to look at from the outside. Is that something that you kind of expected, supeen, or had you had creativity in a past role and then kind of, when you saw Foundry, you thought, yeah, I'm going to get that chance now.

Speaker 3:

Oh yeah. So when I was doing my game arts course with game engines, I had a bit of a creative opportunity to create visual stuff. When I was working as a TD, which means a technical director, you're kind of debugging and scripting in Python for small stuff. Since then I was mostly just programming, but as because your programs are used by artists, you get to see some cool stuff from the way and it feels nice to help artists to really get their full potential in their artworks. I think as a developer at Foundry it's mostly programming and program solving, which is also, I think, another form of creativity. You're just kind of figuring out what to do and then sometimes we see demos done by our people at Foundry or just looking at movies and stuff and it's like wow, that was probably Foundry products at the end of the pipeline. So yeah, it feels great.

Speaker 1:

Yeah, yeah, and all of that is your job. Very nice, gabby yourself. What attracted you to Foundry and how did you end up joining?

Speaker 2:

It was quite similar to Subban in regards to HR approach, but it was the same clue. And well, when I decided to do my master's degree, I look up some universities and I also looked up where people alumni from the university that was applying to where they were working like, what path were they following after the master's degree? And Foundry kept popping on their profiles and I was like, oh and, because I didn't know much about the industry, I didn't know Foundry before, but even before I started my master's, I was like, okay, this could be an option for me after I graduate. And something that really intrigued me was that Foundry's slogan is like imagination engineered. So that was basically what I was looking for.

Speaker 2:

It was engineering and like the creative aspect of it as well. And, like Subban said, the fact that it's a software company, not a studio, will also focus more on my abilities and I feel like I can help and contribute even more. So that's what led me to Foundry, and when I was at the end of my master's degree, I knew that I had to make myself feasible to potential employees. So I focused a lot on promoting my work and skills on LinkedIn and hoping that someone some recruiter could find me and call me did, and she sent me the job details. I went through the interview process, which was a great experience, and here I am now.

Speaker 1:

Yeah, and you see, you mentioned it was creative. Then, when you worked in a bank, I kind of got the feeling from you that it wasn't. Is that what you were looking for in your next row? And Foundry does really take that box.

Speaker 2:

Well, yeah for sure, at the bank was everything pretty robotic and, no, there was not really room for creativity. It was just like I need to develop this teacher and you need to program it as fast as you can and put in production as soon as you can and as soon as you finish that one, there's only one and only one and only one, and you never know exactly what you're doing.

Speaker 2:

You're just like producing everything and you don't even know how the user is going to receive that and it wasn't really like I felt like I was just like a little robot, and here I feel like I have a purpose?

Speaker 1:

Yeah, definitely, I mean day to day. Yes, you have to be happy in your role and, mentally, when you switch off, you have to feel like you know I did something that day, or even at the end of the year. You have to feel like you know I achieved certain things this year, because you just go into the next one feeling like I just did lots of little tasks this year and I don't know how I help people or what I actually achieved. So you're so, so, so right there, and you've both been at Foundry for about six months. So I wanted to ask you are there any standout moments for you or projects that have left a lasting impression? Gabby, should we start with you on that one? Now you're happier than then.

Speaker 2:

You were in the back, yeah so both Subin and I, we both work at the Katana team, so we work on the software called Katana, which is like a light and rendering software, and a particular moment that stands out it's when I created my first Katana node from scratch. Our team focus on is very much centered around USD, universal Seam description and before joining Foundry, my understanding of USD was pretty minimal, so this was both a challenge and an exciting learning opportunity for me to develop this node. Diving deep into how our software is structured while getting like a crush course in USD concepts at the same time, was not a easy task to accomplish. But the moment I successfully developed the node and it was more than just a personal victory it symbolized my like real, tangible contribution to the team and to the company, and the experience left a lasting impression on me because it highlighted the fact that it could truly help to push our projects forward and actually make a difference.

Speaker 1:

Yeah, it's always nice when you say you know, I got in a company and I learned something new, because it's almost as if really good companies they just grab hold of great talent and then they train you up in the areas that they need you to work in, instead of always looking for that person who perhaps you know, that person who doesn't have everything that they need and doesn't exist. But they grab hold of really good talent and continue to develop you along the way and you're really early in Foundry, but you've already learned a completely new skill that you didn't have before. I mean that's brilliant. I mean, lorde, I know what's going to happen in the next six months for you.

Speaker 2:

Yeah, I feel like that happened because the team is extremely supportive, like we are always talking to each other and sharing things and we're open to ask questions anytime and our team is really really good technically, so any questions that we have, they're able to solve it and explaining, teach, so it's a really great environment to learn new things.

Speaker 1:

Yeah, yeah and serving yourself. What about you, the Binnini standout moments and projects that you've worked on in your first six months?

Speaker 3:

I think mine must be a similar thing to Gavi when I first shipped my newly added feature to production so that people can use it. So it's like a node. Node is like something you drop down into the program and connect input and output something else. You can do that by texting, like putting in text, but we made it so that people can do it easily. I felt really proud when I first sent that into the production codes to be used by a lot of people.

Speaker 1:

When you do that, do you get feedback and it's kind of you work as a team to hear what the users thought and how you can improve on that. I take it. It's a different experience from what Gabby was explaining before, of being in a company where you just do a task and you tick it off, but I take it, you get feedback on everything you do as well from the user.

Speaker 3:

When I first joined Foundry, the first thing, I think first thing when you join the company, you just figure out how the life cycle of a project works. So, like making planning review, making planning review, it's like a cycle, like a self-feeding feedback loop. So, and then we have other teams who are doing testing and gathering feedback gathering feedback from clients and Foundry people. So we always ensure that we are actually making sure that this thing that we made will be actually used for its correct purpose. And then we also get continuous feedback on our open forums by whoever's using our products. So, yeah, so very well working cycle.

Speaker 1:

in the end, yeah, yeah, which has since said before, must really help you to move to the next one and the next one, and when you're at the end of the year, you can see all of these things that you've worked on and how many people you've helped, which really will be encouraging for the next year and the year after. Yeah, can we talk to you? I wanted to know a little bit about your onboarding experience and how it helped shape your understanding of the company culture. Gabby, you mentioned your interview process and that you really enjoyed that and that was a positive experience. Can you walk me through what your onboarding experience was like, from interview through to the first few weeks at your company?

Speaker 2:

Yeah, it was really funny. I didn't even tell Chloe about that. But when she reached out she was like can we talk a little bit? And I thought it was already like a big interview. So I prepared myself, I reserved a room in my university and I was like, okay, I'm going to be in this interview for like one hour or whatever and I need to promote myself as best as I can. And but the first interview was with Chloe. She's from HR and she was just like just making sure that I could be part, so it was a part of the company, like are you studying, can you come to London? And all this like basic stuff to start the process. So it was like a 10 minute interview and I was like, okay, it wasn't, now it's.

Speaker 1:

But okay, I'll be fresh. She was nice and you know I could move to the next level.

Speaker 2:

Yeah, and she was like okay, everything's fine, you can. You can continue with the process because the both companies that I worked before it was like just one interview, yes or no or no, and that's it. And then she told me that they would be sending me a like a task for me to do. I could do it in like in a week and send it to them as whenever I could, and it was a C++ task and I made sure to showcase every ability that I had and that I saw that they needed in the job role. So that happened and my team, my current manager and another person from my team, a senior developer they checked the task and they're like okay, this person, this person has the technical abilities that we need. Let's talk to her to check her personality and how she's like at work and so on. So I, they liked my task. They booked the interview. That was more like they were asking questions about the task and they were. They were also asking questions about me and after that, if they liked the result of that interview, there was a third interview, which was a live task one. So they would give me a code and I would have to find like bugs and stuff, and that one was live, they would be watching me. And after that Chloe reached out and say, hey, can we talk? And she said that they would like to offer the position. So that was the interview process, which I believe Subban might be similar, and the onboarding was really nice.

Speaker 2:

On my first day, which was two weeks after Subban's first day On my first day everyone from the team went in person to the company. We met in person. It was really nice, everyone's super nice. We had lunch together and it was really good to see that people from other teams were also like coming and talking to me, introducing themselves and I was already starting to feel part of the company. And another cool thing that they do for onboarding are the buddies. So we had a team buddy and a culture buddy. The team buddy was to ask like technical questions and questions about the team, and the culture buddy was to like learn a little bit more about the culture, founders culture and we had like weekly meetings that I could ask questions. So it was a really good way to like understand the company and see how I could fit within it.

Speaker 1:

So yeah, yeah, that's nice, instead of you get the job and then that's it and you're kind of thrown in. You expected to start your training, but it's nice that you have two different buddies for two different things as well. The culture is just as important as your actual day job on what you're doing on your team. So, yeah, that's really well well pulled out and I can see nodding. I'm assuming you had a very similar interview process and onboarding. Did you also do a live test?

Speaker 3:

as well. So everything I did, I did the same things. I didn't write a single line of C++ before I joined Boundary and I got a C++ question as my interview and I was like I'm so nicely for two weeks and learn everything, super cool, scratch you made it, so it's a miracle.

Speaker 3:

They said we really appreciate your willingness to learn. I think my probably my technicality for C++ wasn't very well Two weeks of learning. But good thing about Foundry that I want to add is that they have mentorship program where you can either sign up or you can sign up to be a mentor or mentee, and I signed up to be a mentee for C++ by a senior developer, a C++ developer in Foundry. So we've been doing mentoring for a few months now since I joined, which is really, really helpful as a new C++ dev. So that's another thing that I wanted to mention that all the support, onboarding documentations, you have a bodies and mentoring and you can always ask questions on Slack channels Anything you need. You can drop it in a channel with hundreds of developers and everyone will come and give their opinions. So, yeah, really collaborative workspace.

Speaker 1:

I will say Amazing and kind of similar to Gabby as well. We were talking earlier about grabbing hold of people that have good skills, maybe not everything that that company is looking for in the job description, and that's a conversation we have on here a lot as well that a lot of ladies see job descriptions. They don't tick all of the boxes and they won't apply, whereas sometimes companies are just looking for great employees. They get you in, they train you up, they put you in a mentoring program and surely over time you're both gonna be far more loyal employees as well, that instead of thinking in a few years or jump ship and go somewhere else, you're furthermore, that you'll want to stay put and really invest your time at Foundry for quite a few good years.

Speaker 3:

Yeah, I will say that's definitely a factor. Yeah.

Speaker 2:

Yeah, I believe I'm not 100% sure, but I have in my memory that Subhan and I we were going for the same role, but James liked us, our manager liked us and I believe that this willingness of Subhan to really want to learn I think he requested a new role just to be able to hire a school, that's incredible.

Speaker 1:

Yeah, I love it when that happens. So you just think you know what? Just? We've met some brilliant people and we're not gonna let them go regardless and we're just gonna train you up in things that we need, or things that also not just things that the company needs, but things that you wanna learn along the way, and that, if you are that type of person that's willing to learn, then, yeah, definitely. That's amazing, though, that they thought you know what, we're just gonna make room, we're just gonna bring you on. So now you're in and you're made it in and you are thriving. What does the typical day look like for you at Foundry?

Speaker 3:

Yeah, so we have typical hours. Usually in the morning we have meetings to discuss what we're up to the other day. That's like a daily meeting to check out like what have you been, how have you been, what are you doing, what are you going to do today any questions as well and then sometimes chit chat about oh, how would we can catching up always good. And then after that it depends on people. But I usually do cold reviews. So I would just look at other people's cold, because they pull up into the cloud that everyone can see and keep feedback or just kind of learn from their cold, which I'm doing a lot because I'm doing it and I'll do that. And then I'll get back to my task and trying to figure out, try to do investigation first what do I need, and stuff like that and then do some actual coding and put that up for review. So that's like the whole cycle of a task.

Speaker 3:

So, depending on how busy I am or how important the task is, I'll squeeze in some extra work. Sometimes I'll do documentations, like writing up stuff so that future myself or other people can look up instead of scavenging for informations. Or for me I'm doing the mentoring. Then that's taking quite a big chunk of my days. I will do like one hour of learning C++ and then every Wednesday I do actual mentoring session. That's like a couple of hours. So my days look very, quite a bit, but I think it's usually people do meetings, then do some coding and then do reviews.

Speaker 1:

Yeah, pretty varied. Then it's not you just do coding and that is your only task, and sometimes it's the stereotype of working in tech that's the only thing you do. But your day is very varied and lots of learning in there as well. Gabby, what's your day like? Is it just as varied?

Speaker 2:

Yeah, it's similar actually. So there's the morning calls and we catch up with everyone and when we are developing tasks one thing that we usually do, especially me and Sue, when we go to Hado's so it's just like we both are in a call. We're working our tasks separately, but if we have any questions we can just reach out. They are informal calls and people can jump in, jump out and yeah, it's really cool to just be able to be there coding. You know someone's on the other side of the line and you can talk to them. And I feel like, depending on the day, we also have different type of calls and we have a dev catch up weekly, which everyone on the team come together and if there's a technical topic that everyone needs to know or something that someone did that they believe it's good that everyone learned what they learned, they can share.

Speaker 2:

And we also do retrospective. So we, after two weeks, we're like, hey, how was this two weeks? How can we improve and what else can? What should we stop doing? What should we stop doing? What should we start to do? And I really like that foundry. We also have social times, so there's like a space in our calendar that we're like 30 minutes. We just come together, have a coffee together Even it's at home, everyone's at home, but we just stop and talk a little bit. And we also have social time with other teams on Fridays, so it's not like, oh, you're always working, you also have plenty of time to breathe a little bit.

Speaker 1:

Yeah, that's nice and, having spoken to quite a few ladies that work at Foundry, it's always as if you both kind of mentioned it as well there there's always someone at the end of the line. It's almost like if you have a problem, you don't have to sit and worry about your own problem on your own, especially if you're hybrid. Sometimes that can be you can feel a little bit lonely or that you're the only one dealing with a problem, whereas it sounds like on your teams it's very. Someone's always there if you do need somebody or not just in the social aspects, but you can just call somebody up and chat through something. That it seems to be a bit of a theme at Foundry, that your teams are very interactive. Is that right, yeah?

Speaker 3:

very organic.

Speaker 2:

Yeah, they tell us not to be stuck in a test by ourselves, like 20 minutes in max, otherwise just reach out. They encourage us actually.

Speaker 1:

Yeah, they're having that feeling of panic at home. On that note of challenges, are there any specific aspects of your role or projects that you find exciting or challenging? Because it's nice to have the excitement, but also you can have the challenge inside as well. That keeps us all going. Are there any aspects there of roles or projects for you that are exciting or challenging? Subin, should we ask you first?

Speaker 3:

Sure, I think, challenging VFX industry. The nature of it is very, very fast changing. It's everything's rolling out. Everyone's rolling out new things every year, this year being the AI and stuff like that. Usd is very new to be on the market and stuff. It's like you're learning everything. Everything changes so fast, so there is a lot to be. You're working on something that's not very charted yet so you just have to figure out how to use that and sometimes there will be very little documentations etc. Especially, I think our team Gavin, my team is USD related. Everything's new. So that's the challenging part. But that's also kind of the exciting part because you're doing something that's only kind of like a bleeding edge. So it's exciting by just the nature of it.

Speaker 3:

And then my role as a developer in Katana working on their products. As a developer, I think the biggest fun or like rewarding thing is your program solve. You just kind of make it work. Sometimes it's not a smooth path. Sometimes you just do a very hacky, hacky things to make things work, which is I find it very fun. It's kind of like a video game or puzzle in a way. You're also exposed to a lot of smart people with great ideas. So when I'm reviewing other people's course, like, oh, you could do this. I ask questions and they say something really mind-blowing and I'm like, oh yeah, I can do that. So it's always like, if you're like intellectually curious, I think you'll be really rewarding to work as a developer.

Speaker 1:

Yeah, and you can see why they grab hold of you so fast as well. So quick because you learn C++ so fast for your interview process Learning.

Speaker 3:

Yeah, yeah, because you're right.

Speaker 1:

Everything moves so fast and for somebody to want to keep learning, that's quite unique to find in somebody. So, yeah, they obviously saw that shining through in you and thought you know what? We're going to grab hold of her. She learned C++ just for her interview, and then you continue to learn along the way Because, as you said, that's kind of something that will never end because you're constantly learning at fast pace. So that's brilliant. Gabby yourself, is that something that kind of echoes with you as well? You're constantly learning, which is exciting but can sometimes be a challenge.

Speaker 2:

Yeah for sure, but I feel like that is with when you work with technology. It's just crazy and it's getting crazier and crazier Every month. There's a new thing with AI, with whatever, so it's really hard but we have to keep up with it and I feel like within the VFX company industry it's pretty similar or even faster, but to me that is really challenging. But there's also other aspect of the job that I found really challenging and because I don't have experience in the industry, like Subin was saying, she worked in studios before and she was able to see firsthand how artists use our tools I've never seen anyone using our tool to do a movie or something. So having to change my mindset to be like artist focus, but at the same time, I need to learn how artists think and how they use our tool. So, within the fact that I have to learn about USD and technology and everything new, I also need to change my mindset to think like a user that I never interacted with Because, for example, at the bank, I had a bank account at the bank.

Speaker 2:

I knew what I needed. Here. I'm not an artist. I can try. I can try to learn. Of course, in my master's degree, of course they showed us how, but it was in a surface level and the things that we're developing are for people that really know what they're doing. So this mindset shift, I'm still learning.

Speaker 1:

Yeah, I'm in a learning curve. Yeah.

Speaker 3:

Yeah, I think for me, even with almost two years at studios, I'm still very lost in how Katana works Surface level knowledge I have, so I can only imagine how difficult it must be for Gabi.

Speaker 1:

Yeah, and as you say, it's a learning path every day that you will start to kind of immerse yourself into what you need to know, gabi, and how that artist works. And yeah, it's going to take some time and, as you said, a whole mental shift as well. But, yeah, brilliant challenge ahead and we need to touch upon a little bit about you being women in tech and whether or not you even counted any specific challenges and how did you navigate through them.

Speaker 1:

It sounds like you've had not an easy path into tech but you have managed to learn yourselves really good roles at Foundry, so have you had any challenges as women in tech as yet that you can share with our community?

Speaker 3:

Super You're so lucky. Ok, yeah, yeah, for sure. I feel like the biggest thing for me is the imposter syndrome. Yes, the imposter syndrome. I think we can all agree that, while everyone has it to some degree, for women I think it really hits hard Because we're always expected to be perfect and confidence just do everything perfectly, and it's like outside pressure is a lot less than the pressure you put on yourself to be perfect. And then there's also, I think, external factors that you don't see much of yourselves in the industry. Most of it, it and tech is a VFX as well as very male dominated, so white men's industries are like a lot of other industry. So you really have to believe in yourself and trying not to be so hard on yourself Because you're only learning. You're just doing your job. The fact that we don't see much of women in especially leadership positions maybe time will solve Things she can call this doing is a great example. So, yeah, my advice, my challenge, was basically imposter syndrome, like, if I have to summarize it, it was that.

Speaker 1:

Yeah, and to see and to hear, as you said, things we do from she can code, just to hear more people saying that it's like, yeah, he feels that way Because everybody, I swear, at some point in their career has fought. They're going to find me out, they're going to know I can't do it. Or, you know, if you're a ridiculous sport, because you know you get in, you pass the test, you're doing good work and it's almost like we just you would sometimes have that voice. So you think I have to be kinder to myself and realize you know, these are the projects I've worked on. We're doing great things, and I think it's just the more that we hear that lots of ladies feel that way. If you used to be sharing your stories today as well, we're so helpful for other ladies that are feeling exactly the same way Can be yourself. Is that something that resonates with you?

Speaker 2:

Yeah, and I'm going to say something that is not from a really credible source, but there was this TikTok audio that is like you. Just you can think it's not really hard, Boys can do it.

Speaker 3:

So that's what I think when I'm like oh my God, I cannot do that.

Speaker 2:

Well, someone did this, and if it was a man, like a boy, like if boys can do it, I can do it. So that's what I think all the time now.

Speaker 1:

It has that ring on your wall. Yeah, I've been one of those days.

Speaker 2:

My brother can do it.

Speaker 3:

I can do it.

Speaker 2:

And that is really true. My brother followed my path. But I would say more things as well, like, like Subin said, there's not much women in tech, and that was really hard for me. When I was in my undergrad, I was the only girl in my class and I graduated the only girl, and even though I was really good at what I was doing, sometimes my work was labeled even by teachers as like cute instead of good. So that was, yeah, I'm not cute. Yeah, that was a time like I had to do this video about certain topics and everyone had to do a video and I really worked on it and the professor saw all of them and I was like, what do you think of my video? And he was like, oh, he was really cute. And I just looked at him and I was like, but was he good?

Speaker 3:

Because he was not doing something for being cute yeah.

Speaker 1:

Oh that is annoying yeah.

Speaker 2:

And when I went to the bank I was also the only backend developer. So thank God there was a front end developer the other only girl in my team and having her was like really good, like someone to talk to and to share experience. So being able to find someone that you can just tell what you're feeling and sometimes they are feeling the same and you can help each other. When I went to my master's degree it was a bit different because I was one of two girls and we helped each other so much that now she's my flatmate and we got jobs together. She got a job at a studio, I got a job at Foundry and we moved to London together. So just having this possible like group of people that you can rely on and can help you will help will make all of us grow together. So, even though it's really challenging, it's also a great opportunity to farm bonds, yeah definitely, and yeah, one where you moved London together and now live together.

Speaker 1:

So, yeah, I mean, we are advocates for networking at Sheik Co, but yeah, moving countries and moving in together is definitely a strong network that will continue to grow. Ladies, we're nearly out of time. I wanted to ask you quickly about what advice do you have for women who have started in their careers. Is there anything that you kind of wish that somebody had told you before you got started? And to be to you.

Speaker 3:

It's kind of a cringe thing, but I will say just do it. Yeah, don't try to be perfect 100% ready. Like you said, just apply. Put yourself out there, update your LinkedIn. If there is a few word matches the job description, just apply. Because at the end of the day, to land a job as a developer, you have to put yourself out there and you have to trust yourself. So I will say you're probably ready. Just go get the job.

Speaker 1:

Yeah, I love that. That. You just said they trust yourself as well. Yeah, how many times we felt like, as you said, about imposter syndrome. So, yeah, trust yourself is brilliant advice, gabby yourself. Any advice that you wish you'd been told.

Speaker 2:

Oh, yeah, I 100% agree with Subin and I would say that you're going to feel sometimes that you're not part of that community, like because you can be the only girl sometimes. And I would say, just embrace this unique perspective that you can help, that you can give out, like your unique viewpoint is not just valuable, it's essential, because tech drives innovation and innovation is filled by diversity. So, embrace your ideas and trust in your abilities and don't shy away from expressing your thoughts and solutions. And, of course, like I said before, find your community. It's crucial to have a support network. So, like Subin is doing right now, look for mentorship programs, network groups and communities for women in tech like this one. So, yeah, I would say, find your community and embrace your unique perspective.

Speaker 1:

Brilliant, lovely advice, and you're absolutely right. And being in a company where you're allowed to show your diversity and to see that as an advantage, and that they want you to speak up because you have a different perspective, then, yeah, that is, if you land yourself in the right job at the right culture, then definitely yes, that's what they're looking for. Ladies, I could keep talking to you for another couple of hours on this subject, so we're going to have to have you back at some point when you've been at Foundry for another six months to hear about your journey. But thank you so much for joining me today. It's been an absolute pleasure chatting with you both. So thank you, subin and Gabby, my pleasure.

Speaker 2:

Thank you for having us.

Speaker 1:

Thank you have everybody listening to us always. Thank you so much for joining us and we hope to see you again next time.

Journeys Into Tech at Foundry
Foundry Work Culture and Onboarding
Foundry Interview Process and Onboarding
Tech Workday Variety and Collaboration
Women in Tech Challenges and Rewards