I new to sql live assessments in general. Is it ok if I run the code for sub queries and parts of the query to see the output or is it expected of me to get everything right before submission?
Any other tips and recommendations for a newbie?
I’m currently using strata scratch to practice but the Interface might be too nice to be true as it shows me the expected output. I’m worried that I won’t see that during the interview. - should I try to avoid checking the expected output?
Thanks 🙏
#dataanalytics #data #datascience
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
I think it’s more how you frame it. If it’s like “Lemme run this to see if it’s right because it really could go either way” that’s a red flag. If it’s more “So first, before I join to activity data, I want to get a table with one row per user. Here I am writing that code. Now, before we move on, let’s take a peak at that. If I were writing this for real, I’d probably stop here and do checks for bulls or duplicates before joining. For the sake of this case, we will just eyeball it”