-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions to Ask your Interviewer #4
Comments
Thanks for submitting an issue! I'll check it at as soon as possible and get back to you. |
One of my favorite questions to ask the hiring manager is |
I have a doc I created with a list of questions. Think it's a good start & would love more feedback for it. |
@vernko want me to assign this one to you? You can include your list plus questions from others like @kevinpyles |
That sounds great!
…On Mon, Jan 31, 2022 at 2:07 PM Carlos Kidman ***@***.***> wrote:
@vernko <https://github.com/vernko> want me to assign this one to you?
You can include your list plus questions from others like @kevinpyles
<https://github.com/kevinpyles>
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHZS6S2TPOE7MUSDXQ2YTNTUY32XPANCNFSM5MZV76NA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@ElSnoMan Would it be better to break these questions be broken into different levels like This is more thinking about people breaking into the industry. We can give them questions to ask, but for some of the questions, they may not have any context if they have never worked in the industry. |
From Vern and Jake Sparks
I could see this as a
post
and/or template in the WikiThe text was updated successfully, but these errors were encountered: