Birch Solutions, Inc. (dba Fern)

Bridging the Gap Between APIs and Developers: The Fern Ecosystem

Fern is redefining how companies deliver developer experiences in an API-first world. Founded in 2022 and acquired by Postman in January 2026, Fern addresses a critical pain point for engineering teams: maintaining high-quality software development kits (SDKs) and API documentation. By treating docs-as-code, Fern allows companies to generate idiomatic, production-ready SDKs across multiple programming languages and publish beautiful, interactive documentation from a single source of truth (like an OpenAPI spec). Their mission is to eliminate the manual toil of keeping docs and client libraries in sync, empowering teams at companies like Square, Auth0, and ElevenLabs to offer top-tier developer experiences. Now operating as a Postman company, Fern's reach is expanding to millions of developers globally, while maintaining its dedicated focus on SDK generation and documentation.

The developer tooling landscape has historically been fragmented, with teams struggling to balance the speed of API development against the necessity of robust, up-to-date documentation. Fern recognized that the traditional approach—where developers manually write and update SDKs and docs—was fundamentally unscalable. This realization birthed a platform that not only automates these processes but elevates the final output to a standard previously achievable only by tech giants with dedicated developer experience (DX) teams. By integrating deeply with existing developer workflows, Fern ensures that whenever an API changes, the corresponding SDKs and documentation are automatically updated, eliminating drift and significantly reducing the risk of integration errors for end-users.

The strategic acquisition by Postman, a titan in the API space, underscores the value of Fern's approach. Postman's vast user base and comprehensive API lifecycle management tools provide the perfect springboard for Fern's specialized capabilities. For developers joining the team now, this represents a unique inflection point. You are stepping into an environment that combines the agility, focus, and innovative spirit of an early-stage startup with the immense distribution power and resources of an established industry leader. The mandate is clear: to build the definitive standard for API consumption, making it easier than ever for developers worldwide to discover, understand, and integrate with any API.

A Culture of Ownership and Craftsmanship

Fern operates with a strong emphasis on engineering excellence and deep ownership. The culture is built around craftsmanship—delivering polished, reliable tools that other developers trust in production environments. As a team that builds developer tools, the internal bar for quality is exceptionally high. Employees are encouraged to take end-to-end responsibility for their features, from conceptualization to deployment. The environment is highly collaborative and fast-paced, typical of a high-growth startup, but it is grounded in a genuine passion for improving the developer ecosystem. Being on-site in New York or San Francisco fosters a tight-knit, in-person culture where whiteboarding and real-time problem-solving are central to the daily workflow.

This dedication to craftsmanship extends beyond the code itself; it permeates every aspect of the company's operations, from product design to customer interactions. The team understands that their users are their peers—other developers who have zero tolerance for poorly designed interfaces or buggy software. Consequently, there is a pervasive culture of constructive feedback and continuous improvement. Code reviews are rigorous, architectural discussions are deep, and every decision is evaluated against its impact on the end-user experience. This environment is intellectually stimulating and demands a high level of technical rigor, making it an ideal proving ground for engineers who are passionate about their craft and eager to push the boundaries of what is possible in developer tooling.

Moreover, the culture at Fern is characterized by a strong sense of autonomy and empowerment. Despite the recent acquisition, the team operates with a significant degree of independence, retaining the entrepreneurial spirit that fueled its initial success. Engineers and product managers are not just order-takers; they are expected to be strategic thinkers who can identify problems, propose innovative solutions, and drive those solutions to completion. This level of ownership fosters a deep sense of pride in the work and creates a highly motivated, deeply engaged team. The in-person work model further amplifies this dynamic, enabling spontaneous brainstorming sessions, rapid iteration, and a strong sense of camaraderie that is often difficult to replicate in fully remote environments.

What You'll Actually Do

Depending on your role, your day-to-day at Fern will revolve around solving complex technical challenges related to code generation, parsing, and user experience. Software Engineers (Frontend, Backend, and Staff) work on the core engine that translates API definitions into robust SDKs for languages like TypeScript, Python, Java, Go, and Rust. You might be optimizing the performance of the generator, expanding support for new language features, or building out the interactive documentation platform that renders API specs beautifully. Deployed Engineers and Technical Account Executives work closely with enterprise customers, helping them integrate Fern into their CI/CD pipelines and ensuring their API consumers have a seamless experience. The work is deeply technical and requires a strong understanding of API design principles and developer workflows.

For those focused on the core generator, the challenges are multifaceted. You will be dealing with the intricacies of abstract syntax trees (ASTs), parsing complex OpenAPI specifications, and ensuring that the generated code adheres to the idiomatic conventions of each target language. This requires not only a deep understanding of multiple programming languages but also a strong grasp of compiler theory and code generation techniques. You will be constantly balancing the need for flexibility—allowing users to customize their SDKs—with the necessity of maintaining a robust, reliable generation process. The impact of your work is immediate and far-reaching; a single optimization in the generator can save countless hours for developers around the world.

On the product and frontend side, the focus is on creating an intuitive, seamless experience for users interacting with the Fern platform. This involves building sophisticated interfaces for managing API definitions, configuring SDK generation, and previewing documentation. You will be working closely with designers to ensure that the platform is not only functional but also aesthetically pleasing and easy to navigate. The goal is to abstract away the complexity of the underlying generation process, providing users with a simple, powerful tool that "just works." For Deployed Engineers and Technical Account Executives, the role is highly consultative. You will be the bridge between Fern and its enterprise customers, helping them navigate complex technical architectures, overcome integration hurdles, and maximize the value they derive from the platform. This requires a unique blend of deep technical expertise and strong communication skills.

Compensation & Benefits

Fern offers competitive compensation packages that reflect the high caliber of talent they seek. Based on publicly available job listings, engineering salaries range from $150K to $300K depending on the level and role. For example, a Deployed Engineer can expect $150K–$250K, while Software Engineers (Frontend/Backend) are typically offered $200K–$250K. Staff Software Engineers and Engineering Managers can command around $300K. Sales roles, such as Technical Account Executives, offer a base of $200K–$350K plus commission. In addition to strong base salaries, Fern provides equity (or equivalent post-acquisition incentives), comprehensive health benefits, and the standard perks associated with a well-funded tech company operating out of premium offices in NYC and SF.

The compensation philosophy at Fern is designed to attract and retain top-tier talent in highly competitive markets. The company recognizes that building world-class developer tools requires engineers who are at the top of their game, and they are willing to pay accordingly. Beyond the base salary, the equity component—or its post-acquisition equivalent—represents a significant opportunity for wealth creation. As Fern continues to scale within the Postman ecosystem, the potential upside is substantial. This aligns the financial interests of the employees with the long-term success of the company, fostering a culture of shared ownership and collective ambition.

In terms of benefits, Fern provides a comprehensive package that supports the health, well-being, and professional development of its employees. This includes top-tier medical, dental, and vision insurance, ensuring that employees and their families have access to high-quality healthcare. The company also offers generous paid time off, recognizing the importance of rest and recharge in maintaining a high-performing team. Furthermore, operating out of premium offices in New York City and San Francisco means that employees have access to state-of-the-art facilities, fully stocked kitchens, and a vibrant, inspiring work environment. The company also invests heavily in professional development, providing opportunities for continuous learning, conference attendance, and mentorship, ensuring that employees are constantly growing and advancing in their careers.

The Interview Process

The interview process at Fern is rigorous and designed to assess both technical prowess and cultural fit. It typically begins with a standard recruiter screen followed by a technical phone interview focusing on algorithms or system design relevant to developer tools. However, the defining feature of Fern's interview process is the paid, in-person "work trial." Instead of relying solely on abstract whiteboard interviews, Fern invites final-round candidates to join the team for a few days to work on a real, scoped project (e.g., building a new product feature like a Product Switcher). This trial allows candidates to experience the company's culture, collaborate directly with future teammates, and demonstrate their practical skills in a real-world setting. Both the candidate and the company use this time to ensure a mutual fit before a final offer is made.

The initial stages of the interview process are designed to establish a baseline of technical competence. The recruiter screen focuses on understanding the candidate's background, career aspirations, and alignment with Fern's mission. The subsequent technical phone interview delves deeper into the candidate's problem-solving abilities, focusing on the specific challenges associated with building developer tools. Candidates can expect questions related to data structures, algorithms, system architecture, and API design. The goal here is not just to see if the candidate can arrive at the correct answer, but to understand their thought process, their ability to communicate complex technical concepts, and their approach to problem-solving under pressure.

The paid, in-person work trial is where the Fern interview process truly sets itself apart. This immersive experience is designed to simulate what it's actually like to work at the company. Candidates are given a real, meaningful project to complete over the course of a few days, working alongside the engineers they would potentially be joining. This provides a unique opportunity for candidates to showcase their practical skills, their ability to learn quickly, and their capacity for collaboration. It also gives them a firsthand look at the company culture, the daily workflows, and the team dynamics. For the company, the work trial provides invaluable insights into the candidate's work ethic, their communication style, and their ability to deliver high-quality results in a real-world setting. This mutual evaluation process ensures that both parties are fully confident in their decision before a final offer is extended.

Why Join / Why Not

Why Join:

If you are passionate about developer tools and want your work to directly impact how thousands of other engineers build software, Fern is an exceptional place to be. The acquisition by Postman provides the stability and resources of an industry giant while allowing the Fern team to maintain its startup agility and focus. You will work alongside highly talented peers on complex, intellectually stimulating problems related to compilers, code generation, and API infrastructure. The paid work trial also ensures that you know exactly what you are signing up for before joining. The opportunity to shape the future of API consumption, combined with a culture that deeply values craftsmanship and ownership, makes Fern a compelling destination for ambitious engineers.

Furthermore, the integration with Postman opens up unprecedented avenues for scale and impact. You will be building tools that have the potential to reach millions of developers globally, setting the standard for how APIs are documented and consumed. The technical challenges are significant, offering a continuous learning curve and the opportunity to deepen your expertise in areas like language parsing, code generation, and distributed systems. The highly collaborative, in-person culture fosters rapid iteration and strong team cohesion, ensuring that you are constantly supported and challenged by your peers. If you thrive in an environment that demands excellence and offers the opportunity to make a massive impact on the developer ecosystem, Fern is an ideal fit.

Why Not:

Fern is an in-person, on-site company with offices in New York and San Francisco; if you are looking for a fully remote role, this is not the right fit. The culture is intense and focused, which is great for career acceleration but may not suit those seeking a highly relaxed environment. Additionally, as part of a recent acquisition, the company will inevitably undergo integration processes with Postman, which can sometimes introduce organizational shifts or changes in long-term strategy. The emphasis on in-person collaboration means that a significant portion of your week will be spent in the office, which may not align with everyone's lifestyle preferences or personal commitments.

Moreover, the high bar for quality and the expectation of deep ownership can be demanding. The work is complex, and the pressure to deliver flawless, production-ready tools is constant. If you prefer a more structured, predictable environment where tasks are clearly defined and the pace is more relaxed, the dynamic, fast-paced nature of Fern might prove overwhelming. The integration with Postman, while offering significant advantages, also introduces a degree of uncertainty. As the two companies align their strategies and operations, there may be periods of transition and adjustment. For individuals who are uncomfortable with ambiguity or who prefer the stability of a fully independent startup, this transitional phase might present challenges.