↳
Two different pictures of work environment given by recruiter and manager. One very rosy and the other more realistic. More importantly, recruiter stressed a great work/life balance and manager did too, but added that I'd be required to work 45 hours per week at least to start. They added further that someone had recently left who could not commit to this. This was a red flag for me and I declined an in-office interview. Less
↳
They have gone through more than 8 developers over a 3 year period. Avoid them if you value your career. They will lie and tar and feather you if they suddenly develop a dislike for you. The manager is insecure, paranoid and plays favorites. Cat lady needs to be medicated. Less
↳
I couldn't answer this.
↳
Select C.container ,AGG.ROWNUM as loop_num, SUM(Units) , AGG.start_time,AGG.END_TIME from Containers C INNER JOIN ( Select ST.container,ST.ROWNUM, ST.start_time,ET.END_TIME from (Select S.container,row_number() OVER (order by Movetime) rownum, (case when S.status='Start' then S.movetime end ) as start_time from containers S WHERE STATUS IN ('Start') ) ST , (Select S.container,row_number() OVER (order by Movetime) rownum, (case when S.status='Complete' then S.movetime end ) as end_time from containers S WHERE STATUS IN ('Complete') ) ET where ST.container=ET.container and ST.rownum=ET.rownum) AGG ON (C.container=AGG.container) AND (C.movetime >=AGG.start_time AND C.movetime <=AGG.end_time) group by C.container,AGG.rownum,AGG.start_time,AGG.end_time Less
↳
I explained how a clustered index was in sequential physical order on disk and a non clustered index used pointers or a hash table for index lookup. I started to explain the advantages/disadvantages of each index type but the two guys interviewing me just seemed so confused and lost. I think I would have been better of simply saying "it makes lookup faster". Less
↳
I explained how a clustered index was in sequential physical order on disk and a non clustered index used pointers or a hash table for index lookup. I started to explain the advantages/disadvantages of each index type and how I would use them. Less
↳
All the information about BI tool should be known to us.
↳
You basically need to know the different ways of Agile. Who the Scrum master is and what your role in it would be. Also, knowing the difference between kanban and sprints would be helpful. Also, it's okay if you do not know 'all' of the BI tools. If you have only used SSRS then you can probably also use Power BI, Tableau, or Excel. You know what you know. As long as you show you can adapt easily you will be fine. Less
↳
Inner Join returns values where the key between the two tables are the same, and values are present in both tables. Outer Join returns the Values from both tables, based on the key, even if there is not any data the joining table. If not value is available, then NULL is returned for that specific Row Data based on the Key Less
↳
Specified in the WHERE clause, joins simply combine data from multiple tables in the result. INNER JOIN, the most common, returns the rows for which the given ON condition is satisfied for both tables. LEFT/RIGHT OUTER JOIN statements return all the rows from the specified table regardless if there is a match in the unspecified table, with the matching rows specified in the ON condition in the unspecified table. Less
↳
Talk slowly, listen carefully and answer with examples
↳
a = a+b; b = a-b; a=a-b;
↳
Wrote a short pseudo code to answer these questions.