Concurrency, message queue, load balancing, caching, distribution, security, are these the highlights of your resume? Java fresh graduate, internship for more than half a year
A beautiful resume can really attract attention and increase the chance of being invited for an interview. Likewise, the interviewer will also have more expectations for you. Then, during the interview process, you will be asked questions as if you were at the level listed on your resume. Once you perform poorly, the interviewer will be disappointed in you.
For example, a company only needs to recruit an intermediate-level person, and you are also qualified for the intermediate-level position, but you make your resume look like a senior-level one. During the interview, if you are not careful, the interviewer will think that you are not even intermediate. Because it was far lower than they expected.
So, it is recommended to seek truth from facts.
It depends on how in-depth you are. Each of the keywords you wrote can be written into a book. Personally, I think more than half a year is too short. I guess it is relatively shallow, which should be the extent of understanding it
Young man, I have a set of "Distributed System Architect" interview questions here. Why don't you try to answer them? If you can answer them all, you can write them.
什么是高可用
什么是雙機(jī)熱備,雙機(jī)熱備有那些缺陷
什么是雙活
請(qǐng)簡述實(shí)現(xiàn)軟件高可用要考慮那些因素
數(shù)據(jù)庫怎樣實(shí)現(xiàn)災(zāi)備
緩存怎樣實(shí)現(xiàn)災(zāi)備
應(yīng)用服務(wù)器怎樣實(shí)現(xiàn)災(zāi)備
Web 服務(wù)器怎樣實(shí)現(xiàn)災(zāi)備
計(jì)劃任務(wù)、定時(shí)周期運(yùn)行的程序怎樣災(zāi)備
消息隊(duì)列怎樣實(shí)現(xiàn)災(zāi)備
雙活的軟件怎樣實(shí)現(xiàn)同一時(shí)刻只能一個(gè)運(yùn)行,或者交替運(yùn)行
背景:
計(jì)劃任務(wù)即周期或定時(shí)運(yùn)行的程序,我們要解決單點(diǎn)故障問題與負(fù)載均衡的問題,在一個(gè)分布式系統(tǒng)中單節(jié)點(diǎn)是不允許的。
設(shè)計(jì)要求:
能夠?qū)崿F(xiàn)高可用,負(fù)載均衡,橫向擴(kuò)展
怎樣處理同時(shí)運(yùn)行產(chǎn)生的沖突問題?
怎樣排隊(duì)運(yùn)行?
任務(wù)如何持久化?
一個(gè)節(jié)點(diǎn)宕機(jī),另一個(gè)節(jié)點(diǎn)怎么接管沒有完成的任務(wù)?
如何橫向擴(kuò)展?
擴(kuò)展,收縮,維護(hù)如果能做到不停機(jī),不影響業(yè)務(wù)?
I think you said it’s not good to write “understand” all the time. You also need a few “familiar”. If you can answer all the above questions without searching, then you can write “familiar”.
Don’t stop at mastering the spelling of these Chinese characters
Use words accurately. It is generally not a big problem to write understanding, but no one will believe it if you write familiar or proficient. But don’t put what you don’t understand on your resume.
After half a year, I think it’s good to understand concurrency first.
Better than most PHP resumes I have seen (not fresh graduates).
The mobile version of SF didn’t even show all the questions, but we were attracted in. This shows how attractive these technologies are.
Of course, the extent to which the subject can master the question is another matter. Don’t exaggerate.
If you are proficient or familiar with negotiation, you can apply for an architect
If you master these, of course it will be a highlight. These are essential skills for architects and senior engineers. If you dare to write these without mastering them, you are seeking death.
You are applying for an architect job! ! It is recommended to master the basics of Java first
Recommendation:
If you have an in-depth understanding of the source code of the relevant framework or have implemented one yourself, you can write about the above points; otherwise, if you have simply read or dealt with related business commons, just write directly to understand
Write more about the business handled by the project and the frameworks and libraries involved. They have just been released. Being pragmatic is the most important thing