Software Testing
Succeed in your first job4 min readPublished November 12, 2026

Your first 90 days as a tester

You got the job. Now what? A practical plan for your first three months: learning the product and the team, getting productive with real bugs, earning trust, asking good questions, and setting up how you'll keep growing.

On this page

Key takeaways

  • Days 1–30: learn. The product, the users, the team, the tools and how work flows from idea to release. Ask lots of questions and write the answers down.
  • Days 31–60: contribute. Test stories on your own, write clear bug reports, join refinement, and take on one small improvement.
  • Days 61–90: own something. An area of the product, a regression checklist, or a first set of automated tests. Then agree with your lead on how you'll grow next.

Before day one

  • Re-read the job ad and your interview notes: what did they say they need?
  • Refresh the basics you'll use daily: bug reports, the bug life cycle, Jira, DevTools.
  • If the product is public, use it as a customer would.

Days 1–30: learn

The product and its users

  • Use the product end to end. Write a one-page map: main users, main flows, what makes money, what would hurt most if it broke.
  • Read support tickets and recent production bugs. They show you where it really fails.

The team and the process

  • Learn who does what: developers, product owner, designers, other testers, support.
  • Understand the workflow: how a story moves from idea to production; what environments exist; how releases happen; what the Definition of Done says.

The tools

  • Get access early: tracker, test management tool, environments, test accounts, logs, chat channels. Missing access is the most common first-week blocker.

Days 31–60: contribute

  • Test stories on your own, from reading the acceptance criteria to closing bugs.
  • Write bug reports that need no follow-up questions: steps, data, environment, evidence.
  • Join refinement and ask one or two "what if...?" questions per story. That's where testers prevent bugs.
  • Pair with a developer to test a story together, or with a senior tester during an exploratory session.
  • Pick one small improvement: a clearer bug template, a missing test account, an outdated regression checklist.

Days 61–90: own something

  • Take ownership of an area of the product: be the person who knows how it should behave and how it breaks.
  • Build or refresh a regression checklist for that area.
  • Automate something small, if automation is part of the role: a smoke test, a few API checks.
  • Have a growth conversation with your lead: what's going well, what to improve, what to learn next (automation, API, performance, the domain), and how success is measured.

Habits that build trust

HabitWhy it matters
Say what you tested and what you didn'tPeople trust testers who are honest about gaps
Report bugs factually, never personally"The total is wrong when..." not "You broke..."
Share findings earlyA risk reported on Tuesday is better than a perfect report on Friday
Ask after trying"I checked X and Y, and I'm stuck on Z" gets help fast and shows effort
Follow throughRetest promptly; close the loop on what you raised
Real-world exampleThe junior who read the support tickets

Elena (an illustrative example) joined a team testing an invoicing app. In her first two weeks, besides her onboarding tasks, she read the last three months of support tickets and grouped them by area.

A pattern stood out: about a third of the complaints were about invoices with foreign currencies, but the team's regression checklist had only one currency test. She shared a one-page summary in the retro, with examples.

The team added a set of multi-currency checks to the regression suite and gave Elena ownership of that area. In the next release, those checks caught a rounding bug before it reached customers.

Lesson: a new tester's fresh eyes are valuable. Combine them with data, share findings early, and you earn trust fast.

Do

Ask questions, write the answers down, deliver small and reliable results, and be transparent about what you tested and what you didn't.

Don't

Stay silent for weeks to avoid "looking junior", or try to change the whole process in your first month.

Check yourself

It's your third week. You find a bug that looks serious, but you're not sure whether it's really a bug or intended behaviour. What do you do?

Show answer

Check what you can first: the requirement or story, the acceptance criteria, any documentation. If it's still unclear, ask a senior tester, the developer or the product owner, briefly and with evidence: "When I do X, I get Y. I expected Z because of [requirement]. Is that intended?" If it turns out to be a bug, log it properly. Raising a possible serious problem early is always better than staying quiet out of uncertainty.