![]() Whether it’s making product, building out processes, writing documentation, or growing a team, we all need to have a bias towards doing things. MAKER/BUILDER MINDSET: ClickTime employees need to be builders. ![]() Finally, the onsite interview consists of a technical exercise with our technical team, plus a couple short conversations with your potential coworkers and our CEO. If we move forward, we'll schedule a technical phone interview. Our interview process begins with a quick phone call to learn more about your background and interests, share more about the role, and help decide if ClickTime is a mutual fit. We're a tight knit (and profitable) group of about 35 people with headquarters in San Francisco and remote employees in Austin, Denver, and beyond. Our mission is to help companies manage projects, reduce labor costs, and drive performance. If you have any questions about our forms, their fields, and the data model behind our directories, we recommend that you read ProgrammableWeb's New API Directory Data Model Explained.ClickTime delivers incredibly friendly time and expense management applications to businesses around the world. ![]() So, any related assets need to pre-exist in our directories in order for you to select them.Īfter adding a library to ProgrammableWeb’s directory, be sure to use our forms to add any related APIs, frameworks, SDKs, pointers to sample source code, and examples of applications that are some how involved with the library or whatever depends on it. The reason for this is that the form below asks you to pick any related frameworks and APIs. For example, we’ve observed a lot of locally installable server applications that come with no APIs and for many of those server apps, third party developers will often build libraries that, once installed, result in the addition of RESTful APIs to those server apps.īefore submitting a library to our directory, please be sure first add the frameworks it depends on to the framework directory and any APIs that it may provision to our API directory. ![]() While we know that not everyone shares this view, ProgrammableWeb reserves the word “library” for bits of software that result in the provisioning (aka “standing-up”) of an API (if the bit of software you have is for consuming APIs, we reserve those for our SDK directory). The purpose of this form is to make a record of libraries that play a role in the API ecosystem. If you still have questions, feel free to email us at ProgrammableWeb directories are about cataloging APIs, SDKs, libraries, frameworks, Web apps and applications that consume APIs (primarily mashups and mobile apps), and pointers to sample source code found elsewhere on the Web. If you have any questions about our forms, their fields, and the data model behind our directories, we recommend that you read ProgrammableWeb's New API Directory Data Model Explained. Each field has extensive help text to assist you in filling out this form.Īfter adding an API to ProgrammableWeb’s directory, be sure to use our forms to add any related SDKs, libraries, frameworks, pointers to sample source code, and examples of applications that consume that API. But you do have to be the provider (the "owner") of an API to have the access rights to maintain that record over the long run. You don't have to be the provider of an API to add it to our directory. These include typical RESTful APIs, SOAPy XML RPC APIs, Javascript APIs found in browsers and even device specific APIs so long as they are mashable into Web apps. Since ProgrammableWeb is predominantly concerned with the Web as a programmable platform, our API directory accomodates Web and other APIs that enable developers to build Web and mobile apps. The purpose of this form is for API providers and other users to add a new API (or edit an an existing one) in ProgrammableWeb's API directory. The ProgrammableWeb directories are about cataloging APIs, SDKs, libraries, frameworks, Web apps and applications that consume APIs (primarily mashups and mobile apps), and pointers to sample source code found elsewhere on the Web.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |