software development
Auto Added by WPeMatico
Make accessibility part of your startup’s products and culture from day one
The world of accessibility has experienced a tipping point thanks to the pandemic, which drove people of all abilities to do more tasks and shopping online.
For the last year, the digital world was the only place brands could connect with their customers. A Forrester survey found that 8 in 10 companies have taken their first steps toward working on digital accessibility.
What’s driving this change besides the increased digital interactions? Fortune 500 companies are finally starting to realize that people with disabilities make up 1 billion of the world’s market. That population and their families control more than $13 trillion in disposable income, according to Return on Disability’s “The Global Economics of Disability.”
However, only 36% of companies in Forrester’s survey are completely committed to creating accessible digital experiences.
Although digital accessibility has been around for decades, companies have not caught on to its benefits until recently. In its latest survey, the WebAIM Million analysis of 1 million home pages found accessibility errors on 97.4% of the websites evaluated.
What does this mean for you? Why should you care about this? Because this is an opportunity for your company to get ahead of the competition and reap the rewards of being an early adopter.
The benefits of digital accessibility
Companies are now realizing the advantages of creating accessible products and properties that go beyond doing the right thing. For one, people are living longer. The World Health Organization says people aged 60 and older outnumber children under 5. Moreover, the world’s population of those who are 60 and older is expected to reach 2 billion by 2050, up from 900 million in 2015.
W3C Web Accessibility Initiative provides an overview on Web Accessibility for Older Users. Here’s what it reveals.
- Hearing loss affects 47% of people aged 61 to 80.
- Vision decline affects 16% of people aged 65 to 74.
- Mild cognitive impairment affects 20% of people over 70.
- Arthritis affects more than 50% of people over 65.
In short, developing accessible digital products helps you reach a much larger audience, which will include you, your co-workers and your family. Everyone is going to become situationally, temporarily or episodically impaired at some point in their lives. Everyone enters a noisy or dark environment that can make it harder to see or hear. An injury or an illness can cause someone to use the internet differently on a temporary basis. People with arthritis, migraines and vertigo experience episodes of pain and discomfort that affect their ability to interact with digital devices, apps and tools.
Additionally, no one has ever advocated against making products and websites accessible to more people. Despite this, the relative universal appeal of accessibility as a principle does not mean that it will be as easy as explaining the need and getting people on board to make major organizational changes. A lot of work remains in raising awareness and educating people about why we need to make these changes and how to go about it.
You have the why. Now here are five things to help you with how to make changes in your company to integrate accessibility as a core part of your business.
1. Tap the right people to create accessible experiences
According to the second annual State of Accessibility Report, only 40% of the Alexa Top 100 websites are fully accessible, proving the needs of people with disabilities are, more often than not, being overlooked when creating web experiences.
To design for people with disabilities, it’s important to have an understanding of how they use your products or web properties. You’ll also want to know what tools will help them achieve their desired results. This starts with having the right people on board.
Hiring accessibility experts to advise your development team will proactively identify potential issues and ensure you design accessibly from the start, as well as create better products. Better yet, hiring people with disabilities brings a deeper level of understanding to your work.
2. Hire designers passionate about accessibility
Having accessibility experts on your team to provide advice and guidance is a great start. However, if the rest of your team is not passionate about accessibility, that can turn into a potential roadblock. When interviewing new designers, ask about accessibility. It’ll gauge a candidate’s knowledge and passion in the area. At the same time, you set an expectation that accessibility is a priority at your organization.
Being proactive about your hires and making sure they will contribute to a culture of accessibility and inclusion will save you major headaches. Accessibility starts in the design and user experience (UX) phase. If your team doesn’t deliver there, then you will have to fix their mistakes later, essentially delaying the project and costing your organization. It costs more to fix things than to build them accessibly in the first place.
3. Remember that accessibility is for everyone
People deciding whether to invest in accessibility often ask themselves how many people are going to use the feature. The reasoning behind the question is understandable from a business perspective; accessibility can be an expense, and it’s reasonable to want to spend money responsibly.
However, the question is rooted in one of the biggest misconceptions in the field. The myth is that accessibility only benefits people who are blind or deaf. This belief is frustrating because it greatly underestimates the number of people with disabilities and minimizes their place in society. Furthermore, it fails to acknowledge that people who may not have a disability still benefit greatly from accessibility features.
Disability is a spectrum that all of us will find ourselves on sooner or later. Maybe an injury temporarily limits our mobility that requires us to perform basic tasks like banking and shopping exclusively online. Or maybe our vision and hearing change as we age, which affects our ability to interact online.
When we understand that accessibility is about designing in a way that includes as many people as possible, we can reframe the conversation around whether it’s worth investing in. This approach sends a clear message: No business can afford to ignore a fast-growing population.
Think about it this way: If you have a choice of taking an elevator or the stairs, which would you take? Most pick the elevator. Those ramps on street corners called curb cuts? They were initially designed for allowing wheelchairs to cross the street.
Yet, many use these ramps, including parents pushing strollers, travelers pulling luggage, skateboarders rolling and workers moving heavy loads on dollies. A feature initially designed for accessibility benefits far more people than the original target audience. That’s the magic of the curb-cut effect.
4. Hire agencies that build accessibly by default
Whether you have a small team or are expanding an in-house accessibility practice, working with an agency can be an effective way to embrace and adopt accessible practices. The secret to a successful partnership is choosing an agency that will help your team grow into its accessibility practice.
The key to finding the right agency is selecting one that builds accessibly by default. When you know you are working with an agency that shares your organization’s values, you have a trusted partner in your mission of improving accessibility. It also removes any guesswork or revisions down the line. This is a huge win, as many designers overlook details that can make or break an experience for a user with a disability.
Working with an agency focused on providing accessible experiences narrows the likelihood of errors going unnoticed and unremedied, giving you confidence that you are providing an excellent experience to your entire audience.
5. Integrate accessibility into your supply chain
On any given day, enterprises and large organizations often work with dozens of stakeholders. From vendors and agencies to freelancers and internal employees, the nature of business today is far-reaching and collaborative. While this is valuable for exchanging ideas, accessibility can get lost in the mix with so many different people involved.
To prevent this from happening, it’s important to align these moving pieces of a business into a supply chain that is focused on accessibility at every stage of the business. When everyone is completely bought in, it cuts the risk of a component being inaccessible and causing issues for you in the future.
The startup advantage
A major challenge that comes up repeatedly is the struggle to change the status quo. Once an organization implements and ingrains inaccessible processes and products into its culture, it is hard to make meaningful change. Even if everyone is willing to commit to the change, the fact is, rewriting the way you do business is never easy.
Startups have an advantage here: They do not bear years of inaccessible baggage. It’s not written into the code of their products. It’s not woven into the business culture. In many ways, a startup is a clean slate, and they need to learn from the trials of their more established peers.
Startup founders have the opportunity to build an accessible organization from the ground up. They can create an accessible-first culture that will not need rewriting 10, 20 or 30 years from now by hiring a diverse workforce with a passion for accessibility, writing accessible code for products and web properties, choosing to work with only third parties who embrace accessibility and advocating for the rights of people with disabilities.
Many of these considerations here have a common denominator: culture. While most people in the technology industry will agree that accessibility is an important and worthy cause to champion, it has a huge awareness problem.
Accessibility needs to be everywhere in software development, from requirements and beyond to include marketing, sales and other non-tech teams. It cannot be a niche concern left to a siloed team to handle. If we, as an industry and as a society, recognize that accessibility is everyone’s job, we will create a culture that prioritizes it without question.
By creating this culture, we will no longer be asking, “Do we have to make this accessible?” Instead, we’ll ask, “How do we make this accessible?” It’s a major mindset shift that will make a tangible difference in the lives of 1 billion people living with a disability and those who eventually will have a disability or temporary, situational or episodic impairments affecting their ability to use online and digital products.
Advocating for accessibility may feel like an uphill battle at times, but it isn’t rocket science. The biggest need is education and awareness.
When you understand the people you build accessible products for and the reasons they need those products, it becomes easier to secure buy-in from people in all parts of your organization. Creating this culture is the first step in a long quest toward accessibility. And the best part is, it gets easier from here.
Powered by WPeMatico
Blameless raises $30M to guide companies through their software lifecycle
Site reliability engineering platform Blameless announced Tuesday it raised $30 million in a Series B funding round, led by Third Point Ventures with participation from Accel, Decibel and Lightspeed Venture Partners, to bring total funding to over $50 million.
Site reliability engineering (SRE) is an extension of DevOps designed for more complex environments.
Blameless, based in San Mateo, California, emerged from stealth in 2019 after raising both a seed and Series A round, totaling $20 million. Since then, it has turned its business into a blossoming software platform.
Blameless’ platform provides the context, guardrails and automated workflows so engineering teams are unified in the way they communicate and interact, especially to resolve issues quicker as they build their software systems.
It originally worked with tech-forward teams at large companies, like Home Depot, that were “dipping [their toes] into the space and now [want] to double down,” co-founder and CEO Lyon Wong told TechCrunch.
The company still works with those tech-forward teams, but in the past two years, more companies sought out resident SRE architect Kurt Anderson to advise them, causing Blameless to change up its business approach, Wong said.
Other companies are also seeing a trend of customers asking for support — for example, in March, Google Cloud unveiled its Mission Critical Services support option for SRE to serve in a similar role as a consultant as companies move toward readiness with their systems. And in February, Nobl9 raised a $21 million Series B to provide enterprises with the tools they need to build service-level-objective-centric operations, which is part of a company’s SRE efforts.
Blameless now has interest from more mainstream companies in the areas of enterprise, logistics and healthcare. These companies aren’t necessarily focused on technology, but see a need for SRE.
“Companies recognize the shortfall in reliability, and then the question they come to us with is how do they get from where they are to where they want to be,” Anderson said. “Often companies that don’t have a process respond with ‘all hands on deck’ all the time, but instead need to shift to the right people responding.”
Lyon plans to use the new funding to fill key leadership roles, the company’s go-to-market strategy and product development to enable the company to go after larger enterprises.
Blameless doubled its revenue in the last year and will expand to service all customer segments, adding small and emerging businesses to its roster of midmarket and large companies. The company also expects to double headcount in the next three quarters.
As part of the funding announcement, Third Point Ventures partner Dan Moskowitz will join Blameless’ board of directors with Wong, Accel partner Vas Natarajan and Lightspeed partner Ravi Mhatre.
“Freeing up engineering to focus on shipping code is exactly what Blameless achieves,” said Moskowitz in a written statement. “The Blameless market opportunity is big as we see teams struggle and resort to creating homegrown playbooks and point solutions that are incomplete and costly.”
Powered by WPeMatico
Build a digital ops toolbox to streamline business processes with hyperautomation
Reliance on a single technology as a lifeline is a futile battle now. When simple automation no longer does the trick, delivering end-to-end automation needs a combination of complementary technologies that can give a facelift to business processes: the digital operations toolbox.
According to a McKinsey survey, enterprises that have likely been successful with digital transformation efforts adopted sophisticated technologies such as artificial intelligence, Internet of Things or machine learning. Enterprises can achieve hyperautomation with the digital ops toolbox, the hub for your digital operations.
The hyperautomation market is burgeoning: Analysts predict that by 2025, it will reach around $860 billion.
The toolbox is a synchronous medley of intelligent business process management (iBPM), robotic process automation (RPA), process mining, low code, artificial intelligence (AI), machine learning (ML) and a rules engine. The technologies can be optimally combined to achieve the organization’s key performance indicator (KPI) through hyperautomation.
The hyperautomation market is burgeoning: Analysts predict that by 2025, it will reach around $860 billion. Let’s see why.
The purpose of a digital ops toolbox
The toolbox, the treasure chest of technologies it is, helps with three crucial aspects: process automation, orchestration and intelligence.
Process automation: A hyperautomation mindset introduces the world of “automating anything that can be,” whether that’s a process or a task. If something can be handled by bots or other technologies, it should be.
Orchestration: Hyperautomation, per se, adds an orchestration layer to simple automation. Technologies like intelligent business process management orchestrate the entire process.
Intelligence: Machines can automate repetitive tasks, but they lack the decision-making capabilities of humans. And, to achieve a perfect harmony where machines are made to “think and act,” or attain cognitive skills, we need AI. Combining AI, ML and natural language processing algorithms with analytics propels simple automation to become more cognitive. Instead of just following if-then rules, the technologies help gather insights from the data. The decision-making capabilities enable bots to make decisions.
Simple automation versus hyperautomation
Here’s a story of evolving from simple automation to hyperautomation with an example: an order-to-cash process.
Powered by WPeMatico
A startup’s guide to software delivery
One of the biggest factors in the success of a startup is its ability to quickly and confidently deliver software. As more consumers interact with businesses through a digital interface and more products embrace those interfaces as the opportunity to differentiate, speed and agility are paramount. It’s what makes or breaks a company.
As your startup grows, it’s important that your software delivery strategy evolves with you. Your software processes and tool choices will naturally change as you scale, but optimizing too early or letting them grow without a clear vision of where you’re going can cost you precious time and agility. I’ve seen how the right choices can pay huge dividends — and how the wrong choices can lead to time-consuming problems that could have been avoided.
The key to success is consistency. Create a standard, then apply it to all delivery pipelines.
As we know from Conway’s law, your software architecture and your organizational structure are deeply linked. It turns out that how you deliver is greatly impacted by both organizational structure and architecture. This is true at every stage of a startup but even more important in relation to how startups go through rapid growth. Software delivery on a team of two people is vastly different from software delivery on a team of 200.
Decisions you make at key growth inflection points can set you up for either turbocharged growth or mounting roadblocks.
Founding stage: Keep it simple
The founding phase is the exciting exploratory phase. You have an idea and a few engineers.
The key during this phase is to keep the architecture and tooling as simple and flexible as possible. Building a company is all about execution, so get the tools you need to execute consistently and put the rest on hold.
One place you can invest without overdoing it is in continuous integration and continuous deployment (CI/CD). CI/CD enables developer teams to get feedback fast, learn from it, and deliver code changes quickly and reliably. While you’re trying to find product-market fit, learning fast is the name of the game. When systems start to become more complex, you’ll have the practices and tooling in place to handle them easily. By not having the ability to learn and adapt quickly, you give your competitors a massive edge.
One other place where early, simple investments really pay off is in operability. You want the simplest possible codebase: probably a monolith and a basic deploy. But if you don’t have some basic tools for observability, each user issue is going to take orders of magnitude longer than necessary to track down. That’s time you could be using to advance your feature set.
Your implementation here may be some placeholders with simple approaches. But those placeholders will force you to design effectively so that you can enhance later without massive rewrites.
Very early stage: Maintain efficiency and productivity
At 10 to 20 engineers, you likely don’t have a person dedicated to developer efficiency or tooling. Company priorities are still shifting, and although it may feel cumbersome for your team to be working as a single team, keep at it. Look for more fluid ways of creating independent workstreams without concrete team definitions or deep specialization. Your team will benefit from having everyone responsible for creating tools, processes and code rather than relying on a single person. In the long run, it will help foster efficiency and productivity.
Powered by WPeMatico
The truth about SDK integrations and their impact on developers
The digital media industry often talks about how much influence, dominance and power entities like Google and Facebook have. Generally, the focus is on the vast troves of data and audience reach these companies tout. However, there’s more beneath the surface that strengthens the grip these companies have on both app developers and publishers alike.
In reality, software development kit (SDK) integrations are a critical component of why these monolith companies have such a prominent presence. For reference, an SDK is a set of software development tools, libraries, code samples, processes and guides that help developers create or enhance the apps they’re building.
Through a digital marketing lens, SDKs provide in-app analytics, insights on campaign testing, attribution information, location details, monetization capabilities and more.
Through a digital marketing lens, SDKs provide in-app analytics, insights on campaign testing, attribution information, location details, monetization capabilities and more. In the case of companies like Google and Facebook, their ability to provide these insights dovetails with their data and reach.
While that does deliver useful capabilities to developers and publishers alike, it also perpetuates the factors contributing to their perceived monopolistic status — and the detriments a lack of competition fosters.
Almost all (90%) ad-monetized Android apps have Google’s Admob SDK integrated, data from Statista showed. Additionally, the Facebook Audience Network SDK is present in 19% of all global Android apps utilizing mobile ads. It’s worth noting that the large majority of alternative “leading” advertising SDKs outside these two players are used less than 13% of the time in Android apps.
As the app ecosystem rapidly expands beyond the borders of mobile, app developers and publishers would benefit immensely from identifying economical and secure ways of adopting more SDKs.
The state of SDK adoption
While there are many SDKs available in the market today, a few key factors contribute to Google and Facebook’s overall dominance. The most basic is around the respective organizations’ reach and industry notoriety. However, a larger component here is the lack of resources and time app developers have.
Powered by WPeMatico
Cycode raises $20M to secure DevOps pipelines
Israeli security startup Cycode, which specializes in helping enterprises secure their DevOps pipelines and prevent code tampering, today announced that it has raised a $20 million Series A funding round led by Insight Partners. Seed investor YL Ventures also participated in this round, which brings the total funding in the company to $24.6 million.
Cycode’s focus was squarely on securing source code in its early days, but thanks to the advent of infrastructure as code (IaC), policies as code and similar processes, it has expanded its scope. In this context, it’s worth noting that Cycode’s tools are language and use case agnostic. To its tools, code is code.
“This ‘everything as code’ notion creates an opportunity because the code repositories, they become a single source of truth of what the operation should look like and how everything should function, Cycode CTO and co-founder Ronen Slavin told me. “So if we look at that and we understand it — the next phase is to verify this is indeed what’s happening, and then whenever something deviates from it, it’s probably something that you should look at and investigate.”
Cycode Dashboard. Image Credits: Cycode
The company’s service already provides the tools for managing code governance, leak detection, secret detection and access management. Recently it added its features for securing code that defines a business’ infrastructure; looking ahead, the team plans to add features like drift detection, integrity monitoring and alert prioritization.
“Cycode is here to protect the entire CI/CD pipeline — the development infrastructure — from end to end, from code to cloud,” Cycode CEO and co-founder Lior Levy told me.
“If we look at the landscape today, we can say that existing solutions in the market are kind of siloed, just like the DevOps stages used to be,” Levy explained. “They don’t really see the bigger picture, they don’t look at the pipeline from a holistic perspective. Essentially, this is causing them to generate thousands of alerts, which amplifies the problem even further, because not only don’t you get a holistic view, but also the noise level that comes from those thousands of alerts causes a lot of valuable time to get wasted on chasing down some irrelevant issues.”
What Cycode wants to do then is to break down these silos and integrate the relevant data from across a company’s CI/CD infrastructure, starting with the source code itself, which ideally allows the company to anticipate issues early on in the software life cycle. To do so, Cycode can pull in data from services like GitHub, GitLab, Bitbucket and Jenkins (among others) and scan it for security issues. Later this year, the company plans to integrate data from third-party security tools like Snyk and Checkmarx as well.
“The problem of protecting CI/CD tools like GitHub, Jenkins and AWS is a gap for virtually every enterprise,” said Jon Rosenbaum, principal at Insight Partners, who will join Cycode’s board of directors. “Cycode secures CI/CD pipelines in an elegant, developer-centric manner. This positions the company to be a leader within the new breed of application security companies — those that are rapidly expanding the market with solutions which secure every release without sacrificing velocity.”
The company plans to use the new funding to accelerate its R&D efforts, and expand its sales and marketing teams. Levy and Slavin expect that the company will grow to about 65 employees this year, spread between the development team in Israel and its sales and marketing operations in the U.S.
Powered by WPeMatico
Opsera raises $15M for its continuous DevOps orchestration platform
Opsera, a startup that’s building an orchestration platform for DevOps teams, today announced that it has raised a $15 million Series A funding round led by Felicis Ventures. New investor HMG Ventures, as well as existing investors Clear Ventures, Trinity Partners and Firebolt Ventures also participated in this round, which brings the company’s total funding to $19.3 million.
Founded in January 2020, Opsera lets developers provision their CI/CD tools through a single framework. Using this framework, they can then build and manage their pipelines for a variety of use cases, including their software delivery lifecycle, infrastructure as code and their SaaS application releases. With this, Opsera essentially aims to help teams set up and operate their various DevOps tools.
The company’s two co-founders, Chandra Ranganathan and Kumar Chivukula, originally met while working at Symantec a few years ago. Ranganathan then spent the last three years at Uber, where he ran that company’s global infrastructure. Meanwhile, Chivukula ran Symantec’s hybrid cloud services.
Image Credits: Opsera
“As part of the transformation [at Symantec], we delivered over 50+ acquisitions over time. That had led to the use of many cloud platforms, many data centers,” Ranganathan explained. “Ultimately we had to consolidate them into a single enterprise cloud. That journey is what led us to the pain points of what led to Opsera. There were many engineering teams. They all had diverse tools and stacks that were all needed for their own use cases.”
The challenge then was to still give developers the flexibility to choose the right tools for their use cases, while also providing a mechanism for automation, visibility and governance — and that’s ultimately the problem Opsera now aims to solve.
Image Credits: Opsera
“In the DevOps landscape, […] there is a plethora of tools, and a lot of people are writing the glue code,” Opsera co-founder Chivukula noted. “But then they’re not they don’t have visibility. At Opsera, our mission and goal is to bring order to the chaos. And the way we want to do this is by giving choice and flexibility to the users and provide no-code automation using a unified framework.”
Wesley Chan, a managing director for Felicis Ventures who will join the Opsera board, also noted that he believes that one of the next big areas for growth in DevOps is how orchestration and release management is handled.
“We spoke to a lot of startups who are all using black-box tools because they’ve built their engineering organization and their DevOps from scratch,” Chan said. “That’s fine, if you’re starting from scratch and you just hired a bunch of people outside of Google and they’re all very sophisticated. But then when you talk to some of the larger companies. […] You just have all these different teams and tools — and it gets unwieldy and complex.”
Unlike some other tools, Chan argues, Opsera allows its users the flexibility to interface with this wide variety of existing internal systems and tools for managing the software lifecycle and releases.
“This is why we got so interested in investing, because we just heard from all the folks that this is the right tool. There’s no way we’re throwing out a bunch of our internal stuff. This would just wreak havoc on our engineering team,” Chan explained. He believes that building with this wide existing ecosystem in mind — and integrating with it without forcing users onto a completely new platform — and its ability to reduce friction for these teams, is what will ultimately make Opsera successful.
Opsera plans to use the new funding to grow its engineering team and accelerate its go-to-market efforts.
Powered by WPeMatico
Time-strapped IT teams can use low-code software to drive quick growth
Many emerging and mature organizations survive or die based on their ability to scale. Scale quicker. Scale cheaper. Scale right.
Typically the IT team bears that burden — on top of countless other demands. IT teams move mountains for their organizations while scaling the tech platform as fast as possible, putting out the latest infrastructure fire and responding to countless day-to-day requests.
The most helpful gift any chief information officer or chief technology officer can give their IT teams is more time. Many people think that means adding another team member. Maybe it does in some cases (if you can find a developer in this tough job market), but giving my team Boomi’s low-code integration platform was one of the best strategic moves for HealthBridge.
The best time to use low-code is when you need to add something to your organization that isn’t unique or doesn’t drive significant business value.
As the least skilled coder on the team, low-code let me develop and deliver four customer-centric self-service portals a year ahead of schedule while my team focused on building and scaling our revenue-driving, custom platform by hand-writing code.
Low-code is quickly becoming commonplace and a popular topic among IT decision-makers. Over the last few years, the market has exploded. Gartner expects it to total $13.8 billion in 2021. That means low-code technology, which we’ve been hearing about for years, is ready for widespread adoption. Today, low-code enables you to streamline (and scale) everything from integration to artificial intelligence.
It’s a secret only some organizations are clued in on, but it’s a great way to scale fast, save on resources and give your team more time. Here’s how.
When to use low-code and when to write code
The best time to use low-code is when you need to add something to your organization that isn’t unique or doesn’t drive significant business value.
For instance, a customer portal is not unique; don’t waste time hand-coding it.
While it’s certainly an extremely helpful feature for our customers, it’s unlikely to drive significant shareholder or investor value. However, it’s key for scaling. Using low-code for a must-have but undifferentiated feature will allow your team to work on more important projects while scaling.
When we started working on the timeline for a customer portal project at HealthBridge, we estimated it would take several sprints per portal to develop, but more pressing development work kept pushing it down the list in our backlog. Waiting a year for a basic feature didn’t seem reasonable to me, so we looked for a workaround.
Powered by WPeMatico
Argentina’s Digital House raises over $50M to help solve LatAm’s tech talent shortage
Digital House, a Buenos Aires-based edtech focused on developing tech talent through immersive remote courses, announced today it has raised more than $50 million in new funding.
Notably, two of the main investors are not venture capital firms but instead are two large tech companies: Latin American e-commerce giant Mercado Libre and San Francisco-based software developer Globant. Riverwood Capital, a Menlo Park-based private equity firm, and existing backer early-stage Latin American venture firm Kaszek also participated in the financing.
The raise brings Digital House’s total funding raised to more than $80 million since its 2016 inception. The Rise Fund led a $20 million Series B for Digital House in December 2017, marking the San Francisco-based firm’s investment in Latin America.
Nelson Duboscq, CEO and co-founder of Digital House, said that accelerating demand for tech talent in Latin America has fueled demand for the startup’s online courses. Since it first launched its classes in March 2016, the company has seen a 118% CAGR in revenues and a 145% CAGR in students. The 350-person company expects “and is on track” to be profitable this year, according to Duboscq.
Digital House CEO and co-founder Nelson Duboscq. Image Credits: Digital House
In 2020, 28,000 students across Latin America used its platform. The company projects that more than 43,000 will take courses via its platform in 2021. Fifty percent of its business comes out of Brazil, 30% from Argentina and the remaining 20% in the rest of Latin America.
Specifically, Digital House offers courses aimed at teaching “the most in-demand digital skills” to people who either want to work in the digital industry or for companies that need to train their employees on digital skills. Emphasizing practice, Digital House offers courses — that range from six months to two years — teaching skills such as web and mobile development, data analytics, user experience design, digital marketing and product development.
The courses are fully accessible online and combine live online classes led by in-house professors, with content delivered through Digital House’s platform via videos, quizzes and exercises “that can be consumed at any time.”
Digital House also links its graduates to company jobs, claiming an employability rate of over 95%.
Looking ahead, Digital House says it will use its new capital toward continuing to evolve its digital training platforms, as well as launching a two-year tech training program — dubbed the the “Certified Tech Developer” initiative — jointly designed with Mercado Libre and Globant. The program aims to train thousands of students through full-time two-year courses and connect them with tech companies globally.
Specifically, the company says it will also continue to expand its portfolio of careers beyond software development and include specialization in e-commerce, digital marketing, data science and cybersecurity. Digital House also plans to expand its partnerships with technology employers and companies in Brazil and the rest of Latin America. It also is planning some “strategic M&A,” according to Duboscq.
Francisco Alvarez-Demalde, co-founder & co-managing partner of Riverwood Capital, noted that his firm has observed an accelerating digitization of the economy across all sectors in Latin America, which naturally creates demand for tech-savvy talent. (Riverwood has an office in São Paulo).
For example, in addition to web developers, there’s been increased demand for data scientists, digital marketing and cybersecurity specialists.
“In Brazil alone, over 70,000 new IT professionals are needed each year and only about 45,000 are trained annually,” Alvarez-Demalde said. “As a result of such a talent crunch, salaries for IT professionals in the region increased 20% to 30% last year. In this context, Digital House has a large opportunity ahead of them and is positioned strategically as the gatekeeper of new digital talent in Latin America, preparing workers for the jobs of the future.”
André Chaves, senior VP of Strategy at Mercado Libre, said the company saw in Digital House a track record of “understanding closely” what Mercado Libre and other tech companies need.
“They move as fast as we do and adapt quickly to what the job market needs,” he said. “A very important asset for us is their presence and understanding of Latin America, its risks and entrepreneurial environment. Global players have succeeded for many years in our region. But things are shifting gradually, and local knowledge of risks and opportunities can make a great difference.”
Powered by WPeMatico
Nobl9 raises $21M Series B for its SLO management platform
SLAs, SLOs, SLIs. If there’s one thing everybody in the business of managing software development loves, it’s acronyms. And while everyone probably knows what a Service Level Agreement (SLA) is, Service Level Objectives (SLOs) and Service Level Indicators (SLIs) may not be quite as well known. The idea, though, is straightforward, with SLOs being the overall goals a team must hit to meet the promises of its SLA agreements, and SLIs being the actual measurements that back up those other two numbers. With the advent of DevOps, these ideas, which are typically part of a company’s overall Site Reliability Engineering (SRE) efforts, are becoming more mainstream, but putting them into practice isn’t always straightforward.
Nobl9 aims to provide enterprises with the tools they need to build SLO-centric operations and the right feedback loops inside an organization to help it hit its SLOs without making too many trade-offs between the cost of engineering, feature development and reliability.
The company today announced that it has raised a $21 million Series B round led by its Series A investors Battery Ventures and CRV. In addition, Series A investors Bonfire Ventures and Resolute Ventures also participated, together with new investors Harmony Partners and Sorenson Ventures.
Before starting Nobl9, co-founders Marcin Kurc (CEO) and Brian Singer (CPO) spent time together at Orbitera, where Singer was the co-founder and COO and Kurc the CEO, and then at Google Cloud, after it acquired Orbitera in 2016. In the process, the team got to work with and appreciate Google’s site reliability engineering frameworks.
As they started looking into what to do next, that experience led them to look into productizing these ideas. “We came to this conclusion that if you’re going into Kubernetes, into service-based applications and modern architectures, there’s really no better way to run that than SRE,” Kurc told me. “And when we started looking at this, naturally SRE is a complete framework, there are processes. We started looking at elements of SRE and we agreed that SLO — service level objectives — is really the foundational part. You can’t do SRE without SLOs.”
As Singer noted, in order to adopt SLOs, businesses have to know how to turn the data they have about the reliability of their services, which could be measured in uptime or latency, for example, into the right objectives. That’s complicated by the fact that this data could live in a variety of databases and logs, but the real question is how to define the right SLOs for any given organization based on this data.
“When you go into the conversation with an organization about what their goals are with respect to reliability and how they start to think about understanding if there’s risks to that, they very quickly get bogged down in how are we going to get this data or that data and instrument this or instrument that,” Singer said. “What we’ve done is we’ve built a platform that essentially takes that as the problem that we’re solving. So no matter where the data lives and in what format it lives, we want to be able to reduce it to very simply an error budget and an objective that can be tracked and measured and reported on.”
The company’s platform launched into general availability last week, after a beta that started last year. Early customers include Brex and Adobe.
As Kurc told me, the team actually thinks of this new funding round as a Series A round, but because its $7.5 million Series A was pretty sizable, they decided to call it a Series A instead of a seed round. “It’s hard to define it. If you define it based on a revenue milestone, we’re pre-revenue, we just launched the GA product,” Singer told me. “But I think just in terms of the maturity of the product and the company, I would put us at the [Series] B.”
The team told me that it closed the round at the end of last November, and while it considered pitching new VCs, its existing investors were already interested in putting more money into the company and since its previous round had been oversubscribed, they decided to add to this new round some of the investors that didn’t make the cut for the Series A.
The company plans to use the new funding to advance its roadmap and expand its team, especially across sales, marketing and customer success.
Powered by WPeMatico