diff --git a/README.md b/README.md index dc3cffd..0184808 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ After publication, verify the exact commit’s Actions task and deployed page bo ## Sections and diagrams -Top-level sections are Organization, Strategy, and Contribution, each with an independent sidebar. The first Organization page is Structure. It contains a dated public-evidence reconstruction, with named functions, job-advertised reporting lines, and explicitly marked planning assumptions. Citation URLs and checked excerpts are preserved in `research/organization/sources.json`; this is not an internally verified employee roster. +Top-level sections are Organization, Strategy, and Contribution, each with an independent sidebar. The first Organization page is Structure. It presents the organizational operating model: leadership, departments, teams, responsibilities and cross-functional delivery. Research and source excerpts remain under `research/organization/`, outside the published documentation. Archify 3.0.1 is vendored under `vendor/archify/` from commit `d5a1333d7447c866a765adac7d4d062f2f02e4d2`. MIT and third-party notices are preserved. `diagrams/` holds editable JSON; `pnpm diagrams:build` validates and generates local standalone viewers before every site build. The iframe is sandboxed without same-origin permission. See `docs/contribution/diagrams.md` for capability analysis, authoring, boundaries, and upgrade procedure. diff --git a/diagrams/organization-reporting.architecture.json b/diagrams/organization-reporting.architecture.json index 3977f0d..4bc9c8d 100644 --- a/diagrams/organization-reporting.architecture.json +++ b/diagrams/organization-reporting.architecture.json @@ -2,16 +2,16 @@ "schema_version": 1, "diagram_type": "architecture", "meta": { - "title": "Eldorado — advertised reporting lines", + "title": "Eldorado leadership and delivery structure", "output": "static/diagrams/organization-reporting/index.html", "quality_profile": "showcase", "legend": { "entries": { "backend": { - "label": "E: evidenced function" + "label": "Leadership / department" }, "frontend": { - "label": "J: advertised role" + "label": "Role / delivery team" } } } @@ -21,7 +21,7 @@ "id": "cto", "type": "frontend", "label": "CTO", - "sublabel": "J: named manager [8]", + "sublabel": "Technology direction", "pos": [ 40, 40 @@ -35,7 +35,7 @@ "id": "head-engineering", "type": "frontend", "label": "Head of Engineering", - "sublabel": "J: named manager [6]", + "sublabel": "Engineering leadership", "pos": [ 400, 40 @@ -49,7 +49,7 @@ "id": "group-em", "type": "frontend", "label": "Group Eng. Manager", - "sublabel": "J: manages 4–5 EMs [6]", + "sublabel": "Engineering group leadership", "pos": [ 760, 40 @@ -63,7 +63,7 @@ "id": "em", "type": "frontend", "label": "Engineering Manager", - "sublabel": "J: leads ~5 engineers [7]", + "sublabel": "Team leadership and delivery", "pos": [ 1120, 40 @@ -77,7 +77,7 @@ "id": "engineers", "type": "frontend", "label": "Software engineers", - "sublabel": "J: advertised team [7]", + "sublabel": "Product Engineering teams", "pos": [ 1480, 40 @@ -91,7 +91,7 @@ "id": "ai-architect", "type": "frontend", "label": "AI Architect", - "sublabel": "J: solo IC; new role [8]", + "sublabel": "AI enablement across engineering", "pos": [ 40, 280 @@ -105,7 +105,7 @@ "id": "coo", "type": "backend", "label": "COO", - "sublabel": "E: Lukas Deksnys [1]", + "sublabel": "Lukas Deksnys", "pos": [ 400, 280 @@ -119,7 +119,7 @@ "id": "ops-qa", "type": "frontend", "label": "QA Specialist (Ops)", - "sublabel": "J: new direct report [11]", + "sublabel": "Independent operational quality", "pos": [ 760, 280 @@ -133,7 +133,7 @@ "id": "cmo", "type": "frontend", "label": "CMO", - "sublabel": "J: named manager [12]", + "sublabel": "Marketing leadership", "pos": [ 1120, 280 @@ -147,7 +147,7 @@ "id": "brand-lead", "type": "frontend", "label": "Brand Team Lead", - "sublabel": "J: advertised role [12]", + "sublabel": "Brand and community", "pos": [ 1480, 280 @@ -163,67 +163,67 @@ "id": "cto-head-engineering", "from": "cto", "to": "head-engineering", - "label": "A: assumed", - "variant": "dashed" + "label": "Leads", + "variant": "default" }, { "id": "head-engineering-group-em", "from": "head-engineering", "to": "group-em", - "label": "J: reports [6]", + "label": "Leads", "variant": "default" }, { "id": "group-em-em", "from": "group-em", "to": "em", - "label": "J: reports [7]", + "label": "Leads", "variant": "default" }, { "id": "em-engineers", "from": "em", "to": "engineers", - "label": "J: leads [7]", + "label": "Leads", "variant": "default" }, { "id": "cto-ai-architect", "from": "cto", "to": "ai-architect", - "label": "J: direct [8]", + "label": "Leads", "variant": "default" }, { "id": "coo-ops-qa", "from": "coo", "to": "ops-qa", - "label": "J: direct [11]", + "label": "Leads", "variant": "default" }, { "id": "cmo-brand-lead", "from": "cmo", "to": "brand-lead", - "label": "J: direct [12]", + "label": "Leads", "variant": "default" } ], "cards": [ { "dot": "cyan", - "title": "Read manager → role/team", + "title": "Leadership and delivery", "items": [ - "J: explicitly advertised reporting/leadership, not a filled-role roster.", - "Solid lines cite job postings; upward lines not sourced are omitted." + "Arrows run from leader to role or team.", + "Functional leaders develop people, standards and delivery capability." ] }, { "dot": "amber", - "title": "Only one assumed connection", + "title": "Cross-functional execution", "items": [ - "CTO → Head of Engineering is assumed (dashed).", - "AI Architect starts solo; no established AI department is asserted." + "Product Owners, Designers and Tech Leads align on product outcomes.", + "AI Enablement works across engineering teams." ] } ] diff --git a/diagrams/organization-structure.architecture.json b/diagrams/organization-structure.architecture.json index 662f947..c585e21 100644 --- a/diagrams/organization-structure.architecture.json +++ b/diagrams/organization-structure.architecture.json @@ -2,16 +2,16 @@ "schema_version": 1, "diagram_type": "architecture", "meta": { - "title": "Eldorado — departments and team evidence", + "title": "Eldorado organization structure", "output": "static/diagrams/organization-structure/index.html", "quality_profile": "showcase", "legend": { "entries": { "backend": { - "label": "E: evidenced function" + "label": "Leadership / department" }, "frontend": { - "label": "J: advertised role" + "label": "Role / delivery team" } } } @@ -21,7 +21,7 @@ "id": "management", "type": "backend", "label": "Management", - "sublabel": "E: CEO / COO named [1]", + "sublabel": "CEO / COO", "pos": [ 660, 40 @@ -35,7 +35,7 @@ "id": "product", "type": "backend", "label": "Product", - "sublabel": "E: careers category [4]", + "sublabel": "Experience and product outcomes", "pos": [ 40, 280 @@ -49,7 +49,7 @@ "id": "technology", "type": "backend", "label": "Technology", - "sublabel": "E: careers category [4]", + "sublabel": "Engineering and platform", "pos": [ 320, 280 @@ -63,7 +63,7 @@ "id": "operations", "type": "backend", "label": "Operations", - "sublabel": "E: careers category [4]", + "sublabel": "Service, resolution and trust", "pos": [ 600, 280 @@ -77,7 +77,7 @@ "id": "marketing", "type": "backend", "label": "Marketing", - "sublabel": "E: careers category [4]", + "sublabel": "Brand and customer growth", "pos": [ 880, 280 @@ -91,7 +91,7 @@ "id": "finance", "type": "backend", "label": "Finance & Accounting", - "sublabel": "E: careers category [4]", + "sublabel": "Financial performance and controls", "pos": [ 1160, 280 @@ -105,7 +105,7 @@ "id": "people", "type": "backend", "label": "HR & Administration", - "sublabel": "E: careers category [4]", + "sublabel": "People and workplace", "pos": [ 1440, 280 @@ -121,113 +121,98 @@ "id": "management-product", "from": "management", "to": "product", - "label": "A: placement", - "variant": "dashed" + "label": "Coordinates", + "variant": "default" }, { "id": "management-technology", "from": "management", "to": "technology", - "label": "A: placement", - "variant": "dashed" + "label": "Coordinates", + "variant": "default" }, { "id": "management-operations", "from": "management", "to": "operations", - "label": "A: placement", - "variant": "dashed" + "label": "Coordinates", + "variant": "default" }, { "id": "management-marketing", "from": "management", "to": "marketing", - "label": "A: placement", - "variant": "dashed" + "label": "Coordinates", + "variant": "default" }, { "id": "management-finance", "from": "management", "to": "finance", - "label": "A: placement", - "variant": "dashed" + "label": "Coordinates", + "variant": "default" }, { "id": "management-people", "from": "management", "to": "people", - "label": "A: placement", - "variant": "dashed" + "label": "Coordinates", + "variant": "default" } ], "cards": [ - { - "dot": "amber", - "title": "Not a verified employee roster — 2026-10-02", - "items": [ - "E = evidenced team/function; J = job-advertised; A = assumed.", - "All dashed department placements are planning assumptions.", - "Source numbers refer to the Structure page; vacancies do not prove occupancy." - ] - }, { "dot": "cyan", "title": "Product", "items": [ - "E: Order/Orders; Categories design [13,14]", - "E: Data Team / J: ranking role [9]", - "J: seller-platform domain [15]", - "A: Sellers & Operations squad" + "Orders; Categories", + "Sellers & Operations", + "Data & Intelligence; Product Design" ] }, { "dot": "amber", "title": "Technology", "items": [ - "J: engineering management chain [6,7]", - "J: AI Architect — solo start [8]", - "J: IT Engineer; Technical Architect [8,10]", - "A: platform/reliability capability group" + "Product Engineering; Quality Engineering", + "Platform & Reliability; Architecture & Security", + "AI Enablement; Internal IT" ] }, { "dot": "cyan", "title": "Operations", "items": [ - "E: Customer Support [11]", - "E: Trust & Resolution; Risk & Fraud [11]", - "J: operational QA directly to COO [11]", - "A: wider COO ownership/lead escalation" + "Customer Support; Trust & Resolution", + "Risk & Fraud", + "Operational Quality" ] }, { "dot": "amber", "title": "Marketing", "items": [ - "J: Brand Lead directly to CMO [12]", - "E: Creative; SEO; PPC & Affiliate [12]", - "E: Influencer; CRM; community [12]", - "A: separate workstream boundaries" + "Brand & Community; Creative; SEO", + "PPC & Affiliate; Influencer", + "CRM" ] }, { "dot": "cyan", "title": "Finance & Accounting", "items": [ - "E: Finance team [5]", - "J: CFO hiring mandate [5]", - "A: FP&A; Accounting/Tax/Controls", - "A: Treasury / Payment Operations" + "Financial Planning & Analysis", + "Accounting, Tax & Controls", + "Treasury & Payment Operations" ] }, { "dot": "amber", "title": "HR & Administration", "items": [ - "E: Talent Acquisition [16]", - "A: People Operations", - "A: Office / Administration", - "A: HR leadership reporting line" + "Talent Acquisition", + "People Operations", + "Office & Administration" ] } ] diff --git a/docs/contribution/diagrams.md b/docs/contribution/diagrams.md index 20159fb..d59924e 100644 --- a/docs/contribution/diagrams.md +++ b/docs/contribution/diagrams.md @@ -9,7 +9,7 @@ description: Author typed JSON diagrams and embed their local interactive viewer | Diagram type | Intended use | | --- | --- | -| Architecture | Components, boundaries and relationships; also used for the evidence-labeled organization views | +| Architecture | Components, boundaries and relationships; also used for the organization structure views | | Workflow | Processes, branches and approval gates | | Sequence | Participants and ordered messages | | Dataflow | Sources, processing and destinations | @@ -34,7 +34,7 @@ pnpm build ```mdx import ArchifyDiagram from '@site/src/components/ArchifyDiagram'; - + ``` Supply a text alternative below each diagram. The wrapper uses a local, base-path-aware iframe with a descriptive title, scripts and downloads enabled, and no same-origin or parent-navigation permissions. The Open full viewer button expands the diagram in a full-screen modal on the current page, with the same iframe sandbox. Close it with the Close button or Escape; focus returns to the opener. It does not open a new tab. The separate standalone HTML asset remains directly addressable and is not itself iframe-sandboxed, so publish only reviewed, trusted diagrams. Generated output is ignored by Git and rebuilt in CI. diff --git a/docs/organization/structure.mdx b/docs/organization/structure.mdx index dac41ca..aa5f93c 100644 --- a/docs/organization/structure.mdx +++ b/docs/organization/structure.mdx @@ -1,101 +1,131 @@ --- title: Structure -description: Distinguish Eldorado’s publicly evidenced organization from advertised roles and planning assumptions. +description: Eldorado’s organizational operating model, departments, teams and responsibilities. --- import ArchifyDiagram from '@site/src/components/ArchifyDiagram'; -**Research snapshot: 2026-10-02.** This is a public-evidence reconstruction for AI strategy planning, **not a verified employee roster** or an internally approved organization chart. +This operating model organizes Eldorado around six departments: **Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration**. Leadership aligns their priorities around marketplace growth, customer trust and efficient delivery. -## What is known +## Leadership -Eldorado names **Vladas Jurkevičius — co-founder and CEO** and **Lukas Deksnys — co-founder and COO** on its official About page.[1] +| Role | Leadership | Responsibility | +| --- | --- | --- | +| Chief Executive Officer | Vladas Jurkevičius | Company direction, business performance, strategic priorities and executive alignment. | +| Chief Operating Officer | Lukas Deksnys | Marketplace operations, customer service, resolution quality and operational performance. | -Its official careers site uses seven hiring categories: **Management, Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration**. Those labels are directly evidenced; treating them as six peer departments beneath Management is a planning arrangement, not a published reporting hierarchy.[4] +Functional leaders translate company priorities into departmental plans. Team leads own execution, people development and service quality within their teams. -### Evidence legend +## Organization overview -- **E — Publicly evidenced:** a named leader, team, function or careers category explicitly appears in an official source. This does not establish every reporting relationship. -- **J — Job-advertised:** a vacancy describes a role, mandate or reporting line. The position may be unfilled or newly created. -- **A — Assumed:** a proposed grouping or missing team boundary used for planning, not a claim about Eldorado’s current structure. Dashed connectors identify assumed placements. + -## Department overview - - - -**Text alternative:** Management is shown above Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration. All six placements beneath Management are assumed. The department names come from the careers taxonomy; the notes in the viewer identify evidenced teams and proposed subdivisions. This view does not assign every function directly to the CEO or COO. +**Management coordinates the six departments.** Each department has a clear business responsibility and a set of teams that deliver it. ## Departments and teams -The following separates **named teams** from **roles, capabilities and domains**. A function mentioned in a vacancy is not automatically a separately staffed team. +### Product -| Department / function | Publicly evidenced teams, roles or domains | Assumed completion for planning | -| --- | --- | --- | -| **Management** | **E:** CEO Vladas Jurkevičius and COO Lukas Deksnys. **J:** CTO and CMO are referenced as reporting managers.[1][8][12] CFO is advertised.[5] No incumbent names are inferred for those three roles. | **A:** a leadership coordination layer across the six functions. Exact executive reporting lines, Board membership and decision rights remain unverified. | -| **Product** | **E:** Order/Orders team; Categories design team, with Boosting & Currency scope; Data Team appears in the ranking Data Scientist vacancy metadata. Data classification and product design evidence.[9][13][14] **J:** Sellers and Operations product-owner domain, including Seller Portal, integrations, onboarding, balances/withdrawals, invoicing and support tooling.[15] | **A:** treat Sellers & Operations as a cross-functional product squad for planning, not a proven standalone team. Do not duplicate Data as a separate peer department. | -| **Technology** | **J:** Head of Engineering → Group Engineering Managers → Engineering Managers → engineers. AI Architect reports to CTO and starts solo. Technical Architect is named as an infrastructure/security partner; IT Engineer is advertised for identity, device management and internal SaaS.[6][8][10] | **A:** CTO → Head of Engineering. Proposed shared platform/reliability and security capability groups, with staffing and reporting unverified. Do not turn AI Architect into an established AI department. | -| **Operations** | **E:** Customer Support, Trust & Resolution, Risk & Fraud. **J:** QA Specialist (Operations) reports directly to COO; separate support/resolution Team Lead mandates cover specialist teams.[11][17][18] | **A:** COO ownership of the wider Operations function and its team-lead escalation chain. Only the QA Specialist’s direct COO line is explicit in the reviewed sources. | -| **Marketing** | **J:** Brand Team Lead reports to CMO. **E:** the wider Marketing team names Creative, SEO, PPC & Affiliate, Influencer, and CRM; brand scope includes organic social, community and brand partnerships.[12] | **A:** model these named disciplines as planning workstreams under Marketing. Separate team managers, headcounts and each discipline’s direct CMO line are not established. | -| **Finance & Accounting** | **E:** Finance team / hiring category. **J:** CFO remit includes planning, reporting, cash/capital, tax, compliance, financial risk and payments; it describes partnership with CEO and Board, not an explicit reporting line.[5] | **A:** FP&A; Accounting/Tax/Controls; Treasury/Payment Operations as three capability groups. These are inferred subdivisions, not proven staffed teams. Financial risk is not the same thing as the Operations Risk & Fraud team. | -| **HR & Administration** | **E:** Talent Acquisition team / role category. **J:** full-cycle IT and non-IT recruitment, partnering with hiring managers.[16] | **A:** People Operations and Office/Administration alongside Talent Acquisition. Separate teams and the HR leader’s reporting line remain unverified. | +**Purpose:** improve the buyer and seller experience and turn marketplace opportunities into valuable product capabilities. -The Sellers and Operations posting establishes a **product domain**, not a named Sellers department. Its mandate crosses seller-facing features, operational tooling and marketplace infrastructure.[15] +| Team | Responsibilities | +| --- | --- | +| Orders | Purchase and post-purchase journeys, order status, delivery experience, dispute flows, feedback and loyalty. | +| Categories | Category experiences, including Boosting and Currency, discovery, conversion and category-specific user journeys. | +| Sellers & Operations | Seller Portal, seller integrations, onboarding and verification, balances and withdrawals, invoicing and operational tooling. | +| Data & Intelligence | Product analytics, experimentation, offer ranking, recommendations and decision support. | +| Product Design | User research, interaction design, design consistency and accessible buyer and seller experiences across product teams. | -## Reporting lines supported by vacancies +Product Owners, Designers and Tech Leads work together on each product area. Product owns priorities and outcomes; Technology owns engineering execution and technical quality. - +### Technology -**Read arrows as manager → role/team.** Solid **J** connectors are explicitly described in vacancies. The dashed **A** link between CTO and Head of Engineering is the only inferred link in this diagram. Separate rows are not connected because their upward reporting lines were not established. +**Purpose:** build and operate a secure, reliable marketplace and improve the effectiveness of engineering. -| Manager / leader | Role or team below it | Status and scope | -| --- | --- | --- | -| Head of Engineering | Group Engineering Manager | **J:** explicitly reports directly to Head of Engineering; the vacancy describes managing 4–5 Engineering Managers.[6] | -| Group Engineering Manager | Engineering Manager | **J:** explicitly named manager in the Engineering Manager vacancy.[7] | -| Engineering Manager | Software engineers | **J:** leads a team of around five engineers. This is the advertised span, not a count of all current engineering teams.[7] | -| CTO | AI Architect | **J:** explicitly direct; a new individual-contributor role, starting solo with a possible future team.[8] | -| COO | QA Specialist (Operations) | **J:** explicitly direct; independent quality work across Customer Support, Trust & Resolution, and Risk & Fraud.[11] | -| CMO | Brand Team Lead | **J:** explicitly direct; brand, organic social, community and brand partnerships remit.[12] | -| Customer Support / Trust & Resolution Team Leads | Their specialists | **J:** support/resolution leadership advert describes teams of 5–10 specialists; the resolution-specific advert also states 5–10. Their own upward manager is not stated.[17][18] | -| CTO | Head of Engineering | **A:** plausible technology reporting arrangement, retained only as a planning assumption. | +| Team / function | Responsibilities | +| --- | --- | +| Product Engineering | Develop and maintain marketplace capabilities in cross-functional product teams. | +| Platform & Reliability | Shared platform services, delivery infrastructure, observability, availability and performance. | +| Architecture & Security | Technical standards, system design, infrastructure security and secure engineering practices. | +| Quality Engineering | Test strategy, automation, release quality and defect prevention. | +| AI Enablement | AI-assisted engineering workflows, developer tools, adoption, standards and safe use of AI. | +| Internal IT | Identity and access, employee devices, internal systems, software administration and joiner–mover–leaver processes. | -Product Owner, Tech Lead and Product Designer are described as collaborating on product direction. That is evidence of cross-functional work, **not** evidence that one line-manages the others.[13][14] +The CTO owns technology direction. The Head of Engineering leads engineering delivery through Group Engineering Managers and Engineering Managers. The AI Architect coordinates AI enablement across engineering, working with Architecture & Security and team leaders. -## What this means for AI strategy +### Operations -**Research interpretation, not an approved roadmap:** use the evidenced organizational owners rather than inventing one central AI department. +**Purpose:** keep marketplace trading dependable and resolve customer issues fairly and efficiently. -- **Engineering enablement:** the AI Architect vacancy focuses on engineering output, adoption, standards and security under the CTO—not ownership of every business AI initiative.[8] -- **Marketplace intelligence:** Product/Data has an advertised ranking and recommendations remit, including experimentation and learning-to-rank.[9] -- **Operations quality:** operational QA explicitly includes auditing AI-handled support and LLM-assisted scoring; customer support leadership includes AI-assisted support and automation.[11][17] -- **Planning assumption:** coordinate these three areas with Product, Operations, Technology and Finance owners. Whether to create a cross-company AI steering group is a future decision, not a finding about current organization. +| Team | Responsibilities | +| --- | --- | +| Customer Support | Buyer and seller assistance, knowledge management, self-service and support workflow automation. | +| Trust & Resolution | Disputes, appeals, refunds, warranties, chargebacks and complex customer cases. | +| Risk & Fraud | Transaction and account risk, fraud prevention, investigations and operational controls. | +| Operational Quality | Independent case reviews, quality standards, calibration, service accuracy and improvement tracking across operational teams. | -## Limits and validation questions +The COO coordinates Operations. Team leads manage specialists and daily service delivery. Operational Quality reports directly to the COO and reviews quality across teams. -- **No complete internal chart was found in the reviewed public sources.** This is not a claim that none exists. Research prioritized official About, careers, vacancy and legal pages; it is not an exhaustive employee or vacancy census. -- **Job postings are time-bound recruitment evidence.** A vacancy can describe a future role or team. Names, staffing, budgets and every executive reporting line still need company confirmation. -- **No reliable total headcount is asserted.** The careers homepage itself contains both “150+” and “200+” descriptions; do not use either to derive department sizes.[2] -- **Legal entities are not departments.** The Terms of Service names GWD Processing FZCO, Eldorado Sales LLC and Halfway House OÜ collectively as Eldorado. This establishes contracting language, not a parent/subsidiary hierarchy or the employing entity of each team.[3] -- **Keep scope distinctions:** marketplace Risk & Fraud, financial risk, AI security, and corporate compliance may collaborate but should not be collapsed into one assumed reporting chain. +### Marketing -Before using this as an operating model, confirm: **(1)** which advertised roles are filled, **(2)** executive and functional reporting lines, **(3)** product squad membership and engineering matrix, **(4)** ownership of Payments, Legal/Compliance and Data, and **(5)** the real team roster and capacity. Replace each **A** only when evidence is supplied. +**Purpose:** attract and retain customers, build the Eldorado brand and grow marketplace demand. -## Sources +| Team / workstream | Responsibilities | +| --- | --- | +| Brand & Community | Brand positioning, campaigns, organic social, community and brand partnerships. | +| Creative | Campaign concepts, visual assets and performance creative. | +| SEO | Organic discovery, search visibility and content performance. | +| PPC & Affiliate | Paid acquisition, affiliate channels and return on marketing investment. | +| Influencer | Creator relationships, influencer programs and campaign delivery. | +| CRM | Customer lifecycle communication, retention, reactivation and campaign personalization. | -[1] https://www.eldorado.gg/about-us — Eldorado About us -[2] https://careers.eldorado.gg — Eldorado Careers homepage -[3] https://www.eldorado.gg/terms-of-service — Eldorado Terms of Service -[4] https://careers.eldorado.gg/jobs — Eldorado Jobs — official hiring categories -[5] https://careers.eldorado.gg/jobs/8394692-chief-financial-officer — Chief Financial Officer -[6] https://careers.eldorado.gg/jobs/8376024-group-engineering-manager — Group Engineering Manager -[7] https://careers.eldorado.gg/jobs/8290012-engineering-manager — Engineering Manager -[8] https://careers.eldorado.gg/jobs/8175478-ai-architect — AI Architect -[9] https://careers.eldorado.gg/jobs/8261309-data-scientist-offer-ranking-recommendations — Data Scientist (Offer Ranking & Recommendations) -[10] https://careers.eldorado.gg/jobs/8363463-it-engineer — IT Engineer -[11] https://careers.eldorado.gg/jobs/8358613-qa-specialist-operations — QA Specialist (Operations) -[12] https://careers.eldorado.gg/jobs/8450323-brand-team-lead — Brand Team Lead -[13] https://careers.eldorado.gg/jobs/8404928-product-designer-orders-team — Product Designer (Orders team) -[14] https://careers.eldorado.gg/jobs/8253165-product-designer — Product Designer -[15] https://careers.eldorado.gg/jobs/8389376-product-owner-sellers-and-operations — Product Owner (Sellers and Operations) -[16] https://careers.eldorado.gg/jobs/8487069-talent-acquisition-partner-junior-mid — Talent Acquisition Partner (Junior - Mid) -[17] https://careers.eldorado.gg/jobs/8381712-customer-support-team-lead — Customer Support Team Lead -[18] https://careers.eldorado.gg/jobs/8483510-trust-resolution-team-lead — Trust & Resolution Team Lead +The CMO coordinates Marketing. The Brand Team Lead owns Brand & Community, with shared support from Creative and the other marketing workstreams. + +### Finance & Accounting + +**Purpose:** maintain financial control, support business decisions and keep marketplace money flows dependable. + +| Team / function | Responsibilities | +| --- | --- | +| Financial Planning & Analysis | Budgets, forecasts, profitability, management reporting and investment analysis. | +| Accounting, Tax & Controls | Accounting, financial reporting, tax, audit coordination and internal controls. | +| Treasury & Payment Operations | Cash management, reconciliation, payout oversight, payment-provider coordination and financial risk. | + +The CFO coordinates Finance & Accounting and works with executive leadership on business performance. Finance, Operations and Product share responsibility for effective payment and withdrawal processes, each within its own area of expertise. + +### HR & Administration + +**Purpose:** help teams attract, develop and retain people and provide an effective working environment. + +| Team | Responsibilities | +| --- | --- | +| Talent Acquisition | Recruitment, candidate experience, hiring coordination and workforce demand support. | +| People Operations | Employee onboarding, development, performance processes, policies and employee experience. | +| Office & Administration | Workplace services, office operations and administrative coordination. | + +HR partners with department leaders on team capacity and development. People Operations works with Internal IT on employee onboarding, role changes and offboarding. + +## Leadership and delivery structure + + + +The diagram shows management responsibility from leader to role or team: + +- **CTO → Head of Engineering → Group Engineering Managers → Engineering Managers → Product Engineering teams.** +- **CTO → AI Architect**, coordinating engineering AI enablement. +- **COO → Operational Quality**, providing independent quality oversight. +- **CMO → Brand Team Lead**, leading Brand & Community. + +Product teams combine product ownership, design, engineering, quality and data expertise. Functional management develops people and professional standards; cross-functional teams deliver business outcomes. + +## How the departments work together + +| Business outcome | Collaboration | +| --- | --- | +| Better buyer experience | Product defines improvements; Technology delivers them; Operations brings customer feedback; Data measures the result. | +| Stronger seller experience | Product and Technology develop seller tools; Operations supports sellers; Finance manages financial processes. | +| Safe and trustworthy trading | Risk & Fraud, Trust & Resolution, Architecture & Security, and Finance coordinate controls and incident responses. | +| Sustainable growth | Marketing develops demand; Product improves conversion and retention; Finance measures profitability. | +| AI-powered execution | AI Enablement supports engineering; Data & Intelligence develops marketplace intelligence; Operations improves service and quality workflows. | + +Department leaders remain accountable for outcomes, controls and service quality as AI becomes part of everyday work. diff --git a/research/organization/README.md b/research/organization/README.md index fad8bee..6f07f2c 100644 --- a/research/organization/README.md +++ b/research/organization/README.md @@ -1,9 +1,7 @@ -# Organization research — 2026-10-02 +# Organization background research -Public-evidence reconstruction, not an approved internal org chart. The canonical reader-facing report is `docs/organization/structure.mdx`. `sources.json` preserves retrieved URLs, access dates and verbatim excerpts checked against fetched page text with the grounded-citations evidence matcher. No private employee data or application forms were accessed. +The source/excerpt ledger and `reconstruction-snapshot.mdx` preserve the original public-evidence investigation. They are background working material, outside the published docs and static assets. -E = publicly evidenced names/categories/functions; J = job-advertised roles and reporting lines, not proof of occupancy; A = planning assumptions. The diagrams carry the same distinction. Department placement beneath Management is a model, not a proven reporting chain. Legal entities and hiring categories must not be conflated with departments. +The reader-facing `docs/organization/structure.mdx` is an organizational operating model, not a research report or an employee roster. Per the user's presentation direction, it describes leadership, departments, teams and responsibilities directly without evidence markers, vacancies or citations. Internet research informs the model; this editorial change does not independently verify staffing, incumbent names or every reporting relationship. -Coverage: official About, careers index and selected job detail pages plus legal Terms. The jobs index was not treated as an exhaustive personnel roster. Search-engine discovery was unhelpful (Google traffic challenge; Bing irrelevant results); all factual findings rely on directly fetched official sources. Exact headcount and unnamed incumbents are deliberately omitted. Current-role dates are access dates, not proof of appointment dates. - -Update source excerpts and access dates, revise the report and both diagrams together, then run `pnpm verify`, `pnpm typecheck`, `pnpm build`, `pnpm verify:build` and browser checks before publication. Revalidate recruitment evidence rather than treating an old vacancy as a permanent org fact. +The original snapshot records which categories and relationships were evidenced, job-advertised or inferred. Retain that provenance for future maintenance, without importing it into the published page, diagram metadata or search index. diff --git a/research/organization/reconstruction-snapshot.mdx b/research/organization/reconstruction-snapshot.mdx new file mode 100644 index 0000000..c1eb1df --- /dev/null +++ b/research/organization/reconstruction-snapshot.mdx @@ -0,0 +1,102 @@ +--- +title: Structure +description: Distinguish Eldorado’s publicly evidenced organization from advertised roles and planning assumptions. +--- + +import ArchifyDiagram from '@site/src/components/ArchifyDiagram'; + +**Research snapshot: 2026-10-02.** This is a public-evidence reconstruction for AI strategy planning, **not a verified employee roster** or an internally approved organization chart. + +## What is known + +Eldorado names **Vladas Jurkevičius — co-founder and CEO** and **Lukas Deksnys — co-founder and COO** on its official About page.[1] + +Its official careers site uses seven hiring categories: **Management, Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration**. Those labels are directly evidenced; treating them as six peer departments beneath Management is a planning arrangement, not a published reporting hierarchy.[4] + +### Evidence legend + +- **E — Publicly evidenced:** a named leader, team, function or careers category explicitly appears in an official source. This does not establish every reporting relationship. +- **J — Job-advertised:** a vacancy describes a role, mandate or reporting line. The position may be unfilled or newly created. +- **A — Assumed:** a proposed grouping or missing team boundary used for planning, not a claim about Eldorado’s current structure. Dashed connectors identify assumed placements. + +## Department overview + + + +**Text alternative:** Management is shown above Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration. All six placements beneath Management are assumed. The department names come from the careers taxonomy; the notes in the viewer identify evidenced teams and proposed subdivisions. This view does not assign every function directly to the CEO or COO. + +## Departments and teams + +The following separates **named teams** from **roles, capabilities and domains**. A function mentioned in a vacancy is not automatically a separately staffed team. + +| Department / function | Publicly evidenced teams, roles or domains | Assumed completion for planning | +| --- | --- | --- | +| **Management** | **E:** CEO Vladas Jurkevičius and COO Lukas Deksnys. **J:** CTO and CMO are referenced as reporting managers.[1][8][12] CFO is advertised.[5] No incumbent names are inferred for those three roles. | **A:** a leadership coordination layer across the six functions. Exact executive reporting lines, Board membership and decision rights remain unverified. | +| **Product** | **E:** Order/Orders team; Categories design team, with Boosting & Currency scope; Data Team appears in the ranking Data Scientist vacancy metadata. Data classification and product design evidence.[9][13][14] **J:** Sellers and Operations product-owner domain, including Seller Portal, integrations, onboarding, balances/withdrawals, invoicing and support tooling.[15] | **A:** treat Sellers & Operations as a cross-functional product squad for planning, not a proven standalone team. Do not duplicate Data as a separate peer department. | +| **Technology** | **J:** Head of Engineering → Group Engineering Managers → Engineering Managers → engineers. AI Architect reports to CTO and starts solo. Technical Architect is named as an infrastructure/security partner; IT Engineer is advertised for identity, device management and internal SaaS.[6][8][10] | **A:** CTO → Head of Engineering. Proposed shared platform/reliability and security capability groups, with staffing and reporting unverified. Do not turn AI Architect into an established AI department. | +| **Operations** | **E:** Customer Support, Trust & Resolution, Risk & Fraud. **J:** QA Specialist (Operations) reports directly to COO; separate support/resolution Team Lead mandates cover specialist teams.[11][17][18] | **A:** COO ownership of the wider Operations function and its team-lead escalation chain. Only the QA Specialist’s direct COO line is explicit in the reviewed sources. | +| **Marketing** | **J:** Brand Team Lead reports to CMO. **E:** the wider Marketing team names Creative, SEO, PPC & Affiliate, Influencer, and CRM; brand scope includes organic social, community and brand partnerships.[12] | **A:** model these named disciplines as planning workstreams under Marketing. Separate team managers, headcounts and each discipline’s direct CMO line are not established. | +| **Finance & Accounting** | **E:** Finance team / hiring category. **J:** CFO remit includes planning, reporting, cash/capital, tax, compliance, financial risk and payments; it describes partnership with CEO and Board, not an explicit reporting line.[5] | **A:** FP&A; Accounting/Tax/Controls; Treasury/Payment Operations as three capability groups. These are inferred subdivisions, not proven staffed teams. Financial risk is not the same thing as the Operations Risk & Fraud team. | +| **HR & Administration** | **E:** Talent Acquisition team / role category. **J:** full-cycle IT and non-IT recruitment, partnering with hiring managers.[16] | **A:** People Operations and Office/Administration alongside Talent Acquisition. Separate teams and the HR leader’s reporting line remain unverified. | + +The Sellers and Operations posting establishes a **product domain**, not a named Sellers department. Its mandate crosses seller-facing features, operational tooling and marketplace infrastructure.[15] + +## Reporting lines supported by vacancies + + + +**Read arrows as manager → role/team.** Solid **J** connectors are explicitly described in vacancies. The dashed **A** link between CTO and Head of Engineering is the only inferred link in this diagram. Separate rows are not connected because their upward reporting lines were not established. + +| Manager / leader | Role or team below it | Status and scope | +| --- | --- | --- | +| Head of Engineering | Group Engineering Manager | **J:** explicitly reports directly to Head of Engineering; the vacancy describes managing 4–5 Engineering Managers.[6] | +| Group Engineering Manager | Engineering Manager | **J:** explicitly named manager in the Engineering Manager vacancy.[7] | +| Engineering Manager | Software engineers | **J:** leads a team of around five engineers. This is the advertised span, not a count of all current engineering teams.[7] | +| CTO | AI Architect | **J:** explicitly direct; a new individual-contributor role, starting solo with a possible future team.[8] | +| COO | QA Specialist (Operations) | **J:** explicitly direct; independent quality work across Customer Support, Trust & Resolution, and Risk & Fraud.[11] | +| CMO | Brand Team Lead | **J:** explicitly direct; brand, organic social, community and brand partnerships remit.[12] | +| Customer Support / Trust & Resolution Team Leads | Their specialists | **J:** support/resolution leadership advert describes teams of 5–10 specialists; the resolution-specific advert also states 5–10. Their own upward manager is not stated.[17][18] | +| CTO | Head of Engineering | **A:** plausible technology reporting arrangement, retained only as a planning assumption. | + +Product Owner, Tech Lead and Product Designer are described as collaborating on product direction. That is evidence of cross-functional work, **not** evidence that one line-manages the others.[13][14] + +## What this means for AI strategy + +**Research interpretation, not an approved roadmap:** use the evidenced organizational owners rather than inventing one central AI department. + +- **Engineering enablement:** the AI Architect vacancy focuses on engineering output, adoption, standards and security under the CTO—not ownership of every business AI initiative.[8] +- **Marketplace intelligence:** Product/Data has an advertised ranking and recommendations remit, including experimentation and learning-to-rank.[9] +- **Operations quality:** operational QA explicitly includes auditing AI-handled support and LLM-assisted scoring; customer support leadership includes AI-assisted support and automation.[11][17] +- **Planning assumption:** coordinate these three areas with Product, Operations, Technology and Finance owners. Whether to create a cross-company AI steering group is a future decision, not a finding about current organization. + +## Limits and validation questions + +- **No complete internal chart was found in the reviewed public sources.** This is not a claim that none exists. Research prioritized official About, careers, vacancy and legal pages; it is not an exhaustive employee or vacancy census. +- **Job postings are time-bound recruitment evidence.** A vacancy can describe a future role or team. Names, staffing, budgets and every executive reporting line still need company confirmation. +- **No reliable total headcount is asserted.** The careers homepage itself contains both “150+” and “200+” descriptions; do not use either to derive department sizes.[2] +- **Legal entities are not departments.** The Terms of Service names GWD Processing FZCO, Eldorado Sales LLC and Halfway House OÜ collectively as Eldorado. This establishes contracting language, not a parent/subsidiary hierarchy or the employing entity of each team.[3] +- **Keep scope distinctions:** marketplace Risk & Fraud, financial risk, AI security, and corporate compliance may collaborate but should not be collapsed into one assumed reporting chain. + +Before using this as an operating model, confirm: **(1)** which advertised roles are filled, **(2)** executive and functional reporting lines, **(3)** product squad membership and engineering matrix, **(4)** ownership of Payments, Legal/Compliance and Data, and **(5)** the real team roster and capacity. Replace each **A** only when evidence is supplied. + +## Sources + +[1] https://www.eldorado.gg/about-us — Eldorado About us +[2] https://careers.eldorado.gg — Eldorado Careers homepage +[3] https://www.eldorado.gg/terms-of-service — Eldorado Terms of Service +[4] https://careers.eldorado.gg/jobs — Eldorado Jobs — official hiring categories +[5] https://careers.eldorado.gg/jobs/8394692-chief-financial-officer — Chief Financial Officer +[6] https://careers.eldorado.gg/jobs/8376024-group-engineering-manager — Group Engineering Manager +[7] https://careers.eldorado.gg/jobs/8290012-engineering-manager — Engineering Manager +[8] https://careers.eldorado.gg/jobs/8175478-ai-architect — AI Architect +[9] https://careers.eldorado.gg/jobs/8261309-data-scientist-offer-ranking-recommendations — Data Scientist (Offer Ranking & Recommendations) +[10] https://careers.eldorado.gg/jobs/8363463-it-engineer — IT Engineer +[11] https://careers.eldorado.gg/jobs/8358613-qa-specialist-operations — QA Specialist (Operations) +[12] https://careers.eldorado.gg/jobs/8450323-brand-team-lead — Brand Team Lead +[13] https://careers.eldorado.gg/jobs/8404928-product-designer-orders-team — Product Designer (Orders team) +[14] https://careers.eldorado.gg/jobs/8253165-product-designer — Product Designer +[15] https://careers.eldorado.gg/jobs/8389376-product-owner-sellers-and-operations — Product Owner (Sellers and Operations) +[16] https://careers.eldorado.gg/jobs/8487069-talent-acquisition-partner-junior-mid — Talent Acquisition Partner (Junior - Mid) +[17] https://careers.eldorado.gg/jobs/8381712-customer-support-team-lead — Customer Support Team Lead +[18] https://careers.eldorado.gg/jobs/8483510-trust-resolution-team-lead — Trust & Resolution Team Lead + diff --git a/scripts/portal.test.mjs b/scripts/portal.test.mjs index 2f75c55..2e0c87c 100644 --- a/scripts/portal.test.mjs +++ b/scripts/portal.test.mjs @@ -59,24 +59,19 @@ test('Archify is pinned, licensed and rebuilt, not a remote embed', () => { assert(!wrapper.includes('target="_blank"')); assert(wrapper.includes('Close full-screen diagram')); }); -test('organization research distinguishes evidence, advertised roles and assumptions', () => { +test('organization page presents an operating model, not research notes', () => { const page = read('docs/organization/structure.mdx'); - assert(page.includes('2026-10-02') && page.includes('not a verified employee roster')); + assert(page.includes('operating model') && page.includes('## Departments and teams')); + const prohibited = /assum|job.advert|vacanc|publicly evidenced|research snapshot|## Sources|\[\d+\]|\b[EJA]:\s/i; + assert(!prohibited.test(page)); assert(page.includes('Vladas Jurkevičius') && page.includes('Lukas Deksnys')); - assert(page.includes('Assumed') && page.includes('Publicly evidenced')); - assert(!page.includes('Illustrative integration example')); - const ledger = JSON.parse(read('research/organization/sources.json')); - const citations = [...page.split('## Sources')[0].matchAll(/\[(\d+)\]/g)].map(m => Number(m[1])); - assert(citations.length > 10); - for (const id of citations) assert(ledger.sources.some(s => s.id === id && s.quotes?.length), `Missing evidence ${id}`); + assert(existsSync('research/organization/reconstruction-snapshot.mdx')); + assert(JSON.parse(read('research/organization/sources.json')).sources.every(s => s.quotes?.length)); for (const name of ['organization-structure', 'organization-reporting']) { const spec = JSON.parse(read(`diagrams/${name}.architecture.json`)); + assert(!prohibited.test(JSON.stringify(spec))); const ids = new Set(spec.components.map(n => n.id)); assert.equal(ids.size, spec.components.length); - for (const edge of spec.connections) { - assert(ids.has(edge.from) && ids.has(edge.to)); - assert(edge.label.startsWith('J:') || edge.label.startsWith('A:')); - if (edge.label.startsWith('A:')) assert.equal(edge.variant, 'dashed'); - } + for (const edge of spec.connections) assert(ids.has(edge.from) && ids.has(edge.to)); } }); diff --git a/scripts/verify.mjs b/scripts/verify.mjs index 42014f0..5b81a57 100644 --- a/scripts/verify.mjs +++ b/scripts/verify.mjs @@ -21,12 +21,15 @@ if (process.argv.includes('--build')) { } assert(!readdirSync('build/diagrams', {recursive: true}).some(f => f.endsWith('.delivery.json')), 'Private build receipts must not be published'); const diagram = read('build/diagrams/organization-structure/index.html'); - assert(diagram.includes('A: placement') && diagram.includes('node-technology')); + assert(diagram.includes('Coordinates') && diagram.includes('node-technology')); + assert(!/A: placement|E: careers|J: advertised/.test(diagram)); assert(!diagram.includes('Example leadership')); const reporting = read('build/diagrams/organization-reporting/index.html'); - assert(reporting.includes('AI Architect') && reporting.includes('A: assumed')); + assert(reporting.includes('AI Architect') && reporting.includes('Leads')); + assert(!/A: assumed|J: direct/.test(reporting)); const structure = read('build/organization/structure/index.html'); - assert(structure.includes('Vladas Jurkevičius') && structure.includes('not a verified employee roster')); + assert(structure.includes('Vladas Jurkevičius') && structure.includes('operating model')); + assert(!/Research snapshot|Job-advertised|careers\.eldorado\.gg|Assumed/.test(structure)); assert(!structure.includes('Illustrative integration example')); assert(!diagram.includes('/opt/data/'), 'No build paths in published diagrams'); const home = read('build/index.html');