Tech Jobs No Coding

Hey everyone, I'm M U Sunny and welcome back to my Website. So, ever since joining a big tech company, I feel like my eyes have been opened to all these new roles that don't require a computer science degree and don't require you to program. I'll kind of be giving you a run down of five different roles that I've seen at these larger tech companies. So, if you're someone who's interested in breaking into tech, this video is going to be super helpful. Make sure to check out part one of this video where I talk about more common roles that you'll see. And let's get started. So, the first role you'll see at these larger tech companies that don't require you to program and don't require you to have a CS degree, is the Manual QA role. So,

 if you're not familiar with The Software Development Life Cycle, a really important piece of that is testing. Developers don't want to release products out into the world that have a lot of bugs, sorry, features, that might crash the app or they don't want to release things that will be causing problems and will be difficult to use. So, a huge part of software development is testing. So, developers are writing unit tests, end to end tests, as well as doing system tests and load balancing tests. Another part of this testing process is manual testing, which is done by Manual QA. They're responsible for finding bugs, using different test cases and looking for edge cases to make sure the product is working as expected. Let's say developers decide to build a page for walking in. So, the Manual QA person will be responsible for putting different test cases into that log in text box. So, they'll be putting in different characters, uppercase letters, they'll basically be trying to see if there is any input or edge cases that will break that log in text box. They'll be pressing different buttons to see if there is somehow a button that can break the app.

 

 They'll also be checking how the app behaves under different internet connections. So, if there's low internet connection, what is the user going to see? So, basically that's an example of what Manual QA is responsible for doing. And after they test the app, of course they're gonna report and document any of their findings to the development team and to the product team, and they're also going to be building out testing systems and procedures that sort of test the apps in the future. So, if you're interested in learning how to program eventually, this can be kind of a stepping stone to a new role which is called Software Engineer In Test. And a Software Engineer In Test is responsible for basically automating this manual QA process and building out test infrastructure and test libraries. Now, let's move onto the next role. So, the next role I've seen in the bigger tech companies, I think is a really cool role, is called Tech Writing. So,

 

 just like household items, you'll find that software also needs a guide. There needs to be written manuals to teach people how to actually use different products. Technical Writers do a variety of things. You'll see them meeting with developers to actually do walk through of how to use a product, even reading the initial guides created by developers about how a product actually works. Then they'll take these walk through and distill that information into something that's easy for the customer to read and to understand. They're also going to be creating diagrams to show how products work, code samples, even instructional and educational videos. So, when there are new features and there are new changes, even new versions to a product,

 

 they're responsible for keeping that documentation up-to-date. They're also responsible for creating best practices. This is all to make it easy for the customer to use a product. Even though programming is not necessary to be a technical writer, it does help to have a programming background or to have a technical background as well. Now, let's move onto the next role, which is the Business Analyst role. This is by far the most nebulous role because to be honest, it's gonna depend on what company you're working for, what team you're on, that's gonna determine your actual day to day. So, you'll see them doing a variety of tasks. One of the most popular tasks you'll see them doing is gathering the requirements that businesses need. So,

 

 it's really important to match what software developers are working on with actual business value. And by gathering requirements, the business analyst can help make sure the developers are working on the right tasks. They're also responsible for doing a lot of analysis, so they're analyzing the business domain, looking at the processes in the systems that the business has. And business analysts are also doing the data analysis and collecting different metrics and information, and analyzing that information on Excel. So, speaking of data analysis, I do want to thank the sponsor of this video, Data Camp. Becoming data fluent can help unlock new and high paying career opportunities. Data Camp is an online learning platform that makes acquiring data skills easier and more convenient. Data Camp has courses for all different levels and courses on data science, machine learning, and non-coding data concepts. If you're not sure where to start, you can take one of DataCamp's free assessments and get personalized learning recommendations. But if you're interested in becoming a business analyst,

 

 I recommend this Data Analysis in Excel course, which helps you develop Excel skills that you can use in your day to day work. If you're interested in DataCamp, please visit the link in the description box down below and check out the first chapter of any course for free. So, the fourth role on this list is the Agile Project Manager or Scrub Master. Often development teams typically have three different groups of people. You have the product manager and the product owners, you have the software developers, and then you also have the project managers.

So, before we hop into the day to day of what Scrum Masters actually do, I think it's important to actually understand what Agile and Scrum are. Agile is a methodology in a system of delivering software. A Scrum on the other hand is a type of Agile methodology and the big thing with Scrum is that it's based on these time box intervals called sprints. So, basically developing teams work in sprints to complete and build out products. So, now let's talk about what a Scrum Master actually does. A Scrum Master/PM is basically focused on completing tasks and also following this Scrum methodology to complete tasks more efficiently. So, the first thing that they do is that they usually are looking at all the tasks that needs to be done, deciding what needs to be backlogged,

 

and what needs to be prioritized. Next, they're creating a plan for the sprint, and a main sprint goal. During the sprint, they're responsible for making sure the developers are on track, and they do this by doing something called daily standup, or a daily Scrum meeting. And it's basically a meeting every morning, depending on the team you have to see are you on track to finish the project by the right time. And at the end of the sprint, they'll just review what tasks have been done, what tasks need to be carried over to the next sprint. They'll find ways to sort of change things up if there needs to be a change in the system. And then, your main goal is to kinda iterate and iterate on this task management system to make it efficient, so that tasks are getting pushed and the product is improving and engineers are sorta delivering things on time.

 

 Now, let's move on to the last position, which is the Policy Analyst. And I think this is actually one of the coolest roles, and if I had known this when I was trying to break into tech, if I wasn't interested in being a developer, I would have definitely considered this. This is a role that's very common in social media companies, like TikTok, Instagram, and Facebook, and that is the role of the Policy Analyst. So, for these major social media companies, they need a team that's responsible for creating community guidelines and creating community policies. This is actually a very difficult task because you need to create guidelines based on the local community and also the country as a whole too. So, different localities will have different guidelines and different policies based on the rules and the policies of that country. They develop these policies and guidelines by discussing it with different politicians, different local community leaders, and different NGO's,

 

 depending on the areas that they're in. These guidelines also need to be inclusive of different communities and different cultures. And it's also really important to create good guidelines because we all know the power of social media and how the wrong content can have a very harmful effect on a community. We will also see them enforcing these guidelines and these policies, also ensuring that destructive content is removed and monitoring and making sure that that destructive content isn't staying for a long time. They're also creating large scale strategies of how to actually track and remove this disruptive content. So, those are the five roles that I feel like you should check out if you're interested in breaking into tech. Make sure to check out part one of this video, because that has five more roles that you can consider if you don't want to program and you're not interested in getting a computer science degree but you still want to be in tech.

And let's get started. So, the first role you'll see at these larger tech companies that don't require you to program and don't require you to have a CS degree, is the Manual QA role. So, if you're not familiar with The Software Development Life Cycle, a really important piece of that is testing. Developers don't want to release products out into the world that have a lot of bugs, sorry, features, that might crash the app or they don't want to release things that will be causing problems and will be difficult to use. So, a huge part of software development is testing. So, developers are writing unit tests, end to end tests, as well as doing system tests and load balancing tests. Another part of this testing process is manual testing, which is done by Manual QA.

 

They're responsible for finding bugs, using different test cases and looking for edge cases to make sure the product is working as expected. Let's say developers decide to build a page for walking in. So, the Manual QA person will be responsible for putting different test cases into that log in text box. So, they'll be putting in different characters, uppercase letters, they'll basically be trying to see if there is any input or edge cases that will break that log in text box. They'll be pressing different buttons to see if there is somehow a button that can break the app. They'll also be checking how the app behaves under different internet connections. So, if there's low internet connection, what is the user going to see? So, basically that's an example of what Manual QA is responsible for doing. And after they test the app,

 

of course they're going to report and document any of their findings to the development team and to the product team, and they're also going to be building out testing systems and procedures that sort of test the apps in the future. So, if you're interested in learning how to program eventually, this can be kind of a stepping stone to a new role which is called Software Engineer In Test. And a Software Engineer In Test is responsible for basically automating this manual QA process and building out test infrastructure and test libraries. Now, let's move onto the next role. So, the next role I've seen in the bigger tech companies, I think is a really cool role, is called Tech Writing. So, just like household items, you'll find that software also needs a guide. There needs to be written manuals to teach people how to actually use different products. Technical Writers do a variety of things. You'll see them meeting with developers to actually do walk through of how to use a product, even reading the initial guides created by developers about how a product actually works.

 

Then they'll take these walk throughs and distill that information into something that's easy for the customer to read and to understand. They're also going to be creating diagrams to show how products work, code samples, even instructional and educational videos. So, when there are new features and there are new changes, even new versions to a product, they're responsible for keeping that documentation up-to-date. They're also responsible for creating best practices. This is all to make it easy for the customer to use a product. Even though programming is not necessary to be a technical writer, it does help to have a programming background or to have a technical background as well. Now, let's move onto the next role, which is the Business Analyst role. This is by far the most nebulous role because to be honest, it's gonna depend on what company you're working for, what team you're on, that's gonna determine your actual day to day. So, you'll see them doing a variety of tasks. One of the most popular tasks you'll see them doing is gathering the requirements that businesses need. So,

 

 it's really important to match what software developers are working on with actual business value. And by gathering requirements, the business analyst can help make sure the developers are working on the right tasks. They're also responsible for doing a lot of analysis, so they're analyzing the business domain, looking at the processes in the systems that the business has. And business analysts are also doing the data analysis and collecting different metrics and information, and analyzing that information on Excel. So, speaking of data analysis, I do want to thank the sponsor of this video, DataCamp. Becoming data fluent can help unlock new and high paying career opportunities. DataCamp is an online learning platform that makes acquiring data skills easier and more convenient. DataCamp has courses for all different levels and courses on data science, machine learning, and non-coding data concepts. If you're not sure where to start, you can take one of DataCamp's free assessments and get personalized learning recommendations. But if you're interested in becoming a business analyst,

 

I recommend this Data Analysis in Excel course, which helps you develop Excel skills that you can use in your day to day work. If you're interested in DataCamp, please visit the link in the description box down below and check out the first chapter of any course for free. So, the fourth role on this list is the Agile Project Manager or Scrub Master. Often development teams typically have three different groups of people. You have the product manager and the product owners, you have the software developers, and then you also have the project managers.

 

So, before we hop into the day to day of what Scrum Masters actually do, I think it's important to actually understand what Agile and Scrum are. Agile is a methodology in a system of delivering software. A Scrum on the other hand is a type of Agile methodology and the big thing with Scrum is that it's based on these time box intervals called sprints. So, basically developing teams work in sprints to complete and build out products. So, now let's talk about what a Scrum Master actually does. A Scrum Master/PM is basically focused on completing tasks and also following this Scrum methodology to complete tasks more efficiently

 

. So, the first thing that they do is that they usually are looking at all the tasks that needs to be done, deciding what needs to be backlogged, and what needs to be prioritized. Next, they're creating a plan for the sprint, and a main sprint goal. During the sprint, they're responsible for making sure the developers are on track, and they do this by doing something called daily standup, or a daily Scrum meeting. And it's basically a meeting every morning, depending on the team you have to see are you on track to finish the project by the right time. And at the end of the sprint, they'll just review what tasks have been done, what tasks need to be carried over to the next sprint.

They'll find ways to sort of change things up if there needs to be a change in the system. And then, your main goal is to kinda iterate and iterate on this task management system to make it efficient, so that tasks are getting pushed and the product is improving and engineers are sorta delivering things on time. Now, let's move on to the last position, which is the Policy Analyst. And I think this is actually one of the coolest roles, and if I had known this when I was trying to break into tech, if I wasn't interested in being a developer, I would have definitely considered this. This is a role that's very common in social media companies, like TikTok,

 

 Instagram, and Facebook, and that is the role of the Policy Analyst. So, for these major social media companies, they need a team that's responsible for creating community guidelines and creating community policies. This is actually a very difficult task because you need to create guidelines based on the local community and also the country as a whole too. So, different localities will have different guidelines and different policies based on the rules and the policies of that country. They develop these policies and guidelines by discussing it with different politicians, different local community leaders, and different NGO's, depending on the areas that they're in.

 

 These guidelines also need to be inclusive of different communities and different cultures. And it's also really important to create good guidelines because we all know the power of social media and how the wrong content can have a very harmful effect on a community. We will also see them enforcing these guidelines and these policies, also ensuring that destructive content is removed and monitoring and making sure that that destructive content isn't staying for a long time. They're also creating large scale strategies of how to actually track and remove this disruptive content. So, those are the five roles that I feel like you should check out if you're interested in breaking into tech. Make sure to check out part one of this video, because that has five more roles that you can consider if you don't want to program and you're not interested in getting a computer science degree but you still want to be in tech. As always,