FinArchives

1. In plain English, please describe your current role and function.

​

I'm a Director of an Engineering Team at BlackRock, one of the world's largest financial companies. My team builds accounting software used internally to support the firm's financial operations.

​

2. On average, how is your time divided across quantitative work (e.g., financial analysis), qualitative work (research and writing), presentations (to investors, management, etc), and other tasks? Please describe what falls into ‘other.’

​

My work sits at the intersection of technology and finance. A large part of my time goes into understanding and translating functional/financial requirements into system architecture and design, then guiding my team to build solutions that are both scalable and compliant with financial and regulatory requirements. The rest of my time splits across hands-on technical work, cross-team coordination, and management responsibilities for my team.

 

3. Where did you attend college and what was your major/minor? Did you participate in any clubs in school or internships that you believe helped you decide what you wanted to pursue as your career? 

​

I attended Macquarie University in Sydney, where I earned a double degree in Actuarial Studies and Computer Science. I also completed an internship in the computer science field as part of my coursework, which helped confirm that software engineering — not actuarial work — was the path I wanted to pursue.

​

4. Do you have a graduate degree, and if so, what type?

​

I don't have a graduate degree. Within my team, some colleagues do hold a master's degree — often because it was the pathway they used to immigrate to and work in the US — but it isn't a requirement for advancement in my field.

 

5. What about certifications like as a chartered financial analyst, certified public accountant, or other similar certifications? 

​

Some professionals in my field hold certifications, but the majority don't. They're not required or generally expected for advancement in engineering roles.

 

6. What did you wish you had known in college that would have made your transition into the working world smoother? 

 

Keep an open mind — you won't necessarily get your first choice of path right, and that's okay. I actually switched from a law degree into computer science because I discovered a real passion for programming. Trusting that instinct and following what I was genuinely drawn to, rather than sticking with an original plan, ended up being one of the best decisions of my career.

 

7. How will the rising prominence of artificial intelligence (“AI”) impact your job and entry level jobs in your industry?

​

AI is fundamentally reshaping my industry. Work that used to take months can now be done in hours, and projects that once required large development teams can now be built by a small handful of people. This is flattening the traditional hierarchy — the gap between experienced and inexperienced engineers is narrowing, and fewer people are needed to produce the same or greater output.

​

8. What skills or qualities do you look for when hiring for an entry job level candidate?

​

I prioritize people who think well on their feet, learn quickly, and adapt easily to new and changing scenarios. Increasingly, I also look for fluency with AI tools — the ability to use AI efficiently to scale your own output and your team's output is becoming a fundamental skill, not a nice-to-have.

​

9. Is there any other information you would like to share that hasn’t been shared through the questions above?

 

Nothing further to add.