\ No newline at end of file
+404: This page could not be found
404
This page could not be found.
\ No newline at end of file
diff --git a/docs/David_Souther_Resume_2024-04-05.pdf b/docs/David_Souther_Resume_2024-04-05.pdf
new file mode 100644
index 0000000..b006d39
Binary files /dev/null and b/docs/David_Souther_Resume_2024-04-05.pdf differ
diff --git a/docs/_next/static/SBwn9sZOGEw6I_SY9crSO/_buildManifest.js b/docs/_next/static/vYmu67NJnpmnO7J4ltKsM/_buildManifest.js
similarity index 100%
rename from docs/_next/static/SBwn9sZOGEw6I_SY9crSO/_buildManifest.js
rename to docs/_next/static/vYmu67NJnpmnO7J4ltKsM/_buildManifest.js
diff --git a/docs/_next/static/SBwn9sZOGEw6I_SY9crSO/_ssgManifest.js b/docs/_next/static/vYmu67NJnpmnO7J4ltKsM/_ssgManifest.js
similarity index 100%
rename from docs/_next/static/SBwn9sZOGEw6I_SY9crSO/_ssgManifest.js
rename to docs/_next/static/vYmu67NJnpmnO7J4ltKsM/_ssgManifest.js
diff --git a/docs/blog.html b/docs/blog.html
index ba47518..1f91f00 100644
--- a/docs/blog.html
+++ b/docs/blog.html
@@ -1 +1 @@
-David Souther
\ No newline at end of file
diff --git a/docs/blog.txt b/docs/blog.txt
index 3e609f1..7343617 100644
--- a/docs/blog.txt
+++ b/docs/blog.txt
@@ -1,5 +1,5 @@
1:HL["/_next/static/css/8089f6746c126975.css",{"as":"style"}]
-0:["SBwn9sZOGEw6I_SY9crSO",[[["",{"children":["blog",{"children":["__PAGE__",{}]}]},"$undefined","$undefined",true],"$L2",[[["$","link","0",{"rel":"stylesheet","href":"/_next/static/css/8089f6746c126975.css","precedence":"next"}]],"$L3"]]]]
+0:["vYmu67NJnpmnO7J4ltKsM",[[["",{"children":["blog",{"children":["__PAGE__",{}]}]},"$undefined","$undefined",true],"$L2",[[["$","link","0",{"rel":"stylesheet","href":"/_next/static/css/8089f6746c126975.css","precedence":"next"}]],"$L3"]]]]
4:I{"id":7767,"chunks":["272:static/chunks/webpack-2089a3194a051c2b.js","971:static/chunks/fd9d1056-edf0048f965d11ef.js","596:static/chunks/596-e3269281f6a80cbc.js"],"name":"default","async":false}
5:I{"id":7920,"chunks":["272:static/chunks/webpack-2089a3194a051c2b.js","971:static/chunks/fd9d1056-edf0048f965d11ef.js","596:static/chunks/596-e3269281f6a80cbc.js"],"name":"default","async":false}
8:I{"id":6852,"chunks":["13:static/chunks/13-a14f4f8488530559.js","599:static/chunks/599-57c8542fa14d7dc7.js","185:static/chunks/app/layout-3e0733cba7c240b0.js"],"name":"","async":false}
diff --git a/docs/blog/behavioral_interviewing.html b/docs/blog/behavioral_interviewing.html
index c8e34a6..05bcfb2 100644
--- a/docs/blog/behavioral_interviewing.html
+++ b/docs/blog/behavioral_interviewing.html
@@ -158,4 +158,4 @@
STAR to XYZ(W)
What have we covered?
Organizations want to hire candidates who will bring value to their teams. A robust hiring process allows organizations to use data to ensure they’re meeting that goal. An industry standard piece of that hiring process is the behavioral interview. This interview explores a candidate’s past performance, so that the organization can infer their future behavior. Candidates should use the STAR method to prepare their personal stories to make it easy for their interviewers to make that decision.
In this article, we followed the STAR-format narratives through two example stories. We saw how a hiring manager or interviewer might follow up on specific points of the stories, and how the candidate may answer those questions. We learned how to research prospective companies to tailor the stories to their values specifically. And for the last mile, we took two quick side trips to think about what questions we might ask our interviewers, and how to turn the STAR stories into XYZ resume bullet points on our resumes.