Spaces:
Sleeping
Sleeping
Commit
·
169210f
1
Parent(s):
0c7d1d5
Upload project while keeping README and .gitattributes
Browse filesThis view is limited to 50 files because it contains too many changes.
See raw diff
- app.py +172 -0
- benefits/Unum_Help_at_hand.txt +13 -0
- benefits/cycle_to_work_scheme.txt +96 -0
- benefits/flexible_working.txt +18 -0
- benefits/getting_together.txt +11 -0
- benefits/help_to_buy_tech.txt +67 -0
- benefits/hybrid_working.txt +57 -0
- benefits/income_protection_and_life_insurance.txt +7 -0
- benefits/lunchers.txt +12 -0
- benefits/pension_scheme.txt +30 -0
- benefits/private_medical_insurance.txt +3 -0
- benefits/season_ticket_loan.txt +9 -0
- benefits/taking_holiday.txt +70 -0
- benefits/work_ready.txt +33 -0
- benefits/working_hours.txt +19 -0
- communities-of-practice/cloud-and-engineering/book-club/edge-value-driven-digital-transformation.txt +24 -0
- communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_got_our_eye_on.txt +9 -0
- communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_read.txt +5 -0
- communities-of-practice/cloud-and-engineering/book-club/library/books_we_recommend.txt +10 -0
- communities-of-practice/cloud-and-engineering/book-club/library/library.txt +5 -0
- communities-of-practice/cloud-and-engineering/book-club/welcome.txt +33 -0
- company/about.txt +34 -0
- company/welcome_pack.txt +69 -0
- guides/Relocation.txt +16 -0
- guides/buddy_guidance.txt +17 -0
- guides/chalet_time_policy.txt +168 -0
- guides/cloud/aws_certification_advice.txt +143 -0
- guides/cloud/aws_partner_certs.txt +75 -0
- guides/cloud/aws_partner_registration.txt +68 -0
- guides/cloud/aws_sandbox.txt +95 -0
- guides/cloud/azure_partner_certs.txt +32 -0
- guides/compensation/expenses.txt +32 -0
- guides/compensation/expenses/eyetest.txt +19 -0
- guides/compensation/salary_pay_slips.txt +9 -0
- guides/compensation/salary_reviews.txt +5 -0
- guides/contributing_to_the_handbook.txt +77 -0
- guides/equality-diversity-and-inclusion/README.txt +21 -0
- guides/equality-diversity-and-inclusion/about-di-community.txt +40 -0
- guides/equality-diversity-and-inclusion/about-open-and-closed-community.txt +45 -0
- guides/equality-diversity-and-inclusion/about-service-team.txt +38 -0
- guides/equality-diversity-and-inclusion/policy.txt +89 -0
- guides/exit_interviews.txt +14 -0
- guides/hiring/career_fairs.txt +46 -0
- guides/hiring/devops_pairing.txt +22 -0
- guides/hiring/pairing.txt +78 -0
- guides/hiring/rationale.txt +15 -0
- guides/hiring/referral_policy.txt +55 -0
- guides/it/Hardware.txt +49 -0
- guides/it/Miro.txt +44 -0
- guides/it/docker.txt +12 -0
app.py
ADDED
@@ -0,0 +1,172 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
import os
|
2 |
+
import glob
|
3 |
+
from pathlib import Path
|
4 |
+
from typing import List
|
5 |
+
from dotenv import load_dotenv
|
6 |
+
from openai import OpenAI
|
7 |
+
import gradio as gr
|
8 |
+
from pinecone import Pinecone, ServerlessSpec
|
9 |
+
|
10 |
+
# Load .env from the script's directory
|
11 |
+
env_path = Path(__file__).resolve().parent / '.env'
|
12 |
+
print("Loading .env from:", env_path)
|
13 |
+
load_dotenv(dotenv_path=env_path)
|
14 |
+
|
15 |
+
# Load environment variables
|
16 |
+
OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
|
17 |
+
PINECONE_API_KEY = os.getenv("PINECONE_API_KEY")
|
18 |
+
PINECONE_ENV = os.getenv("PINECONE_ENV")
|
19 |
+
INDEX_NAME = os.getenv("PINECONE_INDEX", "hr-handbook")
|
20 |
+
|
21 |
+
print("Loaded PINECONE_API_KEY:", PINECONE_API_KEY[:6] + "..." if PINECONE_API_KEY else "NOT FOUND")
|
22 |
+
print("Loaded OPENAI_API_KEY:", OPENAI_API_KEY[:6] + "..." if OPENAI_API_KEY else "NOT FOUND")
|
23 |
+
|
24 |
+
# Initialize OpenAI client
|
25 |
+
client = OpenAI(api_key=OPENAI_API_KEY)
|
26 |
+
|
27 |
+
# Initialize Pinecone (us-east-1)
|
28 |
+
def init_pinecone(index_name: str):
|
29 |
+
pc = Pinecone(api_key=PINECONE_API_KEY)
|
30 |
+
if index_name not in pc.list_indexes().names():
|
31 |
+
pc.create_index(
|
32 |
+
name=index_name,
|
33 |
+
dimension=1536,
|
34 |
+
metric="cosine",
|
35 |
+
spec=ServerlessSpec(
|
36 |
+
cloud="aws",
|
37 |
+
region="us-east-1" # ✅ using us-east-1 region
|
38 |
+
)
|
39 |
+
)
|
40 |
+
return pc.Index(index_name)
|
41 |
+
|
42 |
+
# Load text files
|
43 |
+
def load_documents(root_dir: str) -> List[dict]:
|
44 |
+
docs = []
|
45 |
+
for path in Path(root_dir).rglob("*.txt"):
|
46 |
+
category = path.parts[1] if len(path.parts) > 1 else "general"
|
47 |
+
with open(path, "r", encoding="utf-8", errors="ignore") as f:
|
48 |
+
content = f.read()
|
49 |
+
docs.append({"id": str(path), "text": content, "category": category})
|
50 |
+
return docs
|
51 |
+
|
52 |
+
# Embed and upsert to Pinecone
|
53 |
+
def index_documents(index, docs: List[dict]):
|
54 |
+
for batch_start in range(0, len(docs), 100):
|
55 |
+
batch = docs[batch_start:batch_start + 100]
|
56 |
+
ids = [doc["id"] for doc in batch]
|
57 |
+
texts = [doc["text"] for doc in batch]
|
58 |
+
embeddings = client.embeddings.create(input=texts, model="text-embedding-ada-002")
|
59 |
+
vectors = [
|
60 |
+
(id_, emb.embedding, {"category": doc["category"]})
|
61 |
+
for id_, emb, doc in zip(ids, embeddings.data, batch)
|
62 |
+
]
|
63 |
+
index.upsert(vectors)
|
64 |
+
|
65 |
+
# Query Pinecone
|
66 |
+
def retrieve(query: str, index, category: str = None, k: int = 5) -> List[str]:
|
67 |
+
embed = client.embeddings.create(input=[query], model="text-embedding-ada-002").data[0].embedding
|
68 |
+
kwargs = {"top_k": k, "include_metadata": True}
|
69 |
+
if category:
|
70 |
+
kwargs["filter"] = {"category": {"$eq": category}}
|
71 |
+
res = index.query(vector=embed, **kwargs)
|
72 |
+
return [m["metadata"]["text"] for m in res["matches"] if "text" in m["metadata"]]
|
73 |
+
|
74 |
+
# Generate final answer
|
75 |
+
def generate_answer(query: str, docs: List[str]) -> str:
|
76 |
+
system_prompt = (
|
77 |
+
"You are a helpful HR assistant. Use the provided context to answer the question.\n"
|
78 |
+
"If the answer is not contained in the context, reply that you don't know."
|
79 |
+
)
|
80 |
+
context = "\n\n".join(docs)
|
81 |
+
messages = [
|
82 |
+
{"role": "system", "content": system_prompt},
|
83 |
+
{"role": "user", "content": f"Context:\n{context}\n\nQuestion: {query}"}
|
84 |
+
]
|
85 |
+
response = client.chat.completions.create(model="gpt-3.5-turbo", messages=messages)
|
86 |
+
return response.choices[0].message.content.strip()
|
87 |
+
|
88 |
+
# Gradio logic
|
89 |
+
def answer_question(query: str, category: str):
|
90 |
+
docs = retrieve(query, pinecone_index, category)
|
91 |
+
return generate_answer(query, docs)
|
92 |
+
|
93 |
+
# Main logic
|
94 |
+
if __name__ == "__main__":
|
95 |
+
pinecone_index = init_pinecone(INDEX_NAME)
|
96 |
+
|
97 |
+
if not int(os.getenv("SKIP_INDEXING", "0")):
|
98 |
+
documents = load_documents(".")
|
99 |
+
index_documents(pinecone_index, documents)
|
100 |
+
|
101 |
+
categories = sorted({Path(p).parts[0] for p in glob.glob('*/*.txt')})
|
102 |
+
recommended = {
|
103 |
+
"all": [
|
104 |
+
"Where can I find benefits information?",
|
105 |
+
"How do I request time off?",
|
106 |
+
"What is TechScheme and how does it work?",
|
107 |
+
"What is chalet time?",
|
108 |
+
],
|
109 |
+
"benefits": [
|
110 |
+
"What does private medical insurance cover?",
|
111 |
+
"How do I join the pension scheme?",
|
112 |
+
"What is TechScheme and how does it work?",
|
113 |
+
],
|
114 |
+
"company": [
|
115 |
+
"What is the company's mission?",
|
116 |
+
"Where is the office located?",
|
117 |
+
"What is Made Tech's purpose?",
|
118 |
+
],
|
119 |
+
"guides": [
|
120 |
+
"How do I submit an expense?",
|
121 |
+
"Where is the hiring policy?",
|
122 |
+
"What is chalet time?",
|
123 |
+
"How can I contribute to the handbook?",
|
124 |
+
],
|
125 |
+
"roles": [
|
126 |
+
"What does a data scientist do?",
|
127 |
+
"How do career levels work?",
|
128 |
+
],
|
129 |
+
"communities-of-practice": [
|
130 |
+
"How can I join a community of practice?",
|
131 |
+
"When do CoPs meet?",
|
132 |
+
],
|
133 |
+
}
|
134 |
+
|
135 |
+
with gr.Blocks() as demo:
|
136 |
+
with gr.Row():
|
137 |
+
logo_path = Path(__file__).resolve().parent / "logo.jpeg"
|
138 |
+
logo_value = str(logo_path) if logo_path.exists() else None
|
139 |
+
gr.Image(value=logo_value, width=170, height=170, show_label=False)
|
140 |
+
gr.Markdown("<h1 style='text-align: center; width:100%'>HR Chatbot</h1>")
|
141 |
+
selected_category = gr.State("all")
|
142 |
+
|
143 |
+
with gr.Row():
|
144 |
+
category_buttons = []
|
145 |
+
for cat in ["all"] + categories:
|
146 |
+
btn = gr.Button(cat)
|
147 |
+
category_buttons.append(btn)
|
148 |
+
|
149 |
+
with gr.Row():
|
150 |
+
with gr.Column():
|
151 |
+
examples = gr.Dropdown(
|
152 |
+
choices=recommended["all"],
|
153 |
+
label="Recommended questions",
|
154 |
+
value=recommended["all"][0]
|
155 |
+
)
|
156 |
+
with gr.Column():
|
157 |
+
query = gr.Textbox(label="Ask a question")
|
158 |
+
submit = gr.Button("Submit")
|
159 |
+
answer = gr.Textbox(label="Answer")
|
160 |
+
|
161 |
+
def set_category(cat):
|
162 |
+
return cat, gr.update(choices=recommended.get(cat, recommended["all"]), value=recommended.get(cat, recommended["all"])[0])
|
163 |
+
|
164 |
+
for btn in category_buttons:
|
165 |
+
btn.click(lambda _, cat=btn.value: set_category(cat), inputs=None, outputs=[selected_category, examples])
|
166 |
+
|
167 |
+
examples.change(lambda q: q, inputs=examples, outputs=query)
|
168 |
+
|
169 |
+
submit.click(lambda q, cat: answer_question(q, None if cat == "all" else cat),
|
170 |
+
inputs=[query, selected_category], outputs=answer)
|
171 |
+
|
172 |
+
demo.launch()
|
benefits/Unum_Help_at_hand.txt
ADDED
@@ -0,0 +1,13 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Unum Help@hand
|
2 |
+
|
3 |
+
This benefit is available for all team members, providing you with fast, direct access to medical experts through one easy to use app.
|
4 |
+
The service provides the following:
|
5 |
+
|
6 |
+
- Access to remote GPs: An unlimited number of video consultations with UK based doctors.
|
7 |
+
- Mental Health support: Access to therapists (typically delivered by video consultation).
|
8 |
+
- Physiotherapy: Consultation and treatment with a network of physiotherapists.
|
9 |
+
- Medical second opinions: Access to UK based private consultants.
|
10 |
+
- Life, money, and wellbeing support: Advice on a range of life and work issues (see our [employee assistance section.](https://github.com/madetech/handbook/blob/main/guides/welfare/paid_counselling.md#employee-assistance))
|
11 |
+
- Access to a wellbeing calendar: Packed with resources, awareness dates, and support tools.
|
12 |
+
|
13 |
+
To get started, download the app and log in using the details found in your invitation email.
|
benefits/cycle_to_work_scheme.txt
ADDED
@@ -0,0 +1,96 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Cycle To Work
|
2 |
+
|
3 |
+
We take part in Cycle to Work as we wish to support those who wish to cycle to work whether it's for pleasure, aiming to be healthier, trying to be more green or any other reasons.
|
4 |
+
Made Tech have a limit of £2500 with CycleScheme which can be used to purchase a bike and any accessories you will need. You then pay a monthly 'salary sacrifice' to effectively 'hire' the bike and kit, over a 12 month period. Once this period has been completed you will be given options around owning your bike. The [FAQs section](https://help.cyclescheme.co.uk/article/42-what-is-an-ownership-fee) of their website has lots of information regarding these options.If you leave Made Tech before paying off the purchase, the balance will be taken from your final salary payment.
|
5 |
+
|
6 |
+
|
7 |
+
## Process for getting a bike through Cycle to Work:
|
8 |
+
|
9 |
+
### How do I use CycleScheme?
|
10 |
+
|
11 |
+
Start your application quickly and easily through the CycleScheme portal which you can access via Bob benefits. All you will need is the Employer Code which can be found in the information section of the Bob benefits CycleScheme tile. Once you have entered the Employee code go through the application process using your Payroll number (labelled Employee ID on your bob profile, or can be found on your payslip.)
|
12 |
+
|
13 |
+
Once you have completed the application it will be sent to a member of the people team to approve your request. Once approved you will receive your eCertificate which can then be exchanged for your gear in store or online!
|
14 |
+
|
15 |
+
If you request your product before the 18th of the month your deductions will begin the same month, however if you request your voucher on or after the 18th your deductions will begin the following month.
|
16 |
+
|
17 |
+
### Who are CycleScheme?
|
18 |
+
|
19 |
+
CycleScheme is a great employee benefit which offers the most cost-effective way to get new cycling equipment. The scheme is run via a salary sacrifice meaning you won’t pay tax or national insurance – this saves you between 25% and 39% on your new bike and accessories. This reduced cost is simply deducted out of your payslip over 12 months, so no need to worry about large one-off costs!
|
20 |
+
|
21 |
+
### Is CycleScheme the only provider I can utilise this scheme through?
|
22 |
+
|
23 |
+
Yes, as of 5th December 2022.
|
24 |
+
|
25 |
+
### What is the maximum value I can apply for?
|
26 |
+
The maximum value you can apply for is £2500.
|
27 |
+
|
28 |
+
### How do I know how much to apply for?
|
29 |
+
|
30 |
+
We recommend finding your perfect bike and accessories before applying so you know exactly what amount to apply for. This way you won’t apply for too much or too little – this is really important to get right because you cannot amend your application once you have been approved. You can also use the [Savings Calculator](https://www.cyclescheme.co.uk/calculator) to find out how much you will be saving on your package.
|
31 |
+
|
32 |
+
### How often can I use the Cycle to Work scheme?
|
33 |
+
|
34 |
+
You can only be in one agreement at a time, the next time you will be able to make an application will be once you've repaid your instalments. So if you are going to be paying back over a year, it would be best to think about your cycling needs over the whole year, not just right now.
|
35 |
+
|
36 |
+
### Can I use Cycle to Work to get a bike for a family member, partner or friend?
|
37 |
+
|
38 |
+
No, the items you select must be for yourself.
|
39 |
+
|
40 |
+
### I already own a bike – can I still apply?
|
41 |
+
|
42 |
+
Of course! You may want to get a whole new upgrade, or a second bicycle for a different season or terrain. Just want accessories? Using the Cycle to Work scheme for accessories only is a very popular option for employees who already own a bicycle and just want to upgrade the rest of their equipment!
|
43 |
+
|
44 |
+
### Where can I get my bike and accessories from?
|
45 |
+
|
46 |
+
You can shop in-store or online, with over 2,600 CycleScheme retailers to choose from across the UK.
|
47 |
+
|
48 |
+
### Do I have to get a bike? Can I just get accessories?
|
49 |
+
|
50 |
+
Yes! You are more than welcome to just get cycle accessories. Treat yourself to a new helmet, clothing for every season, locks, lights and much more!
|
51 |
+
|
52 |
+
|
53 |
+
### What is an eCertificate?
|
54 |
+
|
55 |
+
An eCertiificate is the voucher you will be given once your application is approved. This is how you can purchase your bike or any equipment or accessories.
|
56 |
+
|
57 |
+
### Do I have to spend my eCertificate all at once?
|
58 |
+
|
59 |
+
Although you do not have to use your eCertificate all at once, we would advise that you do as your salary sacrifice amount will be according to the total amount you applied for, even if you spend less.
|
60 |
+
|
61 |
+
### Can I amend my application once I've applied?
|
62 |
+
|
63 |
+
Technically once you have submitted your application, you are unable to amend it. What you would need to do is cancel your application and reapply for your new amount.
|
64 |
+
|
65 |
+
### Do I have to cycle to work every day?
|
66 |
+
No, the government guidelines state that you should use your bike and accessories for commuting for at least 50% of its usage however you do not have to log your bikes mileage and we thoroughly encourage you to use your bike in your spare time.
|
67 |
+
|
68 |
+
### What happens if my bike gets damaged or stolen?
|
69 |
+
|
70 |
+
This one’s down to you! Looking after the bike is your responsibility, so we encourage you to purchase insurance. CycleScheme offers insurance options with Bikmo through their website.
|
71 |
+
|
72 |
+
### What happens to the bike at the end of the scheme?
|
73 |
+
|
74 |
+
Once your hire period has come to an end, CycleScheme team will get in touch to discuss your options (Own it later, Own it now and Return.) The [FAQs section](https://help.cyclescheme.co.uk/article/42-what-is-an-ownership-fee) of their website has lots of information regarding these options.
|
75 |
+
|
76 |
+
### Who owns the bike?
|
77 |
+
|
78 |
+
CycleScheme are the legal owners of the bike from the start of the hire period, the bike is leased to you. Once you reach the end of your initial 12 month hire period, ownership of the bike will then automatically be transferred to you depending on which ownership option you choose at the end of your initial agreement. Should you not wish to purchase the equipment you can continue to loan it until it is 4 years old at which point the bike automatically becomes yours (unless you wish to return it.)
|
79 |
+
|
80 |
+
|
81 |
+
### What are 'hire periods' and 'hire agreements'?
|
82 |
+
|
83 |
+
Your hire agreement is essentially the ‘terms and conditions’ of CycleScheme, which you will sign when you apply. Your hire period is the period that this agreement is valid for - this is also the period in which you will pay your salary sacrifice (12 months.)
|
84 |
+
|
85 |
+
### What if I leave my company within my Hire Agreement?
|
86 |
+
|
87 |
+
We completely understand that life can be unpredictable. If you were to leave your company or be made redundant in your hire period, the remaining gross balance would simply be deducted from your last payslip.
|
88 |
+
|
89 |
+
### How does Cycle to Work differ to Interest Free Finance that some retailers offer?
|
90 |
+
|
91 |
+
Through CycleScheme, you will save between 25% and 39% through tax and national insurance and the cost will simply be deducted from your payslip. You’ll also get loads of free extras, discounts and benefits on the CycleScheme website which you would not get on Interest Free Finance! For example, a bike costing £1000 could cost as little as £56.60 a month over 12 months on CycleScheme - compared to £83.33 through Interest Free Finance.
|
92 |
+
|
93 |
+
### Once I put in my application via the CycleScheme website how long will it take to process my application?
|
94 |
+
|
95 |
+
We will review any new requests every Friday afternoon so you shouldnt be waiting for more than one week for approval from Made Tech.
|
96 |
+
|
benefits/flexible_working.txt
ADDED
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Flexible Working
|
2 |
+
|
3 |
+
Generally, we work Monday to Friday in all roles. But for a variety of reasons, people may need to work fewer than 5 days per week.
|
4 |
+
We try to accommodate for this when we can. But because of client considerations, and to manage any other business impact, we have a process for requesting a flexible working pattern.
|
5 |
+
|
6 |
+
## Some things to consider
|
7 |
+
|
8 |
+
**Notice** - Please provide as much notice as you can - ideally 2 months or more - for a request to change your working patterns. It helps us make sure our client commitments can continue to be met.
|
9 |
+
|
10 |
+
**Project and scheduling needs** - As project and scheduling needs change, we'll do our best to accommodate flexible working patterns. But there may be very occasional times when we need to discuss temporary or permanent changes to a flexible working schedule. We'll try to give you as much notice as we can of any possible change.
|
11 |
+
|
12 |
+
**Getting paid** - Your salary and any bonus payments will be pro-rated as a percentage of a 5 day week. For example, if you work 4 out of 5 days, your salary and any bonus would be reduced by 20%.
|
13 |
+
|
14 |
+
**Pension** - As your salary is reduced, so too will your individual and employer pension contributions. You may like to increase your individual contribution to account for this.
|
15 |
+
|
16 |
+
**Trial period** - If you request a flexible working pattern, there’s usually a trial period to assess the feasibility before any final change is confirmed.
|
17 |
+
|
18 |
+
**Reduced working hours** - We can only support reduced working hours and not compressed hours or other patterns (such as annualised hours etc).
|
benefits/getting_together.txt
ADDED
@@ -0,0 +1,11 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Getting together as a team and company
|
2 |
+
|
3 |
+
## Our monthly meet ups
|
4 |
+
Our Social Committee is made up of reps for each region, who are in charge of organising monthly regional socials. These socials will be low-key, often office based activities (don’t worry, drinks & snacks/dinner will be provided!)The intention is to facilitate more frequent gatherings, allowing us to stay connected on a regular basis 🍕🍜
|
5 |
+
|
6 |
+
If you have any suggestions DM one of the reps for your region, and if you would like to get involved reach out to the People Team!
|
7 |
+
|
8 |
+
## Our Winter & Summer parties
|
9 |
+
Every year we hold a larger winter and summer event to celebrate our achievements over the last 6 months and to get together to socialise, network and mingle with our peers and wider team.
|
10 |
+
|
11 |
+
_As drinking is exclusionary in nature to those who don't like or can't be around alcohol we make efforts to make sure it's not the centre of our culture whilst at the same time acknowledging it's important to some._
|
benefits/help_to_buy_tech.txt
ADDED
@@ -0,0 +1,67 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Help to buy Tech with TechScheme
|
2 |
+
|
3 |
+
We've signed up to TechScheme which is accessible through Bob Benefits to make it easier and more affordable for our team to buy the latest tech gadgets.
|
4 |
+
|
5 |
+
TechScheme lets you get the latest tech, such as Smart Phones, Smart Watches and/or Game Consoles, up to a maximum value of £2,000. You apply for an eCertificate worth the value of your shopping basket - so decide what you want to buy before you apply for this perk. You then repay this amount via your salary across 12 months. Powered by Currys to allow you to choose from thousands of products, and take advantage of the sales! Your voucher is valid for up to two years, so no need to spend it all at once!
|
6 |
+
|
7 |
+
You can now shop at Ikea for all your furtiture, flat pack & meatball needs! The process works the exact same, simply select Ikea as your chosen retailer at check out.
|
8 |
+
|
9 |
+
## TechScheme FAQs
|
10 |
+
|
11 |
+
### 1. How do I apply?
|
12 |
+
|
13 |
+
Head to the TechScheme website which you can access through the Help to buy tech square on Bob Benefits, enter the Employer code (also found in the Tech square on Bob benefits) and complete the application. You will also need your payroll number (labelled Employee ID on your bob profile, or can also be found on your payslip.)
|
14 |
+
|
15 |
+
Once you have completed the application it will be sent to a member of the people team to approve your request. Once approved you will receive your eCertificate which can then be exchanged for your shiny new tech in store or online!
|
16 |
+
|
17 |
+
|
18 |
+
### 2. I've applied when will I get the eCertificate?
|
19 |
+
|
20 |
+
We will review all new applications every Friday afternoon, so you shouldnt have to wait longer than one week for Made Tech approval. Once we have approved and paid for your voucher you will then be sent this automatically from TechScheme.
|
21 |
+
|
22 |
+
### 3. What is TechScheme?
|
23 |
+
|
24 |
+
TechScheme allows you to buy the latest technology through your payroll. Whatever the product you purchase, you can pay back the cost over a set period of time (12 months), interest free and with no credit checks required, it's so simple.
|
25 |
+
|
26 |
+
### 4. How much will the product(s) cost me?
|
27 |
+
|
28 |
+
Your net pay will be reduced by a monthly amount equivalent to the total cost of the product(s) that you've chosen. This will be spread evenly over the selected period of time.
|
29 |
+
|
30 |
+
If you request your product before the 18th of the month your deductions will begin the same month, however if you request your voucher on or after the 18th your deductions will begin the following month.
|
31 |
+
|
32 |
+
### 5. Hold on I'm not buying the actual product?
|
33 |
+
|
34 |
+
No, you're receiving an Instant eGift Card that you can spend online or in-store at any Currys PC World. This enables you to get total flexibility just in case something changes in-store and you can change your mind.
|
35 |
+
|
36 |
+
### 6. Where can I get my Product?
|
37 |
+
|
38 |
+
From Currys PC World network of over 450 stores, which have the largest selection of technology in the UK including all the top brand products. You can purchase online at www.currys.co.uk or www.pcworld.co.uk too.
|
39 |
+
|
40 |
+
### 7. Can I spend more on top of what I buy on TechScheme?
|
41 |
+
|
42 |
+
Yes, of course. You can use your TechScheme voucher to purchase the majority of the product and then pay for the rest!
|
43 |
+
|
44 |
+
### 8. Who owns the product?
|
45 |
+
|
46 |
+
As this is not a tax efficient salary sacrifice scheme, you will wholly own the product from the moment of purchase.
|
47 |
+
|
48 |
+
### 9. Can I select more than one product?
|
49 |
+
|
50 |
+
Yes, your spend limit is £2000, but it's up to you how use that amount all at once or over a few smaller products.
|
51 |
+
|
52 |
+
### 10. What happens if I leave before the end of the payment period?
|
53 |
+
|
54 |
+
If you leave before the end of the payment period, you must pay back the outstanding amount and this will deducted from your final net pay.
|
55 |
+
|
56 |
+
### 11. What if my product gets stolen or damaged?
|
57 |
+
|
58 |
+
It's recommended you obtain separate insurance, or check your product is covered under your home contents insurance policy. Payments from your salary will not stop or be suspended due to loss or damage of the product.
|
59 |
+
|
60 |
+
### 12. What happens if my product breaks?
|
61 |
+
|
62 |
+
If your product breaks you need to get in contact with Currys PC World: Within 30 days of purchase or delivery: You always have the option of an exchange or refund if the fault occurs within 30-days of purchase or delivery. You can return it to the store or arrange a pick up by calling the Knowhow contact centre on 0344 561 1234, or by emailing ([email protected]) Extended range large kitchen appliances cannot be returned to one of Currys PC World stores, please call Knowhow contact centre on 0344 561 1234. Returns and exchanges can only be processed with proof of purchase. This can be the sales receipt, a bank statement or an online sales invoice. Please provide your Currys PC World order numbers when you return a product. Within each product’s guarantee period (normally 12 months from purchase or delivery), Currys PC World offer you a prompt repair service. In all cases, Currys PC World reserves the right to inspect the product and verify the fault. Please call the Knowhow contact centre on 0344 561 1234 or emailing ([email protected]) to arrange a collection. To speed up the process, please have your order number to hand before calling. Currys do not cover faults caused by accident, neglect, misuse or normal wear and tear.
|
63 |
+
|
64 |
+
### 13. How do I request a refund?
|
65 |
+
|
66 |
+
You have a right to withdraw from the benefit and cancel the Funding Plan at any time prior to, and within 14 calendar days of, receipt of an email containing the Redemption Code, such 14 days to begin on the day after receipt of the said Redemption Code (“Cooling Off Period”). If You redeem any of Your Redemption Codes with one of the Authorised Retailers (online or in-store) at any time during the Cooling Off Period You will no longer be able to cancel this Funding Plan.
|
67 |
+
If You wish to cancel the Funding Plan in accordance with “Your Rights” described above You need to send written confirmation of Your request to cancel to Techscheme via email at [email protected], or by post to Techscheme, PO Box 3809, BATH, BA1 1WX.
|
benefits/hybrid_working.txt
ADDED
@@ -0,0 +1,57 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Hybrid Working
|
2 |
+
|
3 |
+
We believe in people working in the best way for our teams and clients - this may sometimes be in person, remotely at home, from a coffee shop or outside of the UK.
|
4 |
+
|
5 |
+
The best outcomes are delivered by blending different ways and places of work - and we want to empower our teams to make the best decisions for their teams, projects and relationships.
|
6 |
+
|
7 |
+
|
8 |
+
### Made Tech offices
|
9 |
+
As part of our Hybrid Working policy, we want to encourage organic purposeful face-to-face sessions that help build relationships and stronger teams, which in turn deliver even better work for our teams and clients. Bringing people together regularly creates more opportunities for relationships to be built within teams, across Made Tech, and with our clients and partners.
|
10 |
+
|
11 |
+
For our group-facing team members, and our client-facing team members that do not have a client onsite requirement, we encourage 2 - 3 days a month in a Made Tech office for purpose-driven activities that will help drive valuable outputs and relationship building.
|
12 |
+
|
13 |
+
### Client office
|
14 |
+
Each of our clients will have their own requirements for Made Tech team members to work from their offices. All client-facing team members will be required to be able to travel to their assigned client office. We expect client-facing teams to create regular opportunities to come together to collaborate and where necessary to align with a client’s specific needs
|
15 |
+
|
16 |
+
### Exceptional Circumstances
|
17 |
+
There may be circumstances where our team members may not be able to attend sites or our offices or may need additional support to be able to do so. We encourage you to reach out to your Line Manager and/or your People Partner to discuss how we can best support you.
|
18 |
+
You can find more information about hybrid working within our Hybrid Working Policy, and the supporting policies such as TOIL, Project Assignments and Reasonable Adjustments Passport - which you view with your Made Tech account.
|
19 |
+
|
20 |
+
### Hybrid working guidance
|
21 |
+
- Check that you're not needed on-site by a client or your team
|
22 |
+
- Ensure you're available for your team ceremonies as normal and are able to dial in without interruption
|
23 |
+
- Be a good Slack citizen and check in regularly and visibly with your team throughout the working day in public channels
|
24 |
+
- Ensure you're not expected for any in-person meetings or sessions
|
25 |
+
|
26 |
+
### Secure Remote Working
|
27 |
+
When remote working, and when onsite with a client, it is important to pay close attention to these security guidelines in addition to your normal security practices:
|
28 |
+
- If you are in a public place, such as a coffee shop, make sure you are handling any sensitive data responsibly and securely. Can you be overseen? Is your connection secure?
|
29 |
+
- Ensure any work-related conversations can’t be overheard. If that’s not possible, try to talk in general terms, and without specific details such as names or clients
|
30 |
+
|
31 |
+
### Working abroad
|
32 |
+
Where possible we will support short-term/ad hoc remote working from outside of the UK (for example if someone wanted to travel and work from abroad for a few weeks during the year and this was viable).
|
33 |
+
Whilst we will always try to support this, in some cases this may not be feasible.
|
34 |
+
|
35 |
+
When considering this option, you will need to:
|
36 |
+
- Discuss with your team (as in some cases, client requirements may not support this)
|
37 |
+
- Inform your line manager
|
38 |
+
- Let the People team know
|
39 |
+
- Ensure you're familiar with our security requirements
|
40 |
+
|
41 |
+
Some things to be aware of when thinking about working abroad:
|
42 |
+
- Client laptops - you are not able to take a client laptop outside of the UK.
|
43 |
+
- VPN - you must use the VPN to access Made Tech systems.
|
44 |
+
- Our IT support - We’re only able to provide support during UK working hours. If there is a major issue with the laptop (or other equipment, such as your charger) you would be responsible for ensuring you are able to continue working until you return to the UK.
|
45 |
+
|
46 |
+
If you remain uncertain or you have any additional questions, please reach out to the Compliance team, Ops, or People.
|
47 |
+
|
48 |
+
### Travel expenses
|
49 |
+
Team members may expense travel to client sites that are outside of their regional office. Travel to and from your allocated office & within your regional office area is not able to be expensed.
|
50 |
+
|
51 |
+
#### What is part of my regional office?
|
52 |
+
- London - within the M25
|
53 |
+
- Manchester - all Manchester postcodes (M postcodes)
|
54 |
+
- Bristol - within a 25KM radius of Bristol city centre
|
55 |
+
- Swansea - within a 25KM radius of Swansea city centre
|
56 |
+
|
57 |
+
You will be able to use our TravelPerks platform to book trains and hotels for your journey. For more information on when and how to use this take a look at the [Travel Perk doc](https://docs.google.com/document/d/1cgASgYU9rjF-y7pa9gJ9FJ8HCBP6M3ntmdgeLZclSPo/edit) and/or head over to our TravelPerks slack channel.
|
benefits/income_protection_and_life_insurance.txt
ADDED
@@ -0,0 +1,7 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Income Protection Cover
|
2 |
+
|
3 |
+
We offer income protection cover for all Made Tech employees. If you are unable to work due to serious illness or disability this policy will pay you 75% of your salary for up to 2 years. The income protection scheme defers for the first 13 weeks of a colleague's absence and an assessment of the absence being eligible for income protection scheme will be taken by the scheme provider.
|
4 |
+
|
5 |
+
# Life Insurance
|
6 |
+
|
7 |
+
We offer life insurance cover for all company employees which will financially support our loved ones following death. This policy pays out 4x your annual salary.
|
benefits/lunchers.txt
ADDED
@@ -0,0 +1,12 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Lunchers
|
2 |
+
|
3 |
+
Once a month in each office we select 5 people to have lunch together on us! Order from your favoriute restaurant, nip to the shops, find a local cafe or head for a walk around Borough Market - the choice is yours!
|
4 |
+
|
5 |
+
## How it works
|
6 |
+
|
7 |
+
- At the start of the month the date for each region will be posted in the Slack channel. To be in with a chance of being selected, book your desk and make sure you are in the office on that day!
|
8 |
+
- The day before lunch the lucky lunchers will be posted in the regions Slack channel - if you cant make it, give your spot to someone else whos in.
|
9 |
+
|
10 |
+
*You can only expense your lunch if you are chosen for lunchers.*
|
11 |
+
|
12 |
+
If you have any questions, ask the People or Finance Team.
|
benefits/pension_scheme.txt
ADDED
@@ -0,0 +1,30 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Pension Scheme
|
2 |
+
|
3 |
+
We have introduced a much-improved pension offering for all employees (as of May 2022). The workplace pension scheme is run by Scottish Widows and follows a contribution matching model where Made Tech matches the level of contribution you decide to make.
|
4 |
+
|
5 |
+
The pension contribution available to you is aligned to your SFIA level:
|
6 |
+
- SFIA 1: 4% employer matched
|
7 |
+
- SFIA 2-4 6% employer matched
|
8 |
+
- SFIA 5: 7% employer matched
|
9 |
+
- SFIA 6: 8% employer matched
|
10 |
+
- SFIA 7: 9% employer matched
|
11 |
+
|
12 |
+
The minimum contribution in every level is 4% (employer matched).
|
13 |
+
There is no maximum contribution, however your salary must remain above the national minimum wage thresholds set by HMRC.
|
14 |
+
If you’d like to adjust your contributions, please [submit a request via Ask Made Tech](https://askmadetech.zendesk.com/hc/en-gb/requests/new).
|
15 |
+
|
16 |
+
Pension contributions are deferred for your first 90 days, if you want to opt in early add the date into the "Pension Scheme" section of your Hibob profile where you will be enrolled on a 4% contribution scheme which you can adjust after your probationary period.
|
17 |
+
|
18 |
+
Our pension scheme is based on a salary sacrifice approach which is more tax-efficient for both employer and employee. We have removed the qualifying earnings limit, which should simplify pension management for those of you who are higher rate taxpayers. If you want to calculate your contributions you can use the calculator on the [Scottish Widows](https://www.scottishwidows.co.uk/retirement/calculators-tools/how-do-you-pay-to-your-pension/salary-sacrifice/) website.
|
19 |
+
|
20 |
+
In order to allocate your preferred contribution, or early opt in, or opt out you'll need to fill in the "Pension Scheme" section of your Hibob profile.
|
21 |
+
|
22 |
+
- You can opt out at any point by updating the pension section of your Hibob profile in the "opted out" section. If you select to opt-out at the start of your employment, any initial deduction will be refunded if this is made within one month of the initial deduction. If you selected to opt out before the cut-off date (on the 18th) it will be processed in the same month, otherwise it will be in the following month.
|
23 |
+
Any deductions made will usually stay in the pension until you're eligible to access your money, financial advice can be obtained to assist you transferring your pension to another provider.
|
24 |
+
- There are also [Government guidelines](https://www.gov.uk/workplace-pensions/if-you-want-to-leave-your-workplace-pension-scheme) on opt-out
|
25 |
+
|
26 |
+
You can read more about Workplace pensions on [gov.uk](https://www.gov.uk/workplace-pensions/about-workplace-pensions)
|
27 |
+
|
28 |
+
You can read more about Pensions and some third party advice on [MoneySavingExpert](http://www.moneysavingexpert.com/savings/discount-pensions)
|
29 |
+
|
30 |
+
For any general pensions queries please enquire via Ask Made Tech.
|
benefits/private_medical_insurance.txt
ADDED
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
1 |
+
# Private Medical Insurance
|
2 |
+
|
3 |
+
We have introduced BUPA Private Medical Insurance to employees who are SFIA 5 (Lead/Principal) and above. This policy will cover the costs of private healthcare from diagnosis through to treatment. This is a taxable benefit and is declarable on a P11D.
|
benefits/season_ticket_loan.txt
ADDED
@@ -0,0 +1,9 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Season Ticket Loan
|
2 |
+
|
3 |
+
On completion of the probation period, we offer a season ticket loan up to the value of one month's net salary.
|
4 |
+
|
5 |
+
You will need to provide a receipt for the season ticket.
|
6 |
+
|
7 |
+
The loan will be repaid automatically at PAYE from your net salary every month. There is no tax benefit, and no interest is payable.
|
8 |
+
|
9 |
+
If you leave the company prior to your loan being repaid, the outstanding balance will be deducted from your final salary payment.
|
benefits/taking_holiday.txt
ADDED
@@ -0,0 +1,70 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Taking Holiday
|
2 |
+
|
3 |
+
We're building a high-performance organisation that delivers great software products. We recognise that this requires a lot of hard work and that for our team to perform at their highest possible level, they need to live a well-balanced life and take regular time-out for rest, relaxation and rejuvenation.
|
4 |
+
|
5 |
+
All team members have 38 days of leave available between June and May, this is inclusive of public and bank holidays (pro-rata for part time colleagues.) We believe this policy will help us to perform at the highest possible level.
|
6 |
+
|
7 |
+
It is important that you and your colleagues feel that holiday is highly available. That holiday is an easily accessible commodity that enables everyone to get the necessary rest that they need.
|
8 |
+
|
9 |
+
Made Tech will support holiday requests that are up to 4 consecutive weeks, if you wish to take longer than this the additional time may be unpaid. Please see our [Flexible Working](flexible_working.md) as the alternative to Flexible Holiday in those situations.
|
10 |
+
|
11 |
+
## How long are you taking?
|
12 |
+
|
13 |
+
We trust you'll use your best judgement when taking holidays. This is the level of notice we expect when you take your holiday:
|
14 |
+
|
15 |
+
* **For 1 day** – you must give at least 3 days notice
|
16 |
+
* **For 2 days** – you must give at least 1 week notice
|
17 |
+
* **For between 3 days - 4 days** – you must give at least 2 weeks notice
|
18 |
+
* **For between 1 week - 2 weeks** – you must give at least 4 weeks notice
|
19 |
+
* **For greater than 2 weeks** – you must give 3 months notice
|
20 |
+
|
21 |
+
The notice guidance is a minimum - please aim to give your team as much notice of upcoming leave as you can. Your team, Delivery Manager and client should all agree to your leave before you schedule this in, and providing notice minimises the chance of problems being raised. Where your team plans work at a regular cadence (e.g. during sprint planning every two weeks), you should aim to make the team aware of any potential leave to help the team remain accountable for commitments made.
|
22 |
+
|
23 |
+
The ability to book holiday/learning days at shorter notice whilst you are within the chalet is an accepted exception to the above notice periods - in those instances please check in with Scheduling to ensure you are not due to be imminently assigned to an account and let your line manager know.
|
24 |
+
|
25 |
+
If you wish to book holiday outside of these guidelines, please make a request to your Head of Capability, Head of Industry, or Head of Business Service who will help you plan for this time off.
|
26 |
+
|
27 |
+
## How will it affect your team?
|
28 |
+
|
29 |
+
Having several team members away at the same time can make life really difficult for everyone else. Try to forward-plan your holiday, so it doesn't have a detrimental affect on your team members or on the company.
|
30 |
+
|
31 |
+
We recommend you check with your Delivery Lead whenever you join a new team. Our general guideline on this is that only 1 person from a small team (less than 4) may be away at any one time. For larger teams (5+) please refer to your Delivery or Team Lead to confirm what works best for your team.
|
32 |
+
|
33 |
+
## Who approves holiday?
|
34 |
+
|
35 |
+
We want to ensure teams own their holidays and that includes thinking about the commercial impact of taking them. To that affect we need to make sure you've done the following before booking holiday:
|
36 |
+
|
37 |
+
* Ask your team members if it's okay with them
|
38 |
+
* Ask your clients if it's okay with them
|
39 |
+
* Ensure your responsibilities are covered whilst you're away
|
40 |
+
* Ensure the Made Tech person leading your client workstream or your line manager provides their agreement
|
41 |
+
* Ensure that the holiday is placed into HiBob
|
42 |
+
|
43 |
+
## How is holiday approved?
|
44 |
+
|
45 |
+
It is the responsibility of the person agreeing to a holiday booking to ensure it is made in aligment to this policy and that the holiday will not impact the quality of service we're able to provide our clients
|
46 |
+
|
47 |
+
## Additional considerations
|
48 |
+
|
49 |
+
* We use the HiBob calendar when working out project allocation and the number of days being billed to clients, so it's important that it is always up-to-date and accurate.
|
50 |
+
|
51 |
+
* Time off due to illness and/or injury are handled separately. Flexible holiday cannot be used for these types of absences.
|
52 |
+
|
53 |
+
* If a team members performance declines significantly due to abuse of this policy, then we reserve the right to review their use of this policy.
|
54 |
+
|
55 |
+
* If you leave Made Tech part way through the year your contractual holiday allowance will be pro-rated to account for your leave date. In some cases this might mean we'll pay you for accrued and unused holiday and in others it might mean you'll have to pay days taken over your pro-rated allowance back.
|
56 |
+
|
57 |
+
## Festive period at Made Tech
|
58 |
+
|
59 |
+
|
60 |
+
### Between Christmas and New Years
|
61 |
+
* We only work for clients during the 3 days between Christmas and New Years if they specifically ask for this. Where there is a client requirement we'd look for volunteers to provide this cover. Most team members will not be working during this time.
|
62 |
+
* Please note - you will need to book this time off as holiday in HiBob unless it has been agreed that you are working.
|
63 |
+
|
64 |
+
### December and January
|
65 |
+
Taking time off works differently for the two weeks before Christmas and the first week in January as this is a popular time for holidays.
|
66 |
+
This means we need to coordinate with our team beyond what we may do ordinarily to ensure that there is fair access to holiday and adequate cover of team members working across client deliveries.
|
67 |
+
|
68 |
+
* We'll consult with our clients as early as possible to understand what level of cover they will need.
|
69 |
+
* Time off requests submitted for this period are typically reviewed and confirmed by mid October.
|
70 |
+
|
benefits/work_ready.txt
ADDED
@@ -0,0 +1,33 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Work Ready
|
2 |
+
|
3 |
+
We know you're ready to work and so we want you to be work ready. We'll [equip you](../guides/it/Hardware.md) with a Macbook (or a PC if you're in Engineering or UCP and would prefer that) which will arrive at your home address prior to your start date.
|
4 |
+
|
5 |
+
In addition to this, you have access to a one off £250 work ready allowance. The allowance allows you to purchase items that will assist you in your job role. It can be used from your first day, and doesn’t need to be used in one go. If you are working your notice period, you are unable to use the budget.
|
6 |
+
|
7 |
+
Before utilising your work ready budget, please complete your DSE (Display screen equipment) training and DSE assessment to assist you in purchasing items required to fit in with DSE requirements.
|
8 |
+
|
9 |
+
To utilise your work ready allowance; simply order the equipment you require then claim it back via expenses on Xero. You must have an invoice or receipt to ensure you can claim it back on Xero. Once on Xero please log the expense under ‘computer equipment <£250’. Once a claim is made you will be added to the next available weekly payment run. For any further questions on expenses please read the [expenses process](../guides/compensation/expenses.md).
|
10 |
+
|
11 |
+
You can see how much of your allowance is left to use by looking at your profile on Bob under the Work Ready section.
|
12 |
+
|
13 |
+
Examples of things you can order:
|
14 |
+
|
15 |
+
- Monitor
|
16 |
+
- Adapters (HDMI, USB-C, etc.)
|
17 |
+
- Keyboards
|
18 |
+
- Mice
|
19 |
+
- Ergonomic chairs, stools, stands
|
20 |
+
- Standing desks
|
21 |
+
- Headphones
|
22 |
+
- Laptop stand
|
23 |
+
- Docking station
|
24 |
+
- Extension lead
|
25 |
+
- Laptop sleeve
|
26 |
+
|
27 |
+
Please order items that are dispatched from the UK. If items are dispatched from outside of the UK you could receive a duty and tax bill that will also have to be deducted from your WFH budget.
|
28 |
+
|
29 |
+
[See a list of popular purchases of office equipment](https://docs.google.com/spreadsheets/d/1aVJx2Qvd6U3H6tHkzeCOY1kVsfcuwXfmXzVWJOFsVYk/edit#gid=0) (internal link). We also have a Slack channel #x-swap-shop for anyone who wants to join and see what people are offering.
|
30 |
+
|
31 |
+
If you are unable to claim items back yourself, please contact the operations team on either [[email protected]](mailto:[email protected]) or through [Ask Made Tech](https://askmadetech.zendesk.com/hc/en-gb) (internal link).
|
32 |
+
|
33 |
+
You will be unable to purchase or expense any items during your notice period.
|
benefits/working_hours.txt
ADDED
@@ -0,0 +1,19 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Working Hours
|
2 |
+
|
3 |
+
We care more about the quality of the work we produce than the amount of hours worked. We believe we individually know how we work best and can therefore set our own hours.
|
4 |
+
|
5 |
+
## Some things to note
|
6 |
+
|
7 |
+
**Setting hours** - We don’t have a set amount of hours you need to work in a day or a week. Many of us will vary our hours day to day while others prefer routine.
|
8 |
+
|
9 |
+
**Start time** - We don’t have a specific start time but we do have our company update on the first Wednesday of every month at 9:30am, and weekly Friday showcases at 4:30pm. You should be in the office or dial in remotely for these meetings.
|
10 |
+
|
11 |
+
**Ending your day** - There isn't a time we expect everyone to switch off their laptop or leave the office. If you're working shorter hours but having problems delivering on your commitments, someone is more likely to check in with you to see if everythings OK, and provide offers of support or some constructive feedback.
|
12 |
+
|
13 |
+
**Longer hours** - The reality of working closely with clients is that there are deadlines. Sometimes working longer to make sure of a smooth launch or to help diagnose and fix a problem is needed. But we do everything we can to make sure these occasions are rare. If you regularly feel this pressure, say more than twice a year, we encourage you to raise this with a manager or another team member.
|
14 |
+
|
15 |
+
**Other team member hours** - You might also feel pressure if you notice other team members regularly seem to work longer hours than you. We suggest finding ways to share and receive open and honest feedback. Unless someone has raised an issue with you, everything’s probably fine.
|
16 |
+
|
17 |
+
**Commitments** - We need to respect our commitments and the time of other team members. If a meeting is scheduled, we ask everyone to be as accommodating as they can. This isn't to say you can't be responsible for setting meeting times that fit your working style better.
|
18 |
+
|
19 |
+
**Contractual hours** - Most of our employment contracts do have set contractual hours. This is because we have a billed delivery operating model with clients that’s based on hours worked. This also helps us to adjust our flexible working policy in case that’s ever needed.
|
communities-of-practice/cloud-and-engineering/book-club/edge-value-driven-digital-transformation.txt
ADDED
@@ -0,0 +1,24 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# EDGE: value-driven digital transformation
|
2 |
+
|
3 |
+
## About
|
4 |
+
Authors: Jim Highsmith, Linda Luu and David Robinson
|
5 |
+
Recommended by: Chasey
|
6 |
+
_[EDGE](https://www.goodreads.com/en/book/show/43567723-edge) embraces an adaptive mindset in the face of market uncertainty, a visible, value-centered portfolio approach that encourages continual value linkages from vision to detailed initiatives, incremental funding that shifts as strategies evolve, collaborative decision-making, and better risk mitigation. This guide shows leaders how to use the breakthrough EDGE approach to go beyond incremental improvement in a world of exponential opportunities._
|
7 |
+
|
8 |
+
## 20th May
|
9 |
+
_Authored by Reuben_. We had our first ever session!! We went over the rough format and covered just managed to cover the introduction and "Chapter 1: The Big Picture". We wondered at whether fast meant good (it doesn't) but expected to talk about that more in later chapters. We also spoke about our [mainly negative] experiences of Agile at scale and the challenges it presents and what it means to us to be agile. Lastly, this chapter talks about the new / digital-age fitness function and we started to ask how we might measure customer value, without externalising what should be internal team metrics. Great stuff! We decided we'd read "Chapter 2: Tech@Core" and "Chapter 3: EDGE Principles" for next time, but might not expect to cover it all as Tech@Core seems an interesting subject!
|
10 |
+
|
11 |
+
## 10th June
|
12 |
+
_Authored by Reuben_. I forgot to take notes... but we spoke about Tech@Core :D
|
13 |
+
|
14 |
+
## 24th June
|
15 |
+
_Authored by Reuben_. I missed this session and I am indebted to Tom for running it. The team chatted about the "EDGE principles", what kinds of governance can reduce waste and increase autonomy, and asked the question of how often principles should change.
|
16 |
+
|
17 |
+
## 8th July
|
18 |
+
_Authored by Reuben_. We had a whopper and covered two chapters - "Chapter 4: Building a Value-Driven Portfolio" and "Chapter 5: Measuring and Prioritizing Value" before deciding it was time to enjoy the Friday afternoon sun (location dependent). We were pleased to welcome Catherine (a DP) into the conversation this week and was great to have her insight! We talked about the value we get from having User Researchers in our delivery teams and working closely with us, the issues we have with teams not having the ideal relationships between the goals, bets and initiatives, and how the EDGE operating model is value-centre rather than being implementation-specific although it tends to have enterprise in mind. The measures of success example on page 81 were very good for seeing how to put customer outcomes first!
|
19 |
+
|
20 |
+
## Resources
|
21 |
+
👉 [An interview with Linda Luu](https://www.youtube.com/watch?v=-HPnr4yuUqc) going over the high-level stuff
|
22 |
+
👉 [An introduction to value-stream mapping](https://www.youtube.com/watch?v=tGDrt8SV5H4) (spin off from 20th May)
|
23 |
+
👉 [A lean-value tree example](https://miro.medium.com/max/1094/1*9KIk8YmivQxv53lEgestAA.png) (image for those without the book)
|
24 |
+
👉 [Weighted Shortest Job First (WSJF)](https://www.scaledagileframework.com/wsjf/) from SAFe is an implementation based on Cost of Delay
|
communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_got_our_eye_on.txt
ADDED
@@ -0,0 +1,9 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Books we've got our eye on
|
2 |
+
|
3 |
+
Please contribute to this list if there's a book you're interested in! We'll include it in the considerations when we're ready to pick up a new book! 💚
|
4 |
+
|
5 |
+
| Title | Author | Watched By |
|
6 |
+
| --- | --- | --- |
|
7 |
+
| [Release It!](https://www.goodreads.com/book/show/1069827.Release_It_) | Michael Nygard | Reuben |
|
8 |
+
|
9 |
+
[👈 Library](./library.md)
|
communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_read.txt
ADDED
@@ -0,0 +1,5 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Books we've read in Book Club
|
2 |
+
|
3 |
+
1. ### [EDGE: value-driven digital transformation](../edge-value-driven-digital-transformation.md)
|
4 |
+
|
5 |
+
[👈 Library](./library.md)
|
communities-of-practice/cloud-and-engineering/book-club/library/books_we_recommend.txt
ADDED
@@ -0,0 +1,10 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Books we recommend
|
2 |
+
|
3 |
+
| Title | Author | Recommended By |
|
4 |
+
| --- | --- | --- |
|
5 |
+
| [Accelerate](https://www.goodreads.com/en/book/show/35747076-accelerate) | Nicole Forsgren, Jez Humble and Gene Kim | Reuben |
|
6 |
+
| [Domain-Driven Design](https://www.goodreads.com/book/show/179133.Domain_Driven_Design) | Eric Evans | Reuben |
|
7 |
+
| [Infrastructure as Code](https://www.goodreads.com/book/show/26544394-infrastructure-as-code) | Kief Morris | Reuben |
|
8 |
+
| [Test-Driven Development: By Example](https://www.goodreads.com/book/show/387190.Test_Driven_Development) | Kent Beck | Reuben |
|
9 |
+
|
10 |
+
[👈 Library](./library.md)
|
communities-of-practice/cloud-and-engineering/book-club/library/library.txt
ADDED
@@ -0,0 +1,5 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Library
|
2 |
+
|
3 |
+
- ✅ [Books we've read](./books_we_have_read.md)
|
4 |
+
- 💡 [Books we recommend](./books_we_recommend.md)
|
5 |
+
- 👀 [Books we've got our eyes on](./books_we_have_got_our_eye_on.md)
|
communities-of-practice/cloud-and-engineering/book-club/welcome.txt
ADDED
@@ -0,0 +1,33 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Welcome to the Book Club
|
2 |
+
|
3 |
+
👋 Welcome to our Cloud and Engineering Book Club! At Made Tech we are passionate about [learning](../../../guides/learning/README.md). In this Book Club, we choose a technical book in the cloud and engineering space and gather once a fortnight to discuss it. We hope to see you there soon!
|
4 |
+
|
5 |
+
This page is about what the Book Club is all about. For all things books, take a look at our [library](./library/library.md).
|
6 |
+
|
7 |
+
## Purpose
|
8 |
+
|
9 |
+
As engineers in delivery teams, we want to continously improve our capabilities and how we deliver working software. By using a technical book to give our minds some direction, we will be able to share our own relevant knowledge and experiences to discuss and build on the book's content - the questions it asks of us - and how it can make us more well-rounded engineers.
|
10 |
+
|
11 |
+
## Format?
|
12 |
+
|
13 |
+
- We meet every other Friday at 1530 for 50 minutes.
|
14 |
+
- Anyone at Made Tech can subscribe to the club's calendar to get the invite. Just head over to the #eng-bookclub Slack channel and pick up the pinned post!
|
15 |
+
- We'll cover off an overview of the chapter.
|
16 |
+
- We'll cover off some of our own highlights.
|
17 |
+
- We'll then vote on some cards and discuss the most popular questions and deep dives that come to mind.
|
18 |
+
- At the end, we'll decide for next time.
|
19 |
+
|
20 |
+
## What do I need to do?
|
21 |
+
|
22 |
+
### Before the meeting
|
23 |
+
|
24 |
+
- 💰 Use your learning budget to get your copy of the book!
|
25 |
+
- 📖 Try and read the agreed sections of the book.
|
26 |
+
- 🧐 While you read, you could try to think about any puzzles that came to mind, any challenges you'd like to pose to the group, any times you've seen the technique work/fail in real life, or just things you find insightful.
|
27 |
+
- 💡 Add your thoughts to the (internal) Trello board, which is pinned to the #eng-bookclub Slack channel.
|
28 |
+
|
29 |
+
### During the meeting
|
30 |
+
|
31 |
+
- 🚶♀️ We'll walk through the cards chapter-by-chapter
|
32 |
+
- 🗣 Chip in where you're happy to, whether that's a card you added, an opinion you want to share or a spur of the moment contribution!
|
33 |
+
- 🧘♀️ Or take a back seat if that's what you're comfortable with.
|
company/about.txt
ADDED
@@ -0,0 +1,34 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# About Made Tech
|
2 |
+
|
3 |
+
As a **purpose-driven organisation**, we believe the **outcomes** we create are more important than the technology we deliver.
|
4 |
+
|
5 |
+
## Our purpose – why we do what we do
|
6 |
+
|
7 |
+
We want to positively impact the future of the country by using technology to improve society, **for everyone**.
|
8 |
+
|
9 |
+
We are already working with **brilliant public servants** to **modernise technology** and **accelerate digital delivery**. But we know we can do more to help those who share our vision.
|
10 |
+
|
11 |
+
## Our vision – what we want the future to look like
|
12 |
+
|
13 |
+
We want to **empower** the public sector to deliver and continuously improve digital services that are user-centric, data-driven and freed from legacy technology.
|
14 |
+
|
15 |
+
To achieve this, we help them to modernise working practices, accelerate digital delivery, drive better decisions through data and enable technology and delivery skills.
|
16 |
+
|
17 |
+
## Our missions – how we will get there
|
18 |
+
|
19 |
+
We empower public sector organisations by helping them to become digital by default.
|
20 |
+
|
21 |
+
- **Modernise** legacy technology and working practices
|
22 |
+
- **Accelerate** digital service and technology delivery
|
23 |
+
- **Drive** better decisions through data and automation
|
24 |
+
- **Enable** technology and delivery skills to build better systems
|
25 |
+
|
26 |
+
## Our values – who we are and how we operate
|
27 |
+
|
28 |
+
**Client focus** - we can only succeed in our mission if we’re a trustworthy partner to the public sector. We build strong and lasting relationships with our clients through empathy, flexibility, and pragmatism.
|
29 |
+
|
30 |
+
**Drive to deliver** - we have a strong drive to deliver successful outcomes for our clients and their users, working hard to keep to our commitments and rapidly delivering software that improve people’s lives.
|
31 |
+
|
32 |
+
**Learning and mentoring** - we’re passionate about learning and growth. Whether it's improving ourselves, the team, or the organisation, we believe in the power of continuous improvement.
|
33 |
+
|
34 |
+
**One team** - we collaborate with colleagues, clients and communities to create an environment which is inclusive, integrated, and where everyone supports delivery of the mission.
|
company/welcome_pack.txt
ADDED
@@ -0,0 +1,69 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Welcome Pack
|
2 |
+
|
3 |
+
If it's your first day today, we'd just like you to know how happy we are to have you with us :)
|
4 |
+
|
5 |
+
To give you an idea of what to expect from your on-boarding, we have written this short guide. It covers the things that we think are important for new starters and we hope it provides a basis for your successful on-boarding.
|
6 |
+
|
7 |
+
Over the next few days and weeks we'll introduce:
|
8 |
+
|
9 |
+
1. **Company mission, [values](about.md#our-values), business services and EOSs** - We'll talk about our mission and why the business exists. We'll tell you why we think it's important to improve software delivery in every organisation and how you can help us to achieve our mission.
|
10 |
+
2. **Peer buddy** — As part of our on-boarding process, we'll introduce you to a company buddy who will be available whenever you need them. If anything crops up (from simple questions to emergencies), feel free to let your buddy know and they will do all they can to help.
|
11 |
+
|
12 |
+
It goes without saying that the rest of the team are here too, so there should be plenty of places to turn if you need anything.
|
13 |
+
3. [**Role expectations**](../roles/README.md) — All our team members have role expectations and we'll work with you to introduce these to you over the coming weeks.
|
14 |
+
4. **Career development 121s** — As part of your on-boarding process and ongoing career development, you'll have a monthly 121 with your Line Manager or one of the company directors. These sessions are an opportunity for us to review your progress, look at areas where we can provide support.
|
15 |
+
5. **Marketplace** — Every Friday, we run showcases. Please contribute to these and once you're feeling confident enough, look to facilitate one of them.
|
16 |
+
6. **Salary, Pensions & Expenses** — We'll take you through how our finances work, where to go to if you have any questions around salary, pensions, benefits or if you need to submit an expense claim.
|
17 |
+
|
18 |
+
## Getting Started Checklist
|
19 |
+
|
20 |
+
Our on-boarding checklist will be in your Hibob profile on your first day. Below are a few things this will cover.
|
21 |
+
|
22 |
+
#### Everyone
|
23 |
+
|
24 |
+
* [ ] Meet your buddy
|
25 |
+
* [ ] Attend first career development 121 to introduce role expectations
|
26 |
+
* [ ] Read the [Acceptable Use Policy](../guides/security/acceptable_use_policy.md) & [Bring Your Own Device Policy](../guides/security/bring_your_own_device.md)
|
27 |
+
* [ ] Ensure your own devices used for [work are secure](../guides/security/bring_your_own_device.md)
|
28 |
+
* [ ] Set up Slack account with picture, name(s), name pronunciation guide and [pronouns](https://www.mypronouns.org/)
|
29 |
+
|
30 |
+
#### Non-Engineers
|
31 |
+
* [ ] Complete the [Github tutorial](https://guides.github.com/activities/hello-world/)
|
32 |
+
|
33 |
+
|
34 |
+
### Signing up for Services
|
35 |
+
|
36 |
+
Below you'll find a list of tools that you will need to do your job. You will be setup with the accounts you'll need on your first day with us.
|
37 |
+
|
38 |
+
Note that Google office applications (Docs, Sheets) are the preferred format for internal office documents, to be stored in Google Drive
|
39 |
+
|
40 |
+
#### Everyone
|
41 |
+
|
42 |
+
* [ ] Google Mail (with 2FA)
|
43 |
+
* [ ] Github (with 2FA)
|
44 |
+
* [ ] Slack (with 2FA)
|
45 |
+
* [ ] 1Password (with 2FA)
|
46 |
+
* [ ] Trello (with 2FA unless using Google Auth to login to Trello)
|
47 |
+
* [ ] HiBob
|
48 |
+
|
49 |
+
Academy Engineers: you can skip these two for now, but you will probably need them once you graduate.
|
50 |
+
|
51 |
+
* [ ] Xero
|
52 |
+
* [ ] Kimble
|
53 |
+
|
54 |
+
#### Sales & Marketing
|
55 |
+
|
56 |
+
* [ ] HubSpot
|
57 |
+
* [ ] Access to [LinkedIn Sales Navigator](https://www.linkedin.com/sales/)
|
58 |
+
|
59 |
+
#### Engineers
|
60 |
+
|
61 |
+
* [ ] Get access to infrastructure for delivery team
|
62 |
+
|
63 |
+
### Setting up your Machine
|
64 |
+
|
65 |
+
#### Engineers
|
66 |
+
|
67 |
+
To get your machine set up with some essentials we've created [First Boot](https://github.com/madetech/first-boot).
|
68 |
+
|
69 |
+
First Boot will install applications like Chrome, Slack, and Sequel Pro as well as installing the latest version of Ruby using `rbenv`, and the latest version of Node using `nvm`.
|
guides/Relocation.txt
ADDED
@@ -0,0 +1,16 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Relocation
|
2 |
+
|
3 |
+
|
4 |
+
|
5 |
+
If you are planning to move address, you’ll need to inform us as early as possible.
|
6 |
+
|
7 |
+
|
8 |
+
To inform us of an upcoming move, you'll need to let the following people know:
|
9 |
+
|
10 |
+
Your line manager -to inform them of any support you may need (booking leave to move house etc).
|
11 |
+
The People team via [[email protected]](mailto:[email protected]) - we need to know if we need to update your office location in bob.
|
12 |
+
Your head(s) of - if a location change is required, they may need to know in case this impacts your current or future projects.
|
13 |
+
|
14 |
+
|
15 |
+
Once you have confirmation of your new address and have spoken to the relevant people, you’ll need to update this in your bob profile.
|
16 |
+
You can do this via 'Actions > Employee Updates > Address Change'.
|
guides/buddy_guidance.txt
ADDED
@@ -0,0 +1,17 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Buddy Guidance
|
2 |
+
|
3 |
+
You've been chosen to be a buddy to a new team member - Yay. Here's some guidance to help you find out what's expected.
|
4 |
+
|
5 |
+
A buddy is a friend at Made Tech. Someone friendly who helps new team members connect and find their way, especially in their first 3 months with us when everything is new to them.
|
6 |
+
|
7 |
+
Being a buddy is a really important way to help a new person integrate into Made Tech.
|
8 |
+
When we're back in the office, you will show them all the good lunch places near the office, take them out for a coffee or lunch and help them find their way in the local area.
|
9 |
+
|
10 |
+
As we're working remotely currently, most or all of your interactions will happen on video calls which we call 'coffee chats'.
|
11 |
+
|
12 |
+
## Buddies
|
13 |
+
- proactively and frequently check in with a new starter to see how they are doing. In the first 3 months you may check in 2-3 times per month. After that time you can work out what suits you both, i.e. monthly catchup/remote lunch
|
14 |
+
- offer their help and answer all questions (or direct to the right person)
|
15 |
+
- explain how things work here and where to find stuff
|
16 |
+
- are available to the new team member for any guidance and often just a chat
|
17 |
+
- are friendly and helpful humans who are here to welcome all our new team members
|
guides/chalet_time_policy.txt
ADDED
@@ -0,0 +1,168 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Chalet time policy
|
2 |
+
|
3 |
+
This document describes how people should spend time when not on client work. This is known as Chalet Time.
|
4 |
+
|
5 |
+
Chalet time should be used to build skills, grow Made Tech’s business and contribute to Communities of Practice.
|
6 |
+
|
7 |
+
## What is chalet time?
|
8 |
+
|
9 |
+
Chalet time is when people are not on client work. For example...
|
10 |
+
|
11 |
+
- A two week gap between someone finishing the software engineering academy and going onto a client project.
|
12 |
+
- A week between a new starter joining the company and their first client project.
|
13 |
+
- A lead designer having three days between their current client project and the next.
|
14 |
+
|
15 |
+
Occasional chalet time is a common part of a business like ours, as client work isn’t always going to perfectly match our skills and availability. It's a good time to focus on other activities.
|
16 |
+
|
17 |
+
## Getting started in the chalet
|
18 |
+
|
19 |
+
Please follow these steps when you join the chalet.
|
20 |
+
|
21 |
+
### 1. Join the [`#chalet`][1] Slack channel.
|
22 |
+
This channel provides up-to-date information on chalet activities and practices. You can use it to ask questions and arrange collaborative work.
|
23 |
+
### 2. Add mandatory chalet meetings to your Google Calendar.
|
24 |
+
You can find Google Calendar links for chalet meetings pinned to the top of the [`#chalet`][1] Slack channel.
|
25 |
+
Members of the Chalet are expected attend these meetings, so that we can:
|
26 |
+
|
27 |
+
- Help people use their chalet time well
|
28 |
+
- Share opportunities and events
|
29 |
+
- Help people with blockers
|
30 |
+
- Build a sense of community
|
31 |
+
|
32 |
+
### 3. Join the [Chalet Community Board][2].
|
33 |
+
Use this board to discover tasks you can undertake while in the chalet, including work with Made Tech departments and Communities of Practice. You can also learn about chalet members and their current projects.
|
34 |
+
|
35 |
+
## Responsibility for using chalet time usefully
|
36 |
+
|
37 |
+
Chalet members and their line managers will be responsible for ensuring this time is used usefully.
|
38 |
+
|
39 |
+
Line management should therefore focus partly on:
|
40 |
+
|
41 |
+
- Agree weekly goals to use chalet time according the highest priorities
|
42 |
+
- Check progress against goals for chalet time in bob
|
43 |
+
- Agree a plan to get someone onto billed client work
|
44 |
+
- Identify blockers someone has doing activities with their chalet time
|
45 |
+
- Identify if someone needs help reaching out to a part of the organisation, so that they can assist or shadow. This could involve introducing someone to a team or advocating on their behalf.
|
46 |
+
|
47 |
+
Each Head of Capability Practice is ultimately accountable for everyone in their practice using chalet time the right way. This will be measured by the average amount of people’s time billed to a client, also known as utilisation.
|
48 |
+
|
49 |
+
## Priorities for chalet time
|
50 |
+
|
51 |
+
The priorities for using chalet time will always stay the same, but the activities that a chalet member should do will depend on their roles and availability.
|
52 |
+
|
53 |
+
If there are no activities that need to be done that match the chalet member's role and availability, chalet time should be used for the next highest priority. For example, if there are no activities that someone could do to find new opportunities on client teams or new business and revenue, that person should do hiring activities.
|
54 |
+
|
55 |
+
### 1. New opportunities on client teams
|
56 |
+
|
57 |
+
1. Billed opportunities, where clients pay for someone’s time
|
58 |
+
2. Invested opportunities, working on a client team, but not billed to begin with, showing value first
|
59 |
+
3. Shadowing, getting experience of how teams work
|
60 |
+
|
61 |
+
### 2. New business and revenue
|
62 |
+
|
63 |
+
1. Bid writing - leading / pairing / shadowing / case studies / research
|
64 |
+
2. Support marketing team create content, like blogging, case studies, talks that promote Made Tech
|
65 |
+
|
66 |
+
### 3. Hiring
|
67 |
+
|
68 |
+
1. Pairing on interviews
|
69 |
+
2. Outreach to potential candidates
|
70 |
+
|
71 |
+
### 4. Research and development
|
72 |
+
|
73 |
+
1. Product development
|
74 |
+
2. Research projects
|
75 |
+
|
76 |
+
### 5. Communities of Practice (CoP)
|
77 |
+
|
78 |
+
- CoPs have regular meetings and ongoing activities. To participate in these, search Slack for channels starting with `#cop`.
|
79 |
+
- CoPs will post opportunities to the [`#chalet`][1] Slack channel and the [Chalet Community Board][2].
|
80 |
+
|
81 |
+
### 6. Learning time
|
82 |
+
|
83 |
+
- Reading
|
84 |
+
- Training courses
|
85 |
+
- Conferences
|
86 |
+
- Pairing and group learning
|
87 |
+
|
88 |
+
### 7. Holiday that can flexibly be moved
|
89 |
+
|
90 |
+
## Booking & scheduling chalet time
|
91 |
+
|
92 |
+
### 1. New opportunities on client teams
|
93 |
+
|
94 |
+
Billed or invested time will be booked by the Scheduling team, just like when someone joins a client team. The chalet member will fill out timesheets for time spent in this team.
|
95 |
+
|
96 |
+
Shadowing should be recorded as ‘Bench/Chalet’ in timesheets.
|
97 |
+
|
98 |
+
### 2. New business and revenue
|
99 |
+
|
100 |
+
Bid writing will be booked by the Scheduling team. The chalet member will fill out timesheets for time spent on the bid.
|
101 |
+
|
102 |
+
Marketing activities should be recorded as ‘Bench/Chalet’ in timesheets.
|
103 |
+
|
104 |
+
### 3. Hiring
|
105 |
+
|
106 |
+
This time should be recorded as ‘Hiring’ in timesheets.
|
107 |
+
|
108 |
+
### 4. Research and development
|
109 |
+
|
110 |
+
This time should be recorded as ‘R&D’ time in timesheets.
|
111 |
+
|
112 |
+
### 5. Communities of Practice
|
113 |
+
|
114 |
+
This time should be recorded as ‘Bench/Chalet’ in timesheets.
|
115 |
+
|
116 |
+
### 6. Learning time
|
117 |
+
|
118 |
+
If your learning activity will make you unavailable for a delivery (eg. a conference or exam) please book this as 'Learning Time' in Bob and let your line manager know. Record this as 'Learning Time' in timesheets.
|
119 |
+
|
120 |
+
Learning activities that won't make you unavailable for a delivery (eg. reading, group learning) should be recorded as ‘Bench/Chalet’ in timesheets.
|
121 |
+
|
122 |
+
We're actively reviewing the Learning process so this may change. If you have any questions please post them in the [`#supply-learning-and-development`][4] Slack channel.
|
123 |
+
|
124 |
+
### 7. Holiday
|
125 |
+
|
126 |
+
Chalet members will [book holiday][5] in the normal way.
|
127 |
+
|
128 |
+
## Responsibility to make activities visible and doable
|
129 |
+
|
130 |
+
Various parts of the business will be responsible for making people aware of activities they can do with chalet time:
|
131 |
+
|
132 |
+
### 1. New opportunities on client teams
|
133 |
+
|
134 |
+
A list of live client accounts is pinned to the [`#chalet`][1] Slack channel. This can be used to learn about clients, and to find opportunities to join client teams.
|
135 |
+
|
136 |
+
Line managers of chalet members will help find opportunities and advocate for them to join client teams, either billed, invested or shadowing.
|
137 |
+
|
138 |
+
### 2. New revenue and business
|
139 |
+
|
140 |
+
Each week, the Bids team will send the Scheduling team details of bids that chalet members can contribute to.
|
141 |
+
|
142 |
+
The Marketing team will share tasks that chalet members can do to promote Made Tech. These will be posted in the [Chalet Community Board][2]. If you need more information about a task, ask the person who created the ticket or post in the [`#team-marketing`][3] Slack channel.
|
143 |
+
|
144 |
+
If you have an idea for a blog post contact James Holloway of the Marketing Team. You can also contact relevant CoPs and teams for input.
|
145 |
+
|
146 |
+
### 3. Hiring
|
147 |
+
|
148 |
+
The Scheduling team will give the Talent Team Coordinators access to the Kimble report of who has chalet time. They can be asked to do extra hiring interviews, or undertake training to do so.
|
149 |
+
|
150 |
+
### 4. Research and development
|
151 |
+
|
152 |
+
The R&D team will add tasks to the [Chalet Community Board][2]. These tasks often involve helping to build products or research new opportunities.
|
153 |
+
|
154 |
+
### 5. Communities of Practice
|
155 |
+
|
156 |
+
Capability and Delivery Heads will maintain a visible backlog of tasks in the [Chalet Community Board][2]. Chalet members can undertake these to improve their community of practice.
|
157 |
+
|
158 |
+
## Length of chalet time activities
|
159 |
+
|
160 |
+
Chalet time activities must be able to deliver some value in small blocks of time: half day, 1 day or 3–5 days. This is so that chalet time can add value if someone joins a client team at short notice.
|
161 |
+
|
162 |
+
Some activities may need more than 5 days. These should still be able to deliver business or personal value in increments of a half day, 1 day or 3–5 days.
|
163 |
+
|
164 |
+
[1]: https://madetechteam.slack.com/archives/C03F23K2RL0 "Chalet Time Team Slack Channel"
|
165 |
+
[2]: https://trello.com/b/7lSGB2Xw/chalet-community-board "Chalet Community Board"
|
166 |
+
[3]: https://madetechteam.slack.com/archives/C01MMH7DGUA "Marketing Team Slack Channel"
|
167 |
+
[4]: https://madetechteam.slack.com/archives/C0226JKA39T "Supply Learning and Development Slack Channel"
|
168 |
+
[5]: https://github.com/madetech/handbook/blob/main/benefits/taking_holiday.md "Taking Holiday"
|
guides/cloud/aws_certification_advice.txt
ADDED
@@ -0,0 +1,143 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# AWS Certification Advice
|
2 |
+
|
3 |
+
- [AWS Certification Advice](#aws-certification-advice)
|
4 |
+
- [Purpose of this guide](#purpose-of-this-guide)
|
5 |
+
- [General](#general)
|
6 |
+
- [Certification Costs](#certification-costs)
|
7 |
+
- [Expensing an Exam](#expensing-an-exam)
|
8 |
+
- [Exams charged in USD](#exams-charged-in-usd)
|
9 |
+
- [AWS Business Training](#aws-business-training)
|
10 |
+
- [AWS Technical Training](#aws-technical-training)
|
11 |
+
- [AWS Certified Cloud Practitioner](#aws-certified-cloud-practitioner)
|
12 |
+
- [Recommended Online Training](#recommended-online-training)
|
13 |
+
- [AWS DevOps Engineer Pathway](#aws-devops-engineer-pathway)
|
14 |
+
- [AWS Certified Developer - Associate](#aws-certified-developer---associate)
|
15 |
+
- [Recommended Online Training](#recommended-online-training-1)
|
16 |
+
- [AWS Certified SysOps Administrator - Associate](#aws-certified-sysops-administrator---associate)
|
17 |
+
- [Recommended Online Training](#recommended-online-training-2)
|
18 |
+
- [AWS Certified DevOps Engineer - Professional](#aws-certified-devops-engineer---professional)
|
19 |
+
- [Recommended Online Training](#recommended-online-training-3)
|
20 |
+
- [AWS Solutions Architect Pathway](#aws-solutions-architect-pathway)
|
21 |
+
- [AWS Certified Solutions Architect - Associate](#aws-certified-solutions-architect---associate)
|
22 |
+
- [Recommended Online Training](#recommended-online-training-4)
|
23 |
+
- [AWS Certified Solutions Architect - Professional](#aws-certified-solutions-architect---professional)
|
24 |
+
- [Recommended Online Training](#recommended-online-training-5)
|
25 |
+
- [AWS Speciality Certifications](#aws-speciality-certifications)
|
26 |
+
|
27 |
+
## Purpose of this guide
|
28 |
+
|
29 |
+
Made Tech are an [AWS Advanced Consulting Partner](https://partners.amazonaws.com/partners/001E0000016ppWOIAY/Made%20Tech) and encourage both technical and non-technical staff to undertake AWS Training and Certifications. This guide will detail some training paths and associated costs.
|
30 |
+
|
31 |
+
AWS provides some non-technical training via the AWS Partner Portal. Guidance on how to create an account and take advantage of this training can be found [here](aws_partner_certs.md).
|
32 |
+
|
33 |
+
## General
|
34 |
+
|
35 |
+
A guide on how to create an AWS Certification account and link it to your Made Tech AWS Partner Account is located [here](aws_partner_certs.md#creating-your-accounts)
|
36 |
+
|
37 |
+
All AWS Exams can be taken remotely from home with either PSI or Pearson Vue.
|
38 |
+
|
39 |
+
## Certification Costs
|
40 |
+
|
41 |
+
Booking an AWS exam costs vary depending on the level of the exam.
|
42 |
+
|
43 |
+
| Exam | Cost | Cost inc tax |
|
44 |
+
| --- | --- | --- |
|
45 |
+
| AWS Cloud Practitioner | $100 | $120 |
|
46 |
+
| AWS Associate Level (Developer, SysOps, Architect) | $150 | $180 |
|
47 |
+
| AWS Professional Level (DevOps Engineer, Architect) | $300 | $360 |
|
48 |
+
| AWS Speciality Exams (Security, Networking, Database, ML, Data) | $300 | $360 |
|
49 |
+
|
50 |
+
Each time you pass an AWS Exam you receive a [free practice exam and 50% off voucher](https://www.certmetrics.com/amazon/candidate/benefit_summary.aspx) for the next exam.
|
51 |
+
|
52 |
+
This means an individual could achieve all 11 AWS Certifications for $1650!
|
53 |
+
|
54 |
+
### Expensing an Exam
|
55 |
+
|
56 |
+
An exam can be expensed. In order to do this, follow the [expenses guide](https://github.com/madetech/handbook/blob/main/guides/compensation/expenses.md). The account should be set to `Other Training Costs` and the name of the exam used as the description.
|
57 |
+
|
58 |
+
#### Exams charged in USD
|
59 |
+
|
60 |
+
If the exam is charged in USD, there are two ways you can submit your expense claim in Xero.
|
61 |
+
|
62 |
+
1. (recommended) Use the currency selection drop down within the “purchase amount” field, select `USD` and enter the amount shown on your invoice. Xero will automatically convert your expense for you to GBP. The amount converted may vary slightly compared to what you were charged.
|
63 |
+
1. Input the amount you were charged in GBP. You will then need to provide proof of purchase (bank statement etc.) which you will have to edit/merge onto the same attachment as the invoice, since Xero only allows 1 attachment.
|
64 |
+
|
65 |
+
## AWS Business Training
|
66 |
+
|
67 |
+
All non-tech employees are encouraged to undertake the [AWS Business Professional Training](https://aws.amazon.com/partners/training/path-bus-pro/) from the AWS Partner Portal.
|
68 |
+
|
69 |
+
## AWS Technical Training
|
70 |
+
|
71 |
+
All technical employees are encouraged to undertake the [AWS Technical Professional Training](https://aws.amazon.com/partners/training/path-tech-pro/) from the AWS Partner Portal.
|
72 |
+
|
73 |
+
## AWS Certified Cloud Practitioner
|
74 |
+
|
75 |
+
The next stage in the AWS Certification journey is the [AWS Certified Cloud Practitioner](https://aws.amazon.com/certification/certified-cloud-practitioner) which is easily achievable by both tech and non-tech employees.
|
76 |
+
|
77 |
+
#### Recommended Online Training
|
78 |
+
1. [Stephane Maarek - Udemy](https://www.udemy.com/course/aws-certified-cloud-practitioner-new/)
|
79 |
+
2. [Pluralsight](https://www.pluralsight.com/paths/aws-certified-cloud-practitioner-clf-c02)
|
80 |
+
3. [Whizlabs](https://www.whizlabs.com/aws-certified-cloud-practitioner/)
|
81 |
+
You can do shorter tests on specific areas (databases, compute, etc.) so you can target specific knowledge.
|
82 |
+
Also if you run through them in Practice mode you can view answers and explanations as you go
|
83 |
+
|
84 |
+
|
85 |
+
## AWS DevOps Engineer Pathway
|
86 |
+
|
87 |
+
After following the basic training and achieving the AWS Certified Cloud Practitioner Certification, Engineers working towards achieving the AWS DevOps Professional Certification should follow this pathway.
|
88 |
+
|
89 |
+
### AWS Certified Developer - Associate
|
90 |
+
|
91 |
+
The [AWS Certified Developer - Associate](https://aws.amazon.com/certification/certified-developer-associate) is probably the most enjoyable certification to work towards for software developers, covering a lot of the developer tools and fun things like Lambda/API Gateway/SQS/SNS etc...
|
92 |
+
|
93 |
+
#### Recommended Online Training
|
94 |
+
1. [Stephane Maarek - Udemy](https://www.udemy.com/course/aws-certified-developer-associate-dva-c01/)
|
95 |
+
2. [Pluralsight](https://www.pluralsight.com/paths/aws-certified-developer-associate-dva-c01)
|
96 |
+
|
97 |
+
### AWS Certified SysOps Administrator - Associate
|
98 |
+
|
99 |
+
The [AWS Certified SysOps Administrator - Associate](https://aws.amazon.com/certification/certified-sysops-admin-associate) is the next step towards the DevOps Pro certification, covering the following domains. Monitoring & Reporting, High Availability, Deployment & Provisioning, Storage & Data Management, Security & Compliance, Networking and Automation & Optimisation.
|
100 |
+
|
101 |
+
#### Recommended Online Training
|
102 |
+
1. [Cantrill.io](https://learn.cantrill.io/p/aws-certified-sysops-administrator-associate)
|
103 |
+
2. [ACloudGuru](https://learn.acloud.guru/course/aws-certified-sysops-administrator-associate)
|
104 |
+
|
105 |
+
### AWS Certified DevOps Engineer - Professional
|
106 |
+
|
107 |
+
The [AWS Certified DevOps Engineer - Professional](https://aws.amazon.com/certification/certified-devops-engineer-professional/) is the last step in the DevOps Pro certification pathway, covering the following domains. SDLC Automation, Configuration Management & Infrastructure as Code, Monitoring & Logging, Policies & Standards Automation, Incident & Event Response, High Availability, Fault Tolerance & Disaster Recovery.
|
108 |
+
|
109 |
+
#### Recommended Online Training
|
110 |
+
1. [Stephane Maarek - Udemy](https://www.udemy.com/course/aws-certified-devops-engineer-professional-hands-on/)
|
111 |
+
2. [Pluralsight](https://www.pluralsight.com/paths/aws-certified-devops-engineer-professional)
|
112 |
+
|
113 |
+
|
114 |
+
## AWS Solutions Architect Pathway
|
115 |
+
|
116 |
+
After following the basic training and achieving the AWS Certified Cloud Practitioner Certification, Engineers working towards achieving the AWS Certified Solutions Architect - Professional should follow this pathway.
|
117 |
+
|
118 |
+
This pathway only consists of the Associate and Pro level Solutions Architect exams, but I would advise looking at other the Associate level courses before undertaking the AWS Solutions Architect Pro, is it is very difficult exam!
|
119 |
+
|
120 |
+
### AWS Certified Solutions Architect - Associate
|
121 |
+
|
122 |
+
The [AWS Certified Solutions Architect - Associate](https://aws.amazon.com/certification/certified-solutions-architect-associate/) is the Associate level Solutions Architect Certification and covers the following domains. Design Resilient Architectures, Design High-Performing Architectures, Design Secure Application & Architectures and Design Cost-Optimisted Architectures.
|
123 |
+
|
124 |
+
#### Recommended Online Training
|
125 |
+
1. [Cantrill.io](https://learn.cantrill.io/p/aws-certified-solutions-architect-associate-saa-c02)
|
126 |
+
2. [ACloudGuru](https://learn.acloud.guru/course/aws-certified-solutions-architect-associate)
|
127 |
+
|
128 |
+
### AWS Certified Solutions Architect - Professional
|
129 |
+
|
130 |
+
The [AWS Certified Solutions Architect - Professional](https://aws.amazon.com/certification/certified-solutions-architect-professional) is the professional level Solutions Architect Certification and probably the most difficult AWS Exam. It covers the following domains. Design for Organisational Complexity, Design for New Solutions, Migration Planning, Cost Control and Continuous Improvement for Existing Solutions.
|
131 |
+
|
132 |
+
#### Recommended Online Training
|
133 |
+
1. [Cantrill.io](https://learn.cantrill.io/p/aws-certified-solutions-architect-professional)
|
134 |
+
2. [ACloudGuru](https://learn.acloud.guru/course/aws-certified-solutions-architect-professional/dashboard)
|
135 |
+
|
136 |
+
|
137 |
+
## AWS Speciality Certifications
|
138 |
+
|
139 |
+
1. [AWS Certified Advanced Networking - Specialty](https://aws.amazon.com/certification/certified-advanced-networking-specialty)
|
140 |
+
2. [AWS Certified Data Analytics - Specialty](https://aws.amazon.com/certification/certified-data-analytics-specialty)
|
141 |
+
3. [AWS Certified Database - Specialty](https://aws.amazon.com/certification/certified-database-specialty)
|
142 |
+
4. [AWS Certified Machine Learning – Specialty](https://aws.amazon.com/certification/certified-machine-learning-specialty)
|
143 |
+
5. [AWS Certified Security - Specialty](https://aws.amazon.com/certification/certified-security-specialty)
|
guides/cloud/aws_partner_certs.txt
ADDED
@@ -0,0 +1,75 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# AWS Training & Certification
|
2 |
+
|
3 |
+
- [Purpose of this guide](#purpose-of-this-guide)
|
4 |
+
- [AWS Certification](#aws-certification)
|
5 |
+
- [Creating your accounts](#creating-your-accounts)
|
6 |
+
- [AWS Training Account](#aws-training-account)
|
7 |
+
- [AWS Partner Network Account](#aws-partner-network-account)
|
8 |
+
- [Linking your Amazon and AWS Partner Accounts](#linking-your-amazon-and-aws-partner-accounts)
|
9 |
+
- [Learning Paths](#learning-paths)
|
10 |
+
- [AWS Business Professional](#aws-business-professional)
|
11 |
+
- [AWS Technical Professional](#aws-technical-professional)
|
12 |
+
- [Employee offboarding](#employee-offboarding)
|
13 |
+
|
14 |
+
## Purpose of this guide
|
15 |
+
|
16 |
+
Made Tech are an [AWS Advanced Consulting Partner](https://partners.amazonaws.com/partners/001E0000016ppWOIAY/Made%20Tech) and require all Made Tech employees to create a user account within the AWS Partner Portal as part of their onboarding process for a number of reasons.
|
17 |
+
|
18 |
+
1. Access to free AWS Partner Training materials.
|
19 |
+
2. Linking employees personal AWS Certification accounts to our Partner account.
|
20 |
+
|
21 |
+
# AWS Certification
|
22 |
+
|
23 |
+
As a Made Tech employee you will be encouraged and supported in taking AWS Certifications. You are advised to create your AWS Certification account using a personal email address so any AWS Certifications you achieve belong to you. This can be the same Amazon account login that you use for doing your shopping on [Amazon](https://www.amazon.co.uk), so you maybe already have an account!
|
24 |
+
|
25 |
+
|
26 |
+
AWS has an extensive Training and Certification framework, and there is a lot of great content we can utilise as an AWS Partner to develop and improve our knowledge when working with AWS services.
|
27 |
+
|
28 |
+
We aim for every Made Tech employee to achieve the AWS Cloud Practitioner Certification, and the AWS Partner Portal provides some valuable free entry level training paths towards taking the Cloud Practitioner exam.
|
29 |
+
|
30 |
+
# Creating your accounts
|
31 |
+
|
32 |
+
There are 2 types of accounts needed to take full advantage of the AWS Training and Certification platform.
|
33 |
+
|
34 |
+
- [AWS Training Account](#aws-training-account)
|
35 |
+
- [AWS Partner Network Account](#aws-partner-network-account)
|
36 |
+
|
37 |
+
## AWS Training Account
|
38 |
+
|
39 |
+
If you have a personal Amazon account you can simply log in to [AWS Training and Certification](https://www.aws.training/SignIn) using the **left side** login.
|
40 |
+
|
41 |
+
This will land you on yet another page where you should click `Login to your account` and will eventually land you in your [Certmetrics Account](https://www.certmetrics.com/amazon/).
|
42 |
+
|
43 |
+
## AWS Partner Network Account
|
44 |
+
|
45 |
+
Head over to the [AWS Partner Network registration guide](aws_partner_registration.md) that will take you through the steps to create an account on the Amazon Partner Network.
|
46 |
+
|
47 |
+
# Linking your Amazon and AWS Partner Accounts
|
48 |
+
|
49 |
+
In order for your AWS Certifications to appear within the Made Tech AWS Partner account, you need to link your person Amazon account to your Amazon Partner Network account.
|
50 |
+
|
51 |
+
1. [Log in to the AWS Partner Network](https://partnercentral.awspartner.com/APNLogin) with your `@madetech.com` email address.
|
52 |
+
2. Click on `View My Profile` from the left hand `QUICK LINKS` menu.
|
53 |
+
3. Click the blue `Edit` button.
|
54 |
+
4. Under `AWS CERTIFICATION` add your personal AWS Certification email address to the `AWS T&C Account Email` field, and select `Yes` for `I consent to share my AWS Certifications with "Made Tech" *`
|
55 |
+
|
56 |
+
Your AWS Certifications will not immediately appear, so check back at a later date.
|
57 |
+
|
58 |
+
# Learning Paths
|
59 |
+
|
60 |
+
## AWS Business Professional
|
61 |
+
|
62 |
+
The recommended AWS Partner training path for non-technical roles is the [AWS Business Professional](https://aws.amazon.com/partners/training/path-bus-pro/).
|
63 |
+
|
64 |
+
## AWS Technical Professional
|
65 |
+
|
66 |
+
The recommended AWS Partner training path for technical roles is the [AWS Technical Professional](https://aws.amazon.com/partners/training/path-tech-pro/).
|
67 |
+
|
68 |
+
# Employee offboarding
|
69 |
+
|
70 |
+
When an employee leaves Made Tech, they should unlink their personal Certification email address from their `@madetech.com` AWS Partner Account. This should be done while they have access to their `@madetech.com` email address as part of their offboarding.
|
71 |
+
|
72 |
+
1. [Log in to the AWS Partner Network](https://partnercentral.awspartner.com/APNLogin) with your `@madetech.com` email address.
|
73 |
+
2. Click on `View My Profile` from the left hand `QUICK LINKS` menu.
|
74 |
+
3. Click the blue `Edit` button.
|
75 |
+
4. Under `AWS CERTIFICATION` remove your personal AWS Certification email address to the `AWS T&C Account Email` field, and select `No` for `I consent to share my AWS Certifications with "Made Tech" *`
|
guides/cloud/aws_partner_registration.txt
ADDED
@@ -0,0 +1,68 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# AWS Partner Network
|
2 |
+
|
3 |
+
- [AWS Partner Network](#aws-partner-network)
|
4 |
+
- [Registration](#registration)
|
5 |
+
- [Step 1: Sign in](#step-1-sign-in)
|
6 |
+
- [Step 2: Join AWS Partner Network](#step-2-join-aws-partner-network)
|
7 |
+
- [Step 3: Let's get started](#step-3-lets-get-started)
|
8 |
+
- [Step 4: Create an APN account](#step-4-create-an-apn-account)
|
9 |
+
- [Step 5: Security code and password](#step-5-security-code-and-password)
|
10 |
+
- [Step 6: Why would you like to join APN?](#step-6-why-would-you-like-to-join-apn)
|
11 |
+
- [Step 7: Tell us about yourself](#step-7-tell-us-about-yourself)
|
12 |
+
- [Step 8: Congratulations](#step-8-congratulations)
|
13 |
+
|
14 |
+
## Registration
|
15 |
+
|
16 |
+
### Step 1: Sign in
|
17 |
+
|
18 |
+
Go to the [aws.training sign in page](https://www.aws.training/SignIn) and click the right hand "Sign In" button to begin creating your Amazon Partner Network account.
|
19 |
+
|
20 |
+

|
21 |
+
|
22 |
+
### Step 2: Join AWS Partner Network
|
23 |
+
|
24 |
+
Click "Join AWS Partner Network"
|
25 |
+
|
26 |
+

|
27 |
+
|
28 |
+
### Step 3: Let's get started
|
29 |
+
|
30 |
+
Click "Let's get started"
|
31 |
+
|
32 |
+

|
33 |
+
|
34 |
+
### Step 4: Create an APN account
|
35 |
+
|
36 |
+
When creating an APN account you should use your **@madetech.com** email address to register.
|
37 |
+
|
38 |
+
Once you have registered, a security code will be emailed to you to use in the next step.
|
39 |
+
|
40 |
+

|
41 |
+
|
42 |
+
### Step 5: Security code and password
|
43 |
+
|
44 |
+
Enter the security code from the email you received along with a password.
|
45 |
+
|
46 |
+

|
47 |
+
|
48 |
+
### Step 6: Why would you like to join APN?
|
49 |
+
|
50 |
+
Select how you heard about APN and what you are looking for support with.
|
51 |
+
|
52 |
+

|
53 |
+
|
54 |
+
### Step 7: Tell us about yourself
|
55 |
+
|
56 |
+
Fill out your contact information, whether you consent to share training and certifications with MadeTech and whether you'd like to receive AWS news and offers.
|
57 |
+
|
58 |
+
**NOTE**
|
59 |
+
|
60 |
+
- Use your **personal Amazon email** for the "AWS Training and Certification Account Email" section of the form in order to take your certifications with you should you leave MadeTech.
|
61 |
+
|
62 |
+

|
63 |
+
|
64 |
+
### Step 8: Congratulations
|
65 |
+
|
66 |
+
You have now registered for the AWS Partner Network
|
67 |
+
|
68 |
+

|
guides/cloud/aws_sandbox.txt
ADDED
@@ -0,0 +1,95 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Made Tech AWS Sandbox
|
2 |
+
|
3 |
+
## Overview
|
4 |
+
|
5 |
+
The Made Tech AWS Sandbox accounts are primarily used for individuals' personal development and testing. We run [AWS SSO](https://aws.amazon.com/single-sign-on/) to simplify and secure the IAM aspect of accessing this account.
|
6 |
+
|
7 |
+
There are 2 accounts you can use:
|
8 |
+
- [Playground account](#playground-account)
|
9 |
+
- [Devops Pairing Interviews Account](#devops-pairing-interviews-account)
|
10 |
+
|
11 |
+
## Playground account
|
12 |
+
|
13 |
+
### Usage Policy
|
14 |
+
|
15 |
+
This AWS account should only be used for temporary short lived test type projects and resources are destroyed every Friday evening.
|
16 |
+
|
17 |
+
The Terraform and config for this cleanup task lives in this [aws-sandbox](https://github.com/madetech/aws-sandbox) GitHub repo.
|
18 |
+
|
19 |
+
### Security
|
20 |
+
|
21 |
+
The AWS Sandbox account is restricted by several service control policies blocking creation of IAM users, and is locked down to three regions (eu-west-1, eu-west-2 and us-east-1)
|
22 |
+
|
23 |
+
### Access
|
24 |
+
|
25 |
+
1. Request for a new user account in the #cop-cloud Slack channel in the `SandboxUsers` group.
|
26 |
+
2. AWS SSO login credentials will be emailed to you.
|
27 |
+
3. Follow the instructions and setup MFA.
|
28 |
+
4. Login via [https://madetech.awsapps.com/start/](https://madetech.awsapps.com/start/)
|
29 |
+
|
30 |
+
### CLI Usage
|
31 |
+
|
32 |
+
Use [aws-vault](https://github.com/99designs/aws-vault) to run CLI commands.
|
33 |
+
|
34 |
+
Reasons for using this tool can be found [here](https://github.com/99designs/aws-vault#how-it-works).
|
35 |
+
|
36 |
+
1. Install [aws-vault](https://github.com/99designs/aws-vault#installing)
|
37 |
+
2. Add the following config to your `~/.aws/config` file.
|
38 |
+
```
|
39 |
+
[profile mt-playground]
|
40 |
+
sso_start_url=https://madetech.awsapps.com/start
|
41 |
+
sso_region=eu-west-2
|
42 |
+
sso_account_id=261219435789
|
43 |
+
sso_role_name=SandboxUser
|
44 |
+
output=json
|
45 |
+
```
|
46 |
+
|
47 |
+
3. Test with `aws-vault exec mt-playground -- aws sts get-caller-identity`
|
48 |
+
4. This pops open a browser where you need to login to create a session.
|
49 |
+
5. Run any CLI based command in the same way e.g `aws-vault exec mt-playground -- terraform apply`
|
50 |
+
|
51 |
+
## Devops Pairing Interviews Account
|
52 |
+
|
53 |
+
This is a separate account for use in devops pairing exercises.
|
54 |
+
|
55 |
+
This account differs in two ways from the main sandbox:
|
56 |
+
- It allows the creation of iam users.
|
57 |
+
- It **deletes all resources inside it every day!**
|
58 |
+
|
59 |
+
### Access
|
60 |
+
Only employees that are conducting devops pairing interviews will be given access
|
61 |
+
|
62 |
+
1. Request your user account to be added to the `DevopsPairingInterviewer` group in the #cop-cloud Slack channel.
|
63 |
+
|
64 |
+
### CLI Usage
|
65 |
+
|
66 |
+
Use [aws-vault](https://github.com/99designs/aws-vault) to run CLI commands.
|
67 |
+
|
68 |
+
Reasons for using this tool can be found [here](https://github.com/99designs/aws-vault#how-it-works).
|
69 |
+
|
70 |
+
1. Install [aws-vault](https://github.com/99designs/aws-vault#installing)
|
71 |
+
2. Add the following config to your `~/.aws/config` file.
|
72 |
+
|
73 |
+
```
|
74 |
+
[profile mt-devops]
|
75 |
+
sso_start_url=https://madetech.awsapps.com/start
|
76 |
+
sso_region=eu-west-2
|
77 |
+
sso_account_id=612473995106
|
78 |
+
sso_role_name=SandboxUser
|
79 |
+
output=json
|
80 |
+
```
|
81 |
+
|
82 |
+
## Admin actions
|
83 |
+
This section is for SSO administrators (i.e. pepole in the `@sandbox-admins` group on slack)
|
84 |
+
|
85 |
+
### Adding new users
|
86 |
+
For when a user has requested to be added to the AWS sandbox
|
87 |
+
- Login to sso https://madetech.awsapps.com/start#/
|
88 |
+
- Click on: `aws account` > `Made Tech` > `Management console`
|
89 |
+
- Now go to https://eu-west-2.console.aws.amazon.com/singlesignon/identity/home?region=eu-west-2#!/users
|
90 |
+
- On the top right click `add user`
|
91 |
+
- Fill in their details (use the part before the @ in their email as username)
|
92 |
+
- Add them to the "SandboxUsers" group
|
93 |
+
- They should now get a email invite to join (valid for the next 7 days)
|
94 |
+
|
95 |
+
|
guides/cloud/azure_partner_certs.txt
ADDED
@@ -0,0 +1,32 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Azure Certification
|
2 |
+
|
3 |
+
- [Azure Certification](#azure-certification)
|
4 |
+
- [Purpose of this guide](#purpose-of-this-guide)
|
5 |
+
- [Azure Partnership](#azure-partnership)
|
6 |
+
- [Linking your Azure certifications to the Azure Partner Portal](#linking-your-azure-certifications-to-the-azure-partner-portal)
|
7 |
+
|
8 |
+
## Purpose of this guide
|
9 |
+
|
10 |
+
Made Tech are a Microsoft Azure Partner and require all Made Tech employees with Microsoft certifications to link their Microsoft Certification Account to the Made Tech Azure Partner Portal as part of their onboarding process for a number of reasons.
|
11 |
+
|
12 |
+
1. Access to free Azure Partner Training materials.
|
13 |
+
2. Maintaining and aquiring partner levels with Azure.
|
14 |
+
|
15 |
+
# Azure Partnership
|
16 |
+
|
17 |
+
As a Made Tech employee you will be encouraged and supported in taking Azure Certifications. You are advised to create your Microsoft Certification account using a personal email address so any Azure Certifications you achieve belong to you.
|
18 |
+
|
19 |
+
Azure has an extensive Training and Certification framework, and there is a lot of great content we can utilise as a Microsoft Azure Partner to develop and improve our knowledge when working with Azure services.
|
20 |
+
|
21 |
+
# Linking your Azure certifications to the Azure Partner Portal
|
22 |
+
|
23 |
+
In order for your Azure Certifications to appear within the Made Tech Azure Partner Portal, you need to link your personal Microsoft Certification Account to the Made Tech Azure Partner Portal.
|
24 |
+
|
25 |
+
Before you do this, you will need to have completed at least one exam or certification in the [Microsoft Learn portal](https://learn.microsoft.com/).
|
26 |
+
|
27 |
+
1. Go to the [Partner Portal](https://partner.microsoft.com/pc/Users/MyAccount).
|
28 |
+
2. Sign in using your **Made Tech Microsoft account**. This should take you to the account page, as shown below.
|
29 |
+
3. Click on the “Associate Microsoft Learning account” button.
|
30 |
+

|
31 |
+
4. This will take you to a new log-in page. Here enter your personal **Microsoft Certification Account** credentials (these are the ones you used to sign up for the exam).
|
32 |
+
5. This will then redirect you back to the above account page and show that you have successfully linked your accounts to the Partner Portal.
|
guides/compensation/expenses.txt
ADDED
@@ -0,0 +1,32 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Expenses
|
2 |
+
|
3 |
+
There is now a fully documented Made Tech expenses policy which covers trains, travel, hotel accommodation, and reimbursement of other business expenses. As it is more detailed than the previous guidance, the policy has been changed to an internally facing document for now. [You can find the document here](https://docs.google.com/document/d/1NthAC1xepzAI07o40c6WxXHbPttNxaCidhJ22eJHD-k/edit#).
|
4 |
+
|
5 |
+
There is additional information on [equipment to enable you to work from home](../../benefits/work_ready.md), and [eye tests](expenses/eyetest.md) on those pages.
|
6 |
+
|
7 |
+
## Travel
|
8 |
+
Made Tech is also now using TravelPerk to enable you to book all your business travel in one place. Payment is made directly by Finance so you don’t have to pay for travel yourself. For more information on when and how to use this take a look at the [TravelPerk document](https://docs.google.com/document/d/12NiB2QxHZ5k8ajqP95fOo2I-GBKZQLuzQutKAiem0DQ/edit#) (internal link).
|
9 |
+
|
10 |
+
### Railcards
|
11 |
+
You can expense Railcards for the use of business travel. Made Tech will reimburse the price of any yearly railcard purchased from April 26th 2023 onwards. If you leave Made Tech you will not be charged for it and dont need to return it, but you cannot expense a railcard during your notice period.
|
12 |
+
|
13 |
+
To purchase and expense a railcard you need to;
|
14 |
+
- purchase a railcard
|
15 |
+
- add it to your TravelPerk account
|
16 |
+
- take a screenshot to show that it has been added
|
17 |
+
- share the image and receipt on Xero when expensing it back.
|
18 |
+
|
19 |
+
## How do you expense?
|
20 |
+
|
21 |
+
Expense claims need to be submitted via [Xero](https://login.xero.com/identity/user/login). If you don’t have a login please drop a message in #ops-finance or email [[email protected]](mailto:[email protected]).
|
22 |
+
|
23 |
+
There is more detail in the policy but all claims must be made within 90 days, and will typically be paid within 2 weeks.
|
24 |
+
|
25 |
+
There are also some approval processes in place:
|
26 |
+
- Normal expenses: Claims that align with the policy will be approved but any claims that are outside of the guidelines will need approval from your Head of Department.
|
27 |
+
- Account expenses: Expenses that are aligned to a specific delivery or account (e.g. client entertainment, travel to meetings, etc) should be agreed with the Delivery Manager and/or account team in advance.
|
28 |
+
- Events and conferences: Expenses need to be approved in advance by the relevant Head of Department.
|
29 |
+
|
30 |
+
For all other information please read the policy document and send any questions to #ops-finance or [[email protected]](mailto:[email protected]).
|
31 |
+
|
32 |
+
|
guides/compensation/expenses/eyetest.txt
ADDED
@@ -0,0 +1,19 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Eye Test Expenses
|
2 |
+
|
3 |
+
Everyone is able to claim back the costs of an annual eye test. You need to:
|
4 |
+
|
5 |
+
- Book the eye test yourself and get a receipt
|
6 |
+
- Submit the receipt for the eye test through Xero, using the category 'Staff discrentionary benefit'.
|
7 |
+
|
8 |
+
## Claiming for Lenses and Frames
|
9 |
+
|
10 |
+
If the outcome of the eye test is that you require glasses for the use of Display Screen Equipment (DSE) or (visual/video display unit (VDU), where an ordinary prescription is not suitable, then Made Tech will make a contribution towards the costs of a pair of glasses.
|
11 |
+
|
12 |
+
- Made Tech will pay for the lenses plus an additional £60 toward any frames that you choose.
|
13 |
+
- After you purchase your frames and lenses, submit the receipts through Xero.
|
14 |
+
|
15 |
+
Please request that the optician provides a report/copy of the prescription indicating these are required specifically for DSE or VDU use.
|
16 |
+
|
17 |
+
**Note:** If you use Westfield Health you may want to reclaim the cost using their service instead, especially if you wish to purchase more expensive frames.
|
18 |
+
|
19 |
+
If you have any questions on this please contact #ops
|
guides/compensation/salary_pay_slips.txt
ADDED
@@ -0,0 +1,9 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Salary & Pay Slips
|
2 |
+
|
3 |
+
We're paid on the 28th of the month, or the Friday before if the 28th falls on a weekend or during a bank holiday.
|
4 |
+
|
5 |
+
Payroll cut off usually falls on the 18th of the month and so if you started on or after that date, you would likely fall into the following month's pay run and recieve backpay for any period worked in the previous month. For example if you started on the 23rd January, your first pay day would be the 28th February and you would recieve pay from 23rd Jan - 28th Feb in that first pay check.
|
6 |
+
|
7 |
+
Our Finance team are responsible for payroll and you will receive an invite to register for our payslip provider just before your first pay day and then receive an e mail each month on pay day confirming when your pay slip is available.
|
8 |
+
|
9 |
+
If you've got any queries on your salary or payslip, please send these to [email protected]
|
guides/compensation/salary_reviews.txt
ADDED
@@ -0,0 +1,5 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Salary Reviews
|
2 |
+
|
3 |
+
Salaries are reviewed in line with our pay review policy - once, each business financial year. They may be adjusted taking into consideration business performance, individual performance and market rates. We reserve the right not to increase salary at review. An increase one year does not set any precedent or influence any future reviews.
|
4 |
+
|
5 |
+
The other path to a salary adjustment is via our Internal mobility process (promotions or lateral moves) within the financial year.
|
guides/contributing_to_the_handbook.txt
ADDED
@@ -0,0 +1,77 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Contributing to the Handbook
|
2 |
+
|
3 |
+
This guide aims to make it easier to submit changes to the Handbook without using `git` or a text editor.
|
4 |
+
|
5 |
+
## Updating and adding pages in Github
|
6 |
+
|
7 |
+
### Creating a page
|
8 |
+
|
9 |
+
1. [Go to the handbook.](https://github.com/madetech/handbook)
|
10 |
+
2. Click through to the folder you want.
|
11 |
+
3. Click "Create new file"
|
12 |
+
4. Type out your contents under "Edit new file" using [Markdown](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
|
13 |
+
5. Preview your changes at any time by clicking "Preview".
|
14 |
+
6. When you're happy with your page, write a short description under "Commit new file". For example, "Add Flexible Holiday Page".
|
15 |
+
7. Select "Create a new branch for this commit" and give it a name relevant to your change. For example, "add-flexible-holiday-page".
|
16 |
+
8. Submit the change by clicking "Propose new file".
|
17 |
+
9. You will be then be able to create a Pull Request to get review of your new page. Click "Create pull request", then share the link with people!
|
18 |
+
|
19 |
+
### Updating a page
|
20 |
+
|
21 |
+
1. [Go to the handbook.](https://github.com/madetech/handbook)
|
22 |
+
2. Navigate to the page you wish to update.
|
23 |
+
3. Click the pencil button in the top right
|
24 |
+
4. Make the necessary changes using [Markdown](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
|
25 |
+
5. Preview your changes at any time by clicking "Preview".
|
26 |
+
6. When you're happy with your page, click "Commit changes" and write a short description under "Commit message". For example "update pension scheme page to include the people team email"
|
27 |
+
7. Select "Create a new branch for this commit" and give it a name relevant to your change. For example, "update-flexible-holiday-page".
|
28 |
+
8. Submit the change by clicking "Propose changes".
|
29 |
+
9. You will be then be able to create a Pull Request to get review of your new page. Click "Create pull request", then share the link with people!
|
30 |
+
|
31 |
+
### Addressing review
|
32 |
+
|
33 |
+
1. Click on the "Files changed" tab on your Pull Request.
|
34 |
+
2. Click on the pencil icon in the toolbar above the file content.
|
35 |
+
3. Make your changes as before, previewing until you're happy with them.
|
36 |
+
4. Under "Commit Changes" describe what this change does. For example, "Fix typo" or "Extend section on getting a company credit card".
|
37 |
+
5. Keep the selected option as "Commit directly". You don't need to create a new branch for every change.
|
38 |
+
6. Press "Commit changes".
|
39 |
+
|
40 |
+
### Finalising the change
|
41 |
+
|
42 |
+
1. Get feedback from the wider company and address any feedback. Once you've had your Pull Request approved, you're ready to finalise your change.
|
43 |
+
2. On the "Conversation" tab of your Pull Request, click "Merge pull request".
|
44 |
+
3. Your new page will now be visible in the Handbook.
|
45 |
+
|
46 |
+
## Approval and merging
|
47 |
+
|
48 |
+
There are broadly two types of change to the handbook, each with a different approval flow.
|
49 |
+
If in doubt, default to the most strict method (Significant changes or additions) or ask for advice on Slack.
|
50 |
+
|
51 |
+
1. Significant changes or additions
|
52 |
+
2. Uncontroversial clarifications
|
53 |
+
|
54 |
+
|
55 |
+
### 1. Significant changes or additions
|
56 |
+
|
57 |
+
This includes changes to policies, changes to the way people are expected to work, changes that express a departure from a previous community norm, etc.
|
58 |
+
|
59 |
+
1. Open pull request
|
60 |
+
2. Shout about the pull request in all relevant Slack channels. This should include announcements, but if it relates to a particular part of Made Tech, also in
|
61 |
+
the channels more relevant to those people.
|
62 |
+
3. Allow enough time for people to review and comment, remembering that they probably have busy schedules. One to two weeks is probably sensible.
|
63 |
+
4. Manage the conversation, seek approvals on GitHub, address feedback.
|
64 |
+
5. When it feels like something close to consensus is established, merge.
|
65 |
+
|
66 |
+
Consensus is subjective, and we can't make a rule that catches all of the important ways it can look.
|
67 |
+
If you're unsure if you've got enough of it, reach out to the community on Slack.
|
68 |
+
|
69 |
+
### 2. Uncontroversial clarifications
|
70 |
+
|
71 |
+
This includes spelling mistakes, poorly worded sections, and writing something down that we all are doing anyway,
|
72 |
+
|
73 |
+
1. Open pull request
|
74 |
+
2. Shout about it in relevant channels
|
75 |
+
3. Address feedback
|
76 |
+
4. Wait for an approval
|
77 |
+
5. Merge
|
guides/equality-diversity-and-inclusion/README.txt
ADDED
@@ -0,0 +1,21 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Equality, Diversity & Inclusion at Made Tech
|
2 |
+
|
3 |
+
Creating a better, fairer society is part of our purpose as an organisation. This starts with our people.
|
4 |
+
|
5 |
+
We strive to make Made Tech an equitable, diverse and inclusive workplace and to provide a working environment that is free from discrimination at all times.
|
6 |
+
|
7 |
+
We understand that everyone has varying needs. We’ll work to make sure that everyone’s needs are supported and met.
|
8 |
+
|
9 |
+
We recognise that our different backgrounds, experiences, views, beliefs, cultures and physical/neurological differences represented enrich us as a company and as individuals. We embrace diversity in all of our activities and acknowledge that variety and difference are integral to the success and future development of our business.
|
10 |
+
|
11 |
+
Read our [Equality, Diversity & Inclusion Policy](policy.md).
|
12 |
+
|
13 |
+
## Teams and communities
|
14 |
+
|
15 |
+
We have a number of ways we support equality, diversity and inclusion at Made Tech.
|
16 |
+
|
17 |
+
We have a [diversity and inclusion service team](about-service-team.md) who are responsible for defining our strategy, setting KPIs and objectives, supporting the wider organisation to take action to deliver on these objectives, and reporting on progress to our leadership team and the wider company. This team is an escalation point for D&I related issues and manages the operation of equality data collection and reporting.
|
18 |
+
|
19 |
+
We have a regular forum, our [diversity and inclusion community meetup](about-di-community.md) for discussing diversity and inclusion matters, scrutinising decisions being made by the diversity and inclusion service team, and making suggestions for future strategy.
|
20 |
+
|
21 |
+
We support [open and closed community groups](about-open-and-closed-community.md) that meet to share experiences, raise issues and promote various aspects of diversity and inclusion. Open communities are free for anyone to join while closed communities are available to join by invite if you identify as belonging to that community.
|
guides/equality-diversity-and-inclusion/about-di-community.txt
ADDED
@@ -0,0 +1,40 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Diversity and inclusion community
|
2 |
+
|
3 |
+
The diversity and inclusion community is an opportunity for anyone at Made Tech to join the conversation on how we progress and promote diversity and inclusion across the business.
|
4 |
+
|
5 |
+
In particular it was set up to:
|
6 |
+
|
7 |
+
- Be open to anyone
|
8 |
+
- Meet on a regular basis
|
9 |
+
- Discuss ideas and issues
|
10 |
+
- Contribute to and review the strategy and plans of the [diversity and inclusion service team](./about-service-team.md)
|
11 |
+
- Hold the diversity and inclusion service team to account for delivering on their plan
|
12 |
+
- Review content changes before they are opened for wider review in the Handbook
|
13 |
+
- Escalate issues
|
14 |
+
|
15 |
+
## When and how does the community meet?
|
16 |
+
|
17 |
+
The community meets on a fortnightly basis via Google Meet. It is facilitated by a representative from the [diversity and inclusion service team](./about-service-team.md) or another nominated individual. The format uses the [Lean Coffee](https://leancoffee.org/) approach where topics can be suggested, prioritised by voting and then discussed in order. The invite is open on Google Calendar so you may add yourself to be reminded, [ask on Slack](https://madetechteam.slack.com/archives/CRAJF24CR) for more information.
|
18 |
+
|
19 |
+
From time-to-time the diversity and inclusion service team may change the format as it sees fit to deliver on its goals and objectives.
|
20 |
+
|
21 |
+
## Can I see what is discussed without joining?
|
22 |
+
|
23 |
+
Minutes are added to the [inclusion repository](https://github.com/madetech/inclusion) for all meetings from the community up to 27/10/2021.
|
24 |
+
More recent minutes are available in this [Google Doc](https://docs.google.com/document/d/1JtDxGlA2v1uX2dycJQKZ_8Ff41t8jeriWqzFkGPQI7w/view)
|
25 |
+
|
26 |
+
## How else can I get involved?
|
27 |
+
|
28 |
+
The community also hangs out on [Slack](https://madetechteam.slack.com/archives/CRAJF24CR). You may also consider joining one or more [open or closed community groups](about-open-and-closed-community.md).
|
29 |
+
|
30 |
+
## Who can join?
|
31 |
+
|
32 |
+
Anyone can join the community meet up and Slack channel. It is attended by all available members of the [diversity and inclusion service team](./about-service-team.md) and anyone else who wants to join in or just watch. It’s totally fine to join for part of the meet up and to keep your camera off if you prefer.
|
33 |
+
|
34 |
+
## How do I raise an issue?
|
35 |
+
|
36 |
+
Issues can be raised using the Lean Coffee format ahead of and during community meetings. This can be useful for organisational-wide issues but if the issue is about someone’s personal experience it may be best to talk to a member of the [diversity and inclusion service team](./about-service-team.md) first.
|
37 |
+
|
38 |
+
Anyone can contact the service team about an issue, or you could choose to raise it through a member of the diversity and inclusion community, or your diversity community group. Details on who to raise issues to are documented in the [#supply-diversity-and-inclusion Slack channel](https://madetechteam.slack.com/archives/CRAJF24CR).
|
39 |
+
|
40 |
+
We have documented general guidance on [raising an issue](https://github.com/madetech/handbook/blob/main/guides/welfare/raising_an_issue.md) elsewhere in the Handbook, or you can get in touch with the People team if you’re not sure who the best person is to speak to.
|
guides/equality-diversity-and-inclusion/about-open-and-closed-community.txt
ADDED
@@ -0,0 +1,45 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Open and closed communities
|
2 |
+
|
3 |
+
Open and closed community groups are collectives of individuals who come together to discuss particular challenges, ideas and experiences with regards to a particular community. These groups are self-organised, and will have their own ways of communicating and scheduling events.
|
4 |
+
|
5 |
+
**An open community group** has open membership meaning anyone can join the group’s Slack channel, events and meetings.
|
6 |
+
|
7 |
+
**A closed community group** is open only to those who are members of those communities. For example, to join the “women in tech” closed community group you would need to identify as a woman in order to have your request for an invite to be accepted. To join you will need to reach out to an organising member to request an invite.
|
8 |
+
|
9 |
+
You can find a list of open and closed communities in the description of the [diversity and inclusion Slack channel](https://madetechteam.slack.com/archives/CRAJF24CR). We share this list during onboarding weeks too.
|
10 |
+
|
11 |
+
## Starting a group
|
12 |
+
|
13 |
+
Anyone can start an open or closed community group as long as they comply with our [Equality, Diversity & Inclusion Policy](policy.md). To start one you should:
|
14 |
+
|
15 |
+
- Create an open or closed or both Slack channel for your group
|
16 |
+
- Notify the [diversity and inclusion service team](about-service-team.md) so they can add your group to the lists we share in Slack and during onboarding
|
17 |
+
- Document either in Slack or a shareable file the purpose of your group and details on how and when you meet
|
18 |
+
- If a closed group, provide details to the diversity and inclusion team on how someone can ask for an invite and what criteria they need to meet
|
19 |
+
|
20 |
+
## Managing a group
|
21 |
+
|
22 |
+
Open and closed community groups are self-organising and therefore need active management by its members to keep going. Civil servants have published a [“community development handbook”](https://www.gov.uk/government/publications/community-development-handbook/community-development-handbook) that provides lots of guidance on how to sustain a community.
|
23 |
+
|
24 |
+
**Please note:** maintaining community groups is mentally and physically tiring – to keep the community sustainable this burden should not just fall on one or two individuals.
|
25 |
+
|
26 |
+
## Support and budgets available
|
27 |
+
|
28 |
+
There are a variety of ways we support open and closed communities to self-organise:
|
29 |
+
|
30 |
+
- The culture and happiness team have budgets available for socials for your group and can provide support in organising events you may want to hold
|
31 |
+
- We have diversity and inclusion and culture and happiness budget available for paying speakers to talk at open or closed events
|
32 |
+
- We are organising a social and awareness calendar for key events that are relevant for our various community groups – this calendar enables our marketing team, employer branding and culture and happiness teams to organise and promote awareness
|
33 |
+
- Our offices can be used for meetings and our existing communication platforms (Slack, Google Meet) can be used to virtual meet
|
34 |
+
|
35 |
+
Ask on Slack if you want to take advantage of this support. If something is not listed here, please speak to the [diversity and inclusion service team](about-service-team.md) who will be happy to find an answer as to whether we can support your request.
|
36 |
+
|
37 |
+
## Issue escalation
|
38 |
+
|
39 |
+
Community groups form around particular identities, needs and/or experiences. If issues are discussed by these groups, they can be raised with the diversity and inclusion service team to be reviewed and supported.
|
40 |
+
|
41 |
+
If an individual has reported an issue to a group, it may be too much of a burden on that individual to escalate the issue themselves. In this case, a nominated individual from the group should be nominated to raise the issue on the affected individuals behalf.
|
42 |
+
|
43 |
+
Details on who to raise issues to are documented in the [#supply-diversity-and-inclusion Slack channel](https://madetechteam.slack.com/archives/CRAJF24CR).
|
44 |
+
|
45 |
+
We have documented general guidance on [raising an issue](https://github.com/madetech/handbook/blob/main/guides/welfare/raising_an_issue.md) elsewhere in the Handbook, or you can get in touch with the People team if you’re not sure who the best person is to speak to.
|
guides/equality-diversity-and-inclusion/about-service-team.txt
ADDED
@@ -0,0 +1,38 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Diversity and inclusion service team
|
2 |
+
|
3 |
+
The diversity and inclusion service team are responsible for and empowered to shape and deliver changes to drive improvements that lead to Made Tech being a more diverse and inclusive place to work. We see this as a necessary ongoing investment needed to ensure equal opportunities are brought about by our work and that we maintain an inclusive culture as we grow.
|
4 |
+
|
5 |
+
Specifically, the diversity and inclusion service team is funded to and is responsible for:
|
6 |
+
|
7 |
+
- Defining our strategy
|
8 |
+
- Setting KPIs and objectives
|
9 |
+
- Co-creating change plans with other service teams
|
10 |
+
- Supporting the wider organisation to take action to deliver on these objectives
|
11 |
+
- Reporting on progress to our leadership team
|
12 |
+
- Being an escalation point with the ability to raise issues at an executive and board-level
|
13 |
+
- Manage operation of equality data collection
|
14 |
+
- Reporting on equality data to drive future decisions and investments
|
15 |
+
- Running the [diversity and inclusion community](about-di-community.md)
|
16 |
+
- Supporting [open and closed communities](about-open-and-closed-community.md) to form and operate
|
17 |
+
|
18 |
+
## Membership
|
19 |
+
|
20 |
+
It is a requirement that an executive director and a member of the leadership team are members of the service team to ensure the team continues to have sufficient authority to make necessary decisions.
|
21 |
+
|
22 |
+
We will run an open recruitment process for other membership places of no less than two places being available per quarter to anyone at Made Tech.
|
23 |
+
|
24 |
+
## Meetings
|
25 |
+
|
26 |
+
The service team shall meet with all available members on a weekly basis to review goals, committed actions and issues. The meeting is 45 minutes and is run by the team’s directly responsible individual or a nominated other.
|
27 |
+
|
28 |
+
The service team is also responsible for ensuring the diversity and inclusion community meets on a regular basis.
|
29 |
+
|
30 |
+
Minutes for these meetings are publically available.
|
31 |
+
Historical records (03/09/2021 - 29/10/2021) are available on [GitHub](https://github.com/madetech/inclusion/tree/HEAD/minutes/SA-weekly)
|
32 |
+
More recent minutes (05/11/2021 onwards) are available in a [Google Doc](https://docs.google.com/document/d/1KlCwH72h7zqmbRFugwTzbcn_fawofRysWyi6qZRaZXg/view)
|
33 |
+
|
34 |
+
## Managing issues
|
35 |
+
|
36 |
+
The service team shall be available for issues to be raised via members of the diversity and inclusion community, open/closed communities or any other individual at Made Tech. Details on who to raise issues to should be documented in the [#supply-diversity-and-inclusion](https://madetechteam.slack.com/archives/CRAJF24CR) Slack channel.
|
37 |
+
|
38 |
+
We have documented general guidance on [raising an issue](../welfare/raising_an_issue.md) elsewhere in the Handbook.
|
guides/equality-diversity-and-inclusion/policy.txt
ADDED
@@ -0,0 +1,89 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Equality, Diversity & Inclusion Policy
|
2 |
+
|
3 |
+
## About this policy
|
4 |
+
|
5 |
+
This policy applies to everyone who works for Made Tech, or who acts on Made Tech’s behalf. All team members have a role in promoting equality, diversity and inclusion at work. We all have a personal responsibility to comply with the policy and to ensure, as far as possible, that others do the same.
|
6 |
+
|
7 |
+
Made Tech is responsible for this policy, and for ensuring that all our staff understand their rights and obligations as detailed within it, and for any necessary training on equal opportunities.
|
8 |
+
|
9 |
+
This policy does not form part of your contract of employment, and we may amend it at any time.
|
10 |
+
|
11 |
+
## The legal framework
|
12 |
+
|
13 |
+
It is illegal to discriminate against a person on the basis of the following [Protected Characteristics](https://www.gov.uk/discrimination-your-rights):
|
14 |
+
|
15 |
+
- Age
|
16 |
+
- Disability
|
17 |
+
- Gender reassignment
|
18 |
+
- Marital or civil partner status
|
19 |
+
- Pregnancy or maternity
|
20 |
+
- Race (including colour, nationality, ethnic or national origin)
|
21 |
+
- Religion, religious belief or similar philosophical belief
|
22 |
+
- Sex
|
23 |
+
- Sexual orientation (ie homosexuality, bisexuality or heterosexuality)
|
24 |
+
|
25 |
+
This list doesn't cover everything that might disadvantage someone. We're interested in fairness for everyone, not just meeting our legal obligations.
|
26 |
+
|
27 |
+
## Diversity and equal opportunities
|
28 |
+
|
29 |
+
This is a broader concept that builds upon the progress made through equal opportunities. Everyone is different and diversity means recognising, respecting and valuing the differences we each bring to work.
|
30 |
+
|
31 |
+
Equal opportunities and diversity work together by identifying and addressing any inequalities and barriers faced by people and by valuing, learning and benefiting from the diverse cultures in society and our staff.
|
32 |
+
|
33 |
+
## Types of discrimination
|
34 |
+
|
35 |
+
### Direct discrimination
|
36 |
+
|
37 |
+
This means treating someone less favourably than you would treat others because of a Protected Characteristic. For example, rejecting a job applicant because of their religion, or not promoting someone because of their sexual orientation. This includes any less favourable treatment because you perceive a person to have a Protected Characteristic (even though they do not in fact have it), or because they associate with a person or group who has a Protected Characteristic.
|
38 |
+
|
39 |
+
### Indirect discrimination
|
40 |
+
|
41 |
+
This means placing someone at a disadvantage through a policy, practice or criterion that applies to everyone but adversely affects people with a particular Protected Characteristic. For example, if a company insisted that all employees work on a Sunday, this would adversely affect Christians. If such a practice or criterion cannot be justified as a reasonable means to an end, then it could be considered unlawful.
|
42 |
+
|
43 |
+
### Harassment
|
44 |
+
|
45 |
+
Harassment related to any of the Protected Characteristics will be unlawful if it consists of unwanted conduct that has the purpose or effect of violating a person’s dignity or creating an intimidating, hostile, offensive, degrading or humiliating environment for that person. If you feel that you have been the subject of harassment please talk to your manager, HR person or a trusted colleague in the first instance if you feel more comfortable doing this.
|
46 |
+
|
47 |
+
### Victimisation
|
48 |
+
|
49 |
+
This is the unfavourable treatment of a person because they have taken action to assert their own legal rights under discrimination law, or assisted someone else to do so. For example, if a disabled employee asserts in a grievance that their employer is not complying with its duty to make reasonable adjustments, and is then systematically excluded from meetings.
|
50 |
+
|
51 |
+
## Equal opportunities in employment
|
52 |
+
|
53 |
+
We commit to avoiding unlawful discrimination in all aspects of employment including recruitment, promotion, opportunities for training, pay and benefits, discipline, and selection for redundancy.
|
54 |
+
|
55 |
+
### Recruitment and selection
|
56 |
+
|
57 |
+
Person and job specifications will be limited to those requirements that are necessary for the effective performance of the job. Candidates for employment or promotion will be assessed objectively against the requirements for the position, and on the basis of merit. Similarly, other selection exercises such as redundancy selection will be conducted against objective criteria. A person’s personal or home commitments will not form the basis of employment decisions except where justified and necessary.
|
58 |
+
|
59 |
+
We will generally advertise vacancies to a diverse section of the labour market. Our advertisements should avoid any kind of stereotyping or wording that may discourage particular groups from applying.
|
60 |
+
|
61 |
+
Job applicants should never be asked questions which might suggest an intention to discriminate on grounds of a Protected Characteristic. For example, you may not ask an applicant if they plan to have children.
|
62 |
+
|
63 |
+
### Working practices
|
64 |
+
|
65 |
+
We will consider any possible indirectly discriminatory effect of our standard working practices, including the number of hours to be worked, the times at which these are to be worked, and the place at which the work is to be carried out. When considering requests for variations to these working practices we will only refuse these if we have good reasons for doing so.
|
66 |
+
|
67 |
+
### Part-time and temporary employees
|
68 |
+
|
69 |
+
We will treat part-time and fixed-term employees the same as comparable full-time or permanent employees, and will ensure that they enjoy no less favourable terms and conditions (albeit on a pro-rata basis where appropriate), unless different treatment is justified.
|
70 |
+
|
71 |
+
### Disability
|
72 |
+
|
73 |
+
We will not ask job applicants about their health or any disability before offering them a position, unless it is to check that they can perform an intrinsic part of the job, or to see if we need to make any particular arrangements to accommodate them at interview. Where necessary, job offers can be made conditional to a satisfactory medical check.
|
74 |
+
|
75 |
+
If you are disabled or become disabled, we would ask you to tell us about your condition, so that we can support you as much as possible, and discuss with you any adjustments that may help you.
|
76 |
+
|
77 |
+
### Monitoring questionnaires
|
78 |
+
|
79 |
+
As part of your onboarding at Made Tech and at regular intervals thereafter you will be asked to complete an equality, diversity and inclusion monitoring questionnaire. The data we collect from these will be used to help us make decisions that help fulfil our equality, diversity and inclusion aims.
|
80 |
+
|
81 |
+
## Breaches of the policy
|
82 |
+
|
83 |
+
All staff members have a right to equality of opportunity, and an obligation to uphold this policy. Managers must take responsibility for implementing the policy and for taking positive steps to promote equality at work.
|
84 |
+
|
85 |
+
If you believe that you have suffered discrimination you can raise the matter through our grievance procedure, or you can talk to your manager, the people team, or a trusted colleague in the first instance if you feel more comfortable doing this. Complaints will be treated in confidence and investigated as appropriate.
|
86 |
+
|
87 |
+
We consider any violation of our equality, diversity and inclusion policy to be a serious matter, and, where appropriate, we may invoke the disciplinary procedure when dealing with a breach. Serious cases of deliberate discrimination may amount to gross misconduct resulting in summary dismissal. Unlawful discrimination may also result in legal proceedings against you personally and against Made Tech, and may leave you and Made Tech liable to pay compensation.
|
88 |
+
|
89 |
+
You must not be victimised or retaliated against for complaining about discrimination. However, making a false allegation deliberately and in bad faith will be treated as misconduct.
|
guides/exit_interviews.txt
ADDED
@@ -0,0 +1,14 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Exit interview
|
2 |
+
|
3 |
+
A sad reality is that sometimes people will leave Made Tech. Below are a set of questions we like to ask during a 30 minute exit interview.
|
4 |
+
|
5 |
+
- Why did you look for a new job?
|
6 |
+
- What made you accept the position?
|
7 |
+
- Did you feel that you were equipped to do your job well?
|
8 |
+
- How would you describe Made Tech culture?
|
9 |
+
- Can you provide more information, specific examples of culture?
|
10 |
+
- What could have been done to keep you?
|
11 |
+
- If you could change anything about your job what would it be? Roles, responsibilities, expectations, customers, etc.
|
12 |
+
- If you could change anything about the company what would it be? Culture, space, people, etc.
|
13 |
+
|
14 |
+
**Disclaimer:** We found these in a [Glassdoor blog article](https://www.glassdoor.co.uk/employers/blog/7-must-ask-exit-interview-questions/).
|
guides/hiring/career_fairs.txt
ADDED
@@ -0,0 +1,46 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Made Tech guide to career fairs
|
2 |
+
|
3 |
+
## What does a careers fair look like?
|
4 |
+
|
5 |
+
There are many stalls setup as a circuit around in a big hall. Students pass by the stalls asking questions about job opportunities and internships.
|
6 |
+
|
7 |
+
Most stalls have two representatives standing to the side or in front of them. Standing behind the desk seemed to put too much of a barrier between students and representatives. Stalls typically had table clothes of the companies colors over them, some with logos. All stalls had big banners behind them with bullet point info about the companies and job opportunities at eye level. A lot of stalls had sweets or chocolate on them along with leaflets and swag ranging from totes, USB sticks, popcorn, pens, paper pads, rubix cubes. Some stalls had challenges like solving a rubix cube with a leaderboard. Some had examples of apps they'd built on laptops. A few stalls had additional podiums they brought a long. Our Google Cardboard were another example of things on tables.
|
8 |
+
|
9 |
+
Typically the staff at the desks were recruiters or HR managers rather than people who actually work in engineering. Companies like Ford, Army, Navy, solicitors, Bloomberg and BAE systems are there. Many wore suits although some seemed much more down to earth. The big brands were the big hitters with students swarming around them for more information. Thats not to say we didn't also have 5 or so swarms during the day.
|
10 |
+
|
11 |
+
Most students want to ask about what we do. Some are Computer Science grads, some are mechanical engineering but still interested in code. Some students are part way through their undergraduate years (3-4 years) and some will be doing postgraduate degrees (~2 years). Some want internships, some want graduate positions. Typically everyone wanted a description of what we work on but some ask about salary and length of internships and other things like day to day activities or work environment.
|
12 |
+
|
13 |
+
On average most students stay from anywhere from 1 minute to 5 minutes. Some just want to grab leaflets but we tried opening conversations with everyone who approached. We tried talking to bigger crowds if many approached at once. Everyone even the shy ones appreciated us approaching them and having a conversation. A lot of people seemed a lot more interested in us after talking to them, most had no idea what we were about from the signage.
|
14 |
+
|
15 |
+
## The patter(n)
|
16 |
+
|
17 |
+
At the start we weren't sure on how to begin conversations but throughout the day we built up a fairly consistent conversation structure that worked for us:
|
18 |
+
|
19 |
+
- Ask whether the student is studying compsci or has touched any code?
|
20 |
+
- Describe the fact we primariy build software, from anything like e-commerce stores, to complex warehousing APIs and even back office tools.
|
21 |
+
- Highlight the fact we go into other businesses to help their teams deliver better software faster. Several times we described moving organisations from delivering software every 3 months to every day.
|
22 |
+
- Go into detail about our code dojos, hack days, retreat, blogging and advise them to read our blog and github to see how we work.
|
23 |
+
- Provide Google Cardboard to take a look at the office.
|
24 |
+
- Try to take details or at least give a leaflet to every person who approaches.
|
25 |
+
- Also invite people to our office, to code dojos or whatever else if you fancy.
|
26 |
+
|
27 |
+
## Things to try next time
|
28 |
+
|
29 |
+
- Name badges with Made Tech logo on them
|
30 |
+
- Sweets are very popular like cadburys celebrations but should also provide vegan alternative too (biscuits or something)
|
31 |
+
- More leaflets, need around 200 probably
|
32 |
+
- Use laptop or two for taking contact details as tablet slow
|
33 |
+
- Challenge that takes maximum of a minute to complete
|
34 |
+
|
35 |
+
## Questions we need to answer
|
36 |
+
|
37 |
+
- How long are internships and when do they start?
|
38 |
+
- What does our graduate scheme look like?
|
39 |
+
- What are the salaries available to interns and graduates?
|
40 |
+
- Do we have any non-technical roles available?
|
41 |
+
|
42 |
+
## Notes for next year
|
43 |
+
|
44 |
+
- Banners should contain information about the fact we build web applications and help other companies do that
|
45 |
+
- Banner text should be at eye line as a lot of people were straining and bending over to read the text. Students seem to use this to wittle out companies, we used it as an opportunity to strike up conversations but worth making it a little easier at a glance.
|
46 |
+
- More technical attractions or gadgets or swag. AutomationLogic had a popcorn machine and beer opening USB sticks.
|
guides/hiring/devops_pairing.txt
ADDED
@@ -0,0 +1,22 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
DevOps pairing works similarly to [regular pairing](./pairing.md)
|
2 |
+
Please [read the regular pairing document](./pairing.md) before this one
|
3 |
+
|
4 |
+
## Goals
|
5 |
+
|
6 |
+
- Our DevOps pairing process is designed to simulate solving a real problem in a delivery.
|
7 |
+
Therefore work should be done on an actual cloud account so that the pair can work past unexpected problems
|
8 |
+
|
9 |
+
- We insist on using infrastructure as code so that interviews can demonstrate these skills as this is often always used in a delivery
|
10 |
+
|
11 |
+
## Preparing to pair
|
12 |
+
The DevOps pairing process needs a little more preparation than normal
|
13 |
+
- For pairing in AWS [you will need a cloud account to use](../cloud/aws_sandbox.md)
|
14 |
+
- Use [this terraform project](https://github.com/madetech/devops-pairing-terraform) to create temporary credentials for the pair
|
15 |
+
|
16 |
+
## Writing code together
|
17 |
+
Please use one of [these scenarios](https://learn.madetech.com/technology/scenarios/cloud/) for the interview pairing exercise.
|
18 |
+
|
19 |
+
## Ending the pairing session
|
20 |
+
When there are five minutes left in the session:
|
21 |
+
- Start to Destroy the resources created in the session
|
22 |
+
- While this is happening, it's good to ask how they thought the interview went, what they would change, how they would write tests to ensure the infrastructure has deployed correctly etc.
|
guides/hiring/pairing.txt
ADDED
@@ -0,0 +1,78 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Pairing with interview candidates
|
2 |
+
|
3 |
+
If you are a Made Tech employee, please refer to this [guide for Software Engineers on how to pair](https://docs.google.com/document/d/1x8fVCx-FB-VU_1EHbGU6yLDn1fDyfa5R/edit?usp=sharing&ouid=113960202795862454830&rtpof=true&sd=true).
|
4 |
+
|
5 |
+
## Why we pair with candidates
|
6 |
+
We’re trying to hire people who we’d like to work with. This is a way to try out "working" with them.
|
7 |
+
|
8 |
+
It won’t give us certainty, but we hope it helps us make better decisions.
|
9 |
+
|
10 |
+
## When you’ll be needed
|
11 |
+
You're only needed for:
|
12 |
+
- The pairing, which starts 30 minutes after the start of the interview, and lasts 30 minutes
|
13 |
+
- The debrief, which usually happens directly after the 1h30 interview, and lasts about 10 minutes
|
14 |
+
|
15 |
+
For example:
|
16 |
+
- An interview is taking place at 2pm, lasting until 3.30pm.
|
17 |
+
- You’ll be needed to pair from 2:30pm, until 3pm.
|
18 |
+
- You'll be invited to discuss the pairing from 3:30pm, for about 10 minutes ("debrief").
|
19 |
+
|
20 |
+
Sometimes an interview might overrun. Read the thread in slack before joining the call.
|
21 |
+
|
22 |
+
## What you are looking for
|
23 |
+
You’ll want to answer these questions about the candidate:
|
24 |
+
- Are they prepared?
|
25 |
+
- Are they writing good quality code?
|
26 |
+
- Are they writing good quality tests?
|
27 |
+
- Are they approaching the problem in an effective way?
|
28 |
+
- Can they clearly explain their approach?
|
29 |
+
- Can they clearly explain their thought process?
|
30 |
+
- Are they easy/fun to collaborate with?
|
31 |
+
|
32 |
+
Taking notes while pairing can help to answer these questions.
|
33 |
+
|
34 |
+
It's good for some of your feedback to have more detail than "yes" or "no".
|
35 |
+
|
36 |
+
## Legal guidance
|
37 |
+
Made Tech have a legal duty to ensure that interviews are fair and free of discrimination. There are [illegal interview questions](https://www.interview-skills.co.uk/free-information/interview-guide/illegal-interview-questions) that must not be asked. While it's unlikely that these would be asked directly in a pairing session, it is important that conversation doesn't stray into these areas.
|
38 |
+
|
39 |
+
## Meeting the candidate
|
40 |
+
The Made Tech people running the interview will let you know when to join.
|
41 |
+
|
42 |
+
It’s OK to spend five minutes getting comfortable at the beginning. Introduce yourself, ask how they are doing.
|
43 |
+
|
44 |
+
Tell the candidate the key facts:
|
45 |
+
- The session lasts ~25 minutes.
|
46 |
+
- We’re going to tackle a small coding challenge together, but it’s OK not to “finish” it.
|
47 |
+
- That you want to pair to understand more about how they work.
|
48 |
+
- That you want them to share things out loud, so you can understand more.
|
49 |
+
|
50 |
+
## Preparing to pair
|
51 |
+
- Ask if they’re familiar with pair programming. If not, explain briefly.
|
52 |
+
- Decide on a pairing style together.
|
53 |
+
- Ask if they’ve done a kata before. If not, explain briefly.
|
54 |
+
- Ask which kata they’d like to do. If they’re not sure, suggest one from [this list](https://learn.madetech.com/technology/katas/). Tennis or Bowling work well.
|
55 |
+
- Ask if they’re familiar with test-driven development (TDD). If not, explain briefly.
|
56 |
+
- Tell the candidate you’d like to write tests as part of doing the kata.
|
57 |
+
- If you’re remote, decide how you’ll pair. You could use Tuple, Live Share, or screen sharing.
|
58 |
+
|
59 |
+
## Writing code together
|
60 |
+
It’s OK to help, but give space for the candidate to show their skills and knowledge. If they get stuck, guide them to the next small step.
|
61 |
+
|
62 |
+
Ask them to write the first test.
|
63 |
+
|
64 |
+
Keep writing code and tests until you've got five minutes left.
|
65 |
+
|
66 |
+
It's OK to keep coding for the last five minutes, or to stop and talk with the candidate instead.
|
67 |
+
|
68 |
+
## Ending the pairing session
|
69 |
+
It’s OK to stop coding five minutes early and talk. You would do this to:
|
70 |
+
- Ask any extra questions
|
71 |
+
- Make the candidate more comfortable (e.g. remind them it’s OK to not finish)
|
72 |
+
|
73 |
+
## Sharing your feedback
|
74 |
+
Join the debrief and share your feedback with the other interviewers.
|
75 |
+
|
76 |
+
It’s OK to be unsure about whether you would hire the candidate.
|
77 |
+
|
78 |
+
Note: See [devops pairing](./devops_pairing.md) for differences to this process
|
guides/hiring/rationale.txt
ADDED
@@ -0,0 +1,15 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Rationale
|
2 |
+
|
3 |
+
We believe that our hiring process should be fair and repeatable. What do we mean by this?
|
4 |
+
|
5 |
+
## Fair
|
6 |
+
|
7 |
+
Made Tech is an equal opportunity employer that is committed to inclusion and diversity. There is a simple reason to this, we know that having people of all different walks of life provide us with new view points and better our ability to achieve our mission.
|
8 |
+
|
9 |
+
## Repeatable
|
10 |
+
|
11 |
+
We want to be able to continually hire new staff! We wish to grow and we recognise in order to do this we require a pipeline that provides consistent results. Ideally we would have a pipeline where we could increase our spend and therefore increase our levels of hiring.
|
12 |
+
|
13 |
+
## Achieving fair and Repeatable
|
14 |
+
|
15 |
+
In order to achieve fair and repeatable hiring we need to define a process. As with the rest of our business we experiment and iterate with our hiring process. By having a clearly defined pipeline we can optimise and change it through conversation. We can also repeat successes by repeating our process.
|
guides/hiring/referral_policy.txt
ADDED
@@ -0,0 +1,55 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Employee Referral Policy
|
2 |
+
|
3 |
+
The main purpose of this employee referral policy is for everyone at Made Tech to use when they need information about how Made Tech’s referral programme works.
|
4 |
+
|
5 |
+
|
6 |
+
## Policy Statements
|
7 |
+
|
8 |
+
If you know someone who you think would be a good addition for a position at Made Tech, please do refer them via our [Pinpoint platform](https://made-tech.pinpointhq.com/employee-dashboard/referral_jobs). If we end up hiring your referred candidate, you may receive a referral payment if eligible. Use the policy guidelines below to determine your eligibility.
|
9 |
+
|
10 |
+
Made Tech will give payments to employees who refer qualified candidates for our job openings.
|
11 |
+
|
12 |
+
This is how our employee referral programme works:
|
13 |
+
|
14 |
+
|
15 |
+
| Monetary Amount | Roles | Payment amt on start date | Payment amt after probation |
|
16 |
+
| ------------------: | :--------------: | -------------------------:| --------------------------: |
|
17 |
+
| £500 | Apprentices | £250 | £250 | |
|
18 |
+
| £1500 | All other roles | £750 | £750 |
|
19 |
+
|
20 |
+
|
21 |
+
__Charity__ – should you wish to not take us up on the personal financial incentive then you can opt to make a charitable donation which we will make on your behalf to our associated charity for the given year of the campaign.
|
22 |
+
|
23 |
+
## Who is eligible to take part?
|
24 |
+
|
25 |
+
All our employees are eligible to take part in this program – as such the program does not include contractors or third-party vendors.
|
26 |
+
|
27 |
+
The only other people exempt from participation are:
|
28 |
+
* Anyone working in our talent roles and hiring managers for positions for which they’re hiring.
|
29 |
+
|
30 |
+
|
31 |
+
## Who can be referred?
|
32 |
+
|
33 |
+
The only groups of people who **cannot** be referred are candidates:
|
34 |
+
* That have applied and been unsuccessful in the past 6 months
|
35 |
+
* Who have terminated from employment with us for any reason within the last 18 months (for example, including resignations).
|
36 |
+
* Current contractors
|
37 |
+
|
38 |
+
## Additional rules for rewards
|
39 |
+
|
40 |
+
* Rewards will be processed within 30 days of each stage and processed in the next available pay run.
|
41 |
+
* We never say no to receiving a profile of a referral and will ensure that someone from our Talent team will review the profile and aim to take action within 5 working days. However, during busy periods, this may take longer. You can refer as many times as you wish. Please be sure to evaluate our roles and requirements and make a judgement on suitability to ensure everyone’s time and expectations are well managed.
|
42 |
+
* The candidate being referred must be someone the employee personally knows through a professional or a personal relationship and we will check the validity of the referral before offer stage.
|
43 |
+
* If the same candidate is referred by multiple employees, the first employee who makes the referral gets a reward, so act fast if you know someone that could be suited to our open positions.
|
44 |
+
* There is a 12 month time limit on a referred candidate, meaning if you refer someone to us and they are not right for the current positions now, you could still receive a payment if they are hired in the next 12 months. You will however not receive a payment if you leave Made Tech.
|
45 |
+
* Any financial reward is open to the usual PAYE deductions (tax), please contact People Ops via our Ask Made Tech portal should you have any questions regarding the deductions – which will be automatically made in your pay cycle.
|
46 |
+
|
47 |
+
|
48 |
+
Thank you to all of our Made Tech teammates for taking the time to consider their networks, social and professional as potential resources for referred candidates.
|
49 |
+
|
50 |
+
|
51 |
+
We may change our referral programme over time. We also reserve the right to remove certain rewards if they prove ineffective or inefficient. We’ll communicate any change in a clear and timely manner. Employees who referred candidates before a reward incentive was removed or changed will still receive the appropriate reward.
|
52 |
+
|
53 |
+
|
54 |
+
We’d like to remind our employees that we are an equal opportunity employer and do not discriminate against protected characteristics. We guarantee that all candidates will be given the same consideration and will pass through our established procedure.
|
55 |
+
|
guides/it/Hardware.txt
ADDED
@@ -0,0 +1,49 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# IT Hardware
|
2 |
+
|
3 |
+
Aura look after all the laptops and other IT infrastructure in the offices. For all laptop issues or questions please email them directly [[email protected]](mailto:[email protected]).
|
4 |
+
For accessories such as monitors, keyboards, etc. take a look [here](https://github.com/madetech/handbook/blob/main/benefits/work_ready.md).
|
5 |
+
|
6 |
+
### Laptops
|
7 |
+
Everyone at Made Tech will be given a laptop aligned to the role they do. The Linux users in Made Tech would like to specifically highlight that Engineers can request Linux machines :)
|
8 |
+
|
9 |
+
The current standard laptop specs for new purchases are:
|
10 |
+
|
11 |
+
**Engineers and UCD**
|
12 |
+
- MacBook Pro (14inch standard display)
|
13 |
+
- Apple M4 with 10-core CPU, 10-core GPU, 16-core Neural Engine
|
14 |
+
- 32GB unified memory
|
15 |
+
- 512GB SSD storage
|
16 |
+
|
17 |
+
OR
|
18 |
+
|
19 |
+
- ThinkPad X1 Carbon Gen 11 or 12 14 inch
|
20 |
+
- Core i7-1355U Processor (E-cores up to 3.70 GHz P-cores up to 5.00 GHz)
|
21 |
+
- 16GB or 32GB of RAM
|
22 |
+
- 512GB SSD
|
23 |
+
- Windows or Linux
|
24 |
+
|
25 |
+
(Gen, processor, memory and overall spec can vary on the ThinkPads - we'll talk to you individually about options.)
|
26 |
+
|
27 |
+
**All other roles**
|
28 |
+
- Air M3 (13 inch)
|
29 |
+
- Apple M3 chip with 8‐core CPU, 8‐core GPU and 16‐core Neural Engine
|
30 |
+
- 16GB unified memory
|
31 |
+
- 256GB SSD storage
|
32 |
+
|
33 |
+
You may have or receive a laptop with a slightly different spec - these are older machines which are still within the 3 or 4 year replacement period (see below).
|
34 |
+
|
35 |
+
Standard laptop specs will be reviewed annually, and as and when Apple change their specs. The last review was January 2025.
|
36 |
+
|
37 |
+
If there is an issue with your laptop please email [[email protected]](mailto:[email protected])
|
38 |
+
|
39 |
+
## Laptop replacement cycles
|
40 |
+
|
41 |
+
**Engineers and UCD** - laptops are currently replaced every 3 years, according to the age of the individual laptop, not how long a user has had it.
|
42 |
+
|
43 |
+
**All other roles** - laptops are replaced every 4 years, according to the age of the individual laptop, not how long a user has had it.
|
44 |
+
|
45 |
+
Please note - the replacement is due on the date the laptop was bought by Made Tech, it it not based on the model year of the laptop.
|
46 |
+
|
47 |
+
When your laptop is due for replacement you'll be contacted by Aura to arrange for a new one to be given to you and return of the old one. You do not have to have a replacement - if you're perfectly happy with the laptop you currently have then great. You can request a replacement at any point after the 3 or 4 year mark, whichever is applicable. New laptops will be whatever the standard spec is for your role at that time.
|
48 |
+
|
49 |
+
As of February 2025 we are running behind on replacements for Pros. We're working through in date order.
|
guides/it/Miro.txt
ADDED
@@ -0,0 +1,44 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Miro
|
2 |
+
|
3 |
+
All the information below and lots more useful stuff can be found on the Made Tech [Miro training board](https://miro.com/app/board/o9J_lkgJ4BU=/) (this is an internal link to a Miro board)
|
4 |
+
|
5 |
+
## Getting access to Miro
|
6 |
+
### New starters
|
7 |
+
All new starters are automatically given a Full Miro licence when they join and are added to the Made Tech Team.
|
8 |
+
|
9 |
+
They can be added to any board or Space in the Made Team Team by any other Made Tech Team member. To add them to another Space or client Team, that Team Admin has to invite them.
|
10 |
+
|
11 |
+
### External users
|
12 |
+
External users **cannot** be added to the Made Tech team, they can only be added to separate client team and Spaces - see Types of Team below. The Team Admin for the client or Space can invite them.
|
13 |
+
|
14 |
+
The licence options are:
|
15 |
+
- Free Restricted - viewing and commenting (this is free)
|
16 |
+
- Full - editing access (this costs us money)
|
17 |
+
|
18 |
+
### Reviews
|
19 |
+
In order to keep licence costs down, access is reviewed every quarter based on usage. If a Full licence hasn’t been used in the previous 2 months it will be changed to a Free Restricted licence. This can be changed back to a Full licence at any point. The licence options are:
|
20 |
+
|
21 |
+
- Free Restricted - viewing and commenting (this is free)
|
22 |
+
- Full - editing access (this costs us money)
|
23 |
+
|
24 |
+
### Leavers
|
25 |
+
If you are leaving Made Tech; please transfer your boards to a new owner in advance. Any boards still owned by you at the point of offboarding will be transferred to a Team Admin.
|
26 |
+
|
27 |
+
Leavers are removed from the Made Tech Team as part of the offboarding process. Leavers need to be manually removed from any other client or project teams by the Team Admin, though Ops will do a clear out once a quarter.
|
28 |
+
|
29 |
+
## Types of Team
|
30 |
+
### The Made Tech Team
|
31 |
+
There is a Made Tech Team which all staff are automatically added to. This is internally facing only - external users **cannot** be added to the Made Tech team. This is so that there is no accidental sharing of internal information.
|
32 |
+
|
33 |
+
Everyone has permissions to set up their own boards within the Made Tech Team, either as part of a Space or individually. These can be kept private, be shared with individuals or with the whole Team.
|
34 |
+
|
35 |
+
### Client & Project Teams
|
36 |
+
There are also Client and Project Teams which individuals can request to be added to, or be invited by the Team Admin. These are completely separate from the Made Tech Team, and from each other, and have been set up to ensure that we are keeping all client data in separate and secure environments.
|
37 |
+
|
38 |
+
These Teams are administered by the Team Admin who is a member of the project team, and only relevant project team members should be invited.
|
39 |
+
|
40 |
+
If you need a new Team creating, contact Aura via email [email protected] or via Slack.
|
41 |
+
|
42 |
+
To join an external team, click on the Made Tech team option at the top of your dashboard so you can see all the teams you have access to, click + Join team and a request will be sent to the admins for that team.
|
43 |
+
|
44 |
+
There is more information on Ask Made Tech - search for Miro.
|
guides/it/docker.txt
ADDED
@@ -0,0 +1,12 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Docker
|
2 |
+
|
3 |
+
Docker is an open platform for developing, shipping, and running applications. Docker enables developers to separate their applications from their infrastructure so they can deliver software quickly. With Docker, they can manage their infrastructure in the same ways they manage their applications. By taking advantage of Docker’s methodologies for shipping, testing, and deploying code quickly, they can significantly reduce the delay between writing code and running it in production.
|
4 |
+
|
5 |
+
Due to changes within Docker, from Jan 2022 any employees using a Made Tech email address must use the Made Tech licence for Docker Desktop and not an individual licence.
|
6 |
+
|
7 |
+
## Onboarding/offboarding
|
8 |
+
If you require a Docker licence please message `[email protected]` with the details of the project / workstream that you need adding to.
|
9 |
+
|
10 |
+
If you are a Delivery Manager / the Lead Engineer on a project then please ensure that you notify the Operations team if a member of your team leaves your project so that we can remove their access to that project.
|
11 |
+
|
12 |
+
If you have left a project and are still in the team on Docker or you no longer require your licence please ensure you let the ops team know by sending a message to [email protected]
|