Submission Guide: Business Case Split Strategy¶

Purpose¶

Submission Strategy Overview¶

Submission Strategy¶

Part 1: Business Case (Initial Submission)¶

What: Strategic documentation, architecture design, and high-level implementation approach When: First submission to the company

Purpose (2)¶

Part 2: Code Appendix (Upon Request)¶

What: Full implementation code, infrastructure as code, and test artifacts When: Upon company request or during interview presentation

Purpose (3)¶

Part 1: Business Case Contents¶

📄 Core Documents¶

• ✅ EXECUTIVE_SUMMARY.md - High-level overview and assumptions
• ✅ HANDOUT.md - Interview presentation handout

🏗️ Architecture & Design (Task 2)¶

• ✅ tasks/02_data_lake_architecture_design/architecture.md - Complete architecture documentation
• ✅ tasks/02_data_lake_architecture_design/diagram.mmd - Architecture diagram source

📊 SQL Solution (Task 3)¶

• ✅ tasks/03_sql/balance_history_2024_q1.sql - Production-ready SQL query
• ✅ tasks/03_sql/SQL_PSEUDOCODE.md - SQL design rationale
• ✅ tasks/03_sql/SQL_DIAGRAM.md - Query flow diagrams

🔄 ETL Design (Task 1 - Design Only)¶

• ✅ tasks/01_data_ingestion_transformation/ASSUMPTIONS_AND_EDGE_CASES.md - Design assumptions and edge case handling
• ✅ tasks/01_data_ingestion_transformation/ETL_PSEUDOCODE.md - ETL logic pseudocode
• ✅ tasks/01_data_ingestion_transformation/ETL_DIAGRAM.md - ETL flow diagrams
• ⚠️ Code snippets only (key functions, not full implementation)
• ❌ NOT included: Full ingest_transactions.py source code

🚀 CI/CD Design (Task 4 - Design Only)¶

• ✅ tasks/04_devops_cicd/cicd_workflow.md - Complete CI/CD workflow design
• ⚠️ Workflow descriptions and diagrams only
• ❌ NOT included: Full .github/workflows/ci.yml YAML
• ❌ NOT included: Full infra/terraform/main.tf Terraform code

📧 Communication (Task 5)¶

Original Scope Deliverables:

• ✅ tasks/05_communication_documentation/stakeholder_email.md - Email for non-technical stakeholders (original scope)
• ✅ tasks/05_communication_documentation/one_pager_tech.md - Technical one-page document (original scope)

Extended Communications (Appendix - Not in original scope):

• ⚠️ tasks/05_communication_documentation/appendix/ - Extended stakeholder communication templates and tools (reference material only)

📚 Supporting Documentation¶

• ✅ docs/technical/TESTING.md - Testing approach and strategy
• ✅ docs/technical/AWS_SERVICES_ANALYSIS.md - AWS services analysis (updated, references AWS_SPARK_SIMPLIFICATION_ANALYSIS.md)

Part 2: Code Appendix Contents¶

💻 Full Implementation Code¶

ETL Code (Task 1)¶

• ✅ tasks/01_data_ingestion_transformation/src/etl/ - Complete ETL implementation
• ingest_transactions.py - Pandas-based ETL (original)
• ingest_transactions_spark.py - PySpark-optimized ETL (recommended)
• All supporting modules (validation, metadata, s3_operations, etc.)
• ✅ tasks/01_data_ingestion_transformation/requirements.txt - Python dependencies
• ✅ tasks/01_data_ingestion_transformation/requirements-spark.txt - PySpark dependencies
• ✅ tasks/01_data_ingestion_transformation/config.yaml - Configuration template
• ⚠️ Note: Test files are excluded from submission (see SUBMISSION_EXCLUSIONS.md)

Infrastructure as Code (Task 4)¶

• ✅ tasks/04_devops_cicd/.github/workflows/ci.yml - Complete GitHub Actions workflow
• ✅ tasks/04_devops_cicd/infra/terraform/main.tf - Complete Terraform infrastructure
• ✅ tasks/04_devops_cicd/infra/terraform/ - Additional Terraform files (if any)

SQL Testing (Task 3)¶

• ⚠️ Note: SQL test files are excluded from submission (see SUBMISSION_EXCLUSIONS.md)
• ✅ tasks/03_sql/balance_history_2024_q1.sql - Production SQL query (included)
• ✅ tasks/03_sql/schema.sql - Schema definition (if exists)

Supporting Files¶

• ⚠️ Note: Development files are excluded (see SUBMISSION_EXCLUSIONS.md):
• Test files and test infrastructure
• Docker files and containerization setup
• Development dependencies and linting configurations
• Sample data files

File Inclusion Matrix¶

Legend¶

• ✅ Included
• ❌ Excluded
• ⚠️ Partial (template/example only)

Packaging Instructions¶

Business Case Package Structure¶

ohpen-case-study-business-case/
├── EXECUTIVE_SUMMARY.md
├── HANDOUT.md
├── SUBMISSION_GUIDE.md (this file)
├── TESTING.md
├── AWS_SERVICES_ANALYSIS.md (if applicable)
└── tasks/
    ├── 01_data_ingestion_transformation/
    │   ├── ASSUMPTIONS_AND_EDGE_CASES.md
    │   ├── ETL_PSEUDOCODE.md
    │   ├── ETL_DIAGRAM.md
    │   └── config.yaml (template only)
    ├── 02_data_lake_architecture_design/
    │   ├── architecture.md
    │   └── diagram.mmd
    ├── 03_sql/
    │   ├── balance_history_2024_q1.sql
    │   ├── SQL_PSEUDOCODE.md
    │   └── SQL_DIAGRAM.md
    ├── 04_devops_cicd/
    │   └── cicd_workflow.md
    └── 05_communication_documentation/
        └── [all communication files]

Code Appendix Package Structure¶

ohpen-case-study-code-appendix/
├── README.md (explains this is the code appendix)
└── tasks/
    ├── 01_data_ingestion_transformation/
    │   ├── src/
    │   │   └── etl/
    │   │       └── ingest_transactions.py
    │   ├── tests/
    │   │   ├── test_etl.py
    │   │   ├── test_integration.py
    │   │   └── conftest.py
    │   ├── sample_data/
    │   ├── requirements.txt
    │   ├── requirements-dev.txt
    │   ├── config.yaml
    │   └── ruff.toml
    ├── 03_sql/
    │   └── tests/
    │       ├── test_balance_query.py
    │       ├── test_data.sql
    │       └── expected_output.csv
    └── 04_devops_cicd/
        ├── .github/
        │   └── workflows/
        │       └── ci.yml
        └── infra/
            └── terraform/
                └── main.tf

Communication Strategy¶

Initial Email (Business Case)¶

Subject (4)¶

Body Template (5)¶

Dear [Hiring Manager/Team],

I'm pleased to submit my response to the Ohpen Data Engineer case study. This submission focuses on the business case, architecture design, and strategic approach.

## What's Included

- Executive summary and design assumptions
- Complete data lake architecture documentation
- SQL solution for month-end balance history
- ETL design (pseudocode, diagrams, edge case handling)
- CI/CD workflow design
- Stakeholder communication templates
- Comprehensive checklist review

## What's Not Included (Available Upon Request)

- Full implementation code (ETL, Terraform, CI/CD YAML)
- Complete test suites
- Infrastructure configuration files

I've structured this submission to demonstrate architectural thinking and design decisions first. The full implementation code is available as a separate appendix that I can provide upon request or during our interview discussion.

I look forward to discussing the design decisions and approach with you.

Best regards,
[Your Name]

Follow-up Email (Code Appendix - if requested)¶

Subject (6)¶

Body Template (1)¶

Dear [Hiring Manager/Team],

As requested, please find attached the complete code appendix for the Ohpen case study submission.

## What's Included (1)

- Full ETL implementation (Python)
- Complete Terraform infrastructure code
- GitHub Actions CI/CD workflow
- Comprehensive test suites
- Configuration files and dependencies

This appendix complements the business case submission and demonstrates the technical implementation depth.

I'm happy to walk through the code during our interview discussion.

Best regards,
[Your Name]

Rationale for Split¶

Why This Split Works¶

1. Demonstrates Strategic Thinking First
2. Shows you can design before coding
3. Highlights architectural decision-making

4. Proves you understand business context

5. Protects Intellectual Property

6. Code is valuable work product
7. Allows you to present code in person

8. Gives you control over when to share full implementation

9. Shows Professional Judgment

10. Demonstrates understanding of what matters to different audiences
11. Shows you can communicate at appropriate levels

12. Proves you understand the difference between design and implementation

13. Interview Advantage

14. Code discussion becomes interview topic
15. Allows you to explain decisions in person
16. Creates natural conversation flow

Quick Reference Checklist¶

Before Sending Business Case¶

• All design documents included
• No full source code files (.py, .tf, .yml)
• SQL query included (it's a query, not infrastructure code)
• All communication documents included
• Architecture diagrams included
• Pseudocode and design rationale included
• Config templates only (not full configs)

Before Sending Code Appendix¶

• All source code files included
• Test files included
• Infrastructure as code included
• Dependencies files included
• README explaining appendix structure

Recent Updates (2026-01-22)¶

• ✅ Updated to reflect current project structure
• ✅ Added PySpark implementation files
• ✅ Clarified exclusions (tests, Docker, dev files)
• ✅ Updated file paths to match current structure
• ✅ Added note about archived documentation

Last Updated: 2026-01-22¶