↑ j4ck 🥶 icebreaker.xyz ↑ pfp
↑ j4ck 🥶 icebreaker.xyz ↑
@j4ck.eth
if you are • looking for work • hiring at your company • have a friend who's doing either of those shoot me a DC 🫡
10 replies
17 recasts
99 reactions

↑ j4ck 🥶 icebreaker.xyz ↑ pfp
↑ j4ck 🥶 icebreaker.xyz ↑
@j4ck.eth
if you're looking for work, check out jobs.icebreaker.xyz if you're hiring, DC @esteez.eth to get added 🫡
2 replies
0 recast
9 reactions

↑ j4ck 🥶 icebreaker.xyz ↑ pfp
↑ j4ck 🥶 icebreaker.xyz ↑
@j4ck.eth
if you want feedback on your CV, have general hiring or job search questions, DC me 🫡 here to be a resource
3 replies
0 recast
4 reactions

jp 🎩 pfp
jp 🎩
@jpfraneto.eth
today i have my first technical interview ever. they added me to a telegram group with 4 other people, and they are extremely welcoming and i feel a good vibe. i have the meeting in 4 hours. what approach do you recommend me to have when going to it?
9 replies
0 recast
4 reactions

Jessi™ pfp
Jessi™
@zwillow
They know you’re qualified, now they want to see if you vibe with them. Keep up the vibes. You’re smart. You got this.
1 reply
1 recast
1 reaction

↑ j4ck 🥶 icebreaker.xyz ↑ pfp
↑ j4ck 🥶 icebreaker.xyz ↑
@j4ck.eth
well candidly i've never done a technical interview. i have done design interviews though generally though: • be respectful of their time, be grateful for the interview, and be yourself bc that's who will be showing up to work! • it's good to show how you think. that's what they're looking for more than a perfect outcome. problem solvers. • take some deep breaths and even power-pose beforehand (basically stand with hands and arms out in a star shape) • remind yourself you are talented and competent. you got this 🫡
2 replies
0 recast
1 reaction

Joshua Hyde (he/him) pfp
Joshua Hyde (he/him)
@jrh3k5.eth
moon is right: it's okay to not know, and demonstrate that you're able to close that knowledge gap. If given the option, choose the tools that you work with best - i.e., if you know JavaScript and are interviewing for a job that uses Go, use JavaScript - doing it in an environment in which you're unfamiliar will cause you to waste time trying to figure out how to do things in Go that you know how to do in JavaScript. You're there to show that you can write good code, not that you're a good Go programmer. Languages can be learned on the job (as I have done, multiple times).
2 replies
0 recast
0 reaction

Moon pfp
Moon
@moon.eth
1. if you don't know the answer explain how you would methodically find the answer. 2. ALWAYS SHOW UP ON TIME. PLACES CAN AND WILL DROP YOU IMMEDIATELY IF YOU'RE LATE.
1 reply
0 recast
0 reaction

Tayyab - d/acc pfp
Tayyab - d/acc
@tayyab
Just one piece of advice: Ask ahead of time for the format of the interview. Sometimes prep work is needed. Ask if they allow you to use AI. Is it a test of ability to code, or do systems design? Or both? Understanding the format allows you best prepare for the specific questions at the interview. Everyone does it differently.
1 reply
0 recast
0 reaction

↑ j4ck 🥶 icebreaker.xyz ↑ pfp
↑ j4ck 🥶 icebreaker.xyz ↑
@j4ck.eth
@tayyab any advice?
0 reply
0 recast
1 reaction

kompreni 🚂 pfp
kompreni 🚂
@kompreni
If they ask you to download/install software to join the meeting, don't. It might be a phishing attempt.
1 reply
0 recast
0 reaction

Retake.tv pfp
Retake.tv
@retake
gl!
0 reply
0 recast
0 reaction