[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article:sansan-interview-40":3},{"meta":4,"markdown":263},{"type":5,"articleId":6,"slug":6,"title":7,"titleEn":8,"category":9,"summary":10,"publishedAt":11,"image":12,"vocabulary":13,"source":260},"article","sansan-interview-40","膨大な量のデータを平然と処理する。Sansanのインフラのすごさが、そこに表れている。","Calmly processing vast volumes of data — that is where the impressiveness of Sansan’s infrastructure shows.","software\u002Fcompanies\u002Fsansan","Interview with Sansan infrastructure engineer Akabane Tomoyuki on building the platform behind Contract One Entry and the scale of Sansan’s data digitization operations.","2026-04-26T00:00:00Z","https:\u002F\u002Fimages.yamiyomi.com\u002Fsansan-interview-40.png",[14,19,23,27,31,35,39,43,47,51,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,168,172,176,180,184,188,192,196,200,204,208,212,216,220,224,228,232,236,240,244,248,252,256],{"word":15,"reading":16,"meaning":17,"level":18},"請求書","せいきゅうしょ","invoice, bill","N2",{"word":20,"reading":21,"meaning":22,"level":18},"契約書","けいやくしょ","contract document",{"word":24,"reading":25,"meaning":26,"level":18},"仕組み","しくみ","mechanism, system",{"word":28,"reading":29,"meaning":30,"level":18},"本部","ほんぶ","headquarters, head office",{"word":32,"reading":33,"meaning":34,"level":18},"部署","ぶしょ","department, section",{"word":36,"reading":37,"meaning":38,"level":18},"活躍","かつやく","to be active, play a role",{"word":40,"reading":41,"meaning":42,"level":18},"事業","じぎょう","business",{"word":44,"reading":45,"meaning":46,"level":18},"支える","ささえる","to support, sustain",{"word":48,"reading":49,"meaning":50,"level":18},"構築","こうちく","construction, building",{"word":52,"reading":53,"meaning":54,"level":55},"醍醐味","だいごみ","real thrill, true charm","N1",{"word":57,"reading":58,"meaning":59,"level":18},"前職","ぜんしょく","previous job",{"word":61,"reading":62,"meaning":63,"level":18},"納品","のうひん","delivery (of goods)",{"word":65,"reading":66,"meaning":67,"level":18},"継続的","けいぞくてき","continuous",{"word":69,"reading":70,"meaning":71,"level":18},"向き合う","むきあう","to face, confront",{"word":73,"reading":74,"meaning":75,"level":55},"歯痒い","はがゆい","frustrating, vexing",{"word":77,"reading":78,"meaning":79,"level":18},"自社","じしゃ","in-house, own company",{"word":81,"reading":82,"meaning":83,"level":18},"運用","うんよう","operation",{"word":85,"reading":86,"meaning":87,"level":18},"企業","きぎょう","company, enterprise",{"word":89,"reading":90,"meaning":91,"level":18},"転職","てんしょく","to change jobs",{"word":93,"reading":94,"meaning":95,"level":18},"魅力","みりょく","charm, appeal",{"word":97,"reading":98,"meaning":99,"level":18},"扱う","あつかう","to handle, deal with",{"word":101,"reading":102,"meaning":103,"level":18},"膨大","ぼうだい","vast, enormous",{"word":105,"reading":106,"meaning":107,"level":18},"処理","しょり","processing",{"word":109,"reading":110,"meaning":111,"level":55},"平然と","へいぜんと","calmly, with composure",{"word":113,"reading":114,"meaning":115,"level":18},"表れる","あらわれる","to appear, be shown",{"word":117,"reading":118,"meaning":119,"level":18},"担う","になう","to shoulder, be in charge of",{"word":121,"reading":122,"meaning":123,"level":18},"初期","しょき","early stage",{"word":125,"reading":126,"meaning":127,"level":18},"段階","だんかい","phase, stage",{"word":129,"reading":130,"meaning":131,"level":18},"最善","さいぜん","the best",{"word":133,"reading":134,"meaning":135,"level":18},"推奨","すいしょう","recommend, encourage",{"word":137,"reading":138,"meaning":139,"level":18},"特徴","とくちょう","feature, characteristic",{"word":141,"reading":142,"meaning":143,"level":18},"事例","じれい","example, case",{"word":145,"reading":146,"meaning":147,"level":18},"基盤","きばん","platform, foundation",{"word":149,"reading":150,"meaning":151,"level":18},"工程","こうてい","process, stage",{"word":153,"reading":154,"meaning":155,"level":18},"導入","どうにゅう","to introduce, adopt",{"word":157,"reading":158,"meaning":159,"level":18},"携わる","たずさわる","to be engaged in",{"word":161,"reading":162,"meaning":163,"level":18},"達成感","たっせいかん","sense of accomplishment",{"word":165,"reading":166,"meaning":167,"level":18},"業務","ぎょうむ","work, duties",{"word":169,"reading":170,"meaning":171,"level":18},"視点","してん","viewpoint, perspective",{"word":173,"reading":174,"meaning":175,"level":18},"重要性","じゅうようせい","importance",{"word":177,"reading":178,"meaning":179,"level":18},"意識","いしき","consciousness, awareness",{"word":181,"reading":182,"meaning":183,"level":18},"変換","へんかん","conversion",{"word":185,"reading":186,"meaning":187,"level":18},"抑える","おさえる","to hold down, reduce",{"word":189,"reading":190,"meaning":191,"level":18},"削減","さくげん","reduction, cut",{"word":193,"reading":194,"meaning":195,"level":18},"直結","ちょっけつ","directly linked",{"word":197,"reading":198,"meaning":199,"level":18},"可用性","かようせい","availability",{"word":201,"reading":202,"meaning":203,"level":18},"信頼性","しんらいせい","reliability",{"word":205,"reading":206,"meaning":207,"level":18},"相当","そうとう","considerably",{"word":209,"reading":210,"meaning":211,"level":18},"重視","じゅうし","to value, emphasize",{"word":213,"reading":214,"meaning":215,"level":18},"述べる","のべる","to mention, state",{"word":217,"reading":218,"meaning":219,"level":18},"検証","けんしょう","verify, validate",{"word":221,"reading":222,"meaning":223,"level":18},"新規","しんき","new, novel",{"word":225,"reading":226,"meaning":227,"level":18},"立ち上げる","たちあげる","to launch, start up",{"word":229,"reading":230,"meaning":231,"level":18},"開始","かいし","to start, begin",{"word":233,"reading":234,"meaning":235,"level":18},"据える","すえる","to place, position",{"word":237,"reading":238,"meaning":239,"level":18},"築く","きずく","to build up",{"word":241,"reading":242,"meaning":243,"level":55},"結実","けつじつ","to bear fruit, come to fruition",{"word":245,"reading":246,"meaning":247,"level":18},"明確","めいかく","clear, definite",{"word":249,"reading":250,"meaning":251,"level":18},"競合","きょうごう","competition, rivalry",{"word":253,"reading":254,"meaning":255,"level":18},"優位性","ゆういせい","advantage, superiority",{"word":257,"reading":258,"meaning":259,"level":18},"貢献","こうけん","contribution",{"name":261,"url":262},"Sansan mimi","https:\u002F\u002Fjp.corp-sansan.com\u002Fmimi\u002F2022\u002F06\u002Finterview-40.html","\n::para\n[紙]{かみ:paper:N4}の[名刺]{めいし:business card:N2}や[請求書]{せいきゅうしょ:invoice, bill:N1}、[契約書]{けいやくしょ:contract document:N1}などのデータ[化]{か:-ization, conversion to:N3}のための[仕組み]{しくみ:mechanism, system:N3}[づくり]{づくり:making, building}とシステム[開発]{かいはつ:development:N4}を[担う]{になう:to shoulder, be in charge of:N2}[技術]{ぎじゅつ:technology:N2}[本部]{ほんぶ:headquarters, head office:N3} Digitization[部]{ぶ:department:N3}。この[部署]{ぶしょ:department, section:N2}においてインフラエンジニアとして[活躍]{かつやく:to be active, play a role:N1}するのが[赤羽]{あかばね:Akabane (surname):N2} [智幸]{ともゆき:Tomoyuki (given name):N1}です。Sansan[株式会社]{かぶしきがいしゃ:corporation, Inc.:N1}の[事業]{じぎょう:business:N4}のコアを[支える]{ささえる:to support, sustain:N3}、インフラ[構築]{こうちく:construction, building:N2}の[醍醐味]{だいごみ:real thrill, true charm:N1}とは。\n\n#en\nThe Technology Division’s Digitization Department is responsible for building the systems and mechanisms that digitize paper business cards, invoices, contracts, and the like. Akabane Tomoyuki is an infrastructure engineer active in this department. What is the true thrill of building the infrastructure that supports the core of Sansan’s business?\n::\n\n::heading\n「Contract One Entry」の[基盤]{きばん:platform, foundation:N1}[構築]{こうちく:construction, building:N2}を[通じて]{つうじて:through:N4}エンジニアとして[成長]{せいちょう:growth:N3}\n\n#en\nGrowing as an engineer through the platform construction of \"Contract One Entry\"\n::\n\n::para\n[前職]{ぜんしょく:previous job:N3}ではSIerに[勤めて]{つとめて:to work for:N3}おり「[納品]{のうひん:delivery (of goods):N1}したらプロジェクトが[終わり]{おわり:end:N4}」という[働き方]{はたらきかた:way of working:N3}をしていました。ひとつのシステムと[継続的]{けいぞくてき:continuous:N1}に[向き合う]{むきあう:to face, confront:N3}ことが[難しく]{むずかしく:difficult:N3}、[歯痒い]{はがゆい:frustrating, vexing:N1}[気持ち]{きもち:feeling:N4}を[覚えて]{おぼえて:to feel, experience:N3}いました。そこで、[自社]{じしゃ:in-house, own company:N4}サービスを[開発]{かいはつ:development:N4}・[運用]{うんよう:operation:N4}している[企業]{きぎょう:company, enterprise:N1}に[転職]{てんしょく:to change jobs:N3}しようと[考えた]{かんがえた:to think:N4}のです。\n\n#en\nAt my previous job I worked for an SIer, where the style was \"project ends when delivery is made.\" It was hard to engage continuously with a single system, and I felt frustrated by that. So I decided to move to a company that develops and operates its own in-house services.\n::\n\n::para\nSansan[株式会社]{かぶしきがいしゃ:corporation, Inc.:N1}に[魅力]{みりょく:charm, appeal:N1}を[感じた]{かんじた:to feel:N3}[理由]{りゆう:reason:N3}としては、まず[扱う]{あつかう:to handle, deal with:N1}データ[量]{りょう:volume, amount:N2}の[膨大]{ぼうだい:vast, enormous:N1}さが[挙げられます]{あげられます:can be cited:N1}。[一日]{いちにち:one day:N5}あたり[数万]{すうまん:tens of thousands:N3}[件]{けん:items, cases:N3}[以上]{いじょう:or more:N4}もの[名刺]{めいし:business card:N2}のデータ[化]{か:-ization, conversion to:N3}[処理]{しょり:processing:N3}を、トラブルも[出さず]{ださず:without causing:N5}に[平然と]{へいぜんと:calmly, with composure:N3}[行って]{おこなって:to carry out:N5}いる。その[点]{てん:point:N3}にSansanのインフラのすごさが[表れて]{あらわれて:to appear, be shown:N3}います。\n\n#en\nOne reason I felt drawn to Sansan was, above all, the sheer volume of data it handles. It calmly processes the digitization of tens of thousands of business cards a day without any trouble. That is where the impressiveness of Sansan’s infrastructure really shows.\n::\n\n::para\nSansanには、インフラエンジニアがプロジェクトの[初期]{しょき:early stage:N3}[段階]{だんかい:phase, stage:N2}からアプリケーションエンジニアやビジネスサイドとコミュニケーションをとって、[最善]{さいぜん:the best:N1}のインフラを[作って]{つくって:to build, make:N4}いく[文化]{ぶんか:culture:N3}があります。そして、Sansanはエンジニアのチャレンジを[推奨]{すいしょう:recommend, encourage:N1}しています。この[特徴]{とくちょう:feature, characteristic:N1}がよく[表れて]{あらわれて:to appear, be shown:N3}いる[事例]{じれい:example, case:N3}が、[契約書]{けいやくしょ:contract document:N1}のデータ[化]{か:-ization, conversion to:N3}を[担う]{になう:to shoulder, be in charge of:N2}「Contract One Entry」の[基盤]{きばん:platform, foundation:N1}[構築]{こうちく:construction, building:N2}です。\n\n#en\nAt Sansan there is a culture where infrastructure engineers communicate with application engineers and the business side from the earliest phase of a project to build the best possible infrastructure. Sansan also encourages engineers to take on challenges. A clear example of this is the platform construction of \"Contract One Entry,\" which handles the digitization of contracts.\n::\n\n::para\n[契約書]{けいやくしょ:contract document:N1}のデータ[化]{か:-ization, conversion to:N3}の[工程]{こうてい:process, stage:N3}を[管理]{かんり:manage, control:N2}するために、Digitization[部]{ぶ:department:N3}で[初めて]{はじめて:for the first time:N3}AWS Step Functionsを[導入]{どうにゅう:to introduce, adopt:N2}しました。また、このプロジェクトでは、インフラ[構築]{こうちく:construction:N2}だけではなく[一部]{いちぶ:part, portion:N3}のアプリケーション[開発]{かいはつ:development:N4}にも[携わる]{たずさわる:to be engaged in:N1}ことができたのです。こうした[数多く]{かずおおく:many, numerous:N3}のチャレンジをしたことで、[大きな]{おおきな:large, big:N5}[達成感]{たっせいかん:sense of accomplishment:N3}を[得られ]{えられ:can gain, obtain:N3}、エンジニアとしても[成長]{せいちょう:growth:N3}できました。\n\n#en\nTo manage the process of digitizing contracts, we introduced AWS Step Functions for the first time in the Digitization Department. In this project I was also able to work on part of the application development, not just the infrastructure. Taking on so many challenges gave me a great sense of accomplishment and helped me grow as an engineer.\n::\n\n::heading\n[事業]{じぎょう:business:N4}に[貢献]{こうけん:contribution:N1}するインフラエンジニアでありたい\n\n#en\nI want to be an infrastructure engineer who contributes to the business\n::\n\n::para\nSansanの[業務]{ぎょうむ:work, duties:N3}を[通じて]{つうじて:through:N4}[身]{み:body, self:N4}についた[視点]{してん:viewpoint, perspective:N1}やスキルはいくつもあります。まず、コストの[重要性]{じゅうようせい:importance:N3}を[意識]{いしき:consciousness, awareness:N3}するようになったことです。Digitization[部]{ぶ:department:N3}は\"アナログ→デジタルの[変換]{へんかん:conversion:N2}[処理]{しょり:processing:N3}\"を[担って]{になって:to be in charge of:N2}います。[扱う]{あつかう:to handle:N1}データ[量]{りょう:volume:N2}が[膨大]{ぼうだい:vast, enormous:N1}だからこそ、1データあたりの[変換]{へんかん:conversion:N2}にかかるコストを[少しでも]{すこしでも:even slightly:N4}[抑える]{おさえる:to hold down, reduce:N1}ことが、[事業]{じぎょう:business:N4}[全体]{ぜんたい:whole, overall:N3}のコスト[削減]{さくげん:reduction, cut:N1}に[直結]{ちょっけつ:directly linked:N1}します。\n\n#en\nThere are several perspectives and skills I have gained through my work at Sansan. First, I have become conscious of the importance of cost. The Digitization Department is in charge of \"analog-to-digital conversion processing.\" Precisely because the data volume we handle is enormous, even a small reduction in the cost per data item translates directly into reducing overall business costs.\n::\n\n::para\nまた、システムのスケーラビリティや[可用性]{かようせい:availability:N3}、[信頼性]{しんらいせい:reliability:N3}を[相当]{そうとう:considerably:N3}に[重視]{じゅうし:to value, emphasize:N1}するようになりました。[例えば]{たとえば:for example:N3}、[先ほど]{さきほど:earlier, a moment ago:N5}[述べた]{のべた:mentioned, stated:N2}「Contract One Entry」の[基盤]{きばん:platform, foundation:N1}[構築]{こうちく:construction:N2}の[際]{さい:time, occasion:N3}にも「[変換]{へんかん:conversion:N2}[対象]{たいしょう:target, subject:N2}のデータ[量]{りょう:volume:N2}が[今後]{こんご:from now on, hereafter:N5}さらに[増えた]{ふえた:to increase:N3}としても、さばき[切れる]{きれる:to be able to handle fully:N4}インフラアーキテクチャになっていること」を、かなりの[時間]{じかん:time:N5}をかけて[検証]{けんしょう:verify, validate:N1}しました。\n\n#en\nI have also come to place considerable weight on system scalability, availability, and reliability. For example, when building the platform for the \"Contract One Entry\" I mentioned earlier, we spent a significant amount of time verifying that \"the infrastructure architecture would be able to handle the data volume even as the conversion target grows substantially in the future.\"\n::\n\n::para\nSansanは[現在]{げんざい:currently, at present:N3}、[数多く]{かずおおく:many, numerous:N3}の[新規]{しんき:new, novel:N3}[事業]{じぎょう:business:N4}を[立ち上げて]{たちあげて:to launch, start up:N4}います。そして、どのような[事業]{じぎょう:business:N4}を[開始]{かいし:to start, begin:N4}する[場合]{ばあい:case, situation:N3}でも、アナログ→デジタルのデータ[化]{か:-ization, conversion to:N3}[処理]{しょり:processing:N3}を、サービスのコアの[機能]{きのう:function, feature:N3}として[据えて]{すえて:to place, position:N1}います。その[機能]{きのう:function, feature:N3}こそ、Sansanが[長年]{ながねん:many years:N5}かけて[築いて]{きずいて:to build up:N2}きたノウハウが[結実]{けつじつ:to bear fruit, come to fruition:N1}したものであり、[明確]{めいかく:clear, definite:N3}な[競合]{きょうごう:competition, rivalry:N2}[優位性]{ゆういせい:advantage, superiority:N3}になる[部分]{ぶぶん:part, portion:N3}だからです。\n\n#en\nSansan is currently launching many new businesses. And no matter what kind of business we start, analog-to-digital data conversion is positioned as a core function of the service. That function is the fruit of the know-how Sansan has built up over many years, and it is the part that forms a clear competitive advantage.\n::\n"]