a day in the life of an engineer working from home

Joma Tech| 00:07:52|Mar 26, 2026

Chapters9

Speaker introduces the infrastructure proposal for Blinder and outlines the plan for design review and customer sync.

A humorous peek at a homebound engineer juggling design reviews, client calls, and everyday distractions while pitching an infrastructure proposal.

Summary

Joma Tech’s day-in-the-life sketch follows a remote engineer as they scramble through a busy morning and a string of meetings about Blinder, a blinds-as-a-service company. The video shows the designer-finalizing proposals, prepping for a design review, and planning a sync with the customer to propose an infrastructure solution. Tension arises over miscommunications, timing, and the need to demonstrate value beyond the product itself. Throughout, the presenter tries to keep the conversation focused on privacy, data handling, and scalability—often clashing with stakeholders who want more immediate features like machine learning. A recurring gag highlights the chaos of a remote workday, from interrupted presentations to wrong-screen moments and a masseuse visit. The humor lands in part because the scenarios—imperfect meetings, late starts, and shifting priorities—mirror real-world remote collaboration. The piece nudges viewers to think about how engineers balance technical depth with stakeholder communication in a distributed environment. Finally, the video ends with a quick deferment to continue the discussion later, underscoring the ongoing nature of product design in a home-office world.

Key Takeaways

Clear agenda and timeboxing matter: multiple meetings show how a concise plan helps keep a distributed team aligned (design review, customer sync, infra proposal).
Stakeholder expectations must be managed: the team debates where ML fits in and whether privacy constraints limit data collection.
Remote-work friction is real: miscommunications, screen-sharing hiccups, and last-minute schedule changes occur even for experienced engineers.
Design proposals must connect business value to architecture: the emphasis on horizontal scaling and infrastructure changes illustrates this link.
Deferring decisions and offering offline follow-ups are common in busy sprints, highlighting the need for structured next steps when consensus isn’t reached.
Privacy-first stance shapes architecture discussions: the team highlights that Blinder prioritizes privacy over data collection for ML.
Communication styles impact outcomes: the interplay between design talks and casual remarks reveals how tone and clarity affect collaboration.

Who Is This For?

Essential viewing for software engineers and product/design teams navigating remote collaboration, stakeholder management, and early-stage infrastructure planning in consumer hardware or SaaS projects.

Notable Quotes

"“Yep. Uh I finalized the design and the proposal and later today I have a design review with the broader team and then after that I have a sync with the customer where I'll propose the infrastructure solution.”"

—Opening setup showing the flow of the day: design, review, client sync.

"“We sell privacy, we sell security, we sell the peace of mind. And window blinds are merely the means for that with with machine learning of course.”"

—Defines Blinder’s value proposition and the tension around ML integration.

"“No, no. We sell privacy-first—we would never collect data from our customers.”"

—The debate over data collection and ML applicability.

"“I think it’ll make a lot more sense once you see the diagram.”"

—Illustrates the common remote-work pitfall of screen-sharing mishaps.

"“Block changed. We’ll talk about that next time.”"

—Ending note pointing to continuing discussions and iterative process.

Questions This Video Answers

How do you run a design review for an infrastructure proposal in a remote team?
What are best practices for balancing privacy with machine learning in a customer-facing product?
What does horizontal scaling mean in the context of an infra proposal for a SaaS/XaaS business?
How can remote professionals manage meeting fatigue and miscommunication when presenting to executives?
What should you include in a customer sync when proposing a new infrastructure solution?

Remote workInfrastructure designHorizontal scalingData privacyProduct design reviewsMachine learning discussionBlinder ( blinds-as-a-service )Joma TechDesign review dynamics

Full Transcript

[Music] Whoa. Hey, so sorry I'm late. I I just No worries. I'm sure there was a lot of traffic from your bedroom to your living room. You know how it is. Monday mornings. Today is Wednesday. Anyways, um any updates on our customer blinder.io? Yep. Uh I finalized the design and the proposal and later today I have a design review with the broader team and then after that I have a sync with the customer where I'll propose the infrastructure solution. Good. Uh let me know if you need any support from me but uh that's all I have for you today. Oh yes. Um performance review is coming up. You said that if I let this project, I hope you set up for a promotion. I sort of perform. Sorry. Go ahead. Go on. So, as I was wondering, sorry, please go. Oh, okay. Cool. Um, I I'll go then. No, no, that's not what I meant. Thanks everyone for joining. I'll be talking about the infrastructure proposal for the company Blinder. Uh they make um hey Steve, do do you uh do do you need some time to Nope, I'm good. Okay. Um so as I was saying, uh Blinder uh provides window blinds as a service. And um I'm sorry. I just want to say that it's totally okay if you need to sit this one out and deal with it. Why would I? There's nothing else I would rather do than listen to your wellprepared presentation. Steve. Um, on second thought, you might be right. Steve, I'm sorry, honey. I'm coming. As I was saying, a company offering blinds as a service will definitely require Shoot. Am I late? I'm so sorry. I I I I thought it was scheduled at 2:35, not 2:30 on the dot. Anyways, so here is my proposal for the info changes to allow for horizontal scaling. Uh, any questions? All right. Well, if there's no questions, uh, you guys can get 25 minutes back. Thanks. Bye. Of course. Yeah. So, that's the highlevel overview of the new design for Blinder. Uh, do you have any questions? Sorry. It's um it's not a big deal, but it kind of bothers me. So, the company name is Blinder without the E, so it's Blinder. Um, okay. Yeah, Blinder. No, Blinder. blinder. All right, we we we can take this offline for another time. Uh what were you saying? Yeah. Do you have any questions about the design? Oh, yeah. Here's the thing. I don't see machine learning anywhere in your proposal. Uh you sell blinds to customers. No, no. We sell privacy, we sell security, we sell the peace of mind. And window blinds are merely the means for that with with machine learning of course. Oh okay. Um what what data sets are we working with? Uh are you collecting their feedbacks, their returns or um wait did did you not hear a word I said we are all about privacy. So we would never collect data from our customers. Actually I I I think I understand our intellectual discrepancy. Okay, oral communication. It's low bandwidth medium. I get it. It's not your fault. Let me just show you a PowerPoint of our design. I think it'll make a lot more sense once you see the diagram. All right. Do you see my screen? Um I I see your screen, but I don't think you're sharing the right one. There we So you understand now right the innovation just a second. Sorry I had a delivery come in. Um yeah we we'll we'll look into that. Um do you have a team of machine learning engineers uh to work with us? No. Why would we? Well how are you going to maintain all this new technology in your system? Well, that's for you guys to figure out. Isn't that the whole point of your team? Anyways, I got to go. My masseuse is here. Oh, one more thing. Block changed. We'll talk about that next time. I'm sorry. And it just so happens this morning was a very good time facial expressions.