Related Posts
Hi,
In tcs my joining date is passed still not received onboarding link.
Is it normal there because been 4 days delay still they are not giving any update.
It’s kinda hectic to call every time to recruiter and get back with the same answer like work in process.
Should I even expect the joining date?
Let me know if anyone faced that kind of situation before. Tata Consultancy even onboarding manger is not giving Reply’s to my. Mails
More Posts
Community Builder
Bowl Leader
Rising Star
Ok. Which of you Trumpers did this?
Please guide me on this
Additional Posts in Data & Analytics Consultants
Mentor
Are there RPA use cases in data work?
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Create a Access Database. Create table and run queries from there. Label it as personal Project experience. I did this out of undergrad and landed a full time role.
SQL Leetcode
Under sell yourself over deliver. Ex. Tell the interviewer you understand the basics (left, right, and inner joins). But give use cases for complex stuff like when to index things, stored procedures, temp tables etc. when doing this say you don’t do the complex stuff everyday. Be candid you would have to google syntax but you would be able to apply quickly. Ultimately you’ll be asked to prove your skill set on a whiteboard. At that point you’ll shock the interviewer in a good way and land the job you’re looking for. Good luck
My response was under the assumption you’ve made it past the recruiter and got an interview. When dealing with recruiters it’s hard to tell whether they are technical or non technical. I would suggest keep all answers short and simple use buzzwords. Personally I would rephrase basic-intermediate to I know SQL well. Purpose is the bait the recruiter to test your knowledge or check the y/n box if you know sql or not.
Key facets of using SQL. Depending on your experience, may be highlight these:
1. Basic Querying, CTEs. Anything associated with fetching of data from DB without considerations of time and load complexity
2. Creating new db, tables. Knowledge of indexing and how that affects your query. Selecting appropriate scale of db instances.
3. Understand and relate the database operations to the services using it. Concepts of caching, updating and fetching data. Avoiding stale data in complex system architectures.
4. Moving on from raw query to ORM such as SQLAlchemy. Using migrations to automate db management.
I highlight my understanding of the underlying concepts - I can't write the code as fast as a dev person could, but I could get it done eventually. I can read anything someone else wrote and ask intelligent questions, and since I understand the concepts it's unlikely I'm going to promise the impossible to a client
You will get sql test anyway so a binary/categorical answer won’t matter that much
Why don’t talking about what you have used, (learn) most companies ask experience because it helps master the skill, if you don’t use SQL, my suggestion is start using it, there are a lot samples you can find online and practice, create your own en and practice, plus you can add PL/SQL to that is a plus, you never stop learning something. Practice is the best teacher. Keep going mate!
Create your your GitHub and load it up with a bunch of folders and READMEs. Interviewers rarely check it.
I am in the same position, you can try reading SQL cookbook by Anthony Molinaro. It talks about how to solve any kind of problem with SQL.
Thou I haven’t started to apply for interviews but I hope it helps. :)