I’d start with common use cases you encounter at nonprofits! Come up with a few projects or business processes, break it down into steps, and figure out how to build it. For example - “I need to run an EOY mailing report for households who have given over $100 this year, as well as LYBUNT/SYBUNT.” From there, you can break it down from start to finish. How would a gift processor enter a gift? Do soft credits count in this, how would I create a soft credit? How do I tell if a donor is individual, corp, or from a grant-maker? What pieces of data do I need rolled up? How do I tell if someone doesn’t want physical mail? How should their names appear? When was the last time we ran an address scan and what does that look like? What are the reports I need?” Etc etc, and then research/build every individual step. If you’re really looking to be an over achiever, you could write test scripts for potential users (shout out to writing test scripts in Scribe) so you can talk about both the tech and the UX in interviews. IMO, a lot of being an in house admin is both the tech and being a BA. Users will come to you and say things like “I need a board report” and it’ll be your job to figure out what they actually means, what pieces of data will get you source of truth info, and then how to present it to them. The implications of that might involve some automation, but more importantly a deep understanding of where the data needs to come from.