[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article:sansan-honne-15":3},{"meta":4,"markdown":171},{"type":5,"articleId":6,"slug":6,"title":7,"titleEn":8,"category":9,"summary":10,"publishedAt":11,"image":12,"vocabulary":13,"source":168},"article","sansan-honne-15","入社後のホンネ［技術本部 データ戦略部 Infrastructureグループ 渡邉 友］","Candid Talk After Joining [Technology Division, Data Strategy Department, Infrastructure Group — Yu Watanabe]","software\u002Fcompanies\u002Fsansan","Infrastructure engineer Watanabe reflects on joining Sansan, catching up in a new tech domain, and the self-driven, cross-functional engineering culture.","2026-04-26T00:00:00Z","https:\u002F\u002Fimages.yamiyomi.com\u002Fsansan-honne-15.png",[14,19,23,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164],{"word":15,"reading":16,"meaning":17,"level":18},"企画","きかく","project, planning","N2",{"word":20,"reading":21,"meaning":22,"level":18},"扱う","あつかう","to handle, deal with",{"word":24,"reading":25,"meaning":26,"level":27},"聞き出す","ききだす","to draw out, elicit","N1",{"word":29,"reading":30,"meaning":31,"level":18},"業務","ぎょうむ","work, duties",{"word":33,"reading":34,"meaning":35,"level":18},"収集","しゅうしゅう","collection, gathering",{"word":37,"reading":38,"meaning":39,"level":18},"蓄積","ちくせき","accumulation, buildup",{"word":41,"reading":42,"meaning":43,"level":27},"利活用","りかつよう","utilization, practical use",{"word":45,"reading":46,"meaning":47,"level":18},"既存","きそん","existing, pre-existing",{"word":49,"reading":50,"meaning":51,"level":18},"保守","ほしゅ","maintenance, upkeep",{"word":53,"reading":54,"meaning":55,"level":18},"運用","うんよう","operation, management",{"word":57,"reading":58,"meaning":59,"level":18},"新規","しんき","new, fresh",{"word":61,"reading":62,"meaning":63,"level":18},"構築","こうちく","construction, building",{"word":65,"reading":66,"meaning":67,"level":18},"並行","へいこう","parallel, concurrent",{"word":69,"reading":70,"meaning":71,"level":18},"担当","たんとう","in charge of, responsible for",{"word":73,"reading":74,"meaning":75,"level":18},"取り除く","とりのぞく","to remove, eliminate",{"word":77,"reading":78,"meaning":79,"level":18},"領域","りょういき","domain, area, field",{"word":81,"reading":82,"meaning":83,"level":18},"抱える","かかえる","to hold, carry (a burden)",{"word":85,"reading":86,"meaning":87,"level":27},"自走","じそう","self-driven, autonomous",{"word":89,"reading":90,"meaning":91,"level":18},"同僚","どうりょう","coworker, colleague",{"word":93,"reading":94,"meaning":95,"level":27},"食らいつく","くらいつく","to cling on, hang in there",{"word":97,"reading":98,"meaning":99,"level":18},"前後","ぜんご","before and after",{"word":101,"reading":102,"meaning":103,"level":27},"自社","じしゃ","one's own company",{"word":105,"reading":106,"meaning":107,"level":18},"貢献","こうけん","contribution",{"word":109,"reading":110,"meaning":111,"level":18},"意識","いしき","awareness, mindset",{"word":113,"reading":114,"meaning":115,"level":18},"集団","しゅうだん","group, collective",{"word":117,"reading":118,"meaning":119,"level":27},"強いて","しいて","if forced to say, if pressed",{"word":121,"reading":122,"meaning":123,"level":27},"守備範囲","しゅびはんい","area of coverage, scope",{"word":125,"reading":126,"meaning":127,"level":27},"境界線","きょうかいせん","boundary line",{"word":129,"reading":130,"meaning":131,"level":18},"品質","ひんしつ","quality",{"word":133,"reading":134,"meaning":135,"level":18},"向上","こうじょう","improvement, advancement",{"word":137,"reading":138,"meaning":139,"level":27},"本部","ほんぶ","headquarters, division",{"word":141,"reading":142,"meaning":143,"level":18},"独立","どくりつ","independent, standalone",{"word":145,"reading":146,"meaning":147,"level":27},"一丸","いちがん","as one unit, united",{"word":149,"reading":150,"meaning":151,"level":18},"取り組む","とりくむ","to tackle, work on",{"word":153,"reading":154,"meaning":155,"level":27},"同居","どうきょ","coexisting, sharing space",{"word":157,"reading":158,"meaning":159,"level":18},"相互","そうご","mutual, reciprocal",{"word":161,"reading":162,"meaning":163,"level":27},"密","みつ","close, dense, tight",{"word":165,"reading":166,"meaning":167,"level":27},"隔て","へだて","separation, barrier",{"name":169,"url":170},"Sansan mimi","https:\u002F\u002Fjp.corp-sansan.com\u002Fmimi\u002F2022\u002F12\u002Fhonne-15.html","\n::para\n[入社]{にゅうしゃ:joining a company:N4}から[少し]{すこし:a little:N4}[時間]{じかん:time:N5}が[経った]{たった:has passed:N3}メンバーに、[現在]{げんざい:current, now:N3}のSansanのエンジニアライフについてホンネを[聞き出す]{ききだす:to draw out, elicit:N5}[当]{とう:this:N3}[企画]{きかく:project, feature:N1}。[扱う]{あつかう:to handle, deal with:N1}プロダクトの[変化]{へんか:change:N3}に[不安]{ふあん:anxiety, unease:N4}を[感じて]{かんじて:feeling:N3}いた[渡邉]{わたなべ:Watanabe (surname):N1}が、Sansanに[入社]{にゅうしゃ:joining a company:N4}[後]{ご:after:N5}どのようにキャッチアップしていったのかインタビューしました。\n\n#en\nIn this feature, we draw out the candid thoughts of members who have been with Sansan for a while about their current engineering life. We interviewed Watanabe, who felt uneasy about the change in the products he would be handling, about how he caught up after joining Sansan.\n::\n\n::heading\n[自社]{じしゃ:one's own company:N4}プロダクトを[大事]{だいじ:important:N4}に[育て]{そだて:to nurture:N3} [事業]{じぎょう:business:N4}に[貢献]{こうけん:contribute:N1}する[集団]{しゅうだん:group:N2}\n\n#en\nA group that carefully nurtures its own products and contributes to the business\n::\n\n::callout\n[現在]{げんざい:currently:N3}どんな[業務]{ぎょうむ:work, duties:N3}をしていますか？\n\n#en\nWhat kind of work are you doing now?\n::\n\n::para\n[営業]{えいぎょう:sales:N2}DXサービス「Sansan」で[収集]{しゅうしゅう:collection:N3}・[蓄積]{ちくせき:accumulation:N1}したデータを[利活用]{りかつよう:utilization:N3}することをメインミッションとする[部]{ぶ:department:N3}で、[既存]{きそん:existing:N1}システムの[保守]{ほしゅ:maintenance:N1}[運用]{うんよう:operation:N4}と[新規]{しんき:new:N3}システムのシステムインフラ[構築]{こうちく:construction, setup:N2}を[並行]{へいこう:in parallel:N2}して[担当]{たんとう:in charge of:N2}しています。\n\n#en\nI work in a department whose main mission is to utilize the data collected and accumulated through the sales DX service \"Sansan.\" I handle the maintenance and operation of existing systems in parallel with the infrastructure setup of new systems.\n::\n\n::callout\nSansanへ[入社]{にゅうしゃ:joining the company:N4}する[前]{まえ:before:N5}に[不安]{ふあん:anxiety:N4}に[感じて]{かんじて:feeling:N3}いたことと、その[不安]{ふあん:anxiety:N4}が[取り除かれた]{とりのぞかれた:was removed:N3}きっかけや[出来事]{できごと:event, incident:N4}があれば[教えて]{おしえて:please tell:N4}ください。\n\n#en\nPlease tell us what you were anxious about before joining Sansan, and any trigger or event that dispelled that anxiety.\n::\n\n::para\n[前職]{ぜんしょく:previous job:N3}でもシステムインフラを[担当]{たんとう:in charge of:N2}していたとはいえ、[扱って]{あつかって:handling:N1}いるプロダクト[自体]{じたい:itself:N4}は[大きく]{おおきく:greatly:N5}[異なる]{ことなる:to differ:N1}ものであったので、[技術]{ぎじゅつ:technology:N2}[領域]{りょういき:domain, area:N2}のキャッチアップには[不安]{ふあん:anxiety:N4}を[抱えた]{かかえた:carried, held:N3}まま[入社]{にゅうしゃ:joining the company:N4}しました。[入社]{にゅうしゃ:joining the company:N4}してみると「[自走]{じそう:self-driven:N4}」が[基本]{きほん:basic, fundamental:N1}であるということはまさしくその[通り]{とおり:as, exactly:N4}でしたが、その[自走]{じそう:self-driven:N4}をサポートしてくれる[先輩]{せんぱい:senior colleague:N1}・[同僚]{どうりょう:coworker:N1}が[多く]{おおく:many:N4}いらっしゃったため、[何]{なん:somehow:N5}とか[食らいつく]{くらいつく:to cling on, keep up:N5}ことができていると[思って]{おもって:thinking:N4}います。\n\n#en\nAlthough I handled system infrastructure in my previous job too, the products themselves were greatly different, so I joined still carrying anxiety about catching up in the technology domain. After joining, it turned out that \"self-driven work\" really is the basis here, but there are many senior colleagues and coworkers who support that self-driven style, so I feel I have managed to hold on.\n::\n\n::callout\n[入社]{にゅうしゃ:joining the company:N4}[前]{まえ:before:N5}と[後]{あと:after:N5}で、Sansanエンジニアに[対する]{たいする:toward:N3}イメージは[変わりました]{かわりました:changed:N3}か？\n\n#en\nDid your image of Sansan engineers change between before and after joining?\n::\n\n::para\n[入社]{にゅうしゃ:joining the company:N4}[前後]{ぜんご:before and after:N5}でイメージの[変化]{へんか:change:N3}はありません。[自社]{じしゃ:one's own company:N4}プロダクトを[大事]{だいじ:important, valued:N4}にしてSansanの[事業]{じぎょう:business:N4}[成長]{せいちょう:growth:N3}に[貢献]{こうけん:contribution:N1}するという[意識]{いしき:awareness, mindset:N3}を[強く]{つよく:strongly:N4}[持って]{もって:holding:N4}いる[集団]{しゅうだん:group:N2}だと[思います]{おもいます:I think:N4}。[強いて]{しいて:if pressed:N4}ギャップを[上げる]{あげる:to raise, cite:N5}とすればエンジニアごとの[守備]{しゅび:defense, coverage:N3}[範囲]{はんい:range, scope:N1}が[広く]{ひろく:broadly:N4}その[境界線]{きょうかいせん:boundary line:N2}が[薄い]{うすい:thin, faint:N2}ということです。\n\n#en\nMy image did not change between before and after joining. They are a group with a strong sense of valuing their own products and contributing to Sansan’s business growth. If I had to cite a gap, it would be that each engineer’s coverage is broad and the boundaries between roles are faint.\n::\n\n::para\n[現在]{げんざい:currently:N3}、[次々]{つぎつぎ:one after another:N3}と[立ち上がって]{たちあがって:being launched:N4}いるプロジェクトやシステムに[対して]{たいして:toward:N3}[全体]{ぜんたい:overall:N3}[的]{てき:like:N4}にその[品質]{ひんしつ:quality:N4}を[向上]{こうじょう:improve:N3}できるような[活動]{かつどう:activity:N3}に[貢献]{こうけん:contribute:N1}したいと[思って]{おもって:thinking:N4}います。[技術]{ぎじゅつ:technology:N2}[本部]{ほんぶ:headquarters:N3}ではさまざまなシステムが[存在]{そんざい:exist:N3}しており、そのナレッジについても[各]{かく:each:N2}システムごとに[独立]{どくりつ:independent:N1}しているような[印象]{いんしょう:impression:N2}を[受けます]{うけます:receive:N3}。\n\n#en\nCurrently I would like to contribute to activities that can improve the overall quality of the projects and systems being launched one after another. Various systems exist within the Technology Division, and I get the impression that the knowledge about them is independent per system.\n::\n\n::para\nやはり、アプリケーション[開発]{かいはつ:development:N4}メンバーとインフラメンバーとで[一丸]{いちがん:as one unit:N2}となって[開発]{かいはつ:development:N4}に[取り組める]{とりくめる:to be able to tackle:N3}ことです。[一丸]{いちがん:as one unit:N2}となるといっても、プロジェクトメンバーとして[同居]{どうきょ:living together, coexist:N3}しているということにとどまらず[相互]{そうご:mutual:N3}に[密]{みつ:close, dense:N1}なコミュニケーションをとりながら[良い]{よい:good:N3}[意味]{いみ:sense, meaning:N4}で[担当]{たんとう:responsibility:N2}の[隔て]{へだて:separation, barrier:N1}を[持たず]{もたず:without holding:N4}に[仕事]{しごと:work:N4}に[取り組める]{とりくめる:to be able to tackle:N3}のはSansanエンジニアならではなのではないかと[思って]{おもって:thinking:N4}います。\n\n#en\nAbove all, it is that application development members and infrastructure members can tackle development as one unit. Being one unit does not stop at just coexisting as project members — we communicate closely with each other and can work without barriers between responsibilities, which I think is something unique to Sansan engineers.\n::\n"]