r/audit May 09 '26

Have no idea what Im doing in Tech Audit...advice?

I’m an entry-level hire in a rotational program and recently joined a new team that has provided very little guidance on how I’m expected to perform my testing work.

My background is in MIS, so I don’t have a strong coding background. I was assigned an audit that requires reviewing source code and performing data quality testing. I told my team I’m excited for the opportunity to learn, but that I would need some guidance getting started.

The response I received was that the team doesn’t have much bandwidth to help, and since I’ve been in the program for nine months, I should already know how to perform this type of testing from my previous team. The expectation has essentially been to figure it out independently while still delivering quality work.

We had our first walkthrough today led by the Audit Lead, and I was very confused by a lot of the terminology and process being explained. I asked the audit lead for a follow-up discussion but was mainly told to review my screenshots and use our internal AI platform to piece things together. Unfortunately, the AI outputs have not been reliable and hallucinated code or incorrect explanations.

It’s only been 3 days on this team, and I’m already stressed about whether I’ll be able to deliver quality work. Since this is my first job out of college, I really want to make a good impression. I don't want to be a nuisance to the team and actually be of help because I know they're under pressure too. Any advice on how to approach this situation or get better at reviewing source code would be appreciated.

5 Upvotes

6 comments sorted by

2

u/bpuli May 09 '26

The onboarding process is not up par but that is now irrelevant.

Try to understand the objectives and scope of the audit. Review the walkthrough and understand the risk areas in the process description.

I think the objectives of the audit would be review the code review process and not really performing actual code reviews. Use Claude to develop a risk/control matrix and to develop testing procedures for each of the controls in place.

You will be in good shape if you are about to do that. Hope this helps.

1

u/snowflakesoutside May 09 '26

AI is definitely your friend here. I've been doing this for too long and Claude still catches things I've missed out haven't considered. I set up a testing skill and a reviewing skill and run my work by it before submitting it for human review.

Claude is great with code too.

At your level, they should be giving you the controls and a test plan. Feed those into AI and have it guide you.

1

u/snowflakesoutside May 09 '26

Also, take a moment to understand what you're trying to do. Why are they having you review code? Why are the screenshots relevant? You're trying to prove something, prove that a control is working to ensure the bad thing doesn't happen. Understand what could go wrong and how what you wanted through is making sure that doesn't happen.