The title says it all, really. I have 8 yoe, but most of this was spent with startups that did not have coding tests. I'm just wondering what I can expect with BOA if anyone knows? Thanks
When I was there it was generally an hour you spend in a meeting room and there was some sort of hacker rank questions.
They’d want to see how you could work through the problem, which libraries you use. You’d probably want to be familiar with the itertools library etc. Throw ideas at them about what you’re thinking and collaborate to solve the problem. They want to see if you’re someone they can work with too.
Each team varies though. Some teams love TDD too, not sure if it will be tested though.
When I talk to hiring panels about technical assessments, they will note when people are quietly working on the problem and not talking to the assessment team - that isn't an issue in its own right, but it speaks to the type of developer you are and might come up in a 50:50 comparison with another candidate.
Be open to saying "So, my thought here is to implement X pattern, and I'm going to use Y library/framework to set up the model. First I'm going to do a, b and c, and then I'll do that as step d". Write down your plan, or stick it in a notepad, and use it as a framework for conversation during the exercise - even if you can do the exercise in your sleep: that's actually an excellent opportunity to explain like you're walking a junior through it, rather than a peer/senior.
It's also good to ask questions for engagement.
If you're quiet and don't know a library/framework that gives a shortcut, they'll think you're lost. If you're vocal and talk through your approach, then you demonstrate your problem solving and that you're going about solving the issue yourself because you didn't know the framework.
It looks like your post pertains to education, or graduate and Early Career advice. Unfortunately, due to an overwhelming influx of threads related to these topics, we are now restricting these threads to a monthly megathread, posted 1st of the month. Please check the announcements at the top of the sub, or this search for this week's post.
Career advice posts for experienced professionals (e.g. 3+ years) are still allowed, but may need to be manually approved by one of the sub moderators (who have been automatically notified).
When I was there it was generally an hour you spend in a meeting room and there was some sort of hacker rank questions.
They’d want to see how you could work through the problem, which libraries you use. You’d probably want to be familiar with the itertools library etc. Throw ideas at them about what you’re thinking and collaborate to solve the problem. They want to see if you’re someone they can work with too.
Each team varies though. Some teams love TDD too, not sure if it will be tested though.
This is good general advice.
When I talk to hiring panels about technical assessments, they will note when people are quietly working on the problem and not talking to the assessment team - that isn't an issue in its own right, but it speaks to the type of developer you are and might come up in a 50:50 comparison with another candidate.
Be open to saying "So, my thought here is to implement X pattern, and I'm going to use Y library/framework to set up the model. First I'm going to do a, b and c, and then I'll do that as step d". Write down your plan, or stick it in a notepad, and use it as a framework for conversation during the exercise - even if you can do the exercise in your sleep: that's actually an excellent opportunity to explain like you're walking a junior through it, rather than a peer/senior.
It's also good to ask questions for engagement.
If you're quiet and don't know a library/framework that gives a shortcut, they'll think you're lost. If you're vocal and talk through your approach, then you demonstrate your problem solving and that you're going about solving the issue yourself because you didn't know the framework.
Communicate, communicate, communicate.
It looks like your post pertains to education, or graduate and Early Career advice. Unfortunately, due to an overwhelming influx of threads related to these topics, we are now restricting these threads to a monthly megathread, posted 1st of the month. Please check the announcements at the top of the sub, or this search for this week's post.
Career advice posts for experienced professionals (e.g. 3+ years) are still allowed, but may need to be manually approved by one of the sub moderators (who have been automatically notified).
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
BOA does Test Driven Development so not having done any unit tests in previous experience will go against you.
What kind of company doesn't do tests or testing??
way too many :D