Implementing a linked list as practice for a coding interview
Names

package LinkedList


By Java's naming convention, package names are in lowercase and follows a 'reversed Internet domain name' prefix. Therefore, LinkedList is not a good package name, but something like com.antarkar.amough may be more suitable.

public class LinkedList


It is usually not recommended to use class names that conflict with those from the standard API, as it may cause confusion at best and compilation errors at worst. Since you are indeed doing a linked list implementation, I don't suppose there's a simpler way around this, just bear this in mind in the future for 'production level code'...

Separation of concerns

The biggest issue about this class, going by 'production level code' and 'coding interview' standards, is that you are mixing I/O operations (i.e. user input and display) with the data structure implementation. These two should stay separate for two simple reasons, if I may classify them under the standards you requested:


Production level code

When codes get into 'production' (depending on your definition), you'll want it to do one thing, do it well, and do it in as minimal as possible. If it's a data structure, it shouldn't know how to interact with System.in and System.out. If logging is required, it will use a (preferably widely-adopted and well-tested) logging framework to do so. Lesser lines of code tend to result in less programming bugs introduced. Lesser instructions (at the JVM level) also translate to more efficient memory usage, too.
Coding interview

Intertwining two unrelated features into a single class may indicate a lack of understanding of OOP concepts. What happens if a GUI-based demonstration is required? Also, how will you unit test your code when the class is interfacing directing with System.in and System.out, when it should be done through proper method arguments and (possibly) String outputs?


I'll recommending browsing through the number of linked list implementations in Java we have here on CR, to compare-and-contrast your implementations with the rest.

Modern code

Without even going into Java 8 features, features like try-with-resources should already be adopted around your Scanner so that you do not need an explicit call to close() at the end. Java 7 already has generic type inference aka the 'diamond operator', so you can remove the unnecessary types. Hashtable is a legacy class that is retrofitted to become part of the Collections framework, so you really ought to be using HashMap.

All these pointers matter if this is for a coding interview, as you'll want to show that you are reasonably kept up to date with the newer developments in your programming language of choice.