Forward Deployed Engineer

32 stories tagged Forward Deployed Engineer on Learning Fanatic.

Lesson 1.2: FDE, solutions engineer, consultant and software engineer Four jobs sit close together and share job titles. Learn four questions that sort any role, and how a forward deployed engineer differs from the rest.
Lesson 1.3: A week in the life of an FDE There is no typical week for a forward deployed engineer, but there is a rhythm. See what a week looks like, how it changes, and how to protect time to build.
Lesson 1.4: The skills map and how to build each one Eight skills cover most of what a forward deployed engineer needs. Learn what each is, how to build it from scratch, and how to find and close your gaps.
Lesson 2.1: Finding the real problem behind the request Customers describe solutions, symptoms and numbers, not problems. Learn a four-layer ladder and five questions that find the real problem before you build.
Lesson 2.2: Mapping stakeholders and who decides Projects stall on people, not code. Learn to map sponsors, users, gatekeepers and blockers, and who decides what, in your first week with a customer.
Lesson 2.3: Scoping a pilot with a success metric A good pilot is a small experiment with a clear metric, a baseline and an exit rule. Learn to scope one, pick the number that proves it, and size it.
Lesson 2.4: Writing the one-page plan for a customer The one-page plan turns discovery into an agreement a customer can read in five minutes. Learn its ten parts, a full example and how to set a date you can keep.
Lesson 3.1: Auditing a customer's data landscape Before you build, find out where the customer's data lives, who owns it and whether it can be used. Learn a one-week audit that finds the surprises early.
Lesson 3.2: APIs, authentication and webhooks Most customer integrations run on APIs, tokens and webhooks. Learn how requests, logins, retries and event alerts work, and build them to survive failure.
Lesson 3.3: Data quality and pipelines for customer data Customer data is never as clean as promised. Learn six quality checks, how to build a pipeline that catches bad rows at the door, and how to keep it running.
Lesson 3.4: Security, access and compliance in a customer's environment Working inside a customer's systems means working under their rules. Learn least access, secrets, masking, logging and compliance, and how to pass a review.
Lesson 4.1: Prototype first, then harden Build a rough working version fast so the customer can react, then make it safe. Learn the three kinds of prototype, a hardening checklist and when to switch.
Lesson 4.2: Build, configure or buy for a customer Each part of a customer solution can be built, configured or bought. Learn six criteria, a scoring table and a three-year cost model to choose well.
Lesson 4.3: Building with language models in a customer setting A demo that wows is not a system a customer can rely on. Learn to start simple, ground answers, test on real cases and keep a person in the loop.
Lesson 4.4: Demo-driven development in the field A regular, honest demo keeps a customer project on course. Learn to plan backwards from the next demo, run one well, handle feedback and avoid faking it.
Lesson 5.1: Cloud, private cloud and on-premises Where software runs decides how you build and ship it. Learn the deployment targets, who is responsible for what, and how to design for the environment.
Lesson 5.2: Packaging, releases and rollbacks A release that cannot be undone is a gamble. Learn to package software, number releases, ship in stages and keep a tested way back for every change.
Lesson 5.3: Observability, alerts and runbooks A system you cannot see is a system you cannot run. Learn the four signals to watch, how to write alerts people act on, and a runbook for 3 a.m.
Lesson 5.4: Handing over without being on call forever A solution only you can run is a dependency, not a delivery. Learn to plan the handover from week one, transfer skills in stages and set the support terms.
Lesson 6.1: Running a demo that lands with any audience Planning a demo is half the job. Learn to read the room, tell the story, handle hard questions and budget the time so the people watching act on what they saw.
Lesson 6.2: Managing expectations and delivering bad news Most customer conflict is a gap between expected and actual. Learn to set honest ranges, tell bad news early and plainly, and say no without losing trust.
Lesson 6.3: Status updates people actually read A status update that nobody reads protects nobody. Learn to lead with the bottom line, use a fixed format, report honest colours and ask for decisions.
Lesson 6.4: Training users and driving adoption Software nobody uses changes nothing. Learn why people resist, how adoption spreads, how to train on real tasks and how to measure whether behaviour changed.
Lesson 7.1: Spotting patterns worth productising Custom work that repeats belongs in the product, but not every repeat does. Learn the signals, a pattern log, a scoring method and a break-even rule.