I see lots of people asking about rates/salaries, question of what to ask for comes up every so often, so I figured I'd write up a guide of how I negotiate my salaries/rates.

Who am I and why should you care - Senior QA Manager with 20+ years in software industry. Maybe you shouldn't care, but you're already here, so why not read it?

So, what to answer when the dreaded question of "what's your expected compensation" comes up?

First negotiation round.

That's right, there are at least TWO rounds of salary negotiations. During the initial interview process and when the offer is made. Take advantage of both. They both have different goals. The first one, during the initial interview stage is for you to make sure that you make the cutoff based on salary range while asking for as much as possible. Second one is there for you to ask for even more now that they got to know you and like you enough to make an offer. First round is usually done by recruiters and they don't give a shit about your salary. All they are doing is making sure you tick checkboxes you have to tick. One of them is being within a range. You job is to find that range and ask for the top end of it.

1. First and foremost you should know that nobody will turn your down because you asked for more money than they are ready to pay. They will say "Actually our current rate is X, would you be willing to work with that?". If you say yes they'll forget what you asked for 10 seconds after that.

2. Know that "What are your salary expectations" is a fishing question that gives you advantage. Your only job here is to give them the number that's higher than they expect to pay, but not outrageously high so that they laugh at you. The question is designed for timid people who think it's a privilege to work, who can be taken advantage of when they ask for less. If you're one of these people, I hope this can help you come out of your negotiations shell.

3. Your mindset should be - if they don't say "uh our rate is actually less" then you didn't ask for enough. Giving them the higher number than they are ready to pay forces them to tell you what's the maximum they are going to pay. Always ask for more.

4. Position your salary demands as "I'm currently getting <what you're asking for> and I'd like to stay in that area".

5. Make sure they know you are open to negotiations.

Here's how a sample negotiation usually go. I know the going rate in my area is 130-140K for my type of role:

• What's your expected compensation?

• Well, currently I'm getting 170K where I work and I'd like to stay in that area. That said, to me an interesting job takes precedence over few thousand here and there, so I definitely don't want the number to stay in a way of us talking. Plus, some of the benefits could be as good as cash in hand.

• Right, so the maximum we're ready to pay for this role is 145K, would that work for you? For benefits we offer 4 weeks of vacation, 5% RRSP match, etc.

• Sure, that sounds great!

I use their question to get the information I need - what are they ready to pay and what are the benefits like. I've interviewed upwards of 50 times over the last ~18 months. Not a single time the interviewer would call it a day based in the number I give them.

Second negotiation round

How to increase the number you give them afterwards. All went well and you got a job offer. Congrats! Now let's increase that number. Always ask for a day or two to think about it. Never agree on the spot, they never expect you to. Here is something to keep in mind - they've just went through exhausting process of interviewing several candidates. They chose you. They want you. They aren't going to shut you out immediately if you approach it respectfully and politely - they definitely don't want to interview people again. Worst they say is "that's the max we can afford". How I approach it:

"I've received a job offer from another company for <what your offer says +10% or +10K, whichever is higher>. Thing is, I would really prefer to work for you - the job sounds a lot more interesting, and I think we're a better fit. Do you think there's some wiggle room for the compensation?". Be prepared to answer the question of "what company is that" (just name a company that exists but doesn't sound exciting. Like AT&T or Bank of America or whatever. Bonus points is if you name their competitors. I've helped couple of my friends and myself get a higher offer this way after the initial offer was already made.

A great addition from/u/Lazy_ML in the comments about this, in case they ask you to show offer letter from said other company:

Many FAANG type companies say their offer letter is confidential and ask you not to share it. You can always use this to deflect the question. It may not get them to match but it won’t make you look like you were bluffing. Many companies also won’t give you the letter until you verbally accept because they don’t want you to shop it around so not having a letter isn’t an indicator of not being truthful (side note: I suggest trying to get the company to confirm the numbers via email, though some mf’s will call you back to confirm). I’ve never provided an offer letter and it has never been an issue (for FAANG as well).

Bonus round 1

DON'T TAKE LESS MONEY THAN THE MARKET AVERAGE. Let's say the average rate for your role is 100K and you're being offered 70K (looking at you, gaming industry. Fuck gaming industry and their labour exploitation). Fuck them. Turn them down. Make sure they understand that the reason you turn them down is their salary is designed to fish at the bottom of the barrel and that's not where you swim.

• Oh you pay less because it's gaming so you're basically getting paid for playing games? Fuck you.

• Oh you pay less because there's a ping pong table? You mean I have to come to the office and get paid less? Fuck you.

• Oh it's oil and gas industry and they want to pay less because it's tough times and oil is cheap? FUCK YOU TWICE. I'm not beneath working for oil and gas but my rate will be at least 30% more than the market average, not less.

These are all real examples from my experience.

But bikes_and_music, it sounds good and all but I need money to pay rent and to eat. I can't just refuse a job offer because they aren't giving a fair wage, I haven't had a job in 6 months, it's a rough market out there!

I hear you. Totally valid. Take the job. Get paid. Feed your family. Keep looking for a job as if you don't have one. Get a better offer and go get paid more. When you leave 2 months down the line make sure they know that you leave because the pay is shit. They will try and guilt you. Oh, you knew what the salary is, why did you accept if you were going to leave! Give them the absolute honest answer - I needed money. I took the job. You knew I wanted more. You know you pay significantly less than the average. If you want talent to stick around pay more money. If you do leave after short period of time don't put them on your resume. This way not only you get better conditions for yourself, you teach them a lesson about being cheapscates.

True story - in March I was offered a 110K job. I wanted 140K. I turned them down. In July I started a job for 150K. By end of Jan I will have made the same amount of money as if I started in March, but I also got 3 extra months off.

Bonus round 2

They offer you less money than the average but dangle "excellent career opportunity" in front of you. As a general rule you should know that this means that whatever promotion you're looking at you'll still be getting less money than the average for that role. Nobody but you can determine whether the opportunity is worth the paycut, but don't go into it thinking with promotion will come the $$$. It won't most likely they'll throw you a title, 5x more job and like 5K extra per year. It's great to have that promotion on your resume but do the math. You're going to stick around at least a year, preferably two after promotion before getting another job at that level. Plus a year to get there. If you're getting 20-30K below average annually that adds up to 60-90K in three years. Is it worth it? Only you can decide, but you need to understand that these are real money you're paying to get that promotion (if they give it to you).

Bonus round 3

Sometimes it's ok to get paid less. One major example is time off. At my previous company when I got a job offer from another place I went to my boss and said "I'm being offered 25% more than you're paying me. I'd like to stay here, and I know you can't increase my salary as much as this, but I was wondering if we could arrange an unlimited vacation situation for me. Doesn't mean I'll go away for 6 months or whatever, but I don't want to clock in and out. I want to have the freedom to work from where I want, when I want, as long as my projects don't complain about me. If they do - feel free to nip this in the bud." I got my unlimited vacation and you can be damn sure I used it to my advantage. Your time is your most valuable commodity. Don't sell it for cheap. I don't even consider this example as "getting paid less", I got paid more as far as I'm concerned because I took like 6-8 months of time off in the next 3 years.

Another example could be an industry that you're passionate about and is not famous for having lots of money. Maybe it's a company that works on some green initiatives. Maybe it's a non-profit that helps feed people in Africa. If you want the job and can afford the paycut - take it. There's nothing like knowing you're helping people.

Bonus round for hiring managers

Normalize telling people when they ask for less than you're prepared to pay. These aren't your money. Your VP/CEO is not going to suck you off just because you save him 5-20K a year. You team is ultimately your boss. If they lose trust in you that's game over. Easiest way to get them on your side is to be upfront - Joe, you asked for 80K but the average wage for this role is 100k so we'd like to offer you 100K.

For you it's just a number. For them it might the difference between being able to put their parents in a nice hospice or needing their spouse to quit work to clean up after them. In other words, 20K/year for a company is a spare change. For a person it can change their life. Don't be a dick. Be a person who changes people's lives for the better.

It took me some time to get to these, I hope they can help some of you to make more money. I've helped multiple acquaintances as well as myself to negotiate their salaries using this. Go get paid. Fight the status quo.

I've been a QA for about 3 years now and have been looking to switch to a better opportunity and to hone automation skills. I'm familiar with Selenium and SQL and etc etc but for some reason after applying to hundreds of jobs in the last 2 months not even one callback, something has to be wrong with my resume. Any guidance can help!

Hi Folks,

I scraped few thousand Quality Assurance Engineer interview questions for Google, Amazon, Oracle, IBM on various sources - (github, glassdoor, indeed and etc.) After cleaning and improving these questions (adding more details, removing less relevant ones, and writing solutions), I’ve compiled around 200 interview questions, which I am publishing for free.

Disclaimer: I'm publishing it for free and I don't make any money on this.
You can check them out at https://prepare.sh/interviews/quality-assurance

I plan to keep adding more companies and questions to cover most major tech firms, so it's a work in progress. If you find this content useful and want to help with code, content, or any other aspect, please DM me!

Okay not yet, I still have plenty of time before I can afford to shed my "golden QA handcuffs" (I make $125k).

But between AI making it easier to use our brains less and AI Agent products claiming they can "do QA", I'm tired, y'all.

Got off a catch-up call with my ex-boss who's now a QA Director at a startup where his boss just asked him to axe all the QA Engineers who don't want to switch to Dev -- all to try out an AI experiment to see if it can do the job of QA.

Dumb leaders, AI making us dumber and more illiterate by the day...idk what our brains will look like in 5 years but even if we're all fine, it's exhausting keeping up with all this or making sense of it.

I've only been in QA for 5 years and I've done lots of mentoring and really milked this QA career of mine, probably more than most 10+-year QA folks do, and it was fun until right about now.

Am I the only one who's tired of all this AI hype and just wants to actually do my job? When I get the money -- probably when my first employer IPOs soonish -- I'm ditching all this tech insanity to start a local yogurt shop.

Tech industry likes to dunk on manual QA as it's dead and worthless position. I recently hired a manual QA who is less than a year into their company and their attention to detail and thoroughness is mindblowing so much so I feel bad for them and wish they were in a role that paid them higher. Probably a lawyer or something.

I simply don't know how can I hire for such strong manual QA, maybe give them a demo project and ask them to do it but it would take 2-3 days to do the interview. Probably can convince company to spend that much money on some hires - pay them for their time. But I don't know if this approach is feasible for smaller companies.

Hi everyone,

I created a job board and decided to share here, as I think it can useful. The job board consists of job offers from FAANG companies (Google, Meta, Apple, Amazon, Nvidia, Netflix, Uber, Microsoft, etc.) and allows you to filter job offers by location, years of experience, seniority level, category, etc.

You can check out the "Quality Assurance" positions here:

https://faang.watch/?categories=Quality+Assurance

Almost all of them include some level of automation QA.

Let me know what you think - feel free to ask questions and request features :)

Most of the people here are not happy with QA jobs and only rant about how QA is a bad career option/how they are feeling stuck/how dev is more rewarding. But no one talks about what they are actually doing to improve their situation, what new technologies they work on, their challenges. This sub feels like a group who is collectively demotivated and only want to validation/sympathy.

A couple of weeks ago, I shared my frustration about not securing an offer for an Automation Testing role after applying to 10+ jobs. Here's the [original post link].

The feedback I received was an eye-opener. Many people pointed out that applying to just 10 jobs wasn’t enough and encouraged me to apply more aggressively. I took the advice seriously and applied to over 500 jobs in just 15 days.

From those applications, I got around 10-12 interview calls. And today, I’m thrilled to share that I’ve received an offer from a product-based company with a 100% hike! 🎉

This was my first time applying for jobs, and I cannot thank this community enough for the amazing advice, from resume reviews to interview preparation tips. You all made this journey so much easier for me.

You guys are the best!!!💪

The company I work for had a wave of layoffs just last month because of AI. I lead 2 teams of QA engineers, 2 on each team, now I am down to just 1 dedicated tester, 2 if you include me because now I have no choice. For context, there are 5 or 6 developers per team, and no BAs so analysis falls on the developers as well.

We had a meeting a while ago to discuss how to move forward with this. Developers will too now cover testing and automation with the help of AI, and I am supposed to help oversee and establish governance on this, as if I don’t already have my hands full with trying to catchup with deliverables. Honestly, I think it’s only a matter of time before my job is taken over by the dev leads and they will soon let me go as well. I need to save myself and start looking for opportunities out there, and I am seriously considering moving out from QA.

Sorry to post another sob story about QA jobs getting replaced by AI. We already have enough of these in this subreddit. I just needed to shout to the void.

Hey QA Folks,

you can remember me from a relatively viral post some time ago in this sub

https://www.reddit.com/r/QualityAssurance/comments/1dn14cy/i_scraped_all_qa_engineer_interview_questions_at/

Recently I was reading this sub and every day there is a question "is AI gonna take away my job or is QA a dead-end career"

Its been more than a year that we ran our company, and its not all roses for us too, but what I wanted to tell you is that we automated many things and were able to operate with only few engineers, however when it comes to QA we and other companies can't automate it. Somebody still needs to check and validate all what AI is producing, Infrastructure, UI, Features and list goes on.

I know that my word doesn't mean much for people who are struggling and lost their jobs but I hope will show you other side that It's market that is crap, not QA, every field is struggling right now so hang in there buds!

so i'm a qa engineer, and we've recently started building an internal ai agent that understands new features, explores the app, and automatically tests everything.

pretty fucking cool, right?

well, now they're planning slack/teams integrations where the agent communicates with developers, creates tickets, follows up on bugs, and basically handles everything a qa engineer does.

and i'm sitting here thinking, motherfucker, that's literally my job. 😭

the worst part? i'm actually helping build this thing.

management calls it "improving productivity." i call it writing my own termination letter in typescript.

genuinely curious, are we making qa better or just building our replacements?

would you help build an ai agent that could eventually replace you?

Had my second round interview today for a QA Automation role at an early stage startup. The interviewer was the founding engineer.

I came prepared with Page Object Model, Playwright, API testing, CI/CD integration, the works. Felt reasonably confident going in.

Then he asked me to build Tic Tac Toe from scratch.

I froze. Said I didn't know how to approach it and the interview pretty much ended there.

Now I'm sitting here wondering if is this a normal QA automation interview question? I know TypeScript and Java, I can write solid test frameworks, automate UI and API flows, set up pipelines. But algorithmic game logic?

The founding engineer also asked "when was the last time you coded" which stung a bit. Felt more like a software engineer interview than a QA automation one. Is this a startup thing where QA and dev roles are blurred? Should QA automation engineers be expected to solve problems like this? Or did I just get a bad interview? Feeling pretty defeated right now. Would love to hear from people who've been through similar experiences.

**TL;DR:** QA automation interview asked me to build Tic Tac Toe. I froze. Now questioning everything. Is this normal?

Edit: Note - the company had openings for qa automation engineer and sdet roles separately. And I applied for the qa automation role.

As a developer, I honestly miss the days when QA meant gatekeeping quality, not just running regression scripts after we merge. Too often now, it feels like QA is just verifying builds and raising tickets like customer support reps with better Jira access. No upstream ownership, no friction, no deep analysis, just ticket triage and "steps to reproduce." I don’t want a passive QA. I want a partner who asks why a bug exists, not just whether it still exists. Someone who challenges product assumptions, catches design flaws early, and tells me my happy path is delusional. If QA is just there to "check" my code after the fact, we’re both doing it wrong. Real QA should break things before they’re even built.

Got laid off after 7.5 years mid June along with few others due to some company restructuring.

Been doing QA for the last 20+ years with a heavy focus on feature (manual testing - UI and API) on SaaS, Enterprise on prem and even desktop software. Last 10+ years though have been SaaS products.

Most of those times, the QA teams were small and automation wasn't a priority up until maybe the last 1 or so?

The mantra for the team was, feature testing to make sure our customers don't have a bad experience. Automation would be secondary so recently. There were existing automated tests from before so refactoring and creating new tests wasn't so bad given I had examples to use.

When we started a new project, we decided to go with Playwright / Python and it was pretty good. I'm still no expert on the Python side but the Playwright docs are pretty good. When Github Copilot and Claude Code were cleared for enterprise use, I was able to crank out tests with the tooling which felt good but also, realized that's where the learning stopped.

Being the lone QA on a team probably doesn't help that.

In any event, I'm panicked. Anxiety is setting in with the job market the way it is. I feel like I'm experienced in all the wrong areas now. It seems most postings are all about automation mixed with "some" manual testing, exploratory testing, test case design, planning etc.

Ageism is creeping in for me, I worry about my family and haven't had an appetite since I got laid off. I'm losing weight, continued of lack of sleep and can't stop doom scrolling the job boards seeing that I'm not qualified anymore. Everyone that I worked with reached out and said that I was great, totally improved the quality and provided confidence that we could deploy everyday. Some said I outgrew the QA role on the team and don't understand how this could happen. There's also no more QA on that team.

Sadly, management didn't see it that way.

I was working remotely and resigned to the fact I would go back into an office locally, except there's only a handful left in this city.

I feel alone, trying to put on a brave face for my family but suffering here in silence. I'm frightened I won't be able to provide for my family since I'm the primary income earner.

I'm not even sure what the point of this post is, other than to get this out of my head and hope to lesson my anxiety.

I am working in the QA domain for the past 10 years , starting from a simple test automation position using java selenium and rest assured. Back in the old days interviews were simple you know coding basics you have testing principles so you are hired. Scaling up to today I was working as a QA lead managing a team of 10 QAs. Suddenly all the qa department became obsolete and outsourced to India.

I started interviewing with high hopes and oh boy its hard.

Test Interviews asking for principal level java engineer but also know python and be able to write code in JavaScript while can debug C# code. Interviews asking for a Senior test automation engineer which will be prodigy on creating CICD pipelines (Jenkins+ AWS+ Azure) and also perform performance tests and deploy test environments. But be also good on documentation and test Managent, create proper bugs and manage the testing of the sprint and risk analysis and and and and......

But regarding the wage? As you are not A DEVELOPER we can't of course compensate you as A DEVELOPER.

I am really considering changing careers and just go to a super market in order to become a cashier.....

So I did some reading around the sub and I saw a couple questions on it, not sure if anyone has an updated opinion. I am hesitant because it does seem way too good to be true, with almost exclusively positive reviews and some questionable reddit comments about it. The webinar I attended today bothered me in that it was really pushed as being so easy anyone could do it and heavily reminding that they can all but guarantee you a 75k+ job within six months. I don't believe either, but what still has my interest is they claim a lot of job and interview prep as well as a post course internship for experience. I was looking at other ASTQB accredited ISTQB foundation test courses and they are of similar cost ($1000-2000) but for only 3 days. Careerist is one month (though it seems drawn out) plus the post course interview prep and internship, which appeals to me as I am really trying to change careers and am nervous about my ability to successfully find any potential jobs on my own (I do not have any tech background, I stumbled into 3D printing but that was a few years back now and I have been doing online teaching for the last three years. My job history is not very long and to be honest I don't have very much experience with applying or interviewing for jobs).

EDIT: I want to edit as I’ve gotten a lot of messages and comments asking… I did not do the course and will not in the future do it and more or less agree with all the negative comments against it.

The question gets asked many times every day and the answers are almost always the same generic responses. Learn Playwright. Learn Python. Learn {insert current popular tool and language}. Often you will see the link to that Github page that lists every possible tool QA tool that ever existed and people just tell them to learn that.

I wanted to write something up and be a little more specific because if you've never programmed before, those answers, while helpful, can be pretty overwhelming. So I have been putting together a slightly more specific list of what you should learn and wanted the communities input to refine it.

First, this is certainly not an exhaustive list. Second this isn't designed to be the order you learn them in, or what level in your career you should learn these things. It designed to work more as a checklist someone can use to get a really strong foundation for Automation. For some things I have also included a few examples where I thought they might help, again they are not an complete list. And this is designed to be as language/framework independent as possible but there are definitely some concepts here that won't apply everywhere.

So comment below however you think it cam improved and maybe we can create a nice document or sticky post that can be linked to so we don't al have to give the same generic answer 10 times a day. Also sorry if the formatting sucks. I copy/pasted it from Google Docs.

General Programming

The Basics

• Variables

• Data Types

• Flow Control Statements

  • Conditionals

  • Loops

• Logical Expressions/Operators

• Simple Data Structures

  • Arrays

  • Lists

• Methods/Functions

• Comments

Mid Level Concepts

• Version Control

• Classes

• Object Oriented Programming Concepts

  • Inheritance

  • Polymorphism

  • Encapsulation

  • Abstraction

• Functional Programming Concepts

• Variable Scope

• Visibility Modifiers

  • Private

  • Public

  • Protected

• Debugging

• Error Handling

• File Manipulation

• Writing readable code

• Asynchronous programming

• Reviewing others code

• Refactoring Code

Advanced Concepts

• Design Patterns

  • Singleton

  • Factory

  • Builder

• Project Structure

• Higher Order Functions

• Immutability

• Advanced DSAs

  • Stack

  • Queue

  • Linked Lists

  • Trees

  • Sorting

• RegEx

• Lambdas

• SOLID Principles

• Recursion

Front End Automation

The Basics

• Web Elements

  • Textboxes

  • Tables

  • Buttons

  • Labels

  • Lists of Elements

• Basic Locators

  • XPaths

  • CSS Selectors

• Assertions

  • Hard

  • Soft

• Waits

• Page Interactions

  • Get Text

  • Clicking

  • Open Menu

• Page Navigation

  • Open URL

  • Go Back/Forward

Mid Level Concepts

• What to Automate

• Improved Locator Strategy

  • Ids

  • Aria Roles

• Browser Management

  • Drivers

  • Cross Browser Testing

  • Browser Profiles/Settings

• Window/Tab navigation

• Design Patterns

  • POM

• Test Hooks

  • Before/After Method

  • Before/After Class

• Fixtures

• Creating Custom Assertions

• Mobile Testing

• Credential Management/Authentication

• Generating Test Data

• Logging

• Reporting

• File Upload/Download

• Cookies

• iFrames

• Debugging/Fixing Failed Tests

• Automatically Re-Running failed tests

• Parallelization

• Screen Shots/Videos

Advanced Concepts

• Test Framework Creation

  • Including choosing the correct framework

• Native App Testing

• Managing CICD Pipelines

• Environment Management

API Automation

The Basics

• Url/Uri

• CRUD Methods

  • GET

  • POST

  • PUT

  • DELETE

• JSON

• Path vs Query Parameters

• Request Body

• Response Body

• Simple Response Codes

  • 200

  • 404

  • 500

Mid Level Concepts

• Headers

• Authentication/Authorization

• Other REST Methods

  • PATCH

  • HEAD

  • TRACE

• Other Response Codes

• Cookies

• Error Handling

• Negative Testing

• Data Generation

• File Upload/Download

• XML

• Logging

• Debugging/Monitoring

  • Splunk

  • Data Dog

  • New Relic

Advanced Concepts

• Test Framework Creation

  • Including choosing the correct framework

• Managing CICD Pipelines

• GraphQL 

• Contract Testing

• Load/Performance Testing

• Security Testing

Other Stuff

• How to Google

• Console/CLI/Terminal commands

• How to use your IDE

• Writing Documentation

• Databases

• Containerization

• Cloud Tooling

• AI Tooling

You make my job and development so much better. You catch the bugs and prevent bad features from getting into production. You write automated tests to ensure any environment updates don't make everything explode. You see every detail in the UI mocks and ensure that the live UI matches. Thank you, thank you! I love working with you.

And to newbies, thank you for learning and taking on this task. Devs aren't always polite and get grumpy about interruptions. We love scheduled messages that we see first thing in the morning as well as movs and screenshots. You will become a great tester the more you practice and the more you learn about your assigned product.

To all the testers who wait at the last minute to test, don't know how to use their proxy tools despite claiming expertise, don't communicate, and require devs to walk you through your job even though you've been in this position for over a decade, quit. Just quit and find another income. Let someone else become a QA tester because you aren't it.

P.S. My favorite tester is moving teams and I'm stuck with the crappy one.

Early in my career I was laser focused on test cases, coverage numbers, and defect counts. Hit the targets, close the sprint, repeat.

It took a few years to realise I was testing features, not products.

The shift that changed everything was starting every new feature with two questions:

"Why is this being built?"

"How will real users actually use this, not how we expect them to?"

That context alone helped me catch more meaningful issues than any test case ever did. Because real users don't follow happy paths.

They skip steps, misread labels, use the product at 11pm on mobile with bad internet, and do things nobody in the sprint planning meeting ever imagined.

The most common mistake I see newer testers make, and it's totally avoidable, is treating test cases as the finish line. They're actually just the starting point. Exploratory testing, curiosity, and challenging assumptions is where the real bugs live.

The second mistake is spending 80% of energy learning automation tools while underinvesting in fundamentals like critical thinking, risk analysis, and understanding user behaviour. Tools change every few years. Those skills don't.

Curious what shifted your approach as you gained experience. Was there a specific project or moment where testing clicked differently for you?

Can anyone recommend any good AIs to aid with making test cases. Just getting tired of having to do from scratch since im alone in the team, still planning on modifying whatever AI makes.

Would also appreciate any tips y'all can give to utilize ai for QA

I started my QA career back in 2019. My first job was full Manual testing,

My second job was also 100% Manual both UI applications and backend testing .

My third job was embedded testing which was also 100% Manual testing. There was automation but it had a different team.

Last week I accepted an offer which is 80% automation and 20% Manual. Finally, I am really happy I can finally get some automation experience.

I am a bit nervous. Hopefully I don’t get fired or something since I don’t have much coding experience.