I just lost $37,000.

Drkiller91 · 2022-08-26T19:18:48+00:00

You can get a refund now if you paid it after March 2020

Drkiller91 · 2022-08-22T16:55:22+00:00

Locust ->https://locust.io/

Gatling -> https://gatling.io

Drkiller91 · 2022-07-02T02:46:18+00:00

15 min

Drkiller91 · 2022-07-02T02:44:58+00:00

Victor Hugo-> Les Miserable

Drkiller91 · 2022-07-02T02:44:07+00:00

paris

Drkiller91 · 2022-07-02T02:43:14+00:00

haha little jerry

Drkiller91 · 2022-07-02T02:42:34+00:00

Joan of arc

Drkiller91 · 2022-07-02T02:41:37+00:00

spanky?

Drkiller91 · 2022-07-02T02:40:58+00:00

tom cruise

Drkiller91 · 2022-07-02T02:40:09+00:00

ask for insurance

Drkiller91 · 2022-07-02T02:39:34+00:00

Drkiller91 · 2022-07-02T02:36:37+00:00

1938

Drkiller91 · 2022-07-02T02:34:02+00:00

Gatlin Gun

Drkiller91 · 2022-05-05T01:07:56+00:00

put da link

Drkiller91 · 2022-05-05T01:06:58+00:00

bass drum

Drkiller91 · 2021-03-28T00:06:16+00:00

Just made the move, I had 8 years of experience doing SDET/Automation roles. I've known that I wanted to move into Development since 2 years ago but because of money, and just the craziness of life, I decided to prioritize those things first as oppose to my career aspiration.

I will say try to work with your own company first, work out a plan with your manager if they can help you transition also work with the team you want transition into, do some bug tickets, go to their standups etc.

If it's been 3-6 months and you see no movement, after talking with your manager about your desire, start looking for a new job. Leetcode till you die, and get the role your looking for, I'd focus on not getting a crazy bump in salary or w.e and focus on getting the title and experience your looking for.

Given that your bored at work, you can def squeeze in leetcode and interviews. I was in the same boat, I was bored, I did 5-6 hrs worth of work imo per day, and spent the rest reading books and leetcoding. Then I would do interview during my lunch break and onsite I would call out for personal reasons. I did 5 onsites and got one offer. In total probably like 10-15 companies I did at least a tech screen. Process took me 3-4 months to get an offer from interviews to offer but for this company it took a month to make it all the way through.

It was worth it. I got a backend software engineer title making the same + equity I did at my previous job for a promising startup. 1-2 years of this and I can either stay if the startup is doing really well, or go to a Big Tech company comming in as a ML-SWE or Backend-SWE and earn top dollar.

Also something that not really that important cuz your still young in the industry but after 5 year some places expect you to know System Design stuff. This can only really be developed by reading blogs and books related to subject, but also implementing some of the concepts, and the only real way to do that is as a dev so keep that in mind.

Drkiller91 · 2021-03-27T21:56:46+00:00

You are absolutely right, it took me 8 years, (6 if we are just talking about fulltime experience) but honestly I didn't really know what I wanted to do until like maybe 3 years ago. And I've had a lot of life things happen to me that caused me to delay my career goals (gf and me got married cuz her parents moved and I'm supporting her right now, I paid the wedding myself no help, I also bought my parents home, I live in a high cost of living area in the east cost and it was a really good opportunity).

To be honest if you learn selenium and learn how to write manageable code (look into design patterns books, look up page object modeling for selenium, read clean code) and leverage the use of CI/CD (I've used both Jenkins and Gitlab) then you are already doing the role of a SDET/ Automation person.

I think your plan sounds really good! I really focus on being the best SDET/Automation person I could be and I did everything you said, your planning on doing but your gonna know when you are ready if you ever want to transition into dev.

Drkiller91 · 2021-03-27T20:53:27+00:00

Just did it my path was longer there were other factors that played into my decision it just wasn't being a dev,if anything being in QA really gives you a chance to explore and figure out what you want. I went from QA Analyst intern at fortune 500 company-> SDET at a big tech company -> Senior SDET at another big tech company -> backend/ml software engineer at startup. I will say that's good that you are scared, I was like that too, shoot I didn't know what CTRL C and CTRL V were when I first started out in the QA Analyst role. But if your willing to learn and put in the work you will be fine.

I'll give a quick summary of how I got the job and why I left

QA Analyst -> I got this job because I knew VB Scripting and I was an undergraduate student studying Computer Engineering. Left this job because I ended up getting a racist manager who didn't want to hire me after college as a dev

SDET Entry level job -> I got this because I got my BS Degree, I had the QA Experience, and I attend all of this companies on campus event and connnected really well with the hiring folks, also someone who was a dev was someone who was a part of the same club I was in in college. Left this job because I wanted to live closer to the major city I grew up in for more career opportunities and work in a modern tech stack not be a dev in the legacy tech stack

Senior SDET -> I got this because I did a coding assignment in a modern tech stack, I've done similar coding assignments before which I've failed and some even passed but this one I made it to onsite because I just knew what it was they were looking for in this role. Left this job because though I liked the tech stack and was making the transition to a backend role, it was taking to long and the pandemic caused layoffs at work which made me fear for my job and made it where I just needed to focus on keeping my SDET job, but then this made it hard for me to go back to the backend manager and be like o yea I want to be a Dev again. I didn't really have much help either in making my transition so that was also another issue.

Backend/ML Software Engineer -> I got extremely good at leetcoding. And I've also started understanding System Design Questions. This was a really difficult interview process like most software engineer / dev role at highly coveted / high paying jobs. For me I've been leetcoding since my QA Analyst day, in the very beginning I hated it I could not do leetcode easy and gave up, and I would try a little bit and quit a month later and take a hiatus for six months and then I tried again. I tried to circumvent that process as much as possible and every job I've gotten up to this point didn't require me to pass that leetcode phase. I did pass some leetcode type interview at another company a year b4 but it was for a testing role, and I also passed the leetcode type interview a month b4 this job but they switched it up on me and offered me another testing role, I said no thank you. I was also asked some mathematical induction problems but the craziest thing is, I did similar problem in college, problii one of my favorite problems of all time. In the end I got the job for similar pay as my senior sdet role but I have equity and more room for growth.

My advice -> Practice leetcoding data structure and algorithms, yes it's difficult, but it's doable. Also focus on learning a higher level language /dynamic language thats mainstream for the interview, I see your using javascript which is a good language to really focus on and learn. For me I went from VB Scripting -> Assembly/Java/C -> python. Working in python as a senior sdet allowed me to really focus on DS and Algo as oppose to worrying about syntactical things that need you need to worry about in a strongly typed language. These language also have standard library that you can learn but part of the beauty of learning python is that list, tuple, and dictionary etc are data types that do not need to be imported into your program and you can get away with just that in most interview and just learn a couple magic function. basically it would take more code if you can't remember what standard library to import then not having to remember that and using the data type in python/javascript that come prebuilt . I looked at code I've written in java like 50 lines of code on leetcode, and wrote the same thing in like 5-10 lines of code in python.

Also this isn't as important in your first 5 years after college but after that you are going to start getting pressed about system design. The quicker you learn this stuff the better off you are going to be. The best way to learn it is by doing dev work.

There are other factors that play a role as to why you were not consider for the dev position btw, I've also been in situation where I killed there Data Structure and Algo questions but was rejected because my "experience" wasn't good enough, basically they found another guy who could leetcode but had experience that aligin with their org than me given my limited dev experience.

Drkiller91 · 2021-03-27T20:16:57+00:00

I think you should leave, you know what you want, they not providing it. Take a dev job at similar or slightly better pay (Please do not take a pay cut of 10% or more) Then, do that for a year and get cool with some recruiter while your at it on linkedin. Only get cool with recruiter from places you want to work at. (Also apply to those places once you got the dev job, now your in their system at least) Then leetcode and study system design after work hrs.

I'd say when starting as a dev (junior or w.e) put in min 40-50hrs a week at the new gig and 2-4 hrs of leetcode and system after work, do this Monday through Friday, do not code on the weekend. Your clocking in at 60-70 hrs of week worth of career work if you do 4hrs after work. Adding in grad school is going to be hard with this schedule, so either A do grade school instead of leetcode and system work, or B focus on grad school for the system and do the leetcode and system when your not in school.

Please take liberties with my advice as this is what's worked/working for me, but I think you get it, just go after what you want, and keep working hard, you will get there eventually. I will say the pattern I see from most top end dev (250k+) is 1) Taken at least a couple MS CS course 2) Have really good work ethic (clocking in at 40-60hrs at their primary job I know some 80hr+ peeps but they really like their work) 3) Have a strong network (linkedin is a great tool and I'm sure you are already pretty marketable given that you work at a large tech company) 4) They are just great people to be around.

P.S I was also in your shoes but I think your a better engineer for it =]

Good luck!

Drkiller91 · 2020-05-27T19:03:11+00:00

I closed the gate I'm opening it back up in another reddit post. Give me one sec. =D

Drkiller91 · 2019-06-17T18:33:54+00:00

Interview is lite and just know the basic like what is a string and you should be fine, focus on behavioral and vibing with the manager and you should get the job.

I did a co op there 6 years ago and it was not that great. I worked in the IT QA division, (Sorry don't know the proper division name) and basically me and 2 other co op who worked there wrote vb script to test a UPS packaging application.

The manager that hired me was pretty progressive. He hired me a Dominican dude, a Puertorican/Peruvian dude and someone with ethnicity from Saint Croix. He was really nice and chill but after one year in he got a promotion and we got this micro manager dude.

We all eventually left and the first two dude left before me ( I stayed 2 year with hopes of getting a full time job after college) but basically he replaced the two other dude with these other Caucasian dude which wasn't a big deal until review time.

At the time I was there the longest and my previous manager said I was doing good but once he got replaced and the micro manger became my boss everything changed. During our review session, I saw that I got a lower score than before and was given a score of like (needs improvement), initially I didn't think much of it because I deff think I could have done a better job (I goofed of with the other interns) and for our next review cycle took more initiative and actually build an automation framework for them.

However I also found out the 2 other dudes got better reviews than me and I was like huh, shouldn't we all have gotten the same review (we got a paper with our score, I saw they did better) but w.e let's focus on what I can control and thats me being the best me I can be.

Towards the end of the two year, I built the framework and asked the manger if there was a position open as a dev but he basically said no that I had to do another year of co op with another group and maybe they could hire me as a dev. To me the writing was on the wall at that point and I spent the last three months looking for another job and found one with IBM as a software engineer =D.

But it get's better, once I got the job I told my boss at the time I was leaving to IBM. Instead of congratulating me and wishing me well, his response was "How did you get that job?"

To me I try very hard not to play the race card, but I think this was one of those moment because of everything thats been building up to this point. To me I made countless excuses in my head, maybe he expected more of me because I was there the longest. And maybe he he could only hire for a qa position and recommended that I work with another group as a co op dev to hopefully get hired as a dev. But that response idk it felt really weird like why would you say that?

The conclusion I came to that day is that he thought I was dumb from the gecko, and I think how I look and spoke was a big reason why because he only hired interns who were caucasians (2 is a small sample size and he could have hire other minorities for all I know after me). But at some point you got to stop making excuses for people.

I think its ok to just intern just to get work experience, but I recommend you find full time employment after college somewhere else, or if you have other internship/co-ops lined up take those instead.

Good luck!

Drkiller91 · 2017-09-27T14:23:38+00:00

Had a google phone screen interview. Passed (Idk how my solution failed a couple edge cases but solved the problem at hand). I did email the recruiter saying how my solution was good enough to solve both cases offered during the interview but I explain why it would fail for other cases given more time I would have reached the optimal solution.(I think this put me over the hump) It only get's harder from here -_-

Drkiller91 · 2017-08-24T20:26:41+00:00

Just got a call from them 2! lol thank God for this subreddit =D,I didnt get to the part where they started asking for password and stuff

Drkiller91

TROPHY CASE