Jobs · Information Technology · Tennessee

Implementation Consultant II, Construction

Built · Nashville Metropolitan Area · 4 wk ago
Information Technology$90k–$115k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes mission, description, guiding principles, what you'll do, what you'll bring, what success looks like, AI & Technology Expectations, salary range, perks, travel requirement, etc. We must not repeat job title. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. We need to map content to these headings. We have: - About the role: mission, description, purpose, guiding principles maybe. Could be "About the role" section. - Responsibilities: "What You'll Do" bullet list. - Requirements/Qualifications/Skills: "What You'll Bring" includes experience, construction industry, etc. Could be split into Requirements and Qualifications and Skills but we can combine? The instruction: Prefer a few substantive sections over many thin ones. So we can have maybe About the role, Responsibilities, Requirements, Benefits, Pay, Schedule? Travel requirement maybe part of Benefits? Or separate? Travel requirement is not a benefit but could be under "Schedule"? Not exactly. Travel requirement is about travel to Nashville twice per year. Could be under "Schedule"? Not really. Could be under "Benefits"? Not. Could be omitted? The instruction: include a section ONLY when posting has real, specific content for it. Travel requirement is specific content; we need a section for it. But allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Travel requirement could fit under "Schedule"? Not exactly; schedule refers to work schedule, maybe remote/hybrid. Travel requirement is about travel, could be under "Schedule"? Might be okay to put under "Schedule" as it's about travel expectations. However schedule usually refers to work hours, full-time/part-time, etc. Not present. Could we create a custom heading? Not allowed; only those headings. So we need to fit travel requirement into one of those. Perhaps "Benefits" includes travel? Not really. Could put under "About the role"? Might be okay to add a paragraph about travel within About the role. But we need to preserve all substantive information; we can embed travel requirement in About the role or Responsibilities? Probably better to add a short paragraph under "About the role" after mission description. Similarly, perks list: uncapped vacation, medical, dental & vision, equity, learning grant, 401k with match. That's benefits. So Benefits section. Pay: salary range $90k-115k. Schedule: Not provided; we should not create Schedule section if not present. So omit Schedule. Qualifications vs Requirements vs Skills: We have "What You'll Bring" which includes experience, construction industry, ability to deliver, communication, process improvements, knowledge of workflows, experience with methodologies, comfort with tools. That's a mix of requirements and skills. We could split into Requirements (experience, years) and Skills (communication, tools). But we can also combine into one section "Requirements" and include all. The instruction: prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. We need to use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not include boilerplate like EEO, legal, etc. Remove duplicated lines. We need to preserve all substantive information: mission, description, guiding principles, what you'll do, what you'll bring, what success looks like, AI & Technology Expectations, salary, perks, travel requirement. We need to decide where to place each piece. Let's outline:

    About the role

    Built's Mission: Connect and simplify doing business in real estate. Built is the AI-powered platform transforming the way real estate is financed, developed, and managed. Purpose-built for real estate and construction, Built began by fixing construction draw management for lenders and has grown into a comprehensive operating system addressing some of the industry’s most complex challenges. Today, Built is a partner to more than 350 lenders, over 80,000 borrowers and owners, and thousands of contractors, powering 86,000 active projects valued at more than $300 billion. Learn more at getbuilt.com.

    Built Technologies is transforming how capital moves through construction and real estate finance - one of the largest, most complex sectors in the economy. Our platform connects lenders, including many of the top U.S. banks, with the owners, developers, and general contractors they finance. When a draw is approved, a builder can pay subcontractors. When a compliance document clears, a project moves forward. The work we do here is not abstract; it has a direct and material impact on how capital flows and how real estate gets built. Our Implementations team delivers the platform experiences that determine whether a lender adopts Built as their operational backbone or walks away. As an Implementation Consultant II, you will manage a strategic portfolio of complex client implementations with growing independence; owning end-to-end delivery for enterprise-scale lending clients and beginning to contribute to how the broader team operates. You bring a track record of successful go-lives, strong client relationships, and the judgment to navigate novel challenges without constant direction. This role supports owners, developers, and general contractors and is especially well suited to someone who brings construction context plus the ability to learn and deliver software.

    Our Guiding Principles: Be Bold. We pursue the biggest problems in our industry, challenge assumptions others take for granted, and take calculated risks to get there. We don't hide behind consensus or committees. Playing it safe is just failing slowly. Help Customers Win. We learn our customers' businesses deeply — how they think, how they deploy capital, what keeps them up at night. We treat their capital like our own. We ship leverage, not features. And we measure ourselves by customer results, not our intentions. Move with Urgency & Purpose. We bias toward delivery over perfection, remove friction from our own paths, and communicate in real time. Momentum compounds — and we build it every day. Own the Outcome. We own outcomes, not just tasks. We hold a high Say:Do ratio and take responsibility from idea through impact. When something breaks, we fix it — we don't wait to be asked. Never Satisfied. We raise the bar continuously. We stay curious, hold exacting standards, debate hard, and hold our opinions loosely when the evidence shifts. Excellence is a habit, not an event.

    Travel Requirement: Employees who are not based in the Nashville area are required to travel to our Nashville office at least twice per year for company gatherings, such as Connect Week. Additional travel to Nashville may be required based on your role and business needs.

    That covers about role and travel.

    Responsibilities

    • Lead complex implementations for owner, developer, and general contractor clients - managing project scope, risk, and timeline with meaningful autonomy and clear accountability for outcomes.
    • Conduct discovery and planning sessions with client stakeholders, translating strategic business goals and workflows into actionable implementation roadmaps.
    • Manage escalations and navigate organizational dynamics on the client side, driving timely resolution of high-impact issues with composure and authority.
    • Identify process improvements and standardization opportunities across your implementation portfolio — document repeatable solutions and share them with the broader team.
    • Contribute to cross-functional initiatives with Sales, Product, and Engineering to improve implementation efficiency, reduce time-to-value, and strengthen client outcomes.
    • Track and communicate implementation metrics, insights, and lessons learned to leadership and the broader team; use data to surface patterns and drive improvement.
    • Leverage AI tools to accelerate project planning, client communication, and risk identification across your portfolio.

    Requirements

    • 2-4 years of experience in SaaS implementation, professional services, or enterprise project delivery, ideally in construction technology, financial services, fintech, or a complex B2B software environment.
    • Construction industry experience is strongly preferred. You have worked for or closely with an owner, developer, general contractor, subcontractor, or construction technology company, and understand the operational realities of running projects.
    • A proven ability to deliver concurrent client implementations on time and to a high standard, with examples of measurable client outcomes you drove.
    • Strong client communication and relationship management skills; you navigate senior stakeholders, handle difficult conversations with confidence, and build trust through consistent follow-through.
    • A track record of identifying process improvements that made implementations faster, more consistent, or more successful for clients.
    • Working knowledge of construction project and financial workflows, such as project set-up, project financials, payables, lien waivers, project controls, or subcontractor/vendor coordination. You can use that context to help a customer translate how they work today into a practical workflow in Built.
    • Some experience with implementation methodologies (Agile, Waterfall, or hybrid approaches) and comfort adapting your approach to the client's environment.
    • Comfort with project management tools, CRM systems, and analytics platforms; ability to learn new tools quickly and apply them effectively.
    We could also include AI & Technology Expectations as part of Requirements or maybe as a separate section? The instruction: only include sections when posting has real specific content. AI & Technology Expectations is specific. Could be a separate section maybe "Skills"? But we already have Requirements covering skills. Could add a subsection under Requirements? But we need to use
    • for any list. Could add another

      Skills

      for AI expectations. However we already have many sections; maybe combine AI expectations into Requirements as a bullet. Let's add a bullet: "Leverage AI tools to enhance the productivity, quality, and speed of your work. Use AI to support drafting, analysis, summarization, and problem-solving across your role. Identify opportunities to streamline workflows and reduce manual effort through automation and AI. Apply AI to sharpen decision-making and strengthen strategic insights. Share effective AI use cases and best practices with your team." That's a bit long but okay as a bullet.

      Benefits

      • Uncapped vacation [US ONLY]
      • Medical, dental & vision insurance
      • Equity in the form of stock options
      • Learning Grant program to support ongoing professional development
      • 401k with match and expedited vesting [US ONLY]

      Pay

      Built’s salary range for this position is $90,000 - 115,000 USD per year. The pay range is designed to accommodate upward mobility in the role, therefore it encompasses the full span of proficiency levels for this role and we believe that the midpoint of the range is competitive in the market. Salary is just one component of Built's total compensation package for employees; your total rewards package at Built will include equity, market-current medical, dental and vision coverage, an unlimited PTO policy, and other benefits.

      We could also include "What Success Looks Like" and "AI & Technology Expectations" maybe as part of Responsibilities or Requirements? But we already covered AI in Requirements bullet. Success looks like could be under Responsibilities? Might be better to add a section "What Success Looks Like" but not in allowed headings. Could incorporate into About the role or Responsibilities as a paragraph. Let's add a paragraph under About the role after guiding principles? Or maybe under Responsibilities as an extra bullet? However the instruction: Use
      • for any list of duties/requirements/benefits. Success looks like is not a list but prose; we could add a

        under About the role or Responsibilities. Let's add a

        under About the role after guiding principles and before travel requirement:

Similar jobs

Implement Consultant II

RealPage, Inc.Massachusetts, United States· 2 mo ago
Consulting$56k/yrapply on careers-realpagepms.icims.com