Hi, jplee3! I work in software engineering so hopefully this advice is helpful.
I would recommend reading
www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/. It's for "programmers," but much of it is applicable to any "knowledge" worker. For that matter, read anything by Patrick McKenzie! For your specific situation, I would recommend learning more about the rest of the business, if you haven't yet. Then you can write not about what you did, but what you accomplished for the business.
For example, have the regression tests that you have written prevented an engineer from deploying a massive mistake costing thousands of dollars? Does the QA team allow the company to advertise their products to bigger companies, or does it work in an industry where stability is essential? Are you in charge of a particular area of the product? If so, are there any reliability/bug metrics that have improved over the year you've been at the company? You can take ownership of that.
Does it seem like none of these apply? If so, I think you might be missing part of the picture: unless the company is really badly run (which is completely possible but unlikely to be the case for long), it wouldn't pay >100k (after payroll taxes) a year for someone that doesn't, in Patrick's words, increase revenue or reduce costs.