00-quick-reference.md

Join — Phone Screen Quick Reference

Company	Join (join.build)
Role	Staff Software Engineer (Web)
Interviewer	Jon (jon@join.build), likely engineering leadership
Platform	Zoom (booked via calendar link)
Format	Phone screen, not a coding interview
Team size	Small engineering team, cross-functional pods (devs, designer, PM, EM)
Founded	2017
Funding	$30M total ($4M seed 2019, $16M Series A 2022, strategic investment from DPR + STO Building Group 2025)
Stack	React, TypeScript, Golang, Postgres, Apollo/GraphQL, Vite, Cypress, RTL, AWS, Terraform, Elastic
Salary range	$175K-$205K (Mike's target: ~$190K)
Your cover letter	Emphasized owning UI quality at scale, React/TypeScript depth, mentoring, and eagerness to learn Go

Key names to know

• Andrew Zukoski (CEO, Co-founder, ex-Google X / Flux.io)
• Drew Wolpert (Co-founder, Head of Design, ex-Flux.io) — addressed in your cover letter
• Jim Forester (Co-founder, Head of Customer Success, ex-Flux.io)
• Ye Wang (Co-founder, ex-Onshape / Autodesk)
• Anna Killgore (Head of Marketing)

01-company-brief.md

Join — Company Brief

What They Do

Join is a preconstruction and design phase management platform for commercial construction. They bring together contractors, owners, and design teams into a unified system of record, integrating real-time cost, schedule, and risk data with design evolution. The goal is to de-risk complex projects and make project delivery predictable at scale.

Their tagline: "Better precon. Better buildings."

Founded in 2017 by a team from Flux.io (a Google X spinout), Join combines deep construction industry expertise with modern technology thinking. Over 50% of the team are alumni from major construction and architecture firms.

Key Products and Capabilities

• Preconstruction Intelligence: Dynamic cost and schedule data linked to design evolution
• Design Management: Track design progress and connect it to cost/schedule impacts
• Stakeholder Engagement: Centralized collaboration for GCs, owners, designers, and trades
• Cost Analysis: Real-time cost trending, scenario modeling, contingency governance
• Risk Management: Active governance tying risks to decisions and schedules (launched April 2026)
• Procurement Coordination: Streamline subcontractor and materials procurement
• Schedule Integration: Connects with Oracle Primavera Cloud, P6, Microsoft Project

They support collaborative delivery models like Design-Build, CMAR, IPD, IFOA, and TVD (Target Value Design).

Traction and Scale

• 1,000+ companies on the platform
• 1,000+ projects managed
• $10B+ in decision impact
• Used by over 50% of ENR Top 50 general contractors
• Clients include DPR Construction, Swinerton, Boldt, Clark Construction, Kitchell, Barton Malow, XL Construction, McCarthy

Leadership

Name	Role	Background
Andrew Zukoski	CEO, Co-founder	Flux.io (Google X spinout)
Drew Wolpert	Head of Design, Co-founder	Flux.io
Jim Forester	Head of Customer Success, Co-founder	Flux.io
Ye Wang	Co-founder	Onshape, Autodesk (manufacturing design tech)
Anna Killgore	Head of Marketing	—

Funding

• 2019: $4M Seed
• 2022: $16M Series A led by SignalFire, with Ironspring Ventures, Metaprop, Building Ventures, Standard Investments ($30M total)
• 2025: Strategic growth investment from DPR Construction (WND Ventures) and STO Building Group

The strategic investments from actual construction companies are notable. It shows deep industry buy-in beyond typical VC funding.

Recent News (Last 6 Months)

• April 7, 2026: Major platform update integrating cost, risk, and schedule into unified preconstruction system. Press release claims they help "eliminate $100K-a-day delays."
• April 2026: Published AI strategy blog post emphasizing open approach via Model Context Protocol (MCP), rejecting closed chatbot approaches
• September 2025: Growth investment from DPR Construction and STO Building Group
• 2025: Multiple case studies published (Parkway with 1,500 projects, Barton Malow, XL Construction for UCSF)

AI Strategy (Important Talking Point)

Join takes a notably thoughtful, open approach to AI. Key points from their recent blog post:

1. Intellectually honest: They acknowledge what AI can and cannot do today. No hype.
2. Open, not closed: They use Model Context Protocol (MCP) instead of building a walled-garden chatbot. Users bring their own AI tools.
3. People-first: AI supports human judgment, it does not replace it. They value their people-driven teams.
4. Ecosystem-oriented: Real preconstruction work spans multiple systems and companies. AI should work across tools, not be trapped in one.

Their framing: "Power BI for construction is Power BI." Horizontal AI platforms (Anthropic, OpenAI, Google) evolve faster than any single vertical vendor can keep up.

They specifically mention Anthropic/Claude in their blog post.

Culture and Values

• "Collaboration-obsessed. People-powered."
• Fully remote, distributed across USA and Canada
• Five core principles:
  1. The built environment matters
  2. Every project is unique, requiring thousands of decisions
  3. Best decisions come from confidence, informed expertise, and proper context
  4. Building a lasting technology company
  5. Serving customers and the communities they build

Competitors and Market Position

• BuildingConnected: Bid management, subcontractor vetting
• Procore: End-to-end construction management (broader but less preconstruction-specific)
• Autodesk Construction Cloud: Design collaboration, integrates with Join for some workflows
• Downtobid: AI-driven bid management
• ConCntric: AI-powered collaborative preconstruction ($10M Series A in 2025)
• Beam AI: Connected preconstruction for bid workflows ($30.5M Series B in 2025)

Join's differentiator: they focus specifically on the preconstruction and design phase, unifying fragmented data across stakeholders. Procore is broader but shallower in precon. BuildingConnected focuses on bidding. Join focuses on the full decision-making lifecycle before ground breaks.

Headquarters

1611 Telegraph Ave, Suite 1500, Oakland, CA 94612 (fully remote team)

02-role-and-jd.md

Staff Software Engineer (Web) — Role Summary

The Role

Join is hiring multiple senior/staff engineers across frontend-heavy, fullstack, and backend-heavy profiles. They specifically want 1-2 engineers with "architect-level frontend expertise" who can own UI quality and reduce dependency on current leadership for frontend reviews. You join a cross-functional team with developers, a designer, a PM, and an engineering manager.

Responsibilities

• Lead through code: write high-quality features, provide thoughtful PR reviews, pair with teammates
• Influence architectural decisions and help establish engineering-wide coding standards
• Collaborate closely with product, design, and engineering leadership on major initiatives
• Drive continuous improvements in developer experience, performance, and reliability
• Reserve regular time for research, learning, and leveling up the team
• Often act as project-level technical lead, breaking down large efforts and supporting junior/mid-level developers

Weekly Time Breakdown

• 25-75% writing code or prepping to write it (EDDs, planning)
• 25-50% reviewing others' code (sync and async)
• 10-20% pairing, knowledge sharing (blog posts, presentations, docs)

Required Qualifications (Core Attributes)

• Clear communication and genuine desire to mentor others on modern engineering practices
• Balanced approach: ship with urgency while articulating tradeoffs and long-term implications
• T-shaped skill set across React, Golang, and Postgres, with deep expertise in at least one

Frontend Expertise (What They're Looking For)

• Large-scale React development: render lifecycle, memoization, state management patterns, TypeScript strategies
• Experience shaping frontend architecture, establishing patterns, reviewing UI code at high volume, leveling up teams
• Comfort with dev tooling (Vite, RTL, Cypress), performance tooling, accessibility considerations
• Familiarity with Apollo/GraphQL and caching layer pitfalls (nice-to-have)

Backend Expertise

• Strong Go idioms, concurrency patterns, generics, TDD
• Profiling, performance optimization, memory management
• Hand-written complex SQL, query planning, indexing, MVCC, advisory locks

Infrastructure/Ops Expertise

• Production systems on AWS (IAM, networking, autoscaling, RDS, ECS, Lambda)
• Terraform expertise for infrastructure as code
• Observability systems (Prometheus, TimescaleDB, metrics pipelines, dashboards)
• Developer experience focus: automating workflows, improving CI/CD

Nice-to-Haves

• AWS deployment via Terraform
• Light Elastic usage
• Event-driven architectures and message queues

Compensation and Benefits

• Salary: $175K-$205K/year
• Equity: Company equity included
• Medical: 100% employer-sponsored premiums
• 401(k): Yes
• PTO: Generous policy including two company-wide shutdown weeks
• Education: Continuing education budget
• Location: Fully remote, USA and Canada

How They Hired

Email resume to jon@join.build, with a PR review example showing positive impact. Mike applied via email on 2026-04-07 and booked a Zoom call the next day. Fast turnaround.

03-your-angle.md

Your Angle — Phone Screen

What to Emphasize

1. You are the frontend architect they're looking for. The JD says they want 1-2 engineers with "architect-level frontend expertise" who can "own UI quality and reduce dependency on current leadership for frontend reviews." That is exactly what you did at Vermont Mutual. Lead with this.

2. You lead through code and reviews, not just titles. The role emphasizes PR reviews, pairing, mentoring, and establishing coding standards. Your cover letter already offered a PR review example. Reinforce that you see code review as a tool for raising quality across the team, not just catching bugs.

3. You care about the product, not just the code. Join builds for an industry where decisions have massive financial consequences ($100K/day delays). Your product engineering mindset (from ASPIRATIONS) and UX-first approach are directly relevant. You care about how the software feels and functions for the humans using it.

4. Your React and TypeScript depth is real and current. 15+ years full-stack experience with deep React and TypeScript expertise built through Vermont Mutual (2020-2025) and Versal (2012-2020). You know render lifecycles, state management, memoization patterns, and TypeScript strategies from building production SPAs at scale.

5. You're genuinely curious about Go and Postgres. Your cover letter said you're "eager to become fluent with Go and to work closely with Postgres." This is T-shaped thinking. The JD explicitly says they're hiring across skill profiles and you don't need deep expertise in every part of the stack.

Talking Points

"Tell me about your experience"

Focus on Vermont Mutual (2020-2025): Led modernization of legacy tools into performant React SPAs. Partnered with 10-20 engineers, designers, and stakeholders. Owned UI development across teams. Advocated for UX-first development and shipped features users praised. Kept releases predictable with CI/CD, clear docs, and cloud deployments.

"Why Join?"

The preconstruction space is fascinating because the decisions made before ground breaks determine whether a project succeeds or fails. Join's approach of unifying cost, schedule, and risk data into a single system of record is compelling. The AI strategy blog post stood out: the open MCP approach instead of a closed chatbot shows real technical and product thoughtfulness. You want to be part of a team that thinks that carefully about how to build.

"What would you do in the first 90 days?"

From your cover letter: Own a complex collaboration flow end to end and make it fast, clear, and reliable. Shape simple component and state architecture. Make loading, empty, and error states explicit. Keep feedback loops tight through pairing, walkthroughs, and review.

"Tell me about code review"

Your reviews focus on intent, naming, testability, and small changes that raise quality without slowing delivery. You offered a PR review example in your application. Reviews are a chance to teach and learn, not just gatekeep.

"Experience with mentoring"

At Vermont Mutual you mentored, paired, and led reviews across a team of 10-20. At Versal you supported partners integrating white-label products and APIs, which required teaching and clear communication.

What NOT to Say

• Don't claim Go or Postgres expertise you don't have. Express genuine eagerness to learn and grow into those areas. They know they're hiring across profiles.
• Don't overstate years on React/TypeScript specifically. Say "15+ years full-stack with deep React and TypeScript expertise." Don't say "15 years of React experience."
• Don't bring up salary. It's a phone screen. If they ask, your target is around $190K within the posted $175-205K range. Let them raise it.
• Don't be generic about "why this company." Reference their specific products, the MCP approach to AI, the recent platform update, the DPR/STO investment. Show you did your homework.
• Don't undersell the construction domain. Even though it's new to you, frame it as exciting. The built environment is meaningful work. Decisions in preconstruction affect real communities.

04-questions-to-ask.md

Questions to Ask

About the Product

1. The April platform update integrated cost, risk, and schedule into a unified view. What was the biggest technical challenge in bringing those three systems together in the UI? How does the frontend handle the complexity of rendering interconnected data across those dimensions?

2. Your case studies mention Target Value Design (TVD) workflows. How much of the product's frontend complexity comes from supporting different delivery models (Design-Build, CMAR, IPD, TVD) versus shared collaboration patterns?

3. How do users typically interact with scenario modeling? Is it a real-time, interactive experience or more of a configure-and-calculate flow? I'm curious about the render and state management challenges there.

4. The MCP approach to AI is really interesting. How are customers actually using it today? Are they connecting Join to Claude or other tools for specific workflows, or is adoption still early?

About the Engineering

5. The JD mentions you want to "reduce dependency on current leadership for frontend reviews." What does the frontend review process look like today, and what would success look like once new staff engineers are in place?

6. What does the frontend architecture look like at a high level? Is it a single large React app, multiple apps, microfrontends? How do you manage complexity and code boundaries?

7. You mention Apollo and GraphQL in the JD. How does the data layer work between the React frontend and the Go backend? Any pain points or areas you're looking to evolve?

8. What does the deploy process look like? How often are you shipping to production, and what does the CI/CD pipeline involve?

About the Team

9. How big is the engineering team right now, and how is it structured? You mention cross-functional pods with a designer, PM, and EM. How many of these pods exist?

10. The JD says 25-50% of time on code review. That's a significant investment. What drives that emphasis? Is it about quality, knowledge sharing, or leveling up the team?

11. How do you think about the balance between frontend-heavy and fullstack engineers? Are the frontend-heavy folks primarily in React, or do they touch Go and Postgres regularly?

About the Customer

12. Your customers are major construction companies like DPR, Barton Malow, and Clark. How close does the engineering team get to end users? Do engineers participate in customer calls or feedback sessions?

13. What's the typical user persona for the product? Is it a preconstruction manager staring at this all day, or is it more of a periodic check-in tool for executives?

About Culture and Growth

14. The AI strategy blog post says you're "intellectually honest" about what AI can and cannot do today. I love that framing. How does that intellectual honesty show up in how the engineering team makes technical decisions generally?

15. What drew you to Join, and what keeps you here?

05-cover-letter.md

Hi Drew and Join team,

What draws me here is owning UI quality at scale in a product that helps teams make clear decisions together during preconstruction. I work best where React and TypeScript meet thoughtful product design. I like tight render lifecycles, predictable state, and interfaces that feel fast and trustworthy. I lead through code, reviews, and mentoring, and I ship with urgency while making tradeoffs explicit.

From 2020 to 2025 at Vermont Mutual I led the move from legacy tools to performant React based SPAs. I partnered with 10 to 20 engineers, designers, and stakeholders and owned UI development across teams. I advocated for UX first development and shipped features users praised. I kept releases predictable with solid CI and CD, clear docs, and dependable cloud deployments. I mentored, paired, and led reviews. I saw you asked for a PR review example and I am happy to share one. My reviews focus on intent, naming, testability, and small changes that raise quality without slowing delivery.

Earlier at Versal I built front end features for education products and designed and maintained third party APIs, a CLI based SDK, and shared libraries. I supported partners integrating white label products and APIs which sharpened instincts for clear contracts and calm production debugging. Before that I built a book import engine and optimized large scale SQL at LibraryThing, and I integrated real time services at Capsule. I am T shaped across front end, APIs, and data with deep expertise in React and TypeScript. I like to learn and I am eager to become fluent with Go and to work closely with Postgres where it improves product outcomes.

What I would take on first. Own a complex collaboration flow end to end and make it fast, clear, and reliable. Shape simple component and state architecture. Make loading, empty, and error states explicit. Keep feedback loops tight through pairing, walkthroughs, and review. I am curious how you define UI quality, how you structure review time, and how you balance speed with craftsmanship as the team grows. My resume is at https://mikebannister.vercel.app/. I would welcome a conversation.

Best, Mike Bannister

What are the most hard hitting impact that Join makes for precon when compared to existing systems? What are the big opportunities in the future?

What's the motivation for hiring right now?

Great mentoryship key to my story

Email and excel