Tag Info

New answers tagged

5

Since you tagged the question with language-agnostic, here's a solution in a language suited to recursive functions and data structures: let rec swapTwo lst acc = match lst with | a::b::tail -> swapTwo tail (a::b::acc) | h::tail -> swapTwo tail (h::acc) | [] -> List.rev acc As for a solution in C++, I don't fancy doing the ...


-2

You first make Work Brakedown Structure (WBS). From WBS create Activity List (Activity Definition), than create estimates for each activity (number of hours/days). Create resources required for each activity. Calculate total resources and time required from this list. Although there are many other factor impacting resource requirements but this answer is ...


0

TheTrainline.com takes a similar approach to Atlassian's, with an at home component where an interviewee will critique and fix a component, and the pairing interview will build a component which uses their improved implementation. Rather than halting at the point where the candidate cannot resolve the problem, approximately half the time is ...


0

One of the most common mistakes I see programmers make is that they don't have knowledge and don't think about time-complexity. One of the first standard problems where you need to grasp time-complexity is actually a quick-sort. Once you know why and how to implement a quicksort it is assumed that you also grasp time-complexity. An you know how Knuth says ...


4

There are many reasons, some of them are good some aren't: Technical interview is a difficult and heuristic process for both participants. Sometimes it is just plain difficult to come with really interesting and original questions(the same is true for answers). Sometimes we just have some deeply ingrained prejudices about what should be and what should ...


0

I'm a great believer in code tests for developers interviewing for a job. However, this sounds like the code test from hell... Code tests should never involve production code. They should be simple and should state that none of the work done will be used by the company. Clearly, the work you did was on production code. You should be paid for all of your ...


1

While you are supposedly getting paid for (some of) your work, this does not sound like a trial project, it sounds like a scam to get cheap/free work out of you. It may be that it is was intended to be a trial project, just not structured or managed very well. But managment that is so bad that it is sounds like a scam, is definitely something you should ...


0

In my experience the personal site/brand/presence is incredibly helpful in having cool job opportunities present themselves. Especially in software development. Good companies won't reject your application if you're without a solid online presence, but having one will definitely help companies find you. Side note: If you're a freelancer looking for gigs, ...


1

We ask all potential employees to write a simple class library and unit test before the in-person or phone interview. We give most people who hand in a CV this test, but we couch this as a "we would like to interview you -- before you arrive, please do this coding assignment and send it to xxxx". Some notes: I would expect the test we give to be under an ...



Top 50 recent answers are included