Please enable JavaScript.
Coggle requires JavaScript to display documents.
Paul Green and Tad Obeigly (Reliability (Measures (Data (Very useful to…
Paul Green and Tad Obeigly
Reliability
PIR Process
Adds value
Helps to increase focus on platform health
Measures
Dashboards
Worked for a while
Didn't seem to get much steerco traction
Thresholds
Examples
Deliberate addition of 0.5secs delay
Needed to send data to Omniture
Invalid job case
Workflow
When a user Hit Apply the Job would expire before the Apply page rendered
Extreme edge case
But bad for the Hirer and Candidate
CV Parsing (Juicy)
8.5 Seconds to parse a CV
Things they care about
Apply for Jobs
1st class citizen
Has to always work
Massive impacts if it fails
Affects things like App Completion rate
0.9% Correlation
Signed in visits
Apply completion rates
Data
Apply completion rates
Zendesk ticketing
Very useful to drive decision making
But on how the system is meeting targets
Not guiding the design of the UI
View at a high-level
Things just work
Job Apply is sancrosanct
Legacy systems
Not much is understood
Where do they fit in?
Why don't we retire products
Never seems to get done
e.g. Screen Jobs
Sales are critical to helping here
Security
SWS Tokens
Have been an issue
Hard to know where the issues are
Legacy systems don't help
Incidents
Customer impacts have to be minimal
Ideally they would never see
downtime or degradation
Especially for Job Apply
Advice to Tech
Understand the OKR's
Profile Apply
Auth0 (Candidate ID)
Interactions with Hirer
Relationships
Engagement
Be proactive
Especially around incident mitigation
Trust
This is important
Ryan has been great
Lots of mutual respect
Helps build good products
Make the right priority calls to Product and Tech
Balancing
80/20
Isn't always right
Sometimes you need more or less
Understanding trade-offs
i.e. What is the cost of not doing?
What drives Product in Connect
Customers must have a
great apply experience
This is fundamental
Where Seek has a distinct competitive advantage
Close the Loop priority
Strong Customer Focus
A/B Testing
Gives value
But only when you really know what the product end state is going to be
Prototyping
Code solutions are always the best way
Mockups and customer surveys can be quicker
Feedback is direct
Saves costly dev work