Initial
This commit is contained in:
76
02-Jobs/Active/SEB Data Architect.md
Normal file
76
02-Jobs/Active/SEB Data Architect.md
Normal file
@@ -0,0 +1,76 @@
|
||||
---
|
||||
company: SEB
|
||||
position: Data Architect
|
||||
applied-date: 2024-12
|
||||
status: rejected
|
||||
priority: high
|
||||
tags: [job-application, seb, data-architect]
|
||||
broker: TBD
|
||||
---
|
||||
|
||||
# SEB - Data Architect
|
||||
|
||||
## 📋 Overview
|
||||
**Job URL**:
|
||||
**Broker**: (Check with Henrik)
|
||||
**Contact Person**:
|
||||
**Applied**: December 2024
|
||||
**Interview**: Completed - did not go well
|
||||
**Status**: Waiting for final response
|
||||
|
||||
## 🎯 Position Match Analysis
|
||||
### Requirements Match
|
||||
- **Technical Skills**: 8/10 - Strong database and architecture background
|
||||
- **Domain Knowledge**: 7/10 - Financial services experience
|
||||
- **Modern Data Terminology**: 4/10 - **This was the problem**
|
||||
- **Overall Fit**: 6/10
|
||||
|
||||
### Key Requirements
|
||||
- [x] Database architecture expertise
|
||||
- [x] Financial services experience
|
||||
- [ ] Data Mesh understanding - **weak articulation**
|
||||
- [ ] Data Governance knowledge - **conceptual only**
|
||||
- [ ] Data Mart design - **not well communicated**
|
||||
|
||||
### My Strengths for This Role
|
||||
1. 25+ years SQL Server expertise
|
||||
2. Financial services domain (TCM, AbaSec)
|
||||
3. Azure cloud architecture
|
||||
4. Integration architecture
|
||||
|
||||
### Gaps That Hurt Me
|
||||
- **Terminology gap**: Understood concepts but couldn't articulate in modern "data architect lingo"
|
||||
- **Data Mesh**: Knew the concepts but couldn't discuss fluently
|
||||
- **Preparation**: Should have studied terminology more before interview
|
||||
|
||||
## 💭 Interview Reflection
|
||||
|
||||
### What Went Wrong
|
||||
- Struggled to articulate experience using modern data architecture terminology
|
||||
- Data Mesh, Data Governance concepts - I understand them but couldn't speak the language
|
||||
- Interviewer probably thought I lacked current knowledge
|
||||
- Should have prepared more on translating my experience to their vocabulary
|
||||
|
||||
### What I Learned
|
||||
- **Critical lesson**: Technical ability ≠ Interview ability
|
||||
- Need to **study terminology** for data architect positions
|
||||
- My experience is relevant - I just need to **translate it**
|
||||
- Should have reviewed: Data Mesh, Data Fabric, Data Catalog, Data Governance frameworks
|
||||
|
||||
### If I Could Do It Again
|
||||
1. Study modern data architecture terminology for 1-2 weeks
|
||||
2. Practice translating my projects into Data Mesh concepts
|
||||
3. Prepare examples of data governance from TCM work
|
||||
4. Map my AbasecGateway work to modern patterns
|
||||
|
||||
## 🎓 Action Items for Future Similar Roles
|
||||
- [ ] Complete Data Mesh learning module
|
||||
- [ ] Study Data Governance frameworks
|
||||
- [ ] Create translation guide: My experience → Modern terms
|
||||
- [ ] Practice interview answers with new terminology
|
||||
- [ ] Create "SEB post-mortem learning note"
|
||||
|
||||
## 🔗 Related
|
||||
- Learning needed: [[Data Mesh]], [[Data Governance]], [[Modern Data Architecture Terminology]]
|
||||
- Similar roles: Watch for more Data Architect positions
|
||||
- Profile: [[Data Architect Profile]] - needs update with terminology
|
||||
72
02-Jobs/Pipeline/Svenska Kraftnät .NET Developer.md
Normal file
72
02-Jobs/Pipeline/Svenska Kraftnät .NET Developer.md
Normal file
@@ -0,0 +1,72 @@
|
||||
---
|
||||
company: Svenska Kraftnät
|
||||
position: .NET Developer
|
||||
applied-date: 2025-01-recent
|
||||
status: submitted
|
||||
priority: high
|
||||
tags: [job-application, svenska-kraftnat, dotnet]
|
||||
broker: TBD
|
||||
---
|
||||
|
||||
# Svenska Kraftnät - .NET Developer
|
||||
|
||||
## 📋 Overview
|
||||
**Job URL**:
|
||||
**Broker**:
|
||||
**Contact Person**:
|
||||
**Applied**: Recently (early January 2025)
|
||||
**Status**: Waiting for response
|
||||
|
||||
## 🎯 Position Match Analysis
|
||||
### Requirements Match
|
||||
- **Backend .NET**: 10/10 - Perfect fit
|
||||
- **SQL Server**: 10/10 - Perfect fit
|
||||
- **Azure**: 10/10 - Strong experience
|
||||
- **ReactJS**: 3/10 - **Only gap**
|
||||
- **Overall Fit**: 9/10 - Nearly perfect
|
||||
|
||||
### Key Requirements
|
||||
- [x] .NET development - **Expert**
|
||||
- [x] SQL Server - **25+ years**
|
||||
- [x] Azure cloud - **Strong**
|
||||
- [x] Backend architecture - **Strong**
|
||||
- [ ] ReactJS - **Gap: We used Angular, not much UI work**
|
||||
|
||||
### My Strengths for This Role
|
||||
1. **Perfect backend match**: .NET, SQL Server, Azure are my core
|
||||
2. **Architecture experience**: Microservices, Clean Architecture
|
||||
3. **Full pipeline experience**: CI/CD, DevOps
|
||||
4. **Senior level**: Can lead and mentor
|
||||
|
||||
### The React Gap
|
||||
- **Reality**: Haven't worked with React specifically
|
||||
- **Related**: Have Angular experience from Tieto
|
||||
- **UI work**: Limited - more backend focused
|
||||
- **Mitigation**: Fast learner, modern frameworks share concepts
|
||||
- **Plan**: Start React learning immediately
|
||||
|
||||
## 🎓 Preparation Plan
|
||||
|
||||
### React Learning Path
|
||||
- [ ] Complete React fundamentals course (Udemy/Pluralsight)
|
||||
- [ ] Build small React app with .NET backend
|
||||
- [ ] Study React + .NET Web API integration
|
||||
- [ ] Prepare to discuss: "I haven't used React in production but have Angular experience and am actively learning React"
|
||||
|
||||
### Interview Preparation
|
||||
- [ ] Prepare backend architecture examples
|
||||
- [ ] SQL Server optimization war stories
|
||||
- [ ] Azure architecture decisions
|
||||
- [ ] Team collaboration examples
|
||||
- [ ] Address React gap honestly but positively
|
||||
|
||||
## 💬 React Gap Talking Points
|
||||
|
||||
**Honest approach**:
|
||||
"I haven't worked with React in production. At Tieto we used Angular for our frontend work, though my primary focus was backend architecture. I understand React's component model and have started learning it because I see it's the industry standard. My strength is backend .NET and SQL Server, which is 90% of this role, and I'm confident I can pick up React quickly given my Angular background and general frontend understanding."
|
||||
|
||||
## 🔗 Related
|
||||
- Profile: [[Backend Developer Profile]]
|
||||
- Skills: [[.NET]], [[SQL Server]], [[Azure]]
|
||||
- Learning: [[React Fundamentals]] - **START ASAP**
|
||||
- Projects: [[AbasecGateway Project]] - great example
|
||||
47
02-Jobs/Pipeline/Vattenfall ML Architect.md
Normal file
47
02-Jobs/Pipeline/Vattenfall ML Architect.md
Normal file
@@ -0,0 +1,47 @@
|
||||
---
|
||||
company: Vattenfall
|
||||
position: Architect - ML Initiative
|
||||
applied-date: 2024-12
|
||||
status: submitted
|
||||
priority: high
|
||||
tags: [job-application, vattenfall, ml-architect]
|
||||
broker: TBD
|
||||
---
|
||||
|
||||
# Vattenfall - Architect for ML Initiative
|
||||
|
||||
## 📋 Overview
|
||||
**Job URL**:
|
||||
**Broker**: (Check with Henrik)
|
||||
**Contact Person**:
|
||||
**Applied**: December 2024
|
||||
**Status**: Waiting for response - Vattenfall known for slow process
|
||||
**Expected Timeline**: Unknown
|
||||
|
||||
## 🎯 Position Match Analysis
|
||||
### Initial Assessment
|
||||
- **Architecture Experience**: Strong fit
|
||||
- **Azure Cloud**: Strong fit
|
||||
- **ML Architecture**: Need to learn specifics
|
||||
- **Overall Fit**: TBD - depends on role details
|
||||
|
||||
### My Questions
|
||||
- What level of ML expertise expected?
|
||||
- More architecture role or ML engineering?
|
||||
- Team structure and stakeholders?
|
||||
|
||||
## 📝 Follow-up Actions
|
||||
- [ ] Check with Henrik on status
|
||||
- [ ] Research Vattenfall's ML initiatives (if public)
|
||||
- [ ] Prepare for potential interview
|
||||
|
||||
## 🎓 Preparation Needed
|
||||
- [ ] Study MLOps patterns
|
||||
- [ ] Azure ML services review
|
||||
- [ ] Model deployment architectures
|
||||
- [ ] ML governance and monitoring
|
||||
|
||||
## 🔗 Related
|
||||
- Profile: [[Technical Architect Profile]]
|
||||
- Skills: [[Azure]], [[Architecture Patterns]]
|
||||
- Learning: [[MLOps Basics]]
|
||||
Reference in New Issue
Block a user