- Oct 2019
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up1
-
Resilient Eventing Framework (Pair)
Add more context on how this fulfills the behavior. (more context)
-
- Sep 2019
-
feedback.sandbox.indeed.net feedback.sandbox.indeed.netB17161
-
Wrote a blog post explaining the
init or impact?
-
-
feedback.sandbox.indeed.net feedback.sandbox.indeed.net
-
YWing
exec?
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up7
-
evaluation of trade-offs and capabilities
to go green, will need to improve evidence of the trade-offs considered. Can retroactively add this after the decision has been made.
-
2019-Q2
Agree with these but need to add context how this demonstrates the behavior. The reader will not have the familiarity I do with this work.
-
2019-Q2
Not clear how these demonstrate the behavior?
-
Completed
add context for coordination
-
Completed
Need context
-
Completed
Add Core?
-
2019-Q2
Add context for how this demonstrates deep knowledge
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up3
-
Summary
In addition to your review, take advantage of the "Resources" links at the bottom of this page for ideas. https://wiki.indeed.com/display/MONEY/Money+Quarterly+Review+Template
Feedback (https://feedback.sandbox.indeed.net/peerfeedback/summary/13355/2019-q2/) will often have good content to pull from
-
2019-Q2
Leverage https://hindsight.sandbox.indeed.net/#astreet to link to code reviews that you participated in for Q2. You had 124 upsource comments!
-
2019-Q2
Document the roles that you interacted with rather than the teams for this behavior
-
- Aug 2019
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up2
-
Evaluate and improve the performance of your team members with guidance from your manager
Any opportunities that surfaced as part of the mob?
The evidence from 2018-Q3 is particularly strong. When thinking of this behavior, what have you personally observed and worked to change or improve about another engineer?
-
Plan and guide the development work of a team of 1-3 engineers with coaching from your manager.
Consider adding more here related to defining stories, determining roadmap/ordering. Particularly for stories other engineers will implement.
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up3
-
2019-Q3
Q2?
-
2019-Q3
Did you mean to enter these as 2019-Q3? I'd expect these to be 2019-Q2.
Consider
"feedback quote" - <Person/Role>
for improved vertical real estate usage. Try the other way and see what you think. Not required.
-
2019-Q2
UAT kickoff?
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up3
-
Contribute substantially to design reviews for projects in your product area
participated versus contributed
-
Help other product teams to solve significant technical problems in your area of expertise
Less execution evidence and greater focus on the "significant technical problems" solved
-
Influence and drive technical direction for your team
seems light
-
- Jul 2019
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up1
-
Mentored/helped Brandon(TDM) to onboard the team and transit to TDM. I helped him understand Indeed's culture (Data Driven and Engineering Innovation encouraged) and TaCo practice.
Should limit this evidence to the highlighted portion and possible include bullet 1.
-
- Jun 2019
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up2
-
Prioritize the several modifications of Xactly
Add additional context on the suggestions and how they enabled the team mission?
-
Suggest ideas
What ideas did you suggest?
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up22
-
2019-Q2
Kafka may be best opportunity to expand on taking an existing technical implementation and using in a new way to apply tax.
As a SWE2, introducing technology used on other teams and applying it in the same way is more of outsized behavior for a SWE1. CJE and PWA are probably evidence that could go away.
-
esigned and built a deep knowledge base Tax Engine to Indeed US Resume Tax
Can you elaborate on how this was built and delivered incrementally?
Providing api, changing api based on feedback, delivering quotes, delivering Invoice integration, reporting on tax values.
-
We evaluated the time limit, performance measurement, A/B testing and etc. to finalize the PWA roadmap
Are you able to link evidence here?
-
Designed the system with datadog to measure the system performance Implemented a lot of application logs for QA/STG/PROD debug or general loggings <>a href="https://bugs.indeed.com/browse/TSDH-93">TSDH-93
These are good starts for Maintainability. Can you detail how these improve maintainability. Help finish the story for the user.
-
reduced ~100% of QA releasing preparation time
evidence needed
-
Plan and guide the development work of a team of 1-3 engineers with coaching from your manager.
Should discuss more in person. Much of this does not seem to directly contribute to the behavior.
-
reduced 74% WIP time
Most places (all?) in document where you reference WIP should probably be changed to Delivery Lead Time (DLT) or Cycle Time that represent time from In Progress to Done. WIP (Work In Progress) refers to how many things are being worked on at a given time.
-
Designed and built a deep knowledge base Tax Engine
Re-using the same Accomplishment (highlighted bullet) across so many Behaviors becomes a distraction. Consider placing the reader focus on the numbered context below as priority.
-
Coordinate work on initiatives that span multiple product teams
Add Resume/Tax work for 2019-Q2.
IU team support for kick-off.
-
Helped Danny to understand the business requirements from stakeholders making sense and give a guideline on defining the goals and estimate deadline (for example Vertex Integration ) )
Could surface this as the accomplishment for the quarter.
Add Danny's role to help reader follow along.
-
2019-Q1
Condense to the 3-4 most impactful demonstrations of this behavior.
Items that start out with "Executed", "Demo", and Automation, First Tech Responder support are probably candidates to remove.
-
2019-Q2
Link to code reviews an opportunity for evidence to include for this behavior.
Correct the evidence below and this has the ability to move to Inconsistently Meeting.
-
Plan and guide the development work of TaCo team with hands-on coaching and wiki documentation to improve team members work efficiency.
Need to link to evidence
-
Participate
Consistently report the activity quarter over quarter to improve readability
-
Done 4 whiteboard and 2 CR and lead 2 Progex with 100% consistency
Not evidence for this behavior
-
Helped IPA team(Jinfan Cheng) on the Empire building issue while she is onboarding the team Helped ITA (Brad Figer ) to rotate MABU key for security purpose
Better evidence for "Engage with others outside of your product team to make both teams successful."
-
Mentored Deserie to use her boxcar service to call the REST API of tax service
Better evidence for "Engage with others outside of your product team to make both teams successful."
-
2019-Q2
Opportunity to add the wiki information you helped establish for IU.
-
Contribute substantially to design reviews for projects in your product area
Were there 2019-Q2 designs to which you substantially participated?
-
2019-Q2
Need to improve context of building the tax engine for this behavior.
Kafka probably not a good example for this behavior.
Java Daemon PWA doesn't apply to this behavior as well.
-
pushed the direction to migrate the legacy boxcar API to REST API.
this is the evidence that needs to be brought up and expanded upon
-
2019-Q2
Add IU preparation support
-
- May 2019
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up7
-
Balance short term results against long-term investment and explain your choices
Need evidence of short-term versus long-term considerations. It likely exists in these examples but cannot be inferred.
Talk about hacks to get something out the door. Or refusal to do hacks to make the right decision for maintainability.
-
2019-Q1
good use of evidence. Continue this.
-
All of these issues were Production issues which meant putting aside development of Recognizing Revenue Recognition across multiple Entities and new entity work for France
This is a better example of "focus on tasks the provide the most business value" more than short vs long-term investments.
-
2019-Q1
evidence in Q1 like 2018Q4 (great evidence last quarter)?
-
2019-Q1
add detail to what you designed and delivered incrementally
-
2019-Q1
teaching FEAR to close EOM without your direct guidance?
-
Mentor new engineers on your team
maybe expand on detail for top 2-3 people what you taught them per quarter?
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up6
-
2019-Q1
evidence feels light for the behavior. likely needs more detail or clarifying context.
-
Helped adopt mob programming as a team process
more detail. What contributions/improvements did you help with?
-
2019-Q1
how did we layer functionality for kafka, Jest, and gotransverse? Evidence needs to call out incremental approach. these are things you did, but the evidence needs to be improved here. Giving you credit for now. ;^)
-
Worked with BA's, PM, and engineers
Not evidence. For each of these, describe a trade-off that took place.
-
Pair programmed to migrate tool from legacy infrastructure to mesos
What trade-offs did we make? spring config, properties, removing dependencies no longer needed, etc.
-
2019-Q1
Needs improvement to evidence.. Talk about how you structured the work, how you determined order, how you chose to work on something.
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up5
-
Executed loosely defined work item
Not evidence of this behavior.
-
outside your immediate team
Looking for evidence of mentorship outside the team. Consider removing the evidence of team members to keep this document short and focused on key accomplishments.
-
(a major bug)
I don't think this was a bug nor had the outcome suggested (less certain on the second part). The system was working as the prior requirements specified.
-
Manual Adjustment suppor
not evidence of this behavior
-
First Tech Responder of Co
Not evidence
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up3
-
Release of Wall pilot to customer service
provide additional detail, plz. link to stories.
-
Found root cause of internal event that was blocking end of month reporting of revenue
link to evidence? more specifics. is this also evidence for "Demonstrate deep knowledge"?
-
Demonstrate deep knowledge of the software systems in your product and how they interact with other products
Add evidence of the systems you've worked with, how the changes span multiple components across team code bases. Be more specific
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up6
-
as a checklist which is our highest priority at this moment.
link not working
-
Understand the desired outcome of your projects and consider multiple approaches to achieve those results
this behavior is part of Business Alignment and is looking for product ideas rather than technical decisions
-
Help PM to plan work to make sure we focus on the work which provides most business valueThe feedback from Parvaiz Daniel helps me better understand the technical nuances that are inputs to planning and sizing work towards a milestone delivery. This exercise helps paint a better picture if decision impacts short or long term. the feedback from Danny Giving clear guidance on time to implementation is a key driver of long term and s
Not clear this is evidence for "focus on tasks"
-
Wrote a design doc for a new feature - exclude existing Users and People, Wrote a design doc for Hierarchy write back, Wrote a design doc for sync hierarchy, Wrote a design doc for Commissions to payments and solicited feedback
not evidence for this behavior
-
from Danny Understanding the balance between outcomes, value-add and risk is very helpful. Having Daniel identify the different strategies we can take with deploying our code would be a value add. Helping product identify things like: Is this code a short term fix or a long term fix? Will we need to revisit this c
This doesn't help shore up this behavior.
-
from Danny Understanding the balance between outcomes, value-add and risk is very helpful. Having Daniel identify the different strategies we can take with d
Danny's comments don't clear map to this behavior
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up4
-
Incrementally validate investment in innovation and new technologies
Call out incremental delivery of GTV integration
-
Contribute substantially to design reviews for projects in your product area
2019-Q1 opportunity to call out design of event publisher/consumer?
-
Persuaded the team and helped re-architect
not clear this is evidence for this behavior
-
Grooming happens daily in the mob
improve specificity... what did you help prioritize/plan
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up2
-
[https://docs.google.com/document/d/1eg8CKVO5mhNAwCiGF2uBwmggU_9f8X7Lr7byemGxbn4/edit?usp=sharing
consider hyperlinking a clear text name here and below to improve readability
-
Translate technical work for Xactly into consumable understanding by the Sales OPS team
Consider bringing the context (translating technical work) into a top-level evidence. The UAT element seems far removed from this evidence.
-
-
feedback.sandbox.indeed.net feedback.sandbox.indeed.net
-
Incrementally validate investment in innovation and new technologies
hallmark and depends upon opportunity
-
Decompose work needed to achieve your team’s product and engineering goals
could also be technical decomposition (rather than story decomposition)
-
Work with product management to prioritize and plan your team’s work items
typically checked by other evidence
-
Evaluate and improve the performance of your team members with guidance from your manager.
peer feedback, design, code reviews, mentoring
-
Debug, solve, and prevent major production issues
demonstrate inclination to fix, doesn't have to work (skill)
-
Influence and drive technical direction for your team
prioritize technical goals design documentation
-
-
feedback.sandbox.indeed.net feedback.sandbox.indeed.net
-
mplemented new “Next Steps”
impact against key metric?
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up3
-
techical RoadMap
link to evidence
-
Debug, solve, and prevent major production issues
add any eom activities?
-
Development cycle time improvement plan
Not for this behavior
-
- Apr 2019
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up1
-
Identify engineering and product improvement opportunities for your team
Opportunity to add more context on things you specifically suggested? like datadog metric integration? For either team or product.
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up3
-
reakaway team (Worked with team to integrate with new technology stacks of Kafka and GoTransverse early in the development lifecycle to create additional confidence in future release schedule. Worked with team to develop tool with custom scripts for testing and debugging kafka queue )
capture thin horizontal slices rather than vertical. Ability to improve earlier evidence in similar manner?
-
Money Platform Improvements (Called meeting with Payments team and shared list of Platform improvement initiatives. Attended subsequent review/prioritization meeting and provided guidance. This contributed to Money T2 Objective: Platform health / Health metrics / SLOs.
not clear the evidence listed maps to the behavior without additional context
-
Plan and guide the development work of a team of 1-3 engineers with coaching from your manager
mob? designs? order of work? grooming
-
- Mar 2019
-
feedback.sandbox.indeed.net feedback.sandbox.indeed.net
-
inancial systems
part of echelon slt initiative
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up3
-
Regularly solicit feedback on your work items
light
-
Identify and resolve documentation gaps for your product area
light
-
Identify engineering and product improvement opportunities for your team
light
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up1
-
Observed and instigated communication
Change instigated to initiated? Add context for what you are soliciting feedback on.
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up4
-
Plan and guide the development work
write actionable stories that other team members execute on
-
sist others in balancing short term results and long term investment
Most of this evidence does not demonstrate short term versus long term trade-offs
-
Development cycle time improvement plan
provide evidence
-
imcreated
typo
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up1
-
Coordinate work on initiatives that span multiple product teams
cross-functional work with Payments and Security, commission calculator queue outage, business w/ intacct, etc.
-
- Feb 2019
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up14
-
Apply appropriate software design and architecture patterns
What design and architectural patterns did you use? Add needed context
-
Attended
Add context for what you learned and were able to introduce
-
Created a monitor for notification of when the Autobiller
was the monitor a new technology/tool?
-
Deliver high-quality, thoughtfully designed, and maintainable software components
Beyond execution, what makes things high-quality, thoughtfully designed, and maintainable?
-
Understand the desired outcome of your projects and consider multiple approaches to achieve those results
Similarly, need to document evidence of multiple approaches considered rather than what was done. Don't need a lot of examples, just 2-3 that are clearly articulated.
As part of the design for REVREG, what other approaches were considered beyond the path you chose?
-
Suggest ideas for how to achieve your team’s mission
improve evidence to tie to Behavior
-
Work with team lead and product managers to prioritize and plan your work items
Expand on grooming and stories you've created that were completed.
-
Execute loosely-defined work items, including defining precise requirements
multiple evidence that is not applicable and/or needing clarification to the Behavior
-
Contributed and attended GoTransverse Discovery Workshop
is this evidence?
-
Share your technical ideas, successes, and failures with other engineers
ensure all evidence clearly relates to this or has context that relates it.
-
Improve the productivity of your team
How does all of the evidence improve productivity?
-
Implemented Manual Charge interface
This is execution evidence... how were you sharing ideas?
-
Created a monitor for notification of when the Autobiller
Not seeing the clear link as evidence of sharing ideas
-
Regularly solicit feedback on your work items
link to code reviews created
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up8
-
make code more maintainable
How specifically? Also remove the "what" (adding new internal identifier)
-
Deliver high-quality, maintainable, and reusable software systems
unit testing, examples of testing notes, wiki documentation
-
Contribute substantially to design reviews for projects in your product area
link design reviews in which you participate (ex: naboo, revreg, etc)
-
Plan and guide the development work of a team of 1-3 engineers with coaching from your manager.
story decomposition and grooming
-
Evaluate and improve the performance of your team members with guidance from your manager
Related to process improvements above
-
internal event
link to evidence (event)
-
Debug, solve, and prevent major production issues
commission queue in Q4 from your quarterly review
-
Drive process improvements for your team
You have lots of evidence for this category to add
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up1
-
2018-Q3
This is an example of execution rather than the behavior listed. This behavior is about identifying alternatives. The refund example is a good one. Should add similar context to future evidence.
-
- Jan 2019
-
feedback.sandbox.indeed.net feedback.sandbox.indeed.net
-
Jefe R&D
live? impact? future? level of innov?
-
- Dec 2018
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up3
-
Regularly solicit feedback on your work items
link design docs, add prior quarter design info and code reviews
-
Regularly solicit feedback on your work items
add code reviews, design documentation links, you have a lot of evidence you're not taking advantage of.
-
Identify engineering and product improvement opportunities for your team
add links to jira stories you've created each quarter
Example I added Q3 with links to jira query. https://go.indeed.com/GLYWG6YYH
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up1
-
Transitioned a daemon
add hyperlinks to jira stories
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.netLevel Up5
-
Create User, People, and Account Assignment mappings
not evidence
-
Create User, People, and Account Assignment mappings and integrations for Xactly
not evidence of follow through
-
3 projects in production -Serenity, Serenity Imhotep Index Builder, Serenity Activity (Design the short term goal and long term goal for salesforce user control system. And set timeline to balance the short term goal and long term goal)
insufficient detail
-
evidence is the 15five of intern
you have the quote? they make good evidence
-
Tweak the outputs with Xactly requirements and quickly fixed bugs
hyperlink the collection of cast tickets
-
- Oct 2018
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.net
-
Follow through on the impact of your projects in production
have evidence of any changes to production configuration you've requested? Also, look for tickets where you are the creator and identified a production problem. (Bug, configuration, runtime resources, etc.)
-
Resolved
Did you identify the issue? If not, don't think this is evidence.
-
Focus on tasks that provide the most expected business value
add context for what you de-prioritized to focus on something more important. Q2 has some evidence. Let's add more perspective and this should be ready for Green.
-
Balance short term results against long-term investment and explain your choices
Need to provide more context on the short and long term decisions. I don't know there is enough evidence here to justify green. What were the short-term choices? What were the long-term choices that were passed over?
-
Understand the desired outcome of your projects and consider multiple approaches to achieve those results
should add CMGS analysis. Need to provide additional context on the multiple approaches considered where you are using evidence. Provide context with your evidence on the multiple approaches considered.
-
Remove Resume Subscriptions
Did this improve the code quality or resiliency? If so, how?
-
Applied Airflow
what made it the right choice?
-
Create
see behavior note
-
Proposed
what did you consider, what chose, why?
-
Introduced
This applies to category above. Also, what about this made it the right pattern?
-
Apply appropriate software design and architecture patterns
For you evidence, add context for how specifically the behavior applied appropriate design patterns. e.g.; What about the IHE design demonstrated appropriate patterns. The act of creating a design does not discuss what pattern you chose or why.
-
Shared my thoughts on using airflow
More appropriate in category above
-
Research and incorporate new technologies and tools into your team
A lot of the evidence here isn't directly attributable. Don't feel the need to add multiple points per quarter because it actually takes away from the important contributions. This category should be focused on new technologies and tools. Not new implementations that use existing tools and technologies.
-
delicate
delicate?
-
Independently design and deliver solutions that span multiple components
Sharpen the content here. Focus on designs and implementations you've been part of and how multiple components are part of the solution. wall (ui), malibu, revcel, revd, revreg, db, invoice service, etc. Ready to go green.
-
Resolved
relevant to this behavior?
-
Manage dependencies of your work items within your cross-functional team
highlight stories you've created outside of the team. DATA, SYSAD, MONEY, etc. to strengthen behavior.
-
Execute loosely-defined work items, including defining precise requirements
Opportunity to reuse stories created by quarter
-
Mentored
Not compelling evidence for "productivity"
-
Collaborate
Not compelling evidence for "productivity"
-
Create
Not compelling evidence for "productivity"
-
Initiated
Not compelling evidence for "productivity"
-
Design
IHE link doesn't work
-
Regularly solicit feedback on your work items
Code reviews created each quarter
-
2018-Q3
IHE Design doc?
-
Initiated
How is this follow through on production?
-
Self initialized
How demonstrates "broad knowledge"?
-
Introduced
How does this demonstrate "broad knowledge"?
-
Provided
Dates on link don't match quarter boundaries. I don't think the PR for BW code provides value.
-
- Aug 2018
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.net
-
Contributed 8 comments during biweekly retros (Shared happy/sad items with other members)
suggest remove?
-
Suggest ideas for how to achieve your team’s mission
context... how you helped prioritize work that met mission
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.net
-
Share your technical ideas, successes, and failures with other engineers
link code review comments, discussion documents, design docs, design reviews attended
-
Regularly solicit feedback on your work items
link code reviews created, design documents, and discussion documents
-
Follow through on the impact of your projects in production
backfill evidence to Q1 and link eom stories you've created
-
Identify engineering and product improvement opportunities for your team
link to stories you've created by quarter. provide some additional detail on each, but should be able to use hindsight query
-
Demonstrate broad knowledge of the software and systems in your team’s product area
Green when we update quarters and evidence
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.net
-
Improve the code quality and resiliency of the systems you work on
Add unit testing and link to evidence
-
Deliver high-quality, thoughtfully designed, and maintainable software components
link evidence
-
Focus on tasks that provide the most expected business value
look for evidence here that demonstrates prioritization of one thing over another rather than execution (built commission data extraction tools)
-
Manage dependencies of your work items within your cross-functional team
link to tickets you've created that span external teams
-
Independently design and deliver solutions that span multiple components
link to evidence
-
Execute loosely-defined work items, including defining precise requirements
link to stories you've created
-
Work with team lead and product managers to prioritize and plan your work items
Add evidence back to Q1 of creating and prioritizing work for LANN
-
Improve the productivity of your team
capture suggestions you've made around documentation and pair reviews
-
Share your technical ideas, successes, and failures with other engineers
Links to code review comments
-
Regularly solicit feedback on your work items
link code reviews you've created and design documentation
-
Identify and resolve documentation gaps for your product area
link to documentation you've created
-
Follow through on the impact of your projects in production
add links to stories you've created as a result of identifying production issues
-
variety of codebases
expand list of repos you've worked on
-
-
levelup.sandbox.indeed.net levelup.sandbox.indeed.net
-
Apply appropriate software design and architecture patterns
I don't want to lower from green to yellow, but the evidence here likely isn't sufficient to warrant green.
-
Provided ideas on Code Practice
specifics
-
Deliver high-quality, thoughtfully designed, and maintainable software components
links
-
Manage dependencies of your work items within your cross-functional team
little to no evidence for green... need to flush out and link. provide links to stories you've created for teams other than our own.
-
Understand the desired outcome of your projects and consider multiple approaches to achieve those results
link evidence
-
Identify engineering and product improvement opportunities for your team
weak evidence
-
Implemented the Transaction Transform & Loader which is the major part of Xactly Implemented the Hierarchy Transform & Loader which is the last part of Xactly HR
1) duplicate 2) this is more about defining future work than execution. https://wiki.indeed.com/display/EM/SWE+2 3) link jira stories you've created is a good example 4) want to ensure you have stories for the UAT work this quarter
-
Follow through on the impact of your projects in production
as a whole, weak evidence for this to be green.
-
Implemented the Hierarchy Transform & Loader which is the last part of Xactly HR
remove
-
Implemented the Transaction Transform & Loader which is the major part of Xactly Implemented the Hierarchy Transform & Loader which is the last part of Xactly HR
Not relevant. https://wiki.indeed.com/display/EM/SWE+2
For this quarter, the work you're doing to define metrics and track production is a great candidate
-
mplemented the Transaction Transform & Loader which is the major part of Xactly (Identified bugs of our ETL) Implemented the Hierarchy Transform & Loader which is the last part of Xactly HR
not relevant. Add code reviews created and any design documentation.
-
Mentor new engineers on your team
light
-
Share your technical ideas, successes, and failures with other engineers
links to evidence
-
peed up Xaclty UAT by providing three formats of test data(ETL, Incent and Xactly )
not clear how this is productivity improvement. improve wording?
-
Execute loosely-defined work items, including defining precise requirements
link to examples
-