No tienes acceso a esta clase

¡Continúa aprendiendo! Únete y comienza a potenciar tu carrera

Convierte tus certificados en títulos universitarios en USA

Antes: $249

Currency
$209

Paga en 4 cuotas sin intereses

Paga en 4 cuotas sin intereses
Suscríbete

Termina en:

19 Días
10 Hrs
35 Min
23 Seg

Teams

7/13
Recursos

En el desarrollo de software existen muchos roles, puestos de trabajo y profesionales en diversas áreas con las que trabajarás. Trabajarás en un equipo, eso con seguridad, y es tu responsabilidad conocer el puesto que cada uno de ellos ocupa en una empresa.

Vocabulario relacionado a una empresa

Veamos una lista de vocabulario apropiado para el trabajo día a día junto con otros profesionales.

Roles y posiciones

Diferentes puestos laborales en una empresa.

  • Engineer or Developer
  • Levels of experience:
    • Junior
    • Regular (Semi-senior)
    • Senior
    • Staff
    • Principal
    • Analyst
    • Architect
    • IC (Individual Contributor): They are not responsible for the work other people in that team do.

Administradores de una startup

“Los jefes” de una empresa.

  • Manager
  • Senior manager
  • Director
  • VP (Vice president)
  • C-Suit or C-Level:
    • Chief Executive Officer (CEO)
    • Chief Financial Officer (CFO)
    • Chief Marketing Officer (CMO)
    • Chief Technology Officer (CTO)
    • Chief Information Officer (CIO)
    • Chief Product Officer (CPO)

Áreas de una startup

Una empresa suele dividirse en áreas dependiendo la necesidad. Por ejemplo, algunas empresas pueden no necesitas área de ciencia de datos.

  • Engineering
  • Product
  • IT (Information Technology)
  • Data Science
  • Operations
  • DevOps - SRE (System Reliability Engineer)

Metodologías, herramientas y conceptos

Términos cotidianos de cualquier equipo de desarrollo de software.

  • Agile terms:
    • Scrum
    • Requirement
    • Deliverable
    • Sprint
    • Backlog
    • Point poker
  • Software project management:
    • Trello
    • Jira
    • Asana
    • Monday

Pruebas

No olvides las pruebas de tu software y los diferentes tipos que existen.

  • Unit test
  • Integration test
  • Smoke test
  • End-to-end test
  • QA (Quality Assurance)
  • CI: (Continuous Integration)
  • TDD (Test Driven Development)

Cada empresa tendrá su propia organización, existen términos que pueden no utilizarlos porque no lo necesitan.

Las organizaciones en la que trabajes serán un mundo distinto y es mejor estar preparado o preparada conociendo el vocabulario con el que te encontrarás.


Contribución creada por: Kevin Fiorentino.

Aportes 35

Preguntas 5

Ordenar por:

¿Quieres ver más aportes, preguntas y respuestas de la comunidad?

6. Teams
.
Engineer or Developer (they’re interchangeable).
Levels of experience:
Junior, regular or just developer, and senior. Staff and principal engineer. Analysts and Architects do a more specific work and are IC (individual contributors). They write code or work by themselves and don’t manage other people’s work. Sometimes you have an IC that is a team leader but they’re not responsible for the work other people in that team do.
.
Management Track:
Standard Manager, Senior Manager, Director, VP (vice president).
C-Suite:
Chief Executive Officer (CEO)
Chief Financial Officer (CFO)
Chief Marketing Officer (CMO)
Chief Technology Officer (CTO)
Chief Information Officer (CIO)
Chief Product Officer (CPO)
.
Departments:
Engineering + Product **
Sales, Marketing and Finance.
IT: Solutions for the inside of the company.
Data Science
Operations
DevOps: Developers and operators (they know the code and the infrastructure it runs on) and that uses code to manage that infrastructure.
SRE (Site Reliability Engineer) Google and Facebook tend to use these names.
.
Team / squad: Sometimes you do pairing (two people collaborate on the same code and computer, it helps create code with fewer errors).
When the code is ready you ship/deploy it to production.
.
All of these tend to use methodologies in the Agile world. Things like Scrum where you have Standup meetings, and you discuss your Requirements and the Deliverables you’re gonna bring to the customer.
Sprints: small periods of time. Things that don’t go in the current sprint tend to be put in the Backlog or the Icebox.
.
To try to figure out how long it will take to build a feature, you play
Points Poker** or Estimation Poker and you put all that information in tools like Trello Board, Jira by Asana or Monday.
.
Tests:
Unit test: for small pieces of code.
Integration test: test parts of the code of different systems working together.
Smoke test: make sure you code doesn’t have obvious mistakes when put into production.
End-to-end test: test your code from the end user to the back end.
All of this is known as QA (quality assurance). Some companies do it all the time. Every time you commit something to your repository using tools that provide CI (continuous integration).
Other companies want developers to write the test before they write the code which is known as TDD (test driven development).

All those technologies are fine, but you are not gonna be working alone, you are gonna be working in a team with other people

.
IC (individual contributors):
People who write code or work by themselves and don’t manage other people’s work.
.
Management
Manager
Senior manager
Director
VP (Vice President)
C-Suite (Chief Suite)
CEO (Chief Executive Officer)
CFO (Chief Finance Officer)
CMO (Chief Marketing Officer)
CTO (Chief Technology Officer)
CIO (Chief Information Officer)
CPO (Chief Product Officer)
.
IT (information technology):
Make solutions for the inside of the company
DevOps (developers and operators):
Employee that knows both, the code and infrastructure it runs on. Uses code to manage that infrastructure
.
Team or squad:
Is a group of people with you work.
.
Backlog
Put in the backlog or the icebox to try to figure out how long it will take to build a feature.
.
Tests
Unit test (test for small pieces of code)
Integration test (different pieces of code code working togheter)
Smoke test (wich is where you make sure that the code you put into production doesn’t have any obvious mistakes)
End-to-end test (when you test your code from the end user to the back end)
QA (Quality assurance)
CI (Continous Integration)
TDD (Test Driven Development)
.

How is your company organized right now?

Quizlet: Inglés para Developers [2022 - Platzi]


👋Hey Devs! I just created some units in Quizlet with the vocabulary and phrases in this course.
.
📚Quizlet is a very famous app to study and create Learning Cards.
I suggest that you study on the ‘Fichas’ mode and set Quizlet to show you the definitions first (I put the clues on ‘Definition’) and try to remember the term on the other side of the card (I put the term to remember on ‘Terms’).
.
🎉Hope this is useful for you!
Quizlet: Inglés para Developers [2022 - Platzi]

👥 Teams

Roles

  • Engineer Developer, both are used interchangeably even if you don’t have an engineering degree from a university
  • Levels Experience
    • Junior
    • Regular
    • Senior
  • Companies have been extending the engineering ladder to include more levels, like:
    • Staff engineer
    • Principal engineer
  • Other companies use the next words to describe more specific work that an engineer might do
    • Analyst Tend to write less code and more descriptions of what the task should be
    • **Architects** Tend to worry more about the general architecture of a system and not the specific details of one component
  • But all of these are what’s known as individual contributors or ICs
    • People who write code or work by themselves and don’t manage other people’s work

Management

  • Management track
  • Manager
  • Senior manager
  • Director
  • VP Vice president
  • C-Suite ⇒ “Suite” as in a room and “C” for chief, which is the first letter in most of the titles of people who are part of that level of an organization
  • CEO ⇒ Chief Executive Officer
  • CFO ⇒ Chief finance officer
  • CMO ⇒ Chief Marketing officer
  • CTO ⇒ Chief Technology officer
  • CIO ⇒ Chief Information officer
  • CPO ⇒ Chief Product officer

<aside>
💡 The differences between CIO and CTO, CTO deals with the technology of a company that build a technology-based product. Whereas a CIO deals the information management for the back of the company.

</aside>

Departments

  • Engineering
  • Product
  • IT
  • Data Science
  • Operations
  • DevOps
  • SRE

Team

  • Team or squad ⇒ Is a group of people with whom you work together on a day-to-day basis
  • Paring ⇒ 2 people sit in front of the same keyboard, computer and the same code
  • Ship
  • Deploy
  • Agile
  • Scrum
  • Standup
  • Requirement
  • Deliverable
  • Sprint
  • Backlog
  • Points poker
  • Trello board
  • Jira
  • Asana
  • Monday

Tests

  • Unit test
  • Integration test
  • Smoke tests
  • End-to-end tests
  • QA ⇒ Quality Assurance
  • CI ⇒ Continuous Integration
  • TDD ⇒ Test Driven Development

Individual Contributors:
engineer, developer, junior, regular, senior, staff, principal, analyst an architect.
Managment track:
manager, senior manager, director, VP, C-suite, CEO, CFO, CMO, CTO, CIO, CPO

IC 👈🏻 Individual Contributors

I´m smartketing officer at PMTN

My current job tittle is “Head”

Who knows the meaning of Yoko? In my organization I have a partner with this role!

Performance Testing
QA= Testing
Manual Testing
Functional Testing
Automatization

DevSecOps =Development + Security + Operations

UAT: User Acceptance Testing

quede impresionado con tanto termino y mas por el CEO, mas que todo por el Chief lo confundia con el cheff ajajajajjjaaj, como cuando uno juega halo, algunos amigos le decian “mira al master cheeff”, tal cual ajajajjajaj, no puedo de la risa ajajajajajaaajaj, de por Dios tanto que aprender.

At a company, I am responsible for the role of “SSR Engineer” or “Semi-Senior Engineer.” They had roles like “JR Engineer” and “Mid-Level Engineer” to me was hard to differentiate it

CT Continius Testing

There is a lot of diferent terms i didn´t know exist, also currently i m a junior developer at a consulting company, i work mainly in the frontend, and i write task in apps like trello or clickup , so far i love the course :D
### **Roles and titles in development teams** When working on a team, it’s important to understand the different roles and titles. Let’s explore some common ones. #### **Developer roles** In English, **engineer** and **developer** are often used interchangeably, even without a formal engineering degree. Titles are usually based on experience: * **Junior developer**: Less experienced. * **Developer**: A regular, mid-level developer. * **Senior developer**: More experienced, with advanced skills. **Some companies add extra levels:** * **Staff engineer**: A more advanced role beyond senior developer. * **Principal engineer**: Focused on complex technical leadership. #### **Specialized roles** * **Analyst**: Focuses more on describing tasks than writing code. * **Architect**: Designs the overall structure of systems rather than individual components. These roles are often called **individual contributors (ICs)**. ICs work independently and may take leadership roles but don’t manage others. #### **Management roles** On the **management track**, roles include: * **Manager**: Oversees team members. * **Senior manager**: Manages other managers. * **Director**: Higher-level leadership. * **VP (Vice President)**: Oversees larger sections of the company. Some companies use the titles **director** or **VP** more generously, while others reserve them for senior positions. At the top level is the **C-suite**, where "C" stands for *Chief*. These executives include: * **CEO**: Chief Executive Officer * **CFO**: Chief Financial Officer * **CMO**: Chief Marketing Officer * **CTO**: Chief Technology Officer (handles product technology) * **CIO**: Chief Information Officer (manages internal operations) A **tech company** will likely have a CTO but not a CIO, while a **bank** may have a CIO but not a CTO. ### **Departments and teams** **Departments** include sales, marketing, and finance, which developers may not interact with much. Developers typically work with: * **Engineering teams**: Build products and services for users. * **IT (Information Technology)**: Manages internal systems for operations. * **Data science teams**: Analyze metrics, collect data, and generate reports. * **Operations teams**: Handle deployments and keep systems running. #### **DevOps and SRE roles** * **DevOps engineer**: Works on both code and infrastructure, managing infrastructure with code. * **Site Reliability Engineer (SRE)**: Similar to DevOps, ensuring systems run smoothly. ### **Team collaboration** Your **team** or **squad** is the group of people you work with daily. Some key collaboration practices include: * **Pair programming**: Two people work on the same computer, reducing errors and improving code quality. * **Shipping or deploying code**: Sending code to production for users. * **Agile methodologies (Scrum)**: An approach for organizing work in short cycles. #### **Scrum practices** * **Stand-up meetings**: Short meetings to discuss progress and tasks. * **Sprints**: Focused work periods to complete specific tasks. * **Backlog**: A list of future tasks. * **Icebox**: Tasks that aren’t planned yet. ### **Project management and estimations** Teams use project management tools to organize tasks and estimate the time needed for features: * **Planning poker**: Developers assign points to estimate task difficulty. * **Task management tools**: * **Trello** (for boards) * **Asana** * **Monday.com** ### **Testing and quality assurance (QA)** Testing ensures that your code works correctly. There are different types of tests: * **Unit tests**: Focus on small pieces of code. * **Integration tests**: Ensure systems work together. * **Smoke tests**: Check for major errors in deployed code. * **End-to-end (E2E) tests**: Test the entire process from user input to backend. #### **Continuous integration (CI) and TDD** * **Continuous Integration (CI)**: Runs tests automatically whenever code is committed. * **Test-Driven Development (TDD)**: Developers write tests before writing the code itself.
ICYI this page contains a collection a collection of open source and public progression frameworks and career ladder of tech companies. <https://progression.fyi/>
I think the correct pronounciation for Jira sounds like *Jee-ra:* <https://youtu.be/ANxN98lGwYY?si=flBcwsQtrz0VlbqZ&t=12>
I learned a lot in this class.
I learn a lot in this class.

QA= Testing

My title in the company is QC semi senior advance…

I think I did not just learn English but also new things in the Development World. This class was very important for me to understand better other words or acronyms that I did not know. Thank you so much, teacher!

Me encantó esta clase porque me sirvió para entender, por fin, la diferencia y definición de ‘Individual Contributors’ como:
Engineer, developer, junior, regular, senior, staff, principal, analyst and Architect.

mi sueño es llegar a un nivel Senior

Currently, I’m not working in technology but I’ll do it, was great to learn a bit about the big picture of this world.
I work as an Electrical engineer so the industry works different.

I’m an engineer. 🧑🏻‍💻

All these terms are new for me, for example:

  • Scrum, - Deliverable or - Smoke test
    So, I only say that I hope to learn all of them.

Yes, I am a Developer Semi Senior Advance it’s like a Regular Developer++

In my company I am known as “Web Developer, specialist” even though my previous job was as a freelance hehe

In my case, we use the same levels for an engineer but related to the electrical field the more you know the highest your level is.

And new terminology keeps… evolving? I don’t know, but big companies keep stretching developer grades, so you may find stuff like:

Junior Advanced
Semi Senior
Senior Engineer
Consultant
Senior Consultant
Subject Matter Expert

And so on…

I have no title. :( But I think I may be IT I develop tools for intern use