12:I[22016,["/_next/static/immutable/chunks/1gpx8n84x1dv2.js","/_next/static/immutable/chunks/3d9-j-u9wnj-v.js","/_next/static/immutable/chunks/19kqa-giu_yeq.js"],""] 13:I[80262,["/_next/static/immutable/chunks/1gpx8n84x1dv2.js","/_next/static/immutable/chunks/3d9-j-u9wnj-v.js","/_next/static/immutable/chunks/19kqa-giu_yeq.js"],"WorkRow"] 14:T150a, - owns **qa end to end** across the mobile apps, consumer web, internal dashboards, and admin tools, from first build through production - plans and runs **test cases, regression cycles, and api validations** against the swagger-documented api surface, tracking bugs and coordinating fixes across teams - owns **release readiness**: release notes, changelogs, and final sign-off, plus watching sentry and search console once a build is live

domi turns a user's physical mailbox into something they can manage from an app: mail gets scanned, and from there it's readable, searchable, and actionable instead of sitting in a stack of paper. i joined in **nov 2025** as **founding qa engineer**, brought on to own product quality as the team built it out. that's not a low-stakes surface to get wrong. domi handles someone's actual mail and paid postage, so a document that renders incorrectly or an upload that silently fails is more than a cosmetic bug. it's someone's mail. "it worked when i tried it" was never going to be enough. a bug that ships is a rewrite waiting to happen. a bug caught before ship is a comment on a pull request.

there was no dedicated qa function before this role. requirements got reviewed by whoever wrote them, testing was whatever the engineer who built a feature had time for, and releases went out on developer confidence rather than a defined check. that's a normal way for a small team to move fast early on. it's also how a real bug, a rare device, a slow network, an edge case in a document upload, reaches a user instead of a test pass. | | before | after | | --- | --- | --- | | requirement review | happens after the code is written | happens before a line ships | | regression | found by whichever surface a user hits | run against a shared, swagger-backed suite | | release sign-off | developer confidence | a dedicated final check, every time | | bug ownership | whoever happens to notice | tracked and routed to the team that owns the fix |

domi isn't just a mobile app. by the time i joined it also had a consumer web client, internal dashboards, and admin tools: four surfaces, mostly built by different corners of a small team. i own qa across all four from initial development through production, instead of each surface only getting whatever testing its own engineer had time for. that means knowing what "normal" looks like on four different surfaces well enough that a regression doesn't have to wait for a user, or a teammate, to report it. a bug in the admin tool doesn't feel as urgent as a crash on mobile, but it's still blocking someone on the team from doing their job, so it gets the same attention.

i plan and run test cases and regression cycles against the app's **swagger-documented api surface**, validating endpoints directly instead of only testing through the ui. that catches a class of bug (a response shape that changed, a status code nobody updated the client for) before it reaches a screen. bugs get tracked and routed to whichever team owns the fix, with repro steps specific enough that nobody has to ask "can you check this again?" i review requirements with product and engineering before code gets written too, looking for the edge case that reads fine in a ticket but breaks the moment a real user hits it.

release readiness sits with me: release notes, changelogs, and final sign-off before a build goes out, not a rubber stamp after the fact. once something ships, **sentry** is where i watch for what testing didn't catch, and **google search console** keeps the web app's actual search visibility honest instead of assumed. that's the difference between qa as a checklist and qa as something that actually holds. a bug that slips through still gets caught, just by monitoring instead of a user complaint.

as the product and team scaled, i helped put qa workflows and documentation in place that the team still uses for releases today. that part doesn't show up in a bug count, but it's the difference between one person catching everything and a process that keeps working after i've moved on to the next thing.

7:["$","main",null,{"className":"animate-fade-up","children":[["$","$L12",null,{"href":"/","className":"mb-8 inline-block text-base leading-6 text-gray transition-colors hover:text-text","children":"← Back"}],["$","h1",null,{"className":"text-[18px] leading-7 font-normal","children":"Work"}],["$","div",null,{"className":"mt-6","children":[["$","$L13","skyclad-ventures",{"item":{"slug":"skyclad-ventures","company":"Skyclad Ventures","role":"Product + Engineering","from":"May 2026","to":"Present","href":"$undefined","icon":"/media/skycladventures.jpeg","order":3,"description":"$undefined","stack":"$undefined","links":"$undefined","locked":true,"body":""},"divider":false,"showDescription":true}],["$","$L13","access-oxbridge",{"item":{"slug":"access-oxbridge","company":"Access Oxbridge","role":"Member","from":"Feb 2026","to":"Present","href":"$undefined","icon":"/media/stealthstartup.jpeg","order":2,"description":"$undefined","stack":"$undefined","links":"$undefined","locked":true,"body":""},"divider":true,"showDescription":true}],["$","$L13","digital-domi",{"item":{"slug":"digital-domi","company":"Digital Domi","role":"Founding QA Engineer","from":"Nov 2025","to":"Present","href":"$undefined","icon":"/media/domilabs.jpeg","order":1,"description":"own qa end to end for a mail app across mobile, web, dashboards, and admin tools, catching what breaks before a release does.","stack":"Swagger · Sentry · Google Search Console · Manual + Automated QA","links":[{"label":"Web","href":"https://digitaldomi.com/","icon":"globe"},{"label":"iOS","href":"https://apps.apple.com/us/app/digital-domi/id6738277048","icon":"apple"},{"label":"Android","href":"https://play.google.com/store/apps/details?id=com.domilabs.domi","icon":"android"}],"locked":false,"body":"$14"},"divider":true,"showDescription":true}],"$L15"]}]]}]