The Six Open Roles and the Screen Behind Them
TrueBiz, a venture-backed merchant risk-intelligence company, has added two openings in the past week, as its current job-board snapshot shows. Its board lists six openings around a technical product: core software, solutions, web development and commercial roles. The core engineering materials point to a demanding, domain-specific bar: candidates must show they can turn a merchant’s web footprint into underwriting evidence and keep that system dependable. YC and lead investor Flourish Ventures also host the vacancies on job platforms that reach a concentrated network of startup and fintech operators.
TrueBiz says its platform uses large language models to analyze a business’s website and broader online presence, then sends risk signals to risk and underwriting teams through an API. TrueBiz says its customers include some of the world’s largest payment networks, fintechs, banks and merchant-services companies.
The current openings are:
- Part-time Web Designer & Developer
- Founding Solutions Engineer
- SDR Manager, Enterprise Outbound
- Growth Lead, Enterprise Outbound
- Head of Sales
- Senior Software Engineer, Core Team
The six titles span core software, solutions work, web development, outbound growth and sales leadership rather than engineering alone. The product promise shapes them unevenly: the core software title is explicitly tied to the risk workflow, while the two enterprise-outbound positions and Head of Sales point to commercial work. The available board records do not spell out the duties or screening criteria for every opening.
The Senior Software Engineer, Core Team seat is the clearest bridge between product and screen. The posting asks candidates to build, ship and maintain production systems, so a résumé that only lists broad fintech or model work does not establish ownership of a live, revenue-generating risk system.
The Founding Solutions Engineer title suggests a connection between the risk API and customer systems, but the available job materials omit a full description, so the role’s technical requirements remain unspecified. The product context raises one question for candidates: can they put a fast, model-backed risk product inside a customer’s underwriting operation? The posting itself does not establish how candidates will be assessed.
Both outbound titles contain Enterprise Outbound, while the Head of Sales opening points to leadership for the wider sales effort. TrueBiz says its product helps risk and underwriting teams understand merchants. The meaning of its signals, the speed of its API and their role in a business decision form relevant product context, but the available materials do not specify the duties or scoring criteria for these three openings.
The Part-time Web Designer & Developer carries the least product-specific title in the set. The available materials do not say whether the role supports the customer product, internal tools or the company’s own website, so calling it a core risk-engineering opening would overstate the evidence. It is the opening for which the available evidence supports the fewest product-specific conclusions.
The materials do not describe an automated filter, rejected keywords or a formal applicant rubric. With no documented filter, the verifiable screen is the published role criteria. For the core software role, those criteria emphasize production-system experience, ownership and judgment, Python, Django and PostgreSQL, end-to-end AWS ownership, AI-assisted development, observability, reliability and customer context. The next question is what that target demands in practice.
Why a 30-Second Risk API Demands a Specific Engineering Profile
The product behind that screen is time-sensitive. TrueBiz’s Web Presence Review takes a merchant’s website and broader web presence, returns a business-model summary and risk rating, and adapts the result to a user’s rules and preferences. The aim is to reduce manual review during merchant underwriting and monitoring.
TrueBiz says its API can deliver 250+ risk signals on any business in under 30 seconds. That is a company product claim; the available materials do not establish it as an independent benchmark or service-level guarantee. The described workflow must collect evidence across the web, synthesize it in context, apply customer-specific rules and return a usable result through an API. The engineering posting treats reliability, latency, debuggability, observability and incident response as part of that work rather than a later addition.
The role lists experience with systems that rely on third-party APIs and LLM APIs while using external data vendors and scraping. It also asks for strong judgment when working with AI-generated code, along with observability, alerting and incident response. Production experience with external data sources therefore matters because TrueBiz’s output depends on evidence assembled across the web. For applicants, the relevant evidence includes how external dependencies and failures were handled while keeping results connected to a customer decision.
TrueBiz says its review can return a business-model summary, risk rating and 250+ data points, with the result tailored to customer rules and preferences. The engineering posting asks candidates to review, test and constrain AI-generated code and to improve workflows that depend on LLM calls. For a résumé, the relevant questions concern the model’s place in that workflow, its surrounding checks and how errors from external data or model calls were handled. A model output that reads fluently is not evidence of a useful assessment.
The posting treats underwriting, compliance, risk, fraud, fintech and payments experience as nice-to-have rather than formal requirements. TrueBiz says the product clarifies a merchant’s identity and activities and flags possible concerns around fraud, compliance or its business model. An application should make that context visible rather than rely on a broad fintech label.
The posting asks for improvements in reliability, latency and debuggability for workflows involving external APIs, web data and LLM calls, alongside observability, alerting and incident response. A claim of speed says little without evidence of where time goes and which dependencies could fail; the relevant record is how the engineer monitored and kept a live, revenue-generating product operating. That makes monitoring and incident response part of the operating requirements, not optional polish.
Together, those duties connect the underwriting use case to the API and to the work needed to keep web evidence, model calls and enterprise users connected. Payment and API experience can support the background, but the posting adds merchant-risk context and strong production judgment. The same accelerator and investor network that distributes the openings also concentrates applicants with startup and fintech experience.
YC S22 and Flourish Ventures: What the Backing Network Signals to Applicants
As a Y Combinator S22 company, TrueBiz raised a $2.4 million seed round led by Flourish Ventures in January 2023. TechCrunch reported that Homebrew, The Fintech Fund and Y Combinator also invested.
The accelerator and investor provide overlapping discovery channels. TrueBiz’s Y Combinator job listing puts the core-team role in front of candidates browsing YC-funded startups. The Flourish Ventures job site lists openings across 84 companies, including TrueBiz, giving applicants another route to the role. The shared YC and investor channels concentrate discovery around TrueBiz even though no formal referral arrangement is documented.
No materials reviewed mention an alumni preference, referral bonus or formal recruiting agreement, so neither affiliation guarantees an advantage. Nor does the absence of a stated preference make the connections irrelevant: job boards and investor relationships still shape which candidates encounter the opening.
Flourish’s portfolio page lists Alloy, an identity-risk system that helps banks and fintechs automate decisions for onboarding, ongoing fraud and AML monitoring, and credit underwriting. Managing partner Emmalyn Shaw explicitly invoked Flourish’s firsthand experience investing in Alloy and other KYC companies when discussing TrueBiz’s KYB opportunity. In a TechCrunch email, she wrote:
“We know firsthand from our investment in Alloy and others in the KYC space the importance of identity verification and due diligence to mitigate fraud and drive revenue.”
She also wrote that KYB introduces a significantly higher degree of complexity. For applicants, the quote points to a more specific kind of experience. Financial-services experience alone is too broad to establish fit with that thesis. The role itself lists payments, fintech, fraud, underwriting, compliance or risk systems as nice-to-have experience. The quote adds a sharper lens: candidates who have handled KYB, identity verification, fraud or underwriting arrive with more context and less need to explain why the problem matters.
Founder Danny Hakimian said TrueBiz’s technology automates the review of company documents captured at registration and combines that review with searches across data sources. His description identifies the central production work: combining registration-document review with data-source searches to build a more complete picture of a company.
The seed proceeds were earmarked for some hiring, expanding product functionality, marketing and sales, so the backing supported both product and commercial growth. Affiliation can increase visibility, not create a shortcut. The core-engineering posting makes the actual evidentiary bar explicit.
What Actually Gets a Résumé Past TrueBiz’s Screen
TrueBiz’s Senior Software Engineer, Core Team opening asks for professional software engineering experience building, shipping and maintaining production systems. TrueBiz says its product uses LLMs within Python-driven workflows, while the role also covers LLM calls, web data and external APIs. The target is an engineer who put LLM-backed risk analysis inside a dependable, revenue-generating product used by underwriting teams and can show the engineering decisions behind that integration.
The posting describes no automated résumé parser or knockout rule, so its published criteria are the available screen. The posting says:
“We care more about demonstrated ownership and judgment than years of experience, but this is not an entry-level role.”
The posting asks for at least three years of experience, but it leaves room for engineers from smaller companies who handled work beyond their formal titles. Ownership means taking a system through production and remaining accountable for edge cases, operational cleanup and customer-impacting bugs.
TrueBiz said its large language models form part of broader Python-driven workflows that analyze businesses, websites, online presence and risk signals. A résumé should show where model output entered that workflow, what checks surrounded it and how the system handled failures in external data or model calls. A résumé that mentions model training but not production integration would miss the posting’s central requirement.
AI fluency covers the engineering process as well as the product. TrueBiz uses AI-assisted tools for implementation, debugging, test generation, refactoring, documentation and code review. The posting names Claude Code, Cursor and Copilot as examples. The evidence it asks for is a reviewable workflow: generated code that is reviewed, tested and constrained, and kept from making the codebase worse.
Payments, fintech, fraud, underwriting, compliance and risk systems appear in the posting as nice-to-have experience, not as formal requirements. More specifically, TrueBiz says it helps teams understand who a merchant is, what it does and whether its online presence suggests fraud, compliance or business-model risk. A generic fintech label will not carry that context on its own.
Enterprise context adds another requirement. This is not a sales role, but TrueBiz expects engineers to understand how technical decisions affect enterprise users and to collaborate with engineering, sales and customer success. The résumé should connect system behavior to the people making a risk decision without claiming responsibility for the sales relationship itself.
The role also lists API Gateway or production API infrastructure and queue-based or asynchronous systems such as Celery as nice-to-have experience. It also seeks experience operating systems that depend on third-party APIs, scraping, external data vendors or LLM APIs. For a résumé, that means an operating record in reliability, latency, debuggability, monitoring and incident response—not a list of vendors.
The named AWS estate is equally concrete: ECS/Fargate, RDS, ElastiCache and S3. The engineer will own and evolve that infrastructure, configure deployments and permissions, support reliability, scaling, observability and cost management, and build CI/CD pipelines, release-management processes and incident-response practices. The posting also names Datadog, OpenTelemetry, CloudWatch and Grafana as examples of relevant observability tools. Configuration alone does not demonstrate the required end-to-end ownership.
TrueBiz’s YC profile lists a team of six, and the role ranges from architecture decisions to new systems, bugs, edge cases, small optimizations and customer-impacting issues. The posting also expects enough React to modify the interface when needed, clean Git practices and comfort with release workflows.
Before applying, separate eligibility from evidence: rewrite the résumé around production systems you owned and the decisions they supported. Show the reliability, latency, debugging, observability and incident-response work you can defend. For AI-tool work, show how you reviewed, tested and constrained generated code. A résumé that cannot show that chain will read as a list of tools, not proof that you can operate systems of this kind.
Out of Scope: Salary Bands, Remote Policy, and Broad Fintech Hiring Trends
The current board at TrueBiz lists salaried roles with these aggregate figures:
| Measure | Amount |
|---|---|
| Aggregate salary band | $93,000–$233,000 |
| Median | $185,000 |
These figures describe the board’s range, not separate offers or a compensation ranking. An October 21, 2026 analysis from EngRadar found that 9% of direct-apply postings from 2,939 measured tech employers disclosed a salary range. The analysis counted deduplicated company-and-title postings over a 90-day window, included both active and closed roles and used employer-reported ranges rather than estimates. Most employers disclosed no range; only a small minority disclosed one for every role. The result describes the wider market’s disclosure habits. It does not establish what a particular TrueBiz role is worth or what will make an application competitive.
Location fields answer a narrower question. TrueBiz’s board records use labels such as Remote (US) and US / CA / Remote (US; CA). Those labels establish the advertised hiring geography, not the team’s operating policy. The records available for this analysis do not specify office attendance, scheduling rules, core hours or how the company measures performance, so they cannot establish whether TrueBiz follows a formal remote, hybrid or in-office model. Remote status can help determine eligibility. It does not reveal how the team coordinates, what standards the work must meet or whether the applicant has the required production background.
Fintech hiring statistics answer a different question. Finjobsly’s 2026 job data said the market had 3,096 active fintech vacancies and that new postings grew 40% month over month. It also identified applied AI/ML engineering, security and risk engineering, and compliance/AML roles as showing the most consistent hiring demand. Those figures show where postings appear, not the evidence TrueBiz will test in an application. They do not indicate whether an applicant has built underwriting systems, operated machine learning in production or made an API dependable enough for a live risk decision.
These figures answer logistical and market questions—pay, eligibility and hiring heat—but not role-specific fit. For TrueBiz, fit still has to be shown through a record of shipping the risk system, not inferred from adjacent sector experience.
A merchant’s site and wider online footprint enter at one end of TrueBiz’s product; a candidate’s account of owning the path should enter the résumé at the other. In a concentrated applicant pool, the proof that matters is a traceable line from web evidence and model output to a dependable API response and a risk or underwriting decision.
Working in frontier tech? Zero G Talent tracks the openings: see every open TrueBiz role, browse frontier tech jobs, the companies hiring, and the people building the field.