aboutsummaryrefslogtreecommitdiff
path: root/blog
diff options
context:
space:
mode:
authorXe Iaso <me@christine.website>2022-06-14 15:04:17 -0400
committerGitHub <noreply@github.com>2022-06-14 15:04:17 -0400
commitad6fba4c79e8b5ab08e2f0db8bc4087f03151f7f (patch)
tree9888fe24eb3ea35ea0f9b54af8723b4a000e6ad9 /blog
parent7541df778165b5a96da714256d011685b476abc0 (diff)
downloadxesite-ad6fba4c79e8b5ab08e2f0db8bc4087f03151f7f.tar.xz
xesite-ad6fba4c79e8b5ab08e2f0db8bc4087f03151f7f.zip
Add salary transparency page (#492)
* Move dhall data and types into `/dhall` folder * Reformat salary transparency data into Dhall * Wire up the old salary transparency page with a custom element * Wire up a new salary transparency page * Expose raw data as JSON * Make dhall types more portable * Remove gallery from the navbar * Make signal boost page point to the new data location * Add salary transparency page to the footer of the site * Add site update post for this Signed-off-by: Xe <me@xeiaso.net>
Diffstat (limited to 'blog')
-rw-r--r--blog/my-career-in-dates-titles-salaries-2019-03-14.markdown22
-rw-r--r--blog/site-update-salary-transparency.markdown42
2 files changed, 49 insertions, 15 deletions
diff --git a/blog/my-career-in-dates-titles-salaries-2019-03-14.markdown b/blog/my-career-in-dates-titles-salaries-2019-03-14.markdown
index b962ec9..97548ea 100644
--- a/blog/my-career-in-dates-titles-salaries-2019-03-14.markdown
+++ b/blog/my-career-in-dates-titles-salaries-2019-03-14.markdown
@@ -3,6 +3,12 @@ title: My Career So Far in Dates/Titles/Salaries
date: 2019-03-14
---
+<div class="warning"><xeblog-conv name="Cadey" mood="coffee">This post is
+outdated, see <a href="/salary-transparency">here</a> for more context on why
+this data is made public. The table on this page will be automatically updated
+to contain the data on my salary transparency page, but you should prefer that
+page over this one when possible.</xeblog-conv></div>
+
Let this be inspiration to whoever is afraid of trying, failing and being fired.
Every single one of these jobs has taught me lessons I've used daily in my
career.
@@ -26,21 +32,7 @@ might not want.
The following table is a history of my software career by title, date and salary
(company names are omitted).
-| Title | Start Date | End Date | Days Worked | Days Between Jobs | Salary | How I Left |
-|:----- |:---------- |:-------- |:----------- |:----------------- |:------ |:---------- |
-| Junior Systems Administrator | November 11, 2013 | January 06, 2014 | 56 days | n/a | $50,000/year | Terminated |
-| Software Engineering Intern | July 14, 2014 | August 27, 2014 | 44 days | 189 days | $35,000/year | Terminated |
-| Consultant | September 17, 2014 | October 15, 2014 | 28 days | 21 days | $90/hour | Contract Lapsed |
-| Consultant | October 27, 2014 | Feburary 9, 2015 | 105 days | 12 days | $90/hour | Contract Lapsed |
-| Site Reliability Engineer | March 30, 2015 | March 7, 2016 | 343 days | 49 days | $125,000/year | Demoted |
-| Systems Administrator | March 8, 2016 | April 1, 2016 | 24 days | 1 day | $105,000/year | Bad terms |
-| Member of Technical Staff | April 4, 2016 | August 3, 2016 | 121 days | 3 days | $135,000/year | Bad terms |
-| Software Engineer | August 24, 2016 | November 22, 2016 | 90 days | 21 days | $105,000/year | Terminated |
-| Consultant | Feburary 13, 2017 | November 13, 2017 | 273 days | 83 days | don't remember | Hired |
-| Senior Software Engineer | November 13, 2017 | March 8, 2019 | 480 days | 0 days | $150,000/year | Voulntary quit |
-| Senior Site Reliability Expert | May 6, 2019 | October 27, 2020 | 540 days | 48 days | CAD$115,000/year (about USD$ 80k and change) | Voluntary quit |
-| Software Designer | December 14, 2020 | *current* | n/a | n/a | CAD$135,000/year (about USD$ 105k and change) | raise |
-| Archmage of Infrastructure | March 1, 2022 | *current* | n/a | n/a | CAD$147,150/year (about USD$ 115k and change) | n/a |
+<xeblog-salary-history></xeblog-salary-history>
Even though I've been fired three times, I don't regret my career as it's been
thus far. I've been able to work on experimental technology integrating into
diff --git a/blog/site-update-salary-transparency.markdown b/blog/site-update-salary-transparency.markdown
new file mode 100644
index 0000000..c274cbc
--- /dev/null
+++ b/blog/site-update-salary-transparency.markdown
@@ -0,0 +1,42 @@
+---
+title: "Site Update: Salary Transparency Page Added"
+date: 2022-06-14
+author: Sephie
+---
+
+<xeblog-hero file="miku-dark-souls" prompt="hatsune miku, elden ring, dark souls, concept art, crowbar"></xeblog-hero>
+
+I have added a [salary transparency
+page](https://xeiaso.net/salary-transparency) to the blog. This page lists my
+salary for every job I've had in tech. I have had this data open to the public
+for years, but I feel this should be more prominently displayed on my website.
+
+As someone who has seen pay discrimination work in action first-hand, data is
+one of the ways that we can end this pointless hiding of information that leads
+to people being uninformed and hirt by their lack of knowledge. By laying my
+hand out in the open like this, I hope to ensure that people are better informed
+about how much money they can make, so that they can be paid equally for equal
+work.
+
+Raw, machine processable data (including employer names) is available at
+`/api/salary_transparency.json`. The JSON format is not stable. Do not treat it as
+such. I reserve the right to change the formatting or semantics of the JSON
+format at any time without warning. The raw data is in `/dhall/jobHistory.dhall`
+in my site's git repository.
+
+I have also taken the time to make sure that the [old
+post](https://xeiaso.net/blog/my-career-in-dates-titles-salaries-2019-03-14)
+maintains an up-to-date list. I do not want to break semantics on my website
+without a very good reason. By leaving the old post un-updated, I feel it would
+be doing a disservice to the community.
+
+Please consider publishing your salary data like this as well. By open,
+voulntary transparency we can help to end stigmas around discussing pay and help
+ensure that the next generations of people in tech are treated fairly. Stigmas
+thrive in darkness but die in the light of day. You can help end the stigma by
+playing your cards out in the open like this.
+
+It can be scary to do this; however every person that does it will make it that
+much more easy for the next person to do it.
+
+Don't be afraid.