Fork me on GitHub

I have a Clojure job interview coming up and I am supposed to walk them through the code of a project that I worked on. Any advice on how can I make this interview a success?

Ben Sless14:10:39

As an interviewer I'd like to see: Project structure Good architecture Good abstraction Testable code Clear entry point Different configuration for different environments

Ben Sless14:10:07

Explain what the project does and how it achieves that

Ben Sless14:10:17

When is the interview?

Ben Sless14:10:48

I'd also ask about challenges, assumptions in the code, scalability, limits, eyc

Christian Pekeler16:10:56

before, make sure you: • understand the high-level business-purpose of that project • have a deep understanding of it • have an opinion on which aspects are good and which could be improved • if possible, try to find out the level of expertise of the person interviewing you during the interview: • explain it top-down (start with a short demo if possible) • pay attention to signals from the interviewer and adjust your explanations accordingly • if you’re not getting clear signals, ask

Christian Pekeler16:10:47

As an interviewer, this has been my favorite kind of interview for the past 3 years. Me being able to understand your explanations and not feeling bad in the process is the most important criteria.


pause and ask them if they have any questions ask them to interrupt you if they're lost try and get to the point maybe explain the high-level design ideas and design decisions you made (be sure to explain alternatives and why you landed on what you landed on)


The interview is on Monday @UK0810AQ2


It’s just a simple reframe dapp that writes and reads the blockchain and the server side sends the smart contract json and the html/css/js to the client. Not sure what good architecture and good abstraction mean in this case. Also whatis scalability and limits? I don't feel there's much to talk about other than explaining what each line of the code does


Well there is always an architecture, if on the ui use reframe can you explain well what's the reframe architecture?


And it doesn't matter if it's a simple app, you can always talk about scalability


What would happen if your application had 10k parallel requests, how would it cope?


The server is deployed on google kubernetes engine, and I don't think the kubernetes architecture is autoscalable. Unfortunately I also don't know what would happen when large number of requests go through and frankly don't know the limit of those requests is. Not sure what's the state of the art for testing this stuff.


Hehe well I'm not asking because I need the answer, just saying that these are questions you should be able to answer


Kubernetes is not really relevant with the architecture, it's more things like event driven or not, async or not etc etc