Some advice

Hi all,
I have an interview next week for the role of a software engineer, and would participate in the whole software life cycle. The following skills are required:
- OO Design concepts
- OO Technology
- Content management
- Client/Server Architecture
- Relational Databases
- Java and Java Frameworks(J2EE,EJB,Servlets,Jboss,JBuilder)
- EAI (Enterprise Application Integration)
Could anyone guide me on what types of questions
I might expect in any of the topics and which salary I can expect in such a position?
Thanks.
Ebage
SCJP
SCEA
[ April 19, 2003: Message edited by: Christian Ebage ]
[ April 19, 2003: Message edited by: Christian Ebage ]

Hi Ebage,

Congratulation! I have some but not all.
1. How do you like to approach projects and tasks?
2. What formal processes have you used? Discuss them.
3. What is the definition of Use Cases and explanation?
4. What tools do you prefer to use for making development easier and why? Could you list the pro and con of the tool?
5. Discuss the goals and best practices of modeling. How can you tell that you have a good model?
6. Is it reasonable to design an immutable Java class to also be subclassable?
7. What is an object? What makes a System Object Oriented?
8. Explain RMI architecture.
9. Explain firewalls in RMI.
10. What is lazy activation?
11. Discuss the features of Java you like to exploit for complex projects or high reuse.
12. Java Threads have several strengths. But one main weakness of a Thread object is that, there is no way to capture and handle runtime exceptions, errors thrown by Threads. How do you handle this case not provided by the Thread class?
13. Give examples of how we can apply principles in Biology or Electronics to improve software development.
They were from the dot com era. The questions may change a lot in the current market.

Cheers,
MCao

Hi MCao,
many thanks for the questions. They are really helpful.
Ebage
SCJP
SCEA

Another question that often gets overlooked is:
What formal systems do you use to determine whether ewn java technology or framework is too immature or mature enough to use on a project?
..And if you made the wrong decison what did you learn and were able to reapply to prevent this?