Conversation
✅ Deploy Preview for cyf-launch ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-tracks ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-curriculum ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-sdc ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-programming ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-common ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-itd ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-piscine ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jcholyhead
left a comment
jcholyhead
left a comment
There was a problem hiding this comment.
This looks good to me.
The one thing I always stress to people about networking is that they should be trying to network across (at a peer level), not up. So they should be trying to speak to software engineers (and not particularly senior ones), rather than engineering managers because that is more likely to result in an actual connection.
| ## Instructions | ||
| - [ ] Each person drafts a short introduction (who you are, what you're learning, what role you're interested in). | ||
| - [ ] In pairs, practice your introductions with each other. | ||
| - [ ] Ask each other 2–3 networking questions and practice listening and responding naturally. |
There was a problem hiding this comment.
it might be useful for the trainees to see some examples of what appropriate "networking questions" are - for me, I like to express (often very fake) interest in whatever the person I'm talking to is doing: "Oh you work in insurance systems? - I bet keeping up with the changes in a regulated industry is challenging - how does knowing those changes are coming impact your roadmap planning?" (ugh that conversation didn't even really happen and I'm already bored).
|
|
||
| Through conversations, people become more than a CV. Others start to understand how you think, what you care about, and where you're trying to go. These are things automated systems struggle to capture. Over time, this context can make a real difference. | ||
|
|
||
| Moving from a conversation to a next step doesn't need to feel awkward: |
There was a problem hiding this comment.
I would explicitly suggest that people ask for other people's LinkedIn at the end of a conversation and add them during the interaction. I've made the mistake myself of thinking I'll remember someone's name and then forgetting it. And I think we should also suggest LinkedIn is better than phone numbers or emails at least initially as it's less private.
| 1. Build familiarity and trust over time. | ||
| 1. Stay motivated and connected during a long job search. | ||
|
|
||
| **Networking isn't:** |
There was a problem hiding this comment.
I really like this framing of what it is and isn't 😃
|
|
||
| Note: Does your message mention something specific from the conversation? Does it avoid asking for anything directly? | ||
|
|
||
| ## Learning Objectives |
There was a problem hiding this comment.
I'd suggest splitting out the group exercises to a different page as currently it's a bit disjointed. The previous exercises on the page felt more individual to be done whilst reading this page but the group one with the mention of the timer is for a different context. This is how I did it on one of the page I was doing which had a similar thing. https://curriculum.codeyourfuture.io/guides/employability/job-search/
|
I think other things it would be good to add are
|
|
|
||
| To use this guide you should: | ||
| - Have a basic understanding of the type of role or area in tech you're interested in | ||
| - Have a LinkedIn profile or be in the process of setting one up |
There was a problem hiding this comment.
I'd recommend adding an internal link to the LinkedIn guide like (../../linkedin-profile)). If you need help with markdown just let me know and I can do the change on your branch.
3 participants
What does this change?
Common Content?
Common Theme?
Issue number: #issue-number
Org Content?
Module | Sprint | Page Type | Block Type
Checklist
Who needs to know about this?