hey everyone ! Any pointers to improve complex SQL problems other than Hackerrank and Leet Code
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’m honestly not sure how you’d do it since:
A. Optimization is super vendor-specific like someone else said.
B. The hardest part of SQL isnt syntax but knowing where the data lives and the intricacies of those specific tables and how they map to other tables. Production DBs are a result of a lot of moving parts and years of accumulated neglect... I’m not sure you could even intentionally recreate that if you tried. Even if you could, tough to expect a candidate to suss that out in the span of an interview.
Personally the hardest SQL question I’ve ever been asked was implementing a window function and this was just talking out how I’d query something against a hypothetical table, not actually firing anything.