A Day In The Life Of A Staff R&D Application Engineer At Broadcom
A typical week for Rasheek, a Staff R&D Application Engineer at Broadcom, involves a Monday planning meeting with their manager to outline deliverables, followed by a flexible workday balancing immediate customer requests ("low hanging fruit") with larger projects like technical documentation for marketing and sales. This approach allows Rasheek to efficiently manage time, tackling urgent issues alongside longer-term goals while maintaining a reasonable work-life balance and incorporating schoolwork.
Project Management, Problem-Solving, Communication, Technical Documentation, Customer Support
Advizer Information
Name
Job Title
Company
Undergrad
Grad Programs
Majors
Industries
Job Functions
Traits
Rasheek Noor
Staff R&D Application Engineer
Broadcom
UC Davis
UCLA Anderson - MBA
Engineering - Electrical
Technology
Product / Service / Software Development and Management
None Applicable, Immigrant
Video Highlights
1. Rasheek's typical work week starts with a Monday meeting to plan deliverables.
2. He prioritizes tasks, tackling easier requests first before moving to larger projects, such as creating technical documents.
3. He balances his work with other commitments, such as schoolwork, demonstrating effective time management skills.
Transcript
What does a day in the life of an application engineer look like?
I wouldn't say there's a specific day that entails my entire average day. Instead, I'll talk about my week and how it's usually structured.
Usually, every Monday, I have a meeting with my manager. We discuss what projects and deliverables need to be completed by the end of the week or the coming week. I usually have this laid out in a one-on-one meeting where I write down what I've done and what I expect to do.
Typically, I get into work around 9:00 AM to 10:30 AM, depending on how busy I am in the morning. I usually start my day off by trying to keep it simple: get some coffee and answer some small, low-hanging fruit emails. Then, I typically look at my deliverables list to see what I need to get done.
I structure my day to act and do as much work as possible while being efficient. I try to leave at a reasonable time, between 5:00 PM and 6:30 PM.
Typically, I'll start my day by looking at any customer cases that need to be answered. If it's an easy customer case, say a customer has a question that's already been documented, I usually try to get rid of those first. After that, I start looking at some of my larger projects.
For instance, if I have a large technical document to complete so our marketing team can sell a product, or for account executives to sell a product to a specific customer, I'll typically start working on those for two to three hours between 1:00 PM and 4:00 PM.
After that, I tend to spend the tail end of my day looking at whether other low-hanging fruits have popped up. Or, if I'm in school, I might need to get schoolwork done as fast as possible or before a due date.