職位描述：

職責描述：

RoleMission

TheITApplicationLeadArchitectwillleadarchitectscommunitytomaintaininglocaltechnicalprincipalsandstandards,triggeranddrivearchitecturereviewoflocalsolutions,ensurealllocalapplicationsaligned.

KeyResponsibilities

?Maintainlocalapplicationsarchitecturalrules,standards,processesandstandards.

?Setupandleadarchitectcommunity,alignalldevelopmentlanguagetracks.

?Triggeranddrivelocalapplicationsarchitecturereview.

?ExpectedtobeupdatedwiththecurrentITmarkettrendscrossplatforms.

?KeycontributortotheKnowledgeShareCommunity.

?Influence,educateandsupporttechnicalleaderstoensuretheappropriatelevelsofqualityonlocalapplicationarchitecture(s).

任職要求：

Requirements:

a.Education

?985or211education

?Computersciencerelatedmajor

?Bacheloratleast

?Overseasuniversitiesmustbethetop20atleastonlocalcountryortop50intheworld

b.Experience/skills

?ExpertasJavatechnical,fullstacktechnicalview,familiarforsomeoriginalcode,suchasSpring,JDK

?In-depthunderstandingfortheapplicationarchitectdesign,andgoodwithdesignlanguage,suchasUML

?Strongsenseandknowledgefortheapplicationrefactordesign

?Atleast10+yearsdevelopmentanddesignexperience,5+yearsatleastforarchitectdesign

?3+yearsheadInternetcompany,suchasAlibaba,Tencent,JD,MeiTuan,etc,andactingasthecoredesignworking,suchasAlibabatechnicalP7+level

?Experiencefortechnicalteammanagementatleast3+years

?Experienceforthehighconcurrencyarchitectdesign,suchasmillionlevelQPSscenario

?Extensiveknowledgewithmajormiddlecomponent,protocolanddevelopmentframeinmarketing,suchasAMQP(RabbitMQ),Kafka,Reids,Monogo,Spark,Zookeeper,Springcloud,SpringBoot,ServiceMesh(Istio),HTTP2,TCP,RPC,etc

?Abilityforbusinesslevelanalyzingandbreakingdown

?Strongcommunicationskillwithtechnicalandnone-technicalscenario

c.英語要:Englishrequest

?LiteracyforEnglish

?FluencywithEnglish

篇2:數據架構師崗位工作職責

1、深入理解MDM主數據管理思想和流程;

2、理解業務數據、主數據與元數據的區別與關系;

3、參與過數據模型的設計與開發;

4、深入理解數據清洗,標準化,轉換,匹配,數據質量、安全管理的原理和業務流程;

5、參與過數據ETL開發與設計;

6、熟練運用主流DBMS,nosql數據庫。

篇3:軟件架構師崗位工作職責

1、領導與協調整個項目中的技術活動(分析、設計和實施等)?

2、推動主要的技術決策,并最終表達為軟件構架?

3、確定和文檔化系統的相對構架而言意義重大的方面,包括系統的需求、設計、實施和部署等“視圖”?

4、確定設計元素的分組以及這些主要分組之間的接口?

5、為技術決策提供規則,平衡各類涉眾的不同關注點,化解技術風險,并保證相關決定被有效的傳達和貫徹?

6、理解、評價并接收系統需求?

7、評價和確認軟件架構的實現