Hacker News new | ask | show | jobs
by jaredsohn 3273 days ago 

   var jobTitler = {
     subject: [
       "Screen", //100
       "Input", //400
       "Dialog", //900
       "Interface", //1600
       "Data", //2500
       "Big Data", //3600
       "Choice", //4900
       "System", //6400
       "Computation", //8100
    ], // 9
     position: [
       "Administrator", //1000
       "Technician", //4000
       "Engineer", //9000
       "Specialist", //16000
       "Architect", //25000
       "Executive", //36000
       ]
   }
https://pippinbarr.github.io/itisasifyouweredoingwork/js/dat...

I'm guessing Computation Executive might be the highest if it uses the position field. (Don't have time to see how this data gets used to set the title.)
1 comments
qbrass 3273 days ago
Top job is Chief Technical Officer, but there's a (guessing bounds error) bug that causes it to stop valuing your work when you're supposed to be promoted from Computational Administrator to Screen Technician.
link
Klockan 3273 days ago
> there's a bug that causes it to stop valuing your work when you're supposed to be promoted

They always say that...

link
qbrass 3273 days ago
the bug is line 1486 of ui-generators.js

  <    if (jobTitlePositionIndex >= jobTitle.position.length) {
  ---
  >    if (jobTitlePositionIndex >= jobTitler.position.length) {
link
justinjlynn 3273 days ago
Unanticipated glitch ceiling in the HR autopromotion system, clearly.
link