Volver al Material

💻 Fluency Class 2 – Current Tech Stack & Projects

Interview-style deep dive into your technical decisions

Model B: Interview & Deep Dive
⏱️
Duration 60 minutes
🎯
Focus Technical discussion
💡
Topic Your tech stack
🗣️
Format Tech interview style
💬
Part 1 – Opening Discussion
8 minutes • Both share experiences

🎯 Goal: Start talking about current work and tech choices

Teacher shares first: "Right now I'm working on a React project with TypeScript. We chose it because the team wanted better type safety..."

Then discuss naturally:

  • What technologies are you currently using?
  • What's your favorite tool/framework right now and why?
  • What's a tech decision you made recently that you're proud of?
💡 Teacher note: Both participants share equally. This sets up the vocabulary they'll need for the interview section.
📚
Part 2 – Vocabulary in Action
7 minutes • Learn by using

📖 Essential Phrases for Tech Discussions

Teacher introduces these while discussing the tech stack:

Phrase When to use it
I'm currently working on "I'm currently working on a microservices architecture"
We opted for / went with "We opted for PostgreSQL over MongoDB"
The main advantage is "The main advantage is faster deployment times"
One trade-off is "One trade-off is increased complexity"
It integrates well with "It integrates well with our existing CI/CD pipeline"
I prefer X over Y because "I prefer TypeScript over JavaScript because of type safety"
🔄 Micro-practice: Each person uses 2-3 phrases to describe a tool they use. Keep it conversational, not formal!
🎙️
Part 3 – Hot Seat Tech Interview
20 minutes • Interview format
🎯 Round 1: Teacher interviews Student (10 min)

Teacher acts as a tech lead/senior dev interviewing about the student's current stack

Sample Interview Questions:
  • "Walk me through your current tech stack. What are you using and why?"
  • "What was the most challenging technical decision you had to make recently?"
  • "How do you decide which framework or library to use for a new project?"
  • "Tell me about a time you had to convince your team to adopt a new technology"
  • "What tools do you use for testing? Why those specifically?"
  • "How do you stay updated with new technologies?"
🔄 Round 2: Student interviews Teacher (10 min)

Now the student becomes the interviewer! Ask about the teacher's tech choices, projects, and technical decisions.

💡 Key point: This should feel like a real tech interview or podcast. Teacher can say "That's interesting, tell me more about..." or "Why did you choose that over alternatives?"
🧩
Part 4 – Scenario Problem-Solving
20 minutes • Discuss solutions together
🎯 Real IT Problem: Choose and discuss

Together, choose ONE scenario and discuss different approaches:

Scenario 1: Scaling a Monolith

Problem: Your monolithic app is getting slow with 10k+ users. Do you refactor to microservices, optimize the current stack, or try serverless?

Discuss: Pros/cons of each approach, what you'd recommend, technologies you'd use

Scenario 2: Choosing a Frontend Framework

Problem: Starting a new project. Team is split between React, Vue, and Svelte. How do you decide?

Discuss: Evaluation criteria, team skills, project requirements, your preference and why

Scenario 3: Database Migration

Problem: Your MySQL database is hitting performance limits. Should you migrate to PostgreSQL, switch to NoSQL, or optimize MySQL?

Discuss: Migration risks, downtime concerns, data consistency, your technical recommendation

🗣️ Remember: Use the vocabulary from Part 2! "We could opt for...", "The main advantage would be...", "One trade-off is..."
💭
Part 5 – Debrief & Reflection
5 minutes • Conversational close

🎯 Final discussion:

  • Which phrase from today will help you most in tech discussions?
  • Did this interview format feel realistic to actual tech interviews?
  • What's one thing about your tech stack you explained better today than before?
💼 Real-world use: These same phrases work in: tech interviews, architecture meetings, code reviews, team discussions, and when pitching new tools to stakeholders.
🎯
Homework Assignment
Practice for next class
📝 Document Your Tech Stack Decisions

Write a technical explanation (200-250 words) as if answering this interview question:

"Describe your current tech stack. Why did you choose these specific technologies, and what trade-offs did you consider?"

Must include:

  • At least 3 phrases from today's vocabulary
  • Specific technology names (frameworks, databases, tools)
  • Reasons for your choices (advantages/trade-offs)
  • Sound confident and professional (like in a real interview)