What is SDET bootcamp?

Are SDET bootcamps worth it?

I've been wondering if it is possible to get the job you want without the help of a recruitment agency. I'm not talking about the kind of agency where you get a recruitment consultant for 400 a month. That's something we all need, no doubt.

There are some good ones out there, but I'm talking about the kind of companies who pay your salary, and provide career coaching (from an agency or in-house). These companies do tend to specialise in some specific sector, such as publishing or banking, but they often have generic teams in every department who require different skillsets. The challenge is getting noticed by the right person.

That's why I decided to join the Google for Startups SDET Bootcamp. It's a 4-day bootcamp in April, just before Google I/O. The cost of the bootcamp is 1695. This includes accommodation, food, training, and even access to the conference for lunch and drinks (and this costs 200). There is no refund, and you cannot change your place of enrolment. But what happens during the bootcamp? Well, a number of my colleagues and I will be working on a set of SDET-related projects. At the end of the bootcamp, we will have delivered our work to Google, so we can present it at Google I/O. We will have earned certificates and, possibly, a position as part of the Google team responsible for building the new developer tools.

Now, that sounds like a deal I couldn't turn down. After all, I'd like to move up the ranks at Google. Plus, it means I can use that time to read and learn more about Android development. And we know that Android development is Google's #1 priority.

I can even see myself staying on after the bootcamp, taking up a temporary position while I earn my full-time job at Google. And then I discovered an SDET bootcamp on Code First's website. It costs 1695 too. But here's the catch: it's in March, a few months before Google I/O, and it lasts 2 days.

Is SDET better than QA?

Why not use a third party company like TestComplete or QTP?

I know these companies are well paid and some can be really good at what they do but then when it comes to a bigger project maybe this type of tester does not come good either because I know sometimes you can work yourself out of a job if you do not have an upper management of your own. How can we go about this testing, so that quality is always kept higher. I just do not know how to get started with all the resources that I have, whether they are in the right places, or I don't even know how to get them, or just the number of people I might have to have working under me.

How can we be efficient when it comes to testing, yet ensure better quality for our users. I am trying to understand how I can make all of this work better when I am starting up from a different level, and not knowing anything about it all.

1 answer. 1) Make sure you have a thorough understanding of the end users needs (the requirements document from the client / the spec from product / whatever)2) Don't just follow the 'build test' mantra which is something testers should be doing!3) Test the functionality of the application by 'walking through' it so that you understand what the user experience is for those key activities that matter to you4) Get a tester to go and actually use the application whilst you are there to confirm it works ok5) Ask your lead / boss / mentor how he has seen the project delivered before. There may be a few things that you need to learn from other people's mistakes rather than just from documentation - maybe a 'best practice' book? So yes - test automation, regression and QA - as well as manual testing - is important. But it isn't that easy to implement, or as straightforward as you may think.

When you automate and reduce the amount of things you have to do manually, it is easy for the 'burden of work' to shift. If your test effort reduces because you have spent less time in the application, and the remaining tests take longer, there could be some 'work for nothing'. So you will still have manual time allocated as the 'extra' effort, just you do the work of two people.

What is SDET bootcamp?

Our SDET Bootcamp is a 5-day course designed to train participants to design, develop and test the core Android features for wearables and smartphones.

Participants will learn how to design wearables using Android Studio, create custom user experiences with an interactive wearables app, build wearable hardware using tools such as Arduino and Android IoT development boards, develop Android Wear watches, build a high-level SDK for wearables, write a device-specific Google Play services app for wearables, and build an on-premises server to host API endpoints, and more.

Course details. We cover topics on Android SDK and wearables for students who are interested in developing Android apps. Our course includes lectures, quizzes, discussion, and exercises that provide hands-on knowledge. The SDET bootcamp consists of five days, with two days of lectures followed by one-day of hands-on labs. Each day is meant for self-paced learning and self-study. Our course is for beginners with no prior Android programming experience.

Who should attend SDET bootcamp? SDET Bootcamp is open for anybody who wants to take their first steps in building apps for wearable devices or smartphones. We recommend that you come if you are in the following areas: Software Engineer, Programmer or Developer. Android Programmer. Interested in wearables. What's included in the course fee? There are 5 different types of pricing options. The course can be taken for free as a self-guided course, for those that want to learn the subject matter and apply what they learn outside of our live course, or paid options are available to meet a maximum number of participants. Read more here.

Is there a recommended minimum number of attendees for the course? Yes! SDET Bootcamp is a five-day, self-paced course, with daily exercises that require a minimum of six people to complete successfully. You must have at least six students (no less than five and no more than ten) working together to complete the weekly assignments. In addition, every student needs to have access to a computer and have the SDET Course Materials provided to the entire group (laptop or tablet). However, we encourage more than six people per class to participate to ensure that the pace of the class remains consistent and the time allocated is sufficient to get students up and running.

Is SDET in demand?

A while back, on a whim, I had decided to ask the question on this site.

At the time I still had nothing more than a vague notion of what an SDET actually was. What I can tell you, though, is that I've seen it employed in a number of positions. Let me start with anecdote. I was about to interview for a job at the time. When we got around to discussing the job requirements (which was before anything else), the hiring manager started talking about the software he was using.

"You know I use MS Word, right?". No, I didn't know that. But I nodded anyway.

"Well, I have it open and working on my computer so that it will be ready when I'm done working on my email." I looked at him incredulously. A couple of questions flew through my mind.

"So you work in a office where every other person opens their email in another program?". "Uh, yeah." I had to bite my lip. I just couldn't tell if he was telling the truth or being coy. Maybe I'd ask about it after the interview.

The interview went great. They were looking for a senior software developer. And they liked the idea of having me on site. So we sat down for the interview. After we talked about everything else, the guy asked me, "Why did you pick us?"

I had to admit that I hadn't exactly thought that far ahead. He told me a bit more about his company. I was still wondering how much of the conversation was real.

"So what software do you use to do your work?". Oh man. I'm going to pretend that he stopped right there. As he was talking about it, I could only think of the worst possible answer he was going to hear.

"Well, what everyone else in my group uses." This time, I kept it together. I started in with the usual stuff. The guy's company sells a lot of software. They use a lot of proprietary software.

"Do you use Microsoft Office? "Well, no. Not really."

He started explaining, again, about how they use MS Word. I knew I had to take control. If I had the opportunity to change this guy's career, I had to do it.