Okay Anon. It's interview time once again. Lay some advice or other shit on me. What should I FOR SURE know?
Background: I aced the phone screen and they're flying me a few states away, giving me a rental car, putting me up in a hotel, and then I have 7 interview sessions.. Yeah, kind nervous.
the contract out to a non-specific three letter government org.
Yeah, i'm just nervous as to what the fuck they're going to be asking me after 4-5 one hour conversations. Sounds fucking exhausting.
And it's really not a brag type thread. I just want to know what I should hammer down today that'll definitely come up.
Fuck off to bussiness retard.
I could program around you, talk my ass off, and communicate with people while having good programming abilities that sounds better then yours.
>Don't go for this job
>Lean to communicate and not just code (Program)
What the fuck do you want me to say?
Your programming skills is all you need and that you can't simply fuck up if you program the day not too?
Fuck off and grow some confidence you retard.
holy shit i'm just asking for advice because i'm nervous for an interview!
What do you think they'll be asking me.
>Assuming I am a NEET.
How fucking dare you you filthy pleb.
First off you disrespectful cunt, not sure about others but I am employed as a software engineer. I make programming code shorter while maintaining programming integrity. I get a weekly paycheck and work in australia.
I get paid well and live well. I bet you earn million a year and think that being paid each week is pleb quality.
>I am not the one assuming cunts are unemployed here.
It's too late we got what we came for.
Yeah i'm hammering down on inheritence heirarchy, polymorphism, virtual classes / methods, templates, etc, maaaybe a bit of smart pointers and destructors (which I don't really know how to use yet).
Then i'll work on some data structure type stuff.
I'm sitting in an airport terminal and this made me kek more than it should.
I 've had a phone + two technical interviews recently for a position of Junior SE. I was nervious af desu senpai.
The first one was just about some projects i did, they wanted to know if i really know wtf is going on or if i lied in my CV. Software design, UML, design patterns, stuff like that.
The second one was full blown 4.5h technical interview where they go as deep as they can on every topic (prog. lang. proficiency, DB, algorithms, front end, automated testing, OOP, a short case study, team fit).
They want to hire you. They want to see how much you do know and set your salary/position/project accordingly. Try to relax and just go with the flow. Try to answer most of the questions, even if you are not sure about it - they want to see how you think and whats your thought process.
Be honest and show them that you are motivated and wanna learn new stuff. Thats all they expect from an Intern/Junior.
Good luck anon.
I know about destructors but some brush up on when exactly smart ones expire is where i'm going to look into.
thanks m8. I've done some database stuff already but i'll be sure I remember all the correct syntax before I get there. Care to share any difficult questions that you had to think about for a while (like design Q's for example.. they're hard to find online).
Only true to an extent.
I learned AngularJS in a day after lying about having mastery of it for the sake of getting interviews, and landed a senior position. Admittedly, it was regurgitating knowledge and C++ is infinitely more complex, but don't underestimate Parkinson's law.
The thing is, every topic starts slow and its easy but eventually you hit a wall. Thats the point. Once that happens, they changed the question and gave me a second chance, but if i still could not get it - next topic.
Basically every topic had that one "hard" question and I cant really remember what it was (and its totally individual anyways).
About the design - I dunno, thats just something I ve learned during my studies and individual projects. They gave me a couple of A4 sheets of paper with req. for a small game. They left the room and gave me 10 minutes to come up with the class diagram. After that I had to defend my design and give reasoning for my choices (why the XYZ inheretance, why would you use this design pattern, etc.)
Its late to read about patterns and stuff, but atleast look into SOLID, and make sure you are profitient with c++ (know all the keywords for example, how to override an operator, templating, etc.).
Worst case scenario - you wont get the job but you ll know how the interview works and what are your weakest points. You ll get the next one.