gtag('config', 'G-6TW216G7W9', { 'user_id': wix.currentUser.id });
top of page

A Day in the Life of a Software Engineer at a Top FinTech Company

Aarya's day as a Software Engineer at a Fortune 100 FinTech company begins with a daily standup meeting to update team members and leadership on progress, goals, and roadblocks, followed by "solutioning" and clarifying business requirements with different teams to ensure proper delivery; the role "encompasses a lot" beyond this as there are coding and repository tasks as well as the need "to take in different hats and fill in the role whenever needed."

Software Engineering, Team Communication, Problem-Solving, Business Requirements, Daily Workflow

Advizer Information

Name

Job Title

Company

Undergrad

Grad Programs

Majors

Industries

Job Functions

Traits

Aarya Mathreja

Software Engineer

Fortune 100 FinTech Company

Arizona State University

Computer Science

Finance (Banking, Fintech, Investing), Technology

Product / Service / Software Development and Management

International Student, Immigrant, Worked 20+ Hours in School

Video Highlights

1. Daily stand-up meetings with team members, product managers, and directors to provide updates on progress, goals for the day, and overall objectives.

2. Solutioning and problem-solving to determine the correct way to implement solutions, often requiring collaboration and communication with different teams.

3. Writing code and pushing it to repositories, along with understanding business requirements to ensure the delivery of expected outcomes.

Transcript

Q3: Day in the life

A lot of the days, we start off with a meeting called a daily standup. Essentially, we work with all the team members, our product manager, and our directors. We give them an update on what we've been up to, what the goal is for today, and what we're working towards.

After that's done, I spend a lot of time just solutioning, trying to figure out if this is the correct way to implement a solution. Sometimes, we work on understanding the business requirements. A lot of the time goes back and forth between different teams, trying to understand if we are delivering what we are supposed to be delivering.

Other than that, I work on writing code and pushing it to our repositories. It encompasses a lot, and my job is to take on different hats and fill in the role whenever needed.

bottom of page