Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 34 additions & 7 deletions template.md
Original file line number Diff line number Diff line change
@@ -1,41 +1,65 @@
# How I Work - [Your Name]
# How I Work - Kenny Luo

## 1. My Role and Responsibilities
- Brief description of your position
As a QA Developer, my job is to perform testing on every release version IBM Concert to catch and report bugs that the development team may have missed when developing new
features. Occasionally I assist developers with providing specific environments of the application as they debug Sev 1 issues.
- Key areas of focus and primary responsibilities
have working knowledge of the features of IBM Concert and keep up to date with new features that are coming in from development
have the knowledge on how to properly test each feature
- How my role contributes to the company's mission

my role contributes to the company’s mission by catching and reporting bugs in the application before the bugs are discovered by the customer. If bugs/issues were raised by the
customer, then that would be a poor customers experience. Thought this does happen sometimes, my job is to reduce this as much as possible.
## 2. My Core Values
- List 3-5 core values that guide your work and decision-making
Priority
Importance
- Brief explanation of how these values manifest in your daily work

While I believe everything is important, it's impossible to complete everything all at once. This is why it's important for me to have constant communication with my manager
to make understand what the priorities are for my work items.
## 3. Communication Preferences
- Preferred methods of communication (e.g., email, Slack, in-person)
slack
- Response times and availability
I usually respond ASAP during the standard 9-5
- Meeting preferences (frequency, duration, style)
I prefer meetings that are 30 minutes. If something needs to be discussed and a decision needs to be made, I think 30 minutes is a sweet spot. In my opinion, most things can be written via slack or email
- How to reach me in emergencies

slack or message my phone
## 4. Work Style
- Are you an early bird or night owl?
I prefer to be an early bird. this is when my brain is rested and sharp.
- Do you prefer collaborative or independent work?
i like a mix of both. Scheduling time to discuss projects and tasks as a group is good for clarifying any doubts. Having focus time to work on my tasks head down is also
valuable.
- How do you approach deadlines and time management?
I prioritize the tasks and dedicate time on items with the highest priority.
- Your approach to work-life integration

as busy as work gets, I need to make time for myself. this includes getting exercise, making time for my loved ones and friends. Around 45 minutes away from the desk during sunlight hours is what I enjoy.
## 5. Decision-Making Process
- How you typically approach problems
First I have to understand what the problem is before I can attempt to form a solution. Once I understand the root cause of a problem, then I start to tackle the problem and
come up with a solution.
- What information you need to make decisions
- How you involve others in decision-making
- Your risk tolerance and how you weigh trade-offs

## 6. Feedback and Growth
- How you prefer to receive feedback
Either in person or over a video call
- How often you like to give/receive feedback
maybe once a month?
- Areas you're currently focusing on for personal/professional growth
Personal: physical health. Doing intermitten fasting. get some form of exercise everydayProfessional: upskill on becomming a DevOps /Infrastructure Engineer.
- Your approach to continuous learning and development
dedicate time every week to upskill on topics that will get me to where I want to be in the future

## 7. Strengths and Potential Biases
- What are your key strengths?
Being able to learn and share knowledge with others
Strong communication skills
- Areas where you might need support or are working to improve
Technical eminence. As technology is always changing, it's a must for me to keep up to date with technolgy and my skills so i stay future proof
- Potential biases or blind spots you're aware of
- How you work to mitigate these biases

Expand All @@ -57,8 +81,11 @@

## 11. Experience and Skill Buckets
- Current Skills and Experiences
- List key areas of expertise
- Notable projects or achievements
- List key areas of expertise:
Prior experience with the cloud (Azure, AWS, GCP, IBM Cloud)
Bash, python, powershell scripting
- Notable projects or achievements:
successfully deploying Filenet operator on EKS for a client (Nelnet) https://ibm.ent.box.com/folder/176354914073?s=60zm8aww459wg5433yyqvegcup5mxgci
- Skills and Experiences I'm Developing
- Areas of focus for personal/professional growth
- New skills I'm currently learning or want to learn
Expand Down