portfolio

I test com­plex sys­tems, build qual­i­ty prac­tices, and help teams think more clear­ly about risk.

Over the last nine years I’ve test­ed dis­trib­uted sys­tems across health­care, e‑commerce, bank­ing, and order ful­fill­ment, from iOS pri­va­cy apps to ware­house inte­gra­tions to mobile bank­ing plat­forms. My back­ground as a for­mer attor­ney shapes how I approach test­ing: I think in edge cas­es, stress-test assump­tions, and look for the gaps between what a sys­tem is sup­posed to do and what it actu­al­ly does when things go wrong.

what I do

Explorato­ry test­ing on com­plex sys­tems
I spe­cial­ize in find­ing the bugs that mat­ter, the ones that slip through auto­mat­ed checks because they require under­stand­ing how sys­tems actu­al­ly behave under real-world con­di­tions. Inte­gra­tion points, ful­fill­ment work­flows, APIs that inter­act in unex­pect­ed ways.

Automa­tion strat­e­gy & test archi­tec­ture
I help teams fig­ure out what to auto­mate, what to test man­u­al­ly, and how to build test­ing approach­es that scale with­out cre­at­ing brit­tle, high-main­te­nance test suites.

Train­ing & cur­ricu­lum devel­op­ment
I’ve built test­ing cur­ric­u­la for devel­op­ers, cre­at­ed onboard­ing pro­grams for peo­ple new to tech, and trained teams on explorato­ry test­ing, risk analy­sis, and work­ing in con­text-dri­ven shops.

Qual­i­ty lead­er­ship & com­mu­ni­ty build­ing
As QE Com­mu­ni­ty Lead at Seek­Well, I run com­mu­ni­ty meet­ings, pub­lish a biweek­ly newslet­ter, and work with a com­mit­tee to iden­ti­fy and stan­dard­ize good test­ing prac­tices across the orga­ni­za­tion.

testing philosophy

I believe soft­ware test­ing is fun­da­men­tal­ly about under­stand­ing sys­tems and advo­cat­ing for users. Good test­ing requires:

  • Con­text over scripts — what mat­ters depends on the sys­tem, the users, and the risk. Script­ed test­ing miss­es what mat­ters.
  • Think­ing in sys­tems — bugs don’t live in iso­la­tion. Under­stand­ing how com­po­nents inter­act, how fail­ures cas­cade, and where the real risk lives mat­ters more than check­ing box­es.
  • Col­lab­o­ra­tion over gate­keep­ing — qual­i­ty is a team sport. The tester’s job isn’t to be the sin­gle point of fail­ure detec­tion, it’s to help the whole team think about risk ear­li­er and bet­ter.

tools & resources

Test­ing Resources — My curat­ed list of books, blogs, exer­cis­es, and com­mu­ni­ties I rec­om­mend
→ github.com/racheljoi/testing-resources

More tools, test exam­ples, and code com­ing soon. I’m cur­rent­ly work­ing on self-host­ed test­ing util­i­ties and exam­ple test suites to share here.

skills

Explorato­ry Test­ing · Inte­gra­tion Test­ing · API Test­ing · Automa­tion Strat­e­gy · Risk Analy­sis · Sys­tems Think­ing · Test Archi­tec­ture · Cur­ricu­lum Devel­op­ment · Con­text-Dri­ven Test­ing · Agile Method­olo­gies · Mobile Test­ing (iOS/Android) · Qual­i­ty Stan­dards · Team Lead­er­ship

Want to work togeth­er?
Con­nect with me on LinkedIn! I respond to mes­sages there.

Scroll to Top