[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article:sansan-interview-130":3},{"meta":4,"markdown":115},{"type":5,"articleId":6,"slug":6,"title":7,"titleEn":8,"category":9,"summary":10,"publishedAt":11,"image":12,"vocabulary":13,"source":112},"article","sansan-interview-130","Sansanの全社基盤を支えるPlatform Engineering Unitの挑戦","The Challenge of the Platform Engineering Unit Supporting Sansan’s Company-wide Infrastructure","software\u002Fcompanies\u002Fsansan","Interview with the leaders of Sansan’s newly formed Platform Engineering Unit about building company-wide developer and auth infrastructure.","2026-04-26T00:00:00Z","https:\u002F\u002Fimages.yamiyomi.com\u002Fsansan-interview-130.png",[14,19,23,27,31,35,39,43,47,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108],{"word":15,"reading":16,"meaning":17,"level":18},"新設","しんせつ","newly established","N2",{"word":20,"reading":21,"meaning":22,"level":18},"集中","しゅうちゅう","to concentrate, focus",{"word":24,"reading":25,"meaning":26,"level":18},"整える","ととのえる","to arrange, prepare",{"word":28,"reading":29,"meaning":30,"level":18},"担う","になう","to shoulder, be in charge of",{"word":32,"reading":33,"meaning":34,"level":18},"携わる","たずさわる","to be engaged in, work on",{"word":36,"reading":37,"meaning":38,"level":18},"課題","かだい","issue, challenge",{"word":40,"reading":41,"meaning":42,"level":18},"従来","じゅうらい","conventionally, traditionally",{"word":44,"reading":45,"meaning":46,"level":18},"個別","こべつ","individual, separate",{"word":48,"reading":49,"meaning":50,"level":51},"共通化","きょうつうか","commonalization, unification","N1",{"word":53,"reading":54,"meaning":55,"level":51},"標準化","ひょうじゅんか","standardization",{"word":57,"reading":58,"meaning":59,"level":18},"負担","ふたん","burden",{"word":61,"reading":62,"meaning":63,"level":51},"軽減","けいげん","reduce, mitigate",{"word":65,"reading":66,"meaning":67,"level":51},"認証","にんしょう","authentication",{"word":69,"reading":70,"meaning":71,"level":51},"認可","にんか","authorization",{"word":73,"reading":74,"meaning":75,"level":51},"信頼性","しんらいせい","reliability",{"word":77,"reading":78,"meaning":79,"level":51},"伴走","ばんそう","run alongside, accompany",{"word":81,"reading":82,"meaning":83,"level":51},"根幹","こんかん","core, foundation",{"word":85,"reading":86,"meaning":87,"level":51},"専門性","せんもんせい","specialisation, expertise",{"word":89,"reading":90,"meaning":91,"level":18},"追求","ついきゅう","pursue, seek",{"word":93,"reading":94,"meaning":95,"level":51},"心臓部","しんぞうぶ","core, heart (of a system)",{"word":97,"reading":98,"meaning":99,"level":51},"守り抜く","まもりぬく","to protect to the end",{"word":101,"reading":102,"meaning":103,"level":18},"一貫","いっかん","consistently, end-to-end",{"word":105,"reading":106,"meaning":107,"level":18},"構築","こうちく","construction, building",{"word":109,"reading":110,"meaning":111,"level":18},"挑む","いどむ","to take on, challenge",{"name":113,"url":114},"Sansan mimi","https:\u002F\u002Fjp.corp-sansan.com\u002Fmimi\u002F2025\u002F09\u002Finterview-130","\n::para\n2025[年]{ねん:year:N5}6[月]{がつ:month:N5}、Sansan[技術]{ぎじゅつ:technology:N2}[本部]{ほんぶ:headquarters, head office:N3}にPlatform Engineering Unitが[新設]{しんせつ:newly established:N2}されました。この[役割]{やくわり:role, function:N3}は、[開発者]{かいはつしゃ:developer:N4}がプロダクトの[機能]{きのう:function, feature:N3}[開発]{かいはつ:development:N4}に[集中]{しゅうちゅう:to concentrate, focus:N4}できる[環境]{かんきょう:environment:N1}を[整える]{ととのえる:to arrange, prepare:N1}ことです。\n\n#en\nIn June 2025, the Platform Engineering Unit was newly established within Sansan’s Technology Division. Its role is to create an environment in which developers can concentrate on building product features.\n::\n\n::heading\nなぜSansanは[今]{いま:now:N5}、「[全社]{ぜんしゃ:whole-company:N3}[共通]{きょうつう:common, shared:N3}[基盤]{きばん:platform, foundation:N1}」の[構築]{こうちく:construction, building:N2}に[挑む]{いどむ:to take on, challenge:N1}のか\n\n#en\nWhy is Sansan now taking on the construction of a \"company-wide common platform\"?\n::\n\n::para\n[水谷]{みずたに:Mizutani (surname):N2}：もともと[私]{わたし:I, me:N4}は、[新規]{しんき:new, novel:N3}[事業]{じぎょう:business:N4}[開発]{かいはつ:development:N4}を[担う]{になう:to shoulder, be in charge of:N2}Strategic Products Engineering Unit（[以下]{いか:the following, hereafter:N4}、SPEU）でSREグループのマネジャーをしていました。[複数]{ふくすう:multiple, several:N2}のサービスに[携わる]{たずさわる:to be engaged in, work on:N1}[中]{なか:in the midst of:N5}で「アプリケーション[開発者]{かいはつしゃ:developer:N4}が、インフラ[設定]{せってい:settings, configuration:N2}などに[時間]{じかん:time:N5}を[取られる]{とられる:to be taken up by:N3}ことが[課題]{かだい:issue, challenge:N2}だ」と[感じる]{かんじる:to feel, sense:N3}ようになったのです。\n\n#en\nMizutani: Originally I was the SRE group manager in the Strategic Products Engineering Unit (SPEU), which handles new-business development. Working across multiple services, I came to feel that application developers losing time to infrastructure configuration was a real problem.\n::\n\n::callout\nOrbitは、Sansan[社内]{しゃない:in-house, internal:N3}[向け]{むけ:intended for:N3}のシステム[開発]{かいはつ:development:N4}[基盤]{きばん:platform, foundation:N1}です。[従来]{じゅうらい:conventionally, traditionally:N1}、[各]{かく:each:N2}プロダクトごとに[個別]{こべつ:individual, separate:N2}[対応]{たいおう:handling, response:N1}していたインフラやCI\u002FCDパイプラインなどを[共通化]{きょうつうか:commonalization, unification:N3}・[標準化]{ひょうじゅんか:standardization:N1}することで、[開発]{かいはつ:development:N4}チームの[負担]{ふたん:burden:N2}を[軽減]{けいげん:reduce, mitigate:N2}します。\n\n#en\nOrbit is an internal system-development platform at Sansan. By commonalizing and standardizing the infrastructure and CI\u002FCD pipelines that were previously handled separately per product, it reduces the burden on development teams.\n::\n\n::callout\nAuth Oneは、Sansanが[提供]{ていきょう:provide, offer:N1}する[認証]{にんしょう:authentication:N1}・[認可]{にんか:authorization:N3}[基盤]{きばん:platform, foundation:N1}です。OpenID Connect（OIDC）のIDプロバイダーとして[機能]{きのう:to function:N3}し、[各]{かく:each:N2}プロダクトに[必要]{ひつよう:necessary, required:N3}なログインやシングルサインオン（SSO）を[共通化]{きょうつうか:commonalization:N3}・[標準化]{ひょうじゅんか:standardization:N1}します。\n\n#en\nAuth One is the authentication and authorization platform provided by Sansan. It functions as an OpenID Connect (OIDC) identity provider, commonalizing and standardizing the login and single sign-on (SSO) that each product needs.\n::\n\n::heading\n[開発者]{かいはつしゃ:developer:N4}に[伴走]{ばんそう:run alongside, accompany:N1}し、[活動]{かつどう:activity, operation:N3}の[根幹]{こんかん:core, foundation:N1}を[支える]{ささえる:to support, sustain:N3}「Application Platform Group」\n\n#en\nRunning alongside developers and supporting the core of their work — \"Application Platform Group\"\n::\n\n::para\n[鷹箸]{たかはし:Takahashi (surname):N1}：[私]{わたし:I, me:N4}たちの[役割]{やくわり:role:N3}は、[大きく]{おおきく:largely, broadly:N5}「プラットフォームエンジニア」と「Embedded SRE」の2つに[分かれる]{わかれる:to be divided, split:N5}。Zhangさんがプラットフォームエンジニアで、[私]{わたし:I, me:N4}はEmbedded SREとして[活動]{かつどう:activity, operation:N3}しています。Embedded SREとは、[特定]{とくてい:specific, particular:N3}の[開発]{かいはつ:development:N4}チームに[深く]{ふかく:deeply:N3}[関わる]{かかわる:to be involved in:N3}、サービスの[信頼性]{しんらいせい:reliability:N3}を[高める]{たかめる:to raise, increase:N5}ながら[開発]{かいはつ:development:N4}[速度]{そくど:speed, velocity:N3}の[向上]{こうじょう:improvement, enhancement:N3}も[担う]{になう:to carry, be responsible for:N2}[役割]{やくわり:role:N3}です。\n\n#en\nTakahashi: Our role is broadly divided into two: \"platform engineer\" and \"Embedded SRE.\" Zhang is a platform engineer, and I work as an Embedded SRE. The Embedded SRE role means getting deeply involved with a specific development team, raising service reliability while also helping improve development speed.\n::\n\n::heading\n[専門性]{せんもんせい:specialisation, expertise:N2}を[追求]{ついきゅう:pursue, seek:N3}し、サービスの[心臓部]{しんぞうぶ:core, heart:N2}を[守り抜く]{まもりぬく:to protect to the end:N3}「Identity Platform Group」\n\n#en\nPursuing specialisation and protecting the heart of the services — \"Identity Platform Group\"\n::\n\n::para\n[樋口]{ひぐち:Higuchi (surname):N1}：「Bill One」やAI[契約]{けいやく:contract:N1}データベース「Contract One」をはじめ、Sansanが[提供]{ていきょう:provide, offer:N1}する[複数]{ふくすう:multiple, several:N2}のプロダクトで[共通]{きょうつう:common, shared:N3}して[利用]{りよう:use, utilize:N3}できる[認証]{にんしょう:authentication:N1}[基盤]{きばん:platform, foundation:N1}「Auth One」の[企画]{きかく:planning:N1}から[設計]{せっけい:design:N2}、[開発]{かいはつ:development:N4}までを[一貫]{いっかん:consistently, end-to-end:N1}して[担う]{になう:to be responsible for:N2}ています。\n\n#en\nHiguchi: We are responsible end-to-end — from planning through design to development — for Auth One, the authentication platform used in common across multiple Sansan products including Bill One and the AI-powered contract database Contract One.\n::\n"]