changes for pipeline and pathing
This commit is contained in:
117
RenderedAssets/CharlesNWyble-ConsultantInfoSheet.md
Normal file
117
RenderedAssets/CharlesNWyble-ConsultantInfoSheet.md
Normal file
@@ -0,0 +1,117 @@
|
||||
# Charles N Wyble Consultant Information Sheet
|
||||
|
||||
## Introduction
|
||||
|
||||
Hello,
|
||||
|
||||
Thank you very much for reaching out to me on this platform in regards to doing some consulting work for you !
|
||||
|
||||
I have been receiving a high number of inquiries and have developed a standardized response letter to help ensure
|
||||
alignment and save everyone time and to reduce back and forth emails/texts/calls in the early stages.
|
||||
|
||||
If you have any introductry questions/comments/concerns not covered by this document, please let me know and I'm happy to address them!
|
||||
|
||||
If you ask me something answered in this reply, I will not respond to you and will not move forward with the engagement, so please read it carefully!
|
||||
|
||||
## Re: share my ID over email
|
||||
|
||||
I am a US Citizen (by birth).
|
||||
|
||||
I am happy to get on a teams/zoom/google meet etc call and show my ID.
|
||||
|
||||
I WILL NOT share my (full or redacted) photo ID over email or any other electronic written communication. If that is a "requirement" then I have no interest in moving forward with this engagement and no further communication is necessary.
|
||||
|
||||
|
||||
## Re: professional references
|
||||
|
||||
I am happy to provide project/professional references once an engagement letter has been signed. The engagement letter has a contingency clause allowing the client to back out if the reference review doesn't meet their requirements.
|
||||
|
||||
I will NOT provide project/professional references up front. If that is a "requirement" then I have no interest in moving forward with this engagement and no further communication is necessary.
|
||||
|
||||
## Re: on-site work/travel/expenses/relocation
|
||||
|
||||
if the role is not able to be performed remotely and is not based in **** I will need to re-locate.
|
||||
|
||||
| Question | Answer |
|
||||
|-------------------------------------------|--------|
|
||||
| Am I open to relocation? | Yes |
|
||||
| Am I willing to re-locate at own expense? | No |
|
||||
| Am I open to up to 100% travel | Yes |
|
||||
|
||||
Please be aware that:
|
||||
|
||||
- I will **only re-locate at the employer expense**.
|
||||
- I will need **two weeks of time** to re-locate.
|
||||
- The net amount of the re-location benefit **MUST be at least ** to fully compensate me for the time/effort to re-locate.
|
||||
- The full re-location benefit **must be provided prior to the confirmed start date**.
|
||||
- I **will NOT** accept a reimbursement based re-location package.
|
||||
- I am happy to come onsite (at client expense (paid up front)) for training/orientation etc.
|
||||
|
||||
\pagebreak
|
||||
|
||||
## Rate Schedule
|
||||
|
||||
|
||||
- **** per hour(w2)
|
||||
- **** per hour (1099/corp to corp)
|
||||
|
||||
|
||||
### On-site/hybrid roles
|
||||
|
||||
Travel Time: 100.00 per hour, two hour minimum
|
||||
|
||||
- **** per hour(w2) or more
|
||||
- **** annually or more
|
||||
- **** per hour (1099/corp to corp) or more
|
||||
|
||||
In regards to compensation type, I am open to:
|
||||
|
||||
- w2
|
||||
- corp to corp (I have my own LLC)
|
||||
- 1099
|
||||
|
||||
If you have a rate for any of the compensation options above, send them all. I will pick which one works best for my situation and the opportunity.
|
||||
|
||||
If it's a different rate with/without benefits, send both.
|
||||
|
||||
If the above is in alignment with this opportunity, please feel free to send me an RTR with the best rate you can offer.
|
||||
|
||||
\pagebreak
|
||||
|
||||
## Details needed for submission
|
||||
|
||||
### My resume
|
||||
|
||||
[Download Candidate resume(format)](https://some.resume.somewhere/some-Resume.pdf)
|
||||
|
||||
I am happy to discuss and make edits to the resume content specific to the opportunity if you feel they are needed.
|
||||
|
||||
### Candidate details
|
||||
|
||||
Here are my complete candidate details for submission to the role.
|
||||
|
||||
| | Question | Answer |
|
||||
|----|---------------------------------------|-------------------------------------|
|
||||
| | Full name | |
|
||||
| | E-mail address | |
|
||||
| | Phone number | |
|
||||
| | Preferred form of contact | |
|
||||
| | Work authorization | |
|
||||
| | Are you employed presently? | |
|
||||
| | Current location | |
|
||||
| | Current timezone | |
|
||||
| | Timezones I can work in | |
|
||||
| | Availability to interview | |
|
||||
| | Availability to start | |
|
||||
| | Highest Education | |
|
||||
| | Graduated Year | |
|
||||
| dd | Name of school | |
|
||||
| | | |
|
||||
| | Location of school | |
|
||||
| | Linkedin Profile | () |
|
||||
| | Github Profile | () |
|
||||
| | Last project | |
|
||||
| | DOB | |
|
||||
| | Total IT/career experience | |
|
||||
| | Open to in-office/hybrid/remote | Yes |
|
||||
| | Any trips planned in next six months? | No |
|
Binary file not shown.
@@ -1,44 +0,0 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<meta name="description" content="Resume links for Charles Wyble">
|
||||
<meta name="author" content="Charles Wyble">
|
||||
<title>Charles N Wyble Consulting Profile Page</title>
|
||||
<link rel="stylesheet" href="styles.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<h1>Welcome to the Charles N Wyble Consulting Profile Page</h1>
|
||||
</header>
|
||||
|
||||
<section class="resume-links">
|
||||
<h2>Consulting profile documents for Charles N Wyble </h2>
|
||||
<ul>
|
||||
<li><a href="./CharlesNWyble-ConsultantProfile.pdf" target="_blank" class="resume-link">Charles N Wyble Consultant Profile (PDF)</a></li>
|
||||
<li><a href="./CharlesNWyble-ConsultantHistory.pdf" target="_blank" class="resume-link">Charles N Wyble Engagement History (PDF)</a></li>
|
||||
</ul>
|
||||
</section>
|
||||
|
||||
<section class="resume-links">
|
||||
<h2>Social media site profiles</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.linkedin.com/in/charles-wyble-412007337" target="_blank" class="resume-link">My linkedin profile</a></li>
|
||||
<li><a href="https://www.github.com/reachableceo" target="_blank" class="resume-link">My GitHub profile</a></li>
|
||||
</ul>
|
||||
</section>
|
||||
|
||||
<section class="resume-links">
|
||||
<h2>Source code for this site</h2>
|
||||
<ul>
|
||||
<li><a href="https://git.knownelement.com/ReachableCEO/profile-consulting.reachableceo.com" target="_blank" class="resume-link">Git repository for this site front end content.</a></li>
|
||||
<li><a href="https://git.knownelement.com/ReachableCEO/ReachableCEO-Profile-consulting" target="_blank" class="resume-link">Git repository for this site backend content.</a></li>
|
||||
</ul>
|
||||
</section>
|
||||
|
||||
<footer>
|
||||
<p>© 2025 ReachableCEO Enterprises LLC. All rights reserved.</p>
|
||||
</footer>
|
||||
</body>
|
||||
</html>
|
@@ -1,74 +0,0 @@
|
||||
/* Reset some default browser styles */
|
||||
* {
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
box-sizing: border-box;
|
||||
}
|
||||
|
||||
body {
|
||||
font-family: Arial, sans-serif;
|
||||
line-height: 1.6;
|
||||
background-color: #f4f4f4;
|
||||
color: #333;
|
||||
padding: 20px;
|
||||
}
|
||||
|
||||
/* Header Styling */
|
||||
header {
|
||||
background-color: #4CAF50;
|
||||
color: white;
|
||||
padding: 20px;
|
||||
text-align: center;
|
||||
border-radius: 8px;
|
||||
}
|
||||
|
||||
header h1 {
|
||||
font-size: 2.5em;
|
||||
}
|
||||
|
||||
header p {
|
||||
font-size: 1.2em;
|
||||
}
|
||||
|
||||
/* Section for resume links */
|
||||
.resume-links {
|
||||
margin-top: 40px;
|
||||
}
|
||||
|
||||
.resume-links h2 {
|
||||
font-size: 2em;
|
||||
margin-bottom: 20px;
|
||||
}
|
||||
|
||||
.resume-links ul {
|
||||
list-style: none;
|
||||
padding-left: 0;
|
||||
}
|
||||
|
||||
.resume-links li {
|
||||
margin: 10px 0;
|
||||
}
|
||||
|
||||
.resume-link {
|
||||
text-decoration: none;
|
||||
font-size: 1.1em;
|
||||
color: #4CAF50;
|
||||
border: 2px solid #4CAF50;
|
||||
padding: 10px 15px;
|
||||
border-radius: 5px;
|
||||
display: inline-block;
|
||||
transition: all 0.3s ease;
|
||||
}
|
||||
|
||||
.resume-link:hover {
|
||||
background-color: #4CAF50;
|
||||
color: white;
|
||||
}
|
||||
|
||||
/* Footer Styling */
|
||||
footer {
|
||||
margin-top: 50px;
|
||||
text-align: center;
|
||||
font-size: 1em;
|
||||
color: #777;
|
||||
}
|
@@ -1,7 +1,7 @@
|
||||
#############################################################################
|
||||
#SET THESE TWO VARIABLE CORRECTLY OR NOTHING WILL WORK
|
||||
export PipelineClientWorkingDir="~/ReachableCEO/ReachableCEO-OutreachMaterial/ReachableCEO-Profile-Consulting/local"
|
||||
export BUILD_OUTPUT_DIR="~/ReachableCEO/ReachableCEO-OutreachMaterial/ReachableCEO-Profile-Consulting/RenderedAssets/"
|
||||
export PipelineClientWorkingDir="/home/localuser/ReachableCEO/ReachableCEO-OutreachMaterial/ReachableCEO-Profile-Consulting/local/"
|
||||
export BUILD_OUTPUT_DIR="/home/localuser/ReachableCEO/ReachableCEO-OutreachMaterial/ReachableCEO-Profile-Consulting/RenderedAssets/"
|
||||
#SET THESE TWO VARIABLE CORRECTLY OR NOTHING WILL WORK
|
||||
#############################################################################
|
||||
|
||||
@@ -35,7 +35,7 @@ export ConsultantLogo="~/localuser/ReachableCEO/ReachableCEOOutreachMaterial/Rea
|
||||
export SourceCode="https://git.knownelement.com/reachableceo/ReachableCEO-Profile-Consulting"
|
||||
export URLCOLOR="blue"
|
||||
export PAGEBACKGROUND="$PipelineClientWorkingDir/build/background3.pdf"
|
||||
export PANDOC_TEMPLATE="eisvogel"
|
||||
export PANDOC_TEMPLATE="$PipelineClientWorkingDir/build/eisvogel.tex"
|
||||
|
||||
###########################
|
||||
# Yaml files used by pandoc
|
||||
|
1073
local/build/eisvogel.tex
Normal file
1073
local/build/eisvogel.tex
Normal file
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user